[Mailman-Users] feature request: rules on new mailing list names?

not mistaken, would there be any resistance to adding this feature? And what would be the best mechanism to do so? Regards, -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA

Re: [Mailman-Users] feature request: rules on new mailing list names?

On 2003-12-08 at 22:14:26-0500 Jon Carnes [EMAIL PROTECTED] wrote: Modify the file ~mailman/Mailman/Utils.py def list_exists(listname) Thanks for the tip. Making list_exists() lie in order to prevent the creation of undesirable lists seems like a kluge, though. Wouldn't it be better to have

removing arbitrary headers [Mailman-Developers] [Mailman-Users]

a good idea. -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman

Re: [Mailman-Users] Sender field

too many options already.) If, however, an option is created to control the behavior, it should definitely default to OFF (no Sender header rewriting), not on. -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA

[Mailman-Users] rejecting spam disables local subscribers on remote lists

We recently implemented a policy such that any incoming message that scores higher than 10 with SpamAssassin is rejected at our MX servers with: 550 5.7.0 message not delivered due to suspect content We've discovered that this policy has interaction problems with recipients at our site who