Jewel Makda wrote: >My list owners were getting hit pretty hard with spam, almost 4,000 just >over a weekend. I did the following which has blocked most if not all >of the spam going to listowners. What I did was the following: >I edited the Defaults.py file to have the -owner messages go through the >same pipeline as the normal messages delivered to list members.
Never edit Defaults.py. Override that which you wish to change by redefining it in mm_cfg.py. See <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.021.htp>. >I know >that one downside to this change is if someone wanted to subscribe to a >list and sent an email to [EMAIL PROTECTED], the request it >would fail to be delivered. Most people contact our list owners directly >through someone they know or with their work email. Since I made this >change I have not seen any disturbances or problems, everything is >running smoothly. I am posting this email to see if there are >ramifications to this change other than the one I mentioned. Many. Are the list owners getting any notices from Mailman? >Here is the change I made to the Defaults.py file: >OWNER_PIPELINE = [ >'SpamDetect', >'Approve', >'Replybot', >'Moderate', >'Hold', >MimeDel', As Brad points out, a ' is missing. I have to assume that this is not a copy and paste of the actual OWNER_PIPELINE. If it is, this error will break everything. >'Scrubber', >'Emergency', >'Tagger', >'CalRecipe', 'CalcRecips', and you don't want it because it builds the recipient list from the non-digest list members. >'AviodDuplicates', As Brad points out. 'AvoidDuplicates', >'Clense', 'Cleanse', >'Cookheaders', >'OwnerRecipe', 'OwnerRecips' and fortunately, this throws away the prior recipient list built by CalcRecips. >'ToOutgoing' >] > >I know I don't need all of the above but I wanted to duplicate how >messages were handled when people send directly to the list. You probably don't want Approve unless you anticipate messages to the owner having and Approved: <password> header to bypass holds. You probably don't want most of what you added. You really don't want to duplicate what happens to list posts for a few reasons, not the least of which is what Brad alludes to - messages to the gate keeper must not be required to pass through the gate. In any case, if what you are trying to do is handle messages from non-members in the same way as they are handled for posts, all you need to add is Moderate, but even this addition will probably block notices from Mailman to the list owner/moderator because these are originally sent to listname-owner from mailman-bounces, listname-owner or listname-bounces, none of which are (normally) list members. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users 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-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
