This is asked pretty frequently on this list. The answer is pretty basic - how do you know it's spam if there are still tests (some of which can reduce the score) that need to be run? Say I get a newsletter that's got the Habeas SWE mark in the headers (-8.0), but it gets 7 pts for content, before the Habeas test is run, and SA stops there. If I'm /dev/null'ing my spam, I'll never see that newsletter that I really did want.
I don't know what order the tests are run in, but I'd prefer that SA run all it's tests before it decides that a message is or isn't spam.
St-
If you run your tests in ascending order of score, wouldn't you eliminate this objection? All negative tests would be run before the positive ones, so once you hit the cutoff you'd know that it really was spam.
However, I think the cutoff should be separate from the trigger value... I do various things for different scores using tmda.
