On Mar 27, 2008, at 1:18 PM, Timo Wingender wrote: > Jason Pruim schrieb: >> >>> >> >> One thing that I've been thinking about in regards to this... Is >> this job the responsibility of mailman? To scan for spam and other >> such things? > Of course this is not the primary job of mailman. But it can help to > reduce the effort to moderate lists. > > If you have an moderator for each list it's no problem if a few spam > messages per day are hold. But if you don't it's much effort to sort > out all the spam.
I see what you're getting at.. I've never looked at it from that stand point before so it didn't make sense to me. I use mailman primarily for internal communication for my company, the ability to send a file to [EMAIL PROTECTED] and it goes to who ever is in the art department that day has been great! > >> >> I do all of my scanning at the front end, all e-mail gets run >> through ASSP to scan blacklists, grey list, etc. etc. then it goes >> to the MTA, which in my case just verifies the account exists (Or >> an alias for it does) and then is delivered to mailman for >> delivery... > Not every site runs ASSP and I am not a fan of greylisting. It > delays mails of legitimate users and once most sites use is spammers > will get around it. I completely agree... Greylisting isn't the best way to use it. I should say though that I might be in a different configuration then you... Most of the people who e-mail my domain are our customers and have their own domain. So I can white list all of our customers since the chance of spam is very low from their company mail servers. Greylisting also helped me get my feet wet with spam related issues since I wasn't ready to start blocking based on content. But now we get too much spam making it around the greylisting so I need to get back into the fight against spam! :) > >> >> Why not run something like that instead of checking for all that >> stuff just before the delivery? >> >>> Again, just my opinion. >>> >>> -- >>> Jo Rhett >>> Net Consonance ... net philanthropy, open source and other >>> randomness >>> _______________________________________________ >>> Mailman-Developers mailing list >>> Mailman-Developers@python.org >>> 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-developers%40python.org/ >>> Unsubscribe: >>> http://mail.python.org/mailman/options/mailman-developers/japruim%40raoset.com >>> >>> Security Policy: >>> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp >>> >> >> -- >> >> Jason Pruim >> Raoset Inc. >> Technology Manager >> MQC Specialist >> 3251 132nd ave >> Holland, MI, 49424-9337 >> www.raoset.com >> [EMAIL PROTECTED] >> >> >> > -- Jason Pruim Raoset Inc. Technology Manager MQC Specialist 3251 132nd ave Holland, MI, 49424-9337 www.raoset.com [EMAIL PROTECTED] _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org 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-developers%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
