[SOLVED] Aliases not working in EXIM4

[bomahony]

I recently P2V'd a debian box, and the aliases file (/etc/aliases) is no longer working. As the physical machine is still working, this machien has been renamed to buzz1 [from buzz].

I changed /etc/mailname, /etc/exim4/update-exim4.conf.conf [and ran the update-exim4.conf script] and also ran newaliases. however it still does not seem to be applying the aliases file:

Live Physical Machine:
buzz:~# exim -bt root@buzz.domain.com
R: system_aliases for root@buzz.domain.com
R: smarthost for cronjobs@domain.com
cronjobs@domain.com
<-- root@buzz.domain.com
router = smarthost, transport = remote_smtp_smarthost
host james3.domain.com [172.16.164.28]

VM:
buzz1:/etc# exim -bt root@buzz1.domain.com
R: smarthost for root@buzz1.domain.com
root@buzz1.domain.com
router = smarthost, transport = remote_smtp_smarthost
host james3.domain.com [172.16.164.28]

[bomahony]

I am going to have to attach the exim -bt information as it wont let me post the domain information

[bomahony]

I have also rebooted a number of times, as well as restarting exim using the init script

[bcsi]

I've never tried EXIM4 under debian (Ok, once under Ubuntu but couldn't figure out the configuration) but I'm running it under SCO on a number of machines.

In my configurations I use a plain text aliases file but I see you run newaliases so I assume that you are using some sort of db access. Do you know for sure if all of the db libraries are available and accessable by exim?

Also, what user is exim running as and does that user have access to the aliases db file?

You can also run exim with debugging. That might give you a clue as to what is going on. For example: exim -d+all -bt root@buzz1.domain.com 2>some_file

Run that on both machines and compare the outputs.

Good luck.

[bomahony]

I dont really know that much about exim , hence why i was posting here

Anyways from that debug:

Machine that works [Buzz]:
15:40:47 5510 --------> smarthost router <--------
15:40:47 5510 local_part=root domain=buzz.domain.com
15:40:47 5510 checking domains
15:40:47 5510 buzz.domain.com in "@:localhost"? yes (matched "@")
15:40:47 5510 buzz.domain.com in "! +local_domains"? no (matched "! +local_domains")
15:40:47 5510 smarthost router skipped: domains mismatch
15:40:47 5510 --------> real_local router <--------
15:40:47 5510 local_part=root domain=buzz.domain.com
15:40:47 5510 real_local router skipped: prefix mismatch

Machine that doesnt work [Buzz1]:
15:39:58 20325 --------> smarthost router <--------
15:39:58 20325 local_part=root domain=buzz1.domain.com
15:39:58 20325 checking domains
15:39:58 20325 buzz1.domain.com in "@:localhost"? no (end of list)
15:39:58 20325 buzz1.domain.com in "! +local_domains"? yes (end of list)
15:39:58 20325 expanding: R: smarthost for $local_part@$domain
15:39:58 20325 result: R: smarthost for root@buzz1.domain.com
15:39:58 20325 R: smarthost for root@buzz1.domain.com
15:39:58 20325 calling smarthost router
15:39:58 20325 smarthost router called for root@buzz1.domain.com
15:39:58 20325 domain = buzz1.domain.com
15:39:58 20325 route_item = * smtp.domain.com byname
15:39:58 20325 buzz1.domain.com in "*"? yes (matched "*")
15:39:58 20325 original list of hosts = "smtp.domain.com" options = byname
15:39:58 20325 expanded list of hosts = "smtp.domain.com" options = byname


So basically it doesnt even get to the system aliases section?

[bcsi]

Ya, it pretty much looks like it.

I think the key here is that it doesn't recognize buzz1.domain.com as the localhost as per:

5:39:58 20325 buzz1.domain.com in "@:localhost"? no (end of list)

So I don't think it's even trying to use aliases. The issue is probably due to the fact that when you copied the original environment to the virtual one and renamed the host name to buzz1, you did change it everywhere from buzz to buzz1 so somewhere it still thinks it's buzz. That's why it's sending the email via the smarthost buzz1.domain.com, which is itself.

At least that's my guess.

[bomahony]

Apologies for the delay. Been dying with a sinus infection so didnt have to work

Thats my guess as well, but i cant find anywhere or think of anywhere that may have been.

Any helpful suggestions?

[bomahony]

Turns out the FQDN and non-FQDN were in the /etc/hosts file. One had a slight spelling error.