A lot of emails for one of my people are getting queued, the mail log shows these messages:
R=lookuphost T=remote_smtp defer (-53): retry time not reached for any host
R=lookuphost T=remote_smtp defer (110): Connection timed out
Why do they mean?
A lot of emails for one of my people are getting queued, the mail log shows these messages:
R=lookuphost T=remote_smtp defer (-53): retry time not reached for any host
R=lookuphost T=remote_smtp defer (110): Connection timed out
Why do they mean?
They mean exactly what they say. The SMTP server tried to contact a remote SMTP server and it was unavailable, so the mail remained in the queue. Usually cause by either:
1. Unavailable remote mail servers (obviously)
2. You being blocked by remote mail servers (possible)
3. DNS resolution not working reliably locally (very possible)
Jonathan Michaelson
Need your cPanel servers secured and tuned?
cPanel Server Configuration, Security, Recovery and Antivirus/AntiSpam Services
Developers of the most effective (and free) Firewall & Security Solution for cPanel Servers - csf
http://www.configserver.com
4. Internet is experiencing a netsplit condition and the SMTP server your service is trying to
reach is located on the other side of the netsplit on another internet fragment.
(Very common lately particularily with the crap Level3 pulled recently)
R=lookuphost T=remote_smtp defer (110): Connection timed out
I keep getting this with 1 domain: cat5ecableguy.com
This domain can send to my server, but we cannot send to it.
DNSstuff & DNS report all seem fine.
I've tried all the solutions found on this forum.
anyone have any tricks to be able to research this or advice?
![]()
Was this ever resolved? I am having similar issues?
Does anyone have any suggestions.
Keith Gallant
JustHosting.ca
http://www.justhosting.ca
We had not discovered why this happened and here was our steps taken to alleviate the problem (which did not work). The resolutions is unknown:
1. the domain in question was on an exchange server.
2. the domain owner ended up adding a new domain to send and receive email from. (same exchange server mind you)
3. The second domain was able to send and receive from/to our domain.
4. We added a PTR record with our upstream provider.
After a year the email started working (9 months infact), my assumption was the user was grey-listing incorrectly however it was never completely determined. There was also some recursive DNS settings we decided to remove at the time, (not sure if it's related).
I wish I could help more, but when things magically start working again, it's hard to determine what was wrong, when nothing you have access to has changed.. ;(