Thanks for clearing up that it doesn't work for the 2nd variable (I'm aware that it is an internal and not and external test, and that it is the SECOND variable, and that it only executes once, etc.)
As a suggestion, you might consider enabling the "nonzero" option for the second variable as well. The reasons for preferring one "nonzero" exit code of (currently 18) individual exit codes are a) The config file will be more compact, b) Fewer lines mean few chances of errors/omissions c) No need to keep worrying about missing the announcement for a new "exit code" whenever Peter decides to extend the list From: supp...@declude.com [mailto:supp...@declude.com] On Behalf Of David Barker Sent: Friday, April 30, 2010 11:14 AM To: declude.junkmail@declude.com Subject: RE: [Declude.JunkMail] Sniffer Integration -> Global Exit Code "nonzero"? The test works as an internal test and not as an external test. The main difference being the location of the exit code. See external is the 1st variable whereas the internal it is the 2nd variable and the NONZERO does not work for that. SNIFFER external nonzero "C:\Smartermail\Declude\Sniffer\xxxxxxx.exe xxxabc123xxxx" 12 0 SNIFFER-TRAVEL SNF x 47 12 0 Also even though there are multiple entries the test only runs once and the resulted exit code is the triggered. David --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to imail...@declude.com, and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
