I have a strange problem with exim, and mailing across my servers that I can't seem to explain.
my server's FQDNs are server-a.company.nl, server-b.company.nl, etc. I have a few servers. On each server I configured the default domain for the admin user to be company.nl (censored of course).
The problem is that since a day I cannot send emails from one server to a mailbox on the other, it gets rejected with the notification failed to verify: Unrouteable address. something's wrong there, and I don't think I changed anything.
On the receiving server, B, I get the errors. However, the configuration should be the same everywhere. Running a caching named on each node, not using directadmin's built-in dns functionality.
Error on sending server (A)
Error on receiving server (B)
[/CODE]
If I check on the receiving server B, I can verify that exim won't verify the sender:
However, on other servers, it runs fine:
I found a temporary workaround by adding server-a's ip to /etc/virtual/whitelist_hosts_ip, and that makes exim accept mails again, but it's a dirty workaround and not a solution.
Any exim guru's that can help me debug this?
my server's FQDNs are server-a.company.nl, server-b.company.nl, etc. I have a few servers. On each server I configured the default domain for the admin user to be company.nl (censored of course).
The problem is that since a day I cannot send emails from one server to a mailbox on the other, it gets rejected with the notification failed to verify: Unrouteable address. something's wrong there, and I don't think I changed anything.
On the receiving server, B, I get the errors. However, the configuration should be the same everywhere. Running a caching named on each node, not using directadmin's built-in dns functionality.
Error on sending server (A)
Code:
2024-04-22 23:32:02 1rz1Gc-00000000V2g-1ck4 ** [email protected] F=<[email protected]> R=lookuphost T=remote_smtp H=mail.seconddomain.eu [178.132.x.x] X=TLS1.2:ECDHE-ECDSA-AES128-GCM-SHA256:128 CV=no: SMTP error from remote mail server after RCPT TO:<[email protected]>: 550-Verification failed for <[email protected]>\n550-Unrouteable address\n550 Sender verify failed
Error on receiving server (B)
Code:
2024-04-22 23:34:02 H=server-a.company.nl [91.229.x.x] sender verify fail for <[email protected]>: Unrouteable address
2024-04-22 23:34:02 H=server-a.company.nl [91.229.x.x] X=TLS1.2:ECDHE-ECDSA-AES128-GCM-SHA256:128 CV=no F=<[email protected]> rejected RCPT <[email protected]>: Sender verify failed
If I check on the receiving server B, I can verify that exim won't verify the sender:
Bash:
# exim -v -bv [email protected]
[email protected] failed to verify: Unrouteable address
[root@server-b company.nl]# dig mx company.nl +short
10 mail.company.nl.
[root@server-b company.nl]# dig mail.company.nl +short
178.132.x.x
However, on other servers, it runs fine:
Bash:
angelo@server-a:~$ exim -v -bv [email protected]
[email protected]
<-- [email protected]
router = localuser, transport = local_delivery
[root@server-c ~]# exim -v -bv [email protected]
[email protected]
<-- [email protected]
router = localuser, transport = local_delivery
I found a temporary workaround by adding server-a's ip to /etc/virtual/whitelist_hosts_ip, and that makes exim accept mails again, but it's a dirty workaround and not a solution.
Any exim guru's that can help me debug this?