[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 ar

Re: [Mailman-Users] Sender field

gt; allow people to turn it off, not to rip this feature completely out > of the system. I would argue that the best course of action is to excise Sender header rewriting entirely and provide no option to turn it on. (Mailman has way too many options already.) If, however, an option is c

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

(or until someone else beats me to it), I think it's definitely a good idea. -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA -- Mailman-Users mailing list [EMAIL PROTECT

Re: [Mailman-Users] More on Sendmail

ets done fiddling with the config for his new list, the alias file entries have already been generated. -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA -- Mailman-Users mai

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 ha

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

pear that Mailman doesn't offer this feature. Am I mistaken? Assuming I'm 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 Tech