Hi,
We were intrigued by the new command host_find_failed in v1.90 of exim. It
seems that it could prevent our mail routing spools from filling up with
frozen mail to '39593.com' or other such rubbish.
We are playing with exim with,
remotemail:
driver = domainlist
transport = remote_smtp
route_list = "* $domain bydns"
host_find_failed = fail_hard
in place of the more usual,
lookuphost:
driver = lookuphost
transport = remote_smtp
To have the same effect as lookuphost, but bouncing mail if the destination
domain does not exist.
This seems to work OK - with exim sending an error message straight away to
the sender of the 'illegal' message - keeping our spools empty! Cool so far
;-)
However, if a mail enters our server with both a non-existent recipient and
sender, exim freezes the returned error message. Why? One would think the
same process would be applied to the error message - when exim discovers that
the new message has a non-existent domain for the new recipient it would
return the message to the sender - in this case postmaster.
Any ideas - bug or silly sysop?
Thanks,
aid
--
Adrian J Bool | mailto:aid@u-net.net
Network Operations | http://www.noc.u-net.net/
U-NET Ltd, UK | tel://44.1925.484461/
--
*** Exim information can be found at
http://www.exim.org/ ***
