My company uses Spam Assassin (with Razor) and we simply love it. However, just the other day, traffic on one of our *own* mailing lists was mistakenly flagged as spam. Checking the Spam Assassin report yielded the following line:
"SPAM: RAZOR2_CHECK (3.9 points) Listed in Razor2, see http://razor.sf.net/"; The service is a subscriber-based mailing list that we've been running for about five years. It requires a successful e-mail challenge-response confirmation before anyone is activated. In fact, the subscription mechanism is almost identical the one used for signing up for this Razor-users list. I guess this is understandable to a certain degree. The nomination procedure relies on humans, which inevitably opens the door to human error. However, it is an error, and I'm certain that some of our subscribers are being affected. (List traffic bouncing, etc.) False positives must happen to other people as well. What do the administrators of other responsible, non-spam mailing lists do when they encounter this problem? If this is not the right forum for this question, then I would greatly appreciate it if someone could point me in the right direction. Many thanks in advance. ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users
