John, One of the other bugs I have seen is if a process takes more than 5 minutes to complete and is configured as a "weight" test and Declude terminates it they use the OS result code of "259" as the returned weight instead of defaulting to zero. Darrell

John Tolmachoff (Lists) writes:
FYI to all running the Beta, I have reviewed and verified a problem brought
to my attention by Kami.
It appears that some times, even though the external test is reporting an
exit code of 0, DecludeJM is treating it as a fail and adding the configured
weight.
This goes for both positive weights like Sniffer and invURIBL and negative
weights like AutoWhite for Declude. Declude support and beta have been notified.
John T
eServices For You

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



------------------------------------------------------------------------
Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers.

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