Hiyo!

I realize that this may run afoul of some other objectives, particularly
those where people want to know all the tests that matched, and perform
supplemental checks based on that info, but I have to wonder, could we
improve the efficiency of SpamAssassin by having it make note of the
'HITS-REQUIRED' score and have it STOP TESTING after it surpasses that
score? 

IE. Is there really any reason to keep testing a piece of mail once we
know it is spam? When our threshold is somewhere between 3 and 10, and I
see mail scoring 20 or 30, I realize that this mail probably passed that
threshold less than half-way into the tests. 

This could, in theory, lower our processor 'cost' for spam considerably.
Thoughts? Good idea? Stupid idea?

- Charles

Reply via email to