% of false positives for default spamassassin implementation?

[spaceman]

Hi All,

Does anyone have any idea how many false positives, if any, I can expect if I turn on SpamAssassin on a hosting account with all the default settings, i.e. no additional tweaking whatsoever?

My educated guess is zero or close to it, because I believe that default threshold score of 5.0 is not very aggressive, therefore only the most obvious spam will be detected.

If this is the case, then this would be a good case for enabled SpamAssassin WITH auto-delete for all hosting accounts. Has anyone else gone down this path, and if so, have you ever had any problems with customers reporting false positives?

Thanks.

 

[spaceman]

Oops. Just read this:

"Set the number of hits required before a mail is considered spam. "n.nn" can be an integer or a real number. 5.0 is the default setting, and is quite aggressive; it would be suitable for a single-user setup, but if you're an ISP installing SpamAssassin, you should probably set the default to be more conservative, like 8.0 or 10.0"

So the default setting of 5.0 is actually quite aggressive. Can anyone give the benefit of their real world experience and indicate what setting they would be comfortable with implementing for all hosting accounts? Do you agree with 8.0 or 10.0? Also, let's say I did want to implement SpamAssassin for all accounts with a setting other than the default 5.0. Is this possible? Some script to WHM feature to do this? Thx.

 

[casey]

Don't set it for the customers. Let them set it on their own. If you set it to delete stuff automatically you are inevitably going to have a customer complaining that an important e-mail was deleted from the server without his knowledge.