On 2004-09-08 at 04:22 -0500, Bruce Kallick wrote:
> Yep, that's what happened -- but when I either precede the 'require
> verify = header_sender' by 'accept hosts = 127.0.0.1' or else replace
> it by 'require verify = sender' the message is accepted and has a
> 'From: postmaster@???' header.
That's added afterwards.
It's not in the data read, so not available to the DATA ACL, hence the
failure before. It is a fix-up applied to accepted messages. The
relevant comment from the source is:
/* If there is no From: header, generate one for local or submission_mode
messages. If there is no sender address, but the sender is local or this is a
local delivery error, use the originator login. This shouldn't happen for
genuine bounces, but might happen for autoreplies. The addition of From: must
be done *before* checking for the possible addition of a Sender: header,
because untrusted_set_sender allows an untrusted user to set anything in the
envelope (which might then get info From:) but we still want to ensure a valid
Sender: if it is required. */
If you want to check what's actually sent to you, you could try
something like:
tcpdump -vvvnpi lo0 -xs1500 port 25
as root, or "lo" instead of "lo0" if on a GNU/Linux box. There are
other options, including logging received headers, but this method's
easiest.
--
Phil Pennock, Senior Systems Administrator, Demon Netherlands
NL Sales: +31 20 422 20 00 Thus Plc NL Support: 0800 33 6666 8
