Steve Thomas wrote:
On Thu, Feb 12, 2004 at 01:25:58PM -0500, spamassassin is rumored to have said:
Something I did notice though was that a few kb email received a huge 38pts. Now, I didn't do any time tests on that email to check how long it actually took to process, but I'm assuming longer than one that only scored a little over 5pts.
Someone more intimate with the code would be better prepared to give an accurate answer, but I have to ask why it would take longer. All the same tests are being run, DNSBLs being queried, razor checks, etc. Whether or not a test result is positive should have little or nothing to do with how long it takes to run.
Should there be an option to tell spamassassin to stop checking and tag the email after it has received a 5pts limit? Kind of a "Why keep looking at it after I know its spam?".
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-
