> These three settings are going to give you false positives galore. > > Our default "suggested" setting is 7.0 and customers can't see it > any lower > than 5.0 > Actually, under our system, I tested for over a month with different levels and, given the underlying scoring system(s), there are very few false positives. For those few FPs, we've setup a SquirrelMail plugin to allow customers to whitelist and blacklist emails and domains. We're using SQL-based preferences.
> RBL checks help a lot, as do Bayes (you don't say if you're using it) and > Razor/Pyzor/DCC. Honestly, without network checks SpamAssassin isnt > anywhere *near* as good. > I have bayes enabled, DCC is installed and enabled, too. I currently am skipping RBL checks (resource issue at the moment). Everything else is at default. I'm pretty sure now that bayes is working after removing the .spamassassin directory and recreating and re-feeding it. > Most spam I see scores in the 10 - 30 range, some even as high as 50, > although there is still quite a bit from 5 to 10. > See, this is what I'm talking about -- I can't ever remember seeing anything over 30, and the vast majority of spam appears to be caught and tagged in the 5-15 range on my system. I had considered installing Razor (seems to be fairly popular), but given a lack of time to test it when deploying, I opted not to do so. ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
