Re: [Mailman-Users] Re: how to remove List-* headers
At 12:37 PM 3/29/02 -0500, Tom Neff wrote: >On Thu, 28 Mar 2002 23:53:00 +1100 >Darryl Harvey <[EMAIL PROTECTED]> wrote: >>I was wondering if there was an option to turn on or off the email >>headers that mailman adds. > >This is one of their ideological hot buttons - you're not supposed to WANT >to turn them off. :) > >Back in the real world - go to $base/Mailman/Handlers/CookHeaders.py - >down in the last few lines - and look for a line saying In 2.1 you can go into mm_cfg.py and break RFC2369 compliance by setting ALLOW_RFC2369_OVERRIDES to 1. That'll enable a policy at your site that list owners can turn it off, which will cause the cgi scripts to display that as an option for them. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Re: [Mailman-Users] Re: how to remove List-* headers
--On Friday, March 29, 2002 9:30 PM -0500 Ron Jarrell <[EMAIL PROTECTED]> wrote: > In 2.1 you can go into mm_cfg.py and break RFC2369 compliance by setting > ALLOW_RFC2369_OVERRIDES to 1. That'll enable a policy at your site that > list owners can turn it off, which will cause the cgi scripts to display > that as an option for them. Quite the contrary, RFC2369 says Implementing these fields will be optional. Therefore, by adding a manager's option for those headers instead of trying to force them on everyone, Mailman 2.1 has finally been brought into RFC2369 compliance. Thanks for the reminder on this environment variable, I hadn't reviewed that part of the 2.1 config yet. My patch works under 2.0.8 and similar versions. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Re: [Mailman-Users] Re: how to remove List-* headers
On Fri, 29 Mar 2002 22:36:45 -0500 Tom Neff <[EMAIL PROTECTED]> wrote: > Quite the contrary, RFC2369 says > Implementing these fields will be optional. > Therefore, by adding a manager's option for those headers instead of > trying to force them on everyone, Mailman 2.1 has finally been brought > into RFC2369 compliance. Nope. The RFC states that conformant systems may or may not implement the various headers (ie optional), it does not state that any given system that supports those headers must also allow them to be disabled. Mailman was conformant previously and now with the config option (which I greatly regret) is still conformant. There has been no change in that regard. -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
