I'm bringing up exim on all our local machines and just ran across this
on our web server. We bind all the virtual ip addresses to the local
interface, and it appears exim scans them all before sending mail,
leading to the following in the debug logs.
Local interface address is 127.0.0.1
Local interface address is 204.174.16.5
Local interface address is 204.174.16.10
Local interface address is 204.174.16.11
Local interface address is 204.174.16.100
Local interface address is 204.174.16.101
Local interface address is 204.174.16.102
Local interface address is 204.174.16.103
Local interface address is 204.174.16.104
Local interface address is 204.174.16.105
and so on for 160 more addresses.
Is there a reason it needs to do this? Isn't 127.0.0.1 sufficient? I
can't think of any problems resulting from this behaviour, other than a
few pages of unwanted debug output while testing but it seems
unnecessary. On the other hand, being able to specify an address to bind
to on outgoing delivery on a per domain basis, and having exim write the
from header to appear to have the hostname represented by that ip
address presents some rather interesting possibilities for virtual mail.
--
Artificial Intelligence stands no chance against Natural Stupidity.
GAT d- -p+(--) c++++ l++ u++ t- m--- W--- !v
b+++ e* s-/+ n-(?) h++ f+g+ w+++ y*
