From: "Marc Perkel" <[EMAIL PROTECTED]> > You're missing the point.
With all due respect, I don't think you really appreciate how Razor works. > It doesn't matter how I have my own system > setup to deal with spam. If I'm sending a newsletter to 30,000 people > and the ISPs - who I have no control over - or the users have their > system rely on the accuracy of Razor - then my newsletter gets censored > because it is either blocked or it is classified in a manner that it > ends up in a junk mail folder that is never read. Razor itself NEVER blocks ANY mail. EVER. It works by *flagging* mail that has been reported as 'known spam'. What any individual sysamin does as a result of Razor flagging it is entirely up to the individual sysadmins. > Yesterday Razor caused the Electronic Frontier Foundation's newsletter > to not reach possibly thousands of subscribing members. I want to be > able to prevent this from happening in the future. How do I contact the > complaining person(s) so that I can remove them from the list and make > sure this doesn't happen the next time? What can I to to ensure that > Razor doesn't flag EFFs newsletter as spam in the future? We've been running Razor on our servers for as long as it has been available, and like ANY spam blocking system, it is prone to produce the occasional false positives, but there is no way I'm ever going to STOP using it because its benefits far outweigh its faults. As for the the occasional false positives, I find this very easy to take care of by adding 'exceptions' to the filter rules - We now have literally DOZENS of these 'exceptions' (built up over the years), and the number of real false positives now recieved are so low as to be non-existant - in fact our *other* filters produce more false positives than Razor does. My suggestion to you would be to inform your 30,000 subscribers that if your newsletter isn't being recieved that they should contact their sysadmin so they can add their own exceptions. This is NOT difficult to do, and any sysadmin running razor will probably be pleased to comply. Naturally, if your 30,000 subscribers were obtained from a purchased mailing list (ie, it isn't something they subscribed to in the first place) then they probably have no interest in your newsletter, and they are not likely to let their sysadmin know that they are not getting them. Also, keep in mind that many of us have a 'honeypot' account that is NEVER used by a real person, and any and all mail sent to such honeypots are automatically reported to razor as being spam. Purchased maillists will almost always include at least one such honeypot. Now, I'm NOT going to insult you by even suggesting that you may be a spammer (especially since I've never yet met a spammer that thinks that THEIR 'newletter/advert/promotion' is really SPAM), but I will say that if you are NOT a spammer, and if you have a genuine user subscribed mailing list, then getting yourself excluded from incorrect razor flaggings would/should be a relatively simply matter of letting your *subcribed* users know that they may need to contact their sysadmin to have your mailings excluded from being razor flagged. It all comes down to working TOGETHER to achieve a common goal. Simply complaining that Razor, spam-assassin, or any other mail filtering system is bad for your business will achieve nothing. Regards Rod ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users
