Re: Exim4 not routing local mail, even after exim4-config (was New 64bit installation: Exim4 Send to Root)
On 28/07/2014 17:01, David Baron wrote:
~$ sudo exim4 -bt root
R: system_aliases for root@dovidhalevi.homelinux.net
R: system_aliases for system_notification@dovidhalevi.homelinux.net
R: userforward for system_notification@dovidhalevi.homelinux.net
R: procmail for system_notification@dovidhalevi.homelinux.net
system_notification@dovidhalevi.homelinux.net
<-- root@dovidhalevi.homelinux.net
router = procmail, transport = procmail_pipe''
~$ sudo exim4 -bt system_notification
R: system_aliases for system_notification@dovidhalevi.homelinux.net
R: userforward for system_notification@dovidhalevi.homelinux.net
R: procmail for system_notification@dovidhalevi.homelinux.net
system_notification@dovidhalevi.homelinux.net
router = procmail, transport = procmail_pipe
Sure looks in order. But it doesn't work.
Are you sure there is a route from (i) whichever machine has the alias
record, and (ii) whichever machine is reached, on port 25, at the IP
address in an MX record at
dovidhalevi.homelinux.net
or, if there is no MX record, whatever machine is reached on port 25
at the IP address pointed to by
dovidhalevi.homelinux.net ?
I had a similar problem to this, when using a NAT router on an ADSL
line, behind which was my exim server. The exim server tried to find
xxx.homelinux.net, found an IP address for it from DNS, tried to reach
the address, but the ADSL router would not - for some reason - accept
outgoing SMTP packets back into itself on port 25, whether looped back
itself, or tromboned by a router upstream in the ISP's network. Or
maybe tromboning like that was blocked by the ISP. Whatever the
reason, I solved the problem in either of 2 ways.
(a) Routed outbound SMTP on a different route, different IP, than the
IP that xxx.homelinux.net pointed to (I used a 3G network), or
(b) set /etc/hosts on the exim machine to point xxx.homelinux.net to
itself so that exim made no attempt to signal externally.
You may already have checked this, but this just seems to me to have a
sense of being a routing problem, rather than an mailserver problem.
Apologies if I'm off-track there.
regards, Ron
Reply to: