Even if it's not good for statistical purposes, what do you think about
a new parameter "stop_on_hold=true/false" wich will stop any further
(external, ressource intensive) tests if the hold value is already
reached?
I think some systems with a lot of traffic can then use more tests, but
only if this is necessary.
It's something we're thinking about. It would require a lot of work the way Declude JunkMail is currently set up, but would be useful if it could prevent resource intensive tests from being run unnecessarily.
-Scott

---
[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.


Reply via email to