Barry, I agree. I don't see any reason these headers should be kept,
since the alterations Mailman makes to the header and body make the
header lines useless and misleading. I made a unified diff from the CVS
tree and sibmitted a patch through Sourceforge. I put "2.1" as the
version, as I was not sure if this applied to 2.1 or 2.2 alpha.
-Thanks, Joe
Barry Warsaw wrote:
> On Sat, 2005-09-10 at 15:03, Joe Peterson wrote:
>
>
>>Anyway, since I run a Mailman system too, I figured this might be a
>>problem. Indeed it is, since the header lines get passed through, and
>>when the check is done, it indicates a failure. DomainKeys recommends
>>mail lists regenerate the keys rather than pass them through.
>>
>>What I tried was pretty simple: Mailman doesn't have to deal with these
>>things itself, but if it strips the old keys from the header, the keys
>>will be regenerated on the way out by the MTA, thereby making the whole
>>process clean.
>
>
>>1) This is a reasonable thing to do (or maybe have an option, or even a
>>way to strip selected headers in the config?)
>>
>>2) If this is the right place to do it.
>
>
> Cleanse.py is the right place to add this. I'd rather add it
> unconditionally than add Yet Another Configuration Option to control it
> though. Is there any reason why you would /not/ want to remove these
> headers?
>
> -Barry
>
_______________________________________________
Mailman-Developers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
