451 Temporary local problem - please try later
-
Hey there! Is this happening with all addresses, or only with a specific address on the system? Do you see any additional details in the Exim logs when this error happens? 0 -
Hey there! Is this happening with all addresses, or only with a specific address on the system? Do you see any additional details in the Exim logs when this error happens?
Hi, at the moment the error only appears when I send messages to specific addresses, for now we have only had problems with three addresses. using roundcube, from the moment you send the message, after a few seconds the red warning appears indicating the 451 error and to try again later.0 -
That's good that it is only specific addresses and not all emails. Are you able to reach the mailserver for those accounts? You can test that by first finding their mailserver with this command: dig mx domain.com That will give you the mailserver in use - here's an example using Google: ==================================================================== # dig mx gmail.com ;; ANSWER SECTION: gmail.com. 1139 IN MX 5 gmail-smtp-in.l.google.com. ==================================================================== Then, you can try to connect to that mailserver from your local server with this: =============================== telnet gmail-smtp-in.l.google.com 25 =============================== Can you try that test and see if you're abe to manually connect, or if that leads us to an error with more details? 0 -
[QUOTE="cPRex, post: 3010621, membro: 586151"> " positivo che si tratti solo di indirizzi specifici e non di tutte le e-mail. Riesci a raggiungere il server di posta per quegli account? Puoi verificarlo trovando prima il loro server di posta con questo comando: scavare dominio mx.com Questo ti dar" il server di posta in uso: ecco un esempio utilizzando Google: ================================================== ================== # scava mx gmail.com ;; SEZIONE RISPOSTA: gmail.com. 1139 IN MX 5 gmail-smtp-in.l.google.com. ================================================== ================== Quindi, puoi provare a connetterti a quel server di posta dal tuo server locale con questo: =============================== telnet gmail-smtp-in.l.google.com 25 =============================== Puoi provare questo test e vedere se riesci a connetterti manualmente o se questo ci porta a un errore con maggiori dettagli?
Non riesco a connettermi, ho provato con dig mx e domain.tld: [root@server ~]# scava mx xxxxxx.com ; <<>> DiG 9.11.36-RedHat-9.11.36-8.el8_8.2 <<>> mx xxxxx.com ;; opzioni globali: +cmd ;; connessione Scaduta; non " stato possibile raggiungere alcun server [root@server ~]# dig mx xxxxxxx.it ; <<>> DiG 9.11.36-RedHat-9.11.36-8.el8_8.2 <<>> mx xxxxxx.it ;; opzioni globali: +cmd ;; connessione Scaduta; nessun server " stato raggiunto0 -
It sounds like there is a firewall error or network problem on the server, as that test works well for me on my local workstation. You might need to reach out to your host to see why the DNS lookups for specific domains are failing, but you could always start by disabling the firewall on the machine as a quick test. 0 -
It sounds like there is a firewall error or network problem on the server, as that test works well for me on my local workstation. You might need to reach out to your host to see why the DNS lookups for specific domains are failing, but you could always start by disabling the firewall on the machine as a quick test.
I'm not sure... for other domain it work fine, I tested with google: [root@server ~]# dig mx gmail.com ; <<>> DiG 9.11.36-RedHat-9.11.36-8.el8_8.2 <<>> mx gmail.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48431 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;gmail.com. IN MX ;; ANSWER SECTION: gmail.com. 3561 IN MX 20 alt2.gmail-smtp-in.l.google.com. gmail.com. 3561 IN MX 40 alt4.gmail-smtp-in.l.google.com. gmail.com. 3561 IN MX 10 alt1.gmail-smtp-in.l.google.com. gmail.com. 3561 IN MX 5 gmail-smtp-in.l.google.com. gmail.com. 3561 IN MX 30 alt3.gmail-smtp-in.l.google.com. ;; Query time: 1 msec ;; SERVER: 161.97.189.52#53(161.97.189.52) ;; WHEN: Sat Oct 14 09:15:49 CEST 2023 ;; MSG SIZE rcvd: 1610 -
This would indicate a DNS issue with the default resolvers that your datacenter has configured. I'd let your host/datacenter know about this so they can look into the issue, but it would indicate the problem is not on your server. 0 -
This would indicate a DNS issue with the default resolvers that your datacenter has configured. I'd let your host/datacenter know about this so they can look into the issue, but it would indicate the problem is not on your server.
Hi, thanks for the reply. I already write my hosting.. Now, I'm waiting for Contabo Host to resolve the issue0
Please sign in to leave a comment.
Comments
9 comments