At 21:41 9/07/03 -0400, Matt Kettler wrote:
At 04:42 PM 7/9/2003 -0800, Chris Ochap wrote:
I know I saw the option for spamassassin/spamd to stop scanning once the
appropriate users score has been reached, but I cannot find it again.  I
have spamd/spamc running on qmail/vpopmail/maildrop with per user
configs.  I don't see it in perldoc Mail::SpamAssassin::Conf, spamd -h,
or spamc -h.  Did I hallucinate this option?  :)


It has been removed because it caused FP's. The problem with this option is that for it to work properly, all negative scoring rules must be run first, then all positive scoring rules... However, for efficiency reasons, SA runs all the header checks first, then all the body checks.

If a message scores over your threshold in the header checks, but would later be dropped down by negative scoring body rules, it would wind up exiting and be incorrectly tagged as spam.

Running the rules in order of score chews up a lot of CPU time, and doesn't benefit many spams.

Also, I think its good to see the "real" score to help judge setting your actual threshold. Seeing that a certain kind of spam got a score of 15 when your threshold is 7 is a lot more useful than just knowing it got "more than 7".


Regards,
Simon



-------------------------------------------------------
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

Reply via email to