There is a boundary case where the hostname in the received header cannot be resolved. This used to always treat the mail as undeliverable. Now there's an option to inject it. The fix just applied ensures that in this case, or any future case, where the remote address or host cannot be determined 127.0.0.1 /localhost are used and a MailAttribute set to indicate the condition. This avoids falling back to the original condition where we could have the Mailet chain falling over.
Interesting dilemma. Why not in the boundary case have it revert to the hostname of the mail server with the POP3 mailbox. To me it seems logical since we are effectively (in reverse) accepting email from there. We can then differentiate between a locally generated message and one that was retrieved from a (trusted) host.
-- Serge Knystautas President Lokitech >>> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
