Nate Sanders wrote: > Mailing lists are going to really make this difficult :-]
Yeah, they make just about any spam solution difficult. We use a global forged mail filter on our server. Any incoming mail to our server from a remote host that is not on a whitelist and claims to be from an internal domain gets rejected with a 554 SMTP code. This solution has completely eliminated the confusion our users experienced when spammers would forge mail from local businesses. (Dear WingNET, such-and-such local business sent me spam, what's up with that?) But the drawback to this solution is that we have to whitelist each user's mailing list server and companies like ebay, etc... (BTW, this forged email blocking software is based on TMDA code, and thus is available under GPL if anyone wants a copy. It's designed to run under qmail-qfilter and thus requires Qmail. Let me know if you want a copy.) Personally, I really like Kyle's solution to filter mailing list traffic BEFORE it hits TMDA. Does anyone know if there is a really good web interface available to automate the creation of server-side filtering rules? I might even be willing to pay for it if it's good enough. I've been looking for something to do server-side filtering from a web interface anyway (currently using maildrop on a per user basis with hand written rules for internal WingNET staff only, and would like to offer it as part of standard email), but it looks like such an interface could make Kyle's solution managable on a server-wide level. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
