all hosts for domain.ca have been failing for a long time (and retry time not reached)

[daflame]

I have a dedicated server and everyone on the server are not able to send email to a particular domain. We receive the following bounce message :

all hosts for 'example.ca' have been failing for a long time (and retry time not reached)

I tried to send an email with Hotmail and it works.

I looked a some threads with this similar issue but didn't find anything that resolve the problem. I tried the "Resolver Configuration" via WHM. I also tried to remove all files in "/var/spool/exim/db" and retart Exim.

Anyone have a clue? Thanks!

 

[cPanelMichael]

Hello @daflame,

It's possible the remote mail server is blocking connection attempts from your server. Can you try connecting to that domain name over port 25 using telnet on your server's command line? EX:

telnet example.ca 25

Let us know the result.

Thank you.

 

[blackwidow02]

We have a shared server and everyone on that server are not able to send email to a particular domain. We receive the following bounce message :

all hosts for 'example.es' have been failing for a long time (and retry time not reached)

I tried to conduct a test email using an account on different server and it works.

I looked at some threads with this similar issue; tried to remove all files in "/var/spool/exim/db" and "/usr/sbin/exim_tidydb -t 1d /var/spool/exim retry > /dev/null" but still didn't find anything that resolve the problem.

Hope you can help me on this. Thank you!

 

[cPanelMichael]

Hello @blackwidow02,

Can you review this post and let us know the result of the suggested test?

Thank you.

 

[blackwidow02]

Hello @cPanelMichael ,

Thank you for your prompt response, I've tried to do the said command and below is the result of the test conducted. Does this mean that the problem is not on our side (our server and accounts on this server)? Thank you very much

 

[cPanelMichael]

Hello @blackwidow02,

The output in the image you provided suggests the domain name you entered is not resolving to an IP address. Is this a domain that you host on your server? If so, can you use a website such as IntoDNS to make sure that domain name uses the correct name servers and that the domain resolves to the cPanel server?

Thank you.

 

[blackwidow02]

Good day @cPanelMichael,

The domain name is not hosted on our server, that domain name is the recipient of the email of one of our client that we host wherein everytime they send an email to that domain they encounter this error 'all hosts for 'example.es' have been failing for a long time (and retry time not reached)'. So it means that the real problem is not on our side but on the recipient's domain?

Thank you again for responding.

 

[cPanelMichael]

Hello @blackwidow02,

Yes, you are correct that the remote mail server hosting the email for that domain is likely the culprit. I recommend contacting that server's support team or email administrator to see if your server's IP address is blocked for a specific reason.

Thank you.

 

[blackwidow02]

Hi @cPanelMichael,

It's now clear to me and verified that the issue is not on our side. Will try to contact their support team and check if our server IP is blocked on their end. Thank you very much for the help!

 

[jagadishn41]

We have a shared server and everyone on that server are not able to send email to a particular domain. We receive the following bounce message :

all hosts for 'oracle.com' have been failing for a long time (and retry time not reached)

tried to remove all files in "/var/spool/exim/db" and "/usr/sbin/exim_tidydb -t 1d /var/spool/exim retry > /dev/null" but not find this code. please get solution for this.

 

[cPRex]

Hey there @jagadishn41

I like this block of commands instead, as these are set to zero-days so it will get all the entries in the database:

/usr/sbin/exim_tidydb -t 0d /var/spool/exim retry > /dev/null
/usr/sbin/exim_tidydb -t 0d /var/spool/exim reject > /dev/null
/usr/sbin/exim_tidydb -t 0d /var/spool/exim wait-remote_smtp > /dev/null

Can you do that and try sending the messages again?