The default exim configuration gives errors like this: May 05 12:03:51 free exim[16698]: 2003-04-27 12:03:51 199od5-0004LJ-00 == blah@blah.com R=system_aliases defer (-1): failed to expand "${lookup{$local_part}lsearch{SYSTEM_ALIASES_FILE}}": failed to open SYSTEM_ALIASES_FILE for linear search: No such file or directory This is because the SYSTEM_ALIASES_FILE isn't specified at build time, and emerge puts it in /etc/mail. If the location of SYSTEM_ALIASES_FILE isn't specified at build time, it defaults to the standard location /etc/aliases. Reproducible: Always Steps to Reproduce: 1.emerge exim 2.cp /etc/exim/exim.conf.sample /etc/exim/exim.conf 3.send an email 4.check /var/log/mail.log for the above error message Actual Results: Error was logged to /var/log/mail.log, and email wasn't sent. Expected Results: It should scan the aliases file, and then send the email. This bug has been reported in the forums before <a href='http://forums.gentoo.org/viewtopic.php?t=50383&highlight=exim+system+aliases'>here</a>. The workaround that I'm using right now is to replace data = ${lookup{$local_part}lsearch{SYSTEM_ALIASES_FILE}} with this: data = ${lookup{$local_part}lsearch{/etc/mail/aliases}}. A better solution would be to alter the ebuild so that it correctly specifies the location of the SYSTEM_ALIASES_FILE when exim is built.
Any progress on this? I am seeing these errors as well. While easily fixed, it would be nice to get it repaired. Cheers.
fixed in -r1
Thank You :)
