Re: ezmlm and BATV

On Wed, Aug 01, 2007 at 09:35:57AM -0700, John Keith wrote:
>     "Update ezmlm to add a Sender: header with the list address (to
>      allow SenderID)"

I'm not sure what's being requested with the rest, but I will comment on
this.  Adding a Sender: header with the list address is also required
for DomainKeys (and probably DKIM) to work properly.  This can be
accomplished trivially by adding the following line to DIR/headeradd:

	Sender: <#l#>@<#h#>

The above is for version 5.0 or later.  Earlier versions should use a
literal list address.

> I don't know exactly what problem they are trying to solve here either.
> The envelope sender works perfectly well to handle delivery bounces as
> it should.  

SenderID and DomainKeys do validation on the visible parts of the
message ie the header.  They validate different parts in different ways,
and are not otherwise directly comparable.  The Sender: header has no
impact on the envelope sender address.

> It's true that email passing through our lists did not originate from
> the list, but rather from the original sender.  That's how lists work.

Well, not entirely.  If it were a simple redirect I would agree, but all
common mailing lists do much more than just simple redirects -- in
addition to handling the actual address list, they also modify the
message (both headers and frequently the body).  As a result, the output
is a new message and the list becomes the new sender of the message, and
needs to be identified as such.
-- 
Bruce Guenter <[email protected]>                http://untroubled.org/
	I do custom software development.  Email me for details.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGsQCH6W+y3GmZgOgRArksAJ99JFfKpKECF8H2/UZDC9mqBgCtNACdEdIB
NS7BHO4dM2GW+2bJwKP4tpQ=
=EjGa
-----END PGP SIGNATURE-----