[Mailman-Developers] Feature request: Reply-To Munging etc.

Barry Warsaw barry at python.org
Thu Mar 8 16:03:38 CET 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 7, 2007, at 12:30 PM, Stephen J. Turnbull wrote:

> Sven Anderson writes:
>
>>> IIRC, if the user sets their subscription to "no-dupes", that user's
>>> address will be removed from the addressee list, as well as from the
>>> list of addresses that Mailman actually distributes to the post to.
>>
>> I just checked this to be sure, but only the latter is true. The  
>> user's
>> address stays in the To/Cc header.
>
> Hm.  I know both are true for my lists (Mailman 2.1.5).

I think you're both right :).  Mailman 2.1 will strip recipients from  
the CC header if explicitly named recipients are members of the list  
and have nodup set.  But Mailman won't strip To headers, nor juggle  
CC and To headers after stripping.

It may not be a bad idea to go all the way with this as Sven  
suggests, at least when not munging.  I do think it will address a  
common complaint about no-munge, and one that's harder to write off  
as "fix your MUA".

I'm not inclined to spend much brain power or LoC trying to "fix"  
reply-to-munging.  I think that's a fundamentally broken use case.   
Good MUAs do the right thing here and if Sven's idea addresses the  
other major complaint then I'd be happy.  If I could drop reply-to  
munging in the next version altogether, I'd be ecstatic.

Thanks, I've added this to the wiki.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iQCVAwUBRfAly3EjvBPtnXfVAQJrLwP/Sk9LbmFfG/hDJ5RddGYpGMdi6YMfFpyl
1/zGj2EeqCThziP0cC+zOMkY7QgdDaQkt8zgOQ1jLsv1UVBEOJ1uxm5Y3JZ/KzDi
W5ZE1KGIEs/X8vDctSsUPMhYNTa9yUnVEBCjatxJ/S4c2dT311/gYtb9NgmWhoux
jfq8Nqd7QSY=
=RjoH
-----END PGP SIGNATURE-----


More information about the Mailman-Developers mailing list