Re: [Declude.JunkMail] Setting MAX Testing Weight

[paul]

As was mentioned here before, it's not a BAD idea to want Declude to stop after X has been reached, but, what if the whitelist came right after that X number?   Scott, are there any plans to, or can Declude already, run the Whitelist tests FIRST, so that if they are whitelisted, forgoes any weight testing alltogether? I think that would be beneficial in this case. If we list the whitelist tests first, will they be run first?    Paul ----- Original Message ----- From: Todd - Smart Mail To: [EMAIL PROTECTED] Sent: Tuesday, September 02, 2003 10:27 PM Subject: Re: [Declude.JunkMail] Setting MAX Testing Weight     I brought this up last week. Anyone see the benefit beside me?  The idea of being able to stop testing once a given Weight has been reached seems to have multiple benefits to me. My numbers indicate that about 45% of my spam would benefit from stopping testing at 4X my Hold Weight.          I know that Declude is not a resource hog but my Declude tests have increased dramatically over the past couple months and I don't see them getting any less in the future.   I've Added 2 x Subjectspaces Spamdomains 4 x Comments Spamcheck And a host of DNS tests.        That's my CPU, Bandwidth, and other resources.   And as more and more people move to spam prevention it seems the DNS Blacklists will get more use.       I guess my point is why continue to test and use resources once you reach a certain point where you're 3X, 4X or 5X your hold weight?        Any thoughts?     Todd Hunter Progressive Systems