Did a bit more digging... "exim -d -bt [email protected]" returns some useful info:
BTW, server hostname is server00.simonandkate.lan >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Testing [email protected] address match: [email protected] [email protected] domain.net in "localhost.localdomain"? no (end of list) [email protected] in "*[email protected]"? no (end of list) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Considering [email protected] >>>>>>>>>>>>>>>>>>>>>>> routing [email protected] --------> system_aliases router <-------- ... ...cut to the result... system_aliases router declined for [email protected] --------> userforward router <-------- local_part=simon domain=simonandkate.net checking for local user seeking password data for user "simon": cache not available getpwnam () succeeded uid=xxx gid=xxx calling userforward router ... ... /home/simon/.forward does not exist userforward router declined for [email protected] --------> procmail router <-------- etc Last one is: --------> localuser router <-------- this accepts it and files for local delivery. This results for simon@ anything the same... ends up local delivered. So do I need to be calling the SMTP relay router before local user router? Is there a recommended order in which the routers should be called? Should my SMTP relay be inserted after the system_aliases router but before the local routers? Simon Quoting "Simon Wilson" <[email protected]>: > I have 3 CentOS 5.2 servers with Exim 4.63. They are not the primary > mail server for our internal LAN. They run Exim and send system > emails to root, with an alias "root: [email protected]" so my real > email account gets root mail. > > They therefore have an SMTP relay set up in the routing configuration > to forward all mail not for localhost (which is everything, as they > have no 'real' local users) to a single internal relay that has > external SMTP access. This has been working fine for a while, i.e. > Exim saw that [email protected] was not local, and passed the emails > out to the SMTP relay. > > I have now installed LDAP on the network, and the servers have been > configured as LDAP clients. The LDAP entry for simon includes my real > email address. > > Problem: Mail to root aliased to [email protected] is now seen as > being local. Log entry is as follows: > > ... => simon <[email protected]> R=localuser T=local_delivery > > It seems as though Exim sees that simon (it throws away the domain > name, even though the domain is not in the exim.conf local domains) > IS now a valid local user (albeit an LDAP one) and tries to deliver > locally. These emails have now vaporized... :( > > getent passwd simon correctly returns the LDAP user. How does Exim > check whether the user is local? And why is it seeing > [email protected][1] as only 'simon' without the domain? > > Exim.conf is standard except for the route to SMTP relay, and a rewrite rule: > *[email protected] $1server01.domain.lan > > domains = @ : localhost : localhost.localdomain > > If anyone could help me sort out my config that would be great > > Simon. > > > > Links: > ------ > [1] mailto:[email protected] > -- > ## List details at http://lists.exim.org/mailman/listinfo/exim-users > ## Exim details at http://www.exim.org/ > ## Please use the Wiki with this list - http://wiki.exim.org/ > > -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
