Can't email to specific address

[Richard G]

We got several servers, but I have a problem sending email from any email account (or domain) from server 1 to a specific email address on server 2.

This is what happens and which I read in the log on server 1.

2016-09-14 13:25:53 1bk8K9-0001Eg-Gx ** [email protected] F=<[email protected]> R=lookuphost T=remote_smtp: retry time not reached for any host after a long failure period
2016-09-14 13:25:53 cwd=/var/spool/exim 7 args: /usr/sbin/exim -t -oem -oi -f <> -E1bk8K9-0001Eg-Gx
2016-09-14 13:25:54 1bk8K9-0001Ez-T7 <= <> R=1bk8K9-0001Eg-Gx U=mail P=local S=1971 T="Mail delivery failed: returning message to sender" from <> for [email protected]
2016-09-14 13:25:54 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1bk8K9-0001Ez-T7
2016-09-14 13:25:54 1bk8K9-0001Eg-Gx Completed
2016-09-14 13:25:54 1bk8K9-0001Ez-T7 => info <[email protected]> F=<> R=virtual_user T=dovecot_lmtp_udp S=2135 C="250 2.0.0 <[email protected]> DnueA8Iz2VerEgAADNWw8g Saved"
2016-09-14 13:25:54 1bk8K9-0001Ez-T7 Completed

This happens instantly, so not after a few seconds.

This is what I can read from the exim logfile on server 2.

2016-09-14 13:37:43 H=hostname.server1.nl [46.xx.xx.xx] incomplete transaction (QUIT) from <[email protected]> for [email protected]

And this is what the returning email says:

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

[email protected]
retry time not reached for any host after a long failure period

It looks as if there would be an issue with that admindomain.nl email address, but there isn't. If I send an email to it from my own private ISP email address of from my gmail addres, the mail gets delivered without issues.
We also tested with another domain on server2 which has no issues receiving mails from server1.

So it looks as if it's only this email address or this email domain (admindomain.nl) which is having the issues receiving emails from server1.

As you can see the logs aren't clear about a good reason so any help to fix this or where to look for a cause would be appreciated!

 

[toml]

It is possible that your exim database is corrupt, try this:
/usr/sbin/exim_tidydb -t 1d /var/spool/exim retry > /dev/null
/usr/sbin/exim_tidydb -t 1d /var/spool/exim reject > /dev/null
/usr/sbin/exim_tidydb -t 1d /var/spool/exim wait-remote_smtp > /dev/null

Then restart exim and see if it clears up your problem

 

[Richard G]

Thank you. Do I have to do this on server 1 or on server 2?
Or can't it do any harm to do this on both servers just to be sure?

By the way, the second line does not work, I tried without the /dev/null to see what's going on and got this result:

/usr/sbin/exim_tidydb -t 1d /var/spool/exim reject
Usage: exim_tidydb [-t <time>] <spool-directory> <database-name>
<database-name> = retry | misc | wait-<transport-name> | callout | ratelimit

In any case the 2 remaining lines and the restart of Exim solved the problem!! Many thanks!!!

 

[toml]

I just found those commands in another forum stating that it fixes that specific error. Looking at our exim databases I do not see a reject database so that command does not need to be executed.

Based on what I see, too this should be done on the sending server.

 

[Richard G]

Oke. I'm glad you found it. As said it fixed the issue. Thank you again!