----- Original Message ----- From: "Rob Salmond" <[EMAIL PROTECTED]>
> probably cut down a lot of CPU overhead by optimizing in both directions, > quitting the spam test process as soon as a message has enough weight to > fail and only running certain tests after others have failed. (Or if others > have not failed?) Maybe for some sort of high traffic mode? Forgive the intrusion (I just troll here, don't actually have JM <yet>), but this idea seems flawed. If you quit testing once a certain weight has been reached, wouldn't you cut off further testing that might reduce that weight? In a system where a score can go up and down depending on the test, unless there is a way to order the tests so negative weighted tests are run first, I'd think that all tests must be accounted for. Just my $0.02. I'll shut up now. Kurt --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
