Cannot send emails since last update
I cannot send emails anywhere and I see you dropped courier which offered the TLS support I needed. Why do you keep changing crap and breaking our servers? We pay you to keep us going. MAil stuck in queue and cannot send via any method. This message is from forcing the queue to send.
LOG: MAIN
cwd=/usr/local/cpanel/whostmgr/docroot 3 args: /usr/sbin/exim -q -v
LOG: queue_run MAIN
Start queue run: pid=7210
delivering 1bEpjQ-0000tG-6h (queue run pid 7210)
Connecting to mail.starfleet.com [212.48.74.205]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
H=mail.starfleet.com [212.48.74.205] Connection timed out
LOG: MAIN
== xxxx@xxxxxxxxxx.com R=dkim_lookuphost T=dkim_remote_smtp defer (110): Connection timed out
delivering 1bEq84-0001oc-Hp (queue run pid 7210)
LOG: retry_defer MAIN
== xxxx@xxxxxxxxxx.com R=dkim_lookuphost T=dkim_remote_smtp defer (-53): retry time not reached for any host
delivering 1bEpdC-0000m8-Hc (queue run pid 7210)
LOG: retry_defer MAIN
== xxxx@xxxxxxxxxxxxx.com R=dkim_lookuphost T=dkim_remote_smtp defer (-53): retry time not reached for any host
delivering 1bEpci-0000lY-8A (queue run pid 7210)
LOG: retry_defer MAIN
== xxxx@xxxxxxxxxx.com R=dkim_lookuphost T=dkim_remote_smtp defer (-53): retry time not reached for any host
delivering 1bEpUl-0000cY-Lq (queue run pid 7210)
LOG: retry_defer MAIN
== xxxx@xxxxxxxx.com R=dkim_lookuphost T=dkim_remote_smtp defer (-53): retry time not reached for any host
LOG: queue_run MAIN
End queue run: pid=7210
-
Hello, The provided error message is sowing that there is network issue from your server to recipient server. Can you please check the network connection from your server using below command. telnet recipient domain name 25
for example telnet xyz.com 250 -
Hello :) Do you experience mail delivery issues for all other domains including Gmail, Hotmail, yahoo etc. or to this specific domain only? As mentioned in the above post, the log entries shows a network or connectivity issues to the destination server. This could also happen if the firewall is blocking connections from/to the recipient server. Do check the firewall settings for any blocks and make an attempt after stopping the firewall. 0 -
Hello, The output you provided suggests an issue with Exim, as opposed to Dovecot. Could you review the previous responses and let us know if they help you to determine the cause of the problem? Also, do you notice any unusual entries in /var/log/exim_mainlog when this happens? Thank you. 0
Please sign in to leave a comment.
Comments
3 comments