I found archived messages about the order in which tests are run, but
nothing which directly applies
to something I noticed in our logs. Whitelisting works, but many messages
are getting tests run on
them before the whitelist. Seems like a waste of CPU. Is there a way to
make Declude skip all
I found archived messages about the order in which tests are run, but nothing which
directly applies
to something I noticed in our logs. Whitelisting works, but many messages are getting
tests run on
them before the whitelist. Seems like a waste of CPU. Is there a way to make Declude
skip all
] On Behalf Of R. Scott Perry
Sent: Thursday, June 26, 2003 9:58 AM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] Test order and whitelist
I found archived messages about the order in which tests are run, but
nothing which directly applies
to something I noticed in our logs. Whitelisting works
: Thursday, June 26, 2003 10:37 AM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] Test order and whitelist
You know, this brings up another point. We use a weighting method and
consider all 20 weights to be spam. Once that weight is reached, it
would make sense to stop testing to save proc time
You know, this brings up another point. We use a weighting method and
consider all 20 weights to be spam. Once that weight is reached, it
would make sense to stop testing to save proc time. Just food for
thought.
That's one we've given some thought to. The catch, though, is negative
weights --
