Re: ezmlm and BATV

Bruce Guenter <[email protected]> writes:

> I'm not sure what's being requested with the rest, 

I believe the BATV part of this discussion pertains to subscriber-only
(or variants of such) lists.  These lists try to match the envelope
sender address to a valid list subscriber, but that doesn't work if the
envelope sender is modified to something such as:

    [email protected]

I suppose we can put wrapper around ezmlm-gate and ezmlm-issubn that
knows how to decode the local part of the address to extract the true
local portion.  Assuming it's cleartext and not encrypted in some way;
though that could be possible as well.

Is there any hope that ezmlm will be BATV aware in the future?  


> 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.

That make sense.  We are already adding various headers, such as
List-Post, List-Help, and so on.  Sender was never required before, but
it seems as though changing times requires us to change as well.  Sounds
like we need to add this as a standard message header for our lists.

>> 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.

Well made point.  Thanks.