Hi Dave (just in case this one got lost),
>> Also even though there are multiple entries the test only runs once and the resulted exit code is the triggered. << I know that all 18 "SNF" rule lines only require one invocation of Sniffer - which are then evaluated 18 different way. Fair enough. I also know that the 3 "SNFIP" rule lines are only one invocation - which is evaluated 3 different ways. And then there is the "SNFIPREP" rule. So I need to clarify this in my head. Will all 22 "SNF." rules (even though they are using 3 different commands) evaluate ONE invocation of Sniffer (just different return fields) or is EACH of these 3 command groups (SNF, SNFIP, SNFIPREPS) a separate entity that requires additional overhead? Since there is overlap between: SNFIPREP (which evaluates the GDUdb) and SNFIP (which also evaluates the GDUdb) and SNF-IP-RULES and SNFTRUNCATE (which also evaluate the GDUdb) - and I'm wondering if eliminating the SNFIP and SNFIPREP and just sticking with the SNF rules (which already has exit codes 20 and 63) would further reduce the Sniffer overhead by 2/3? Best Regards, Andy From: [email protected] [mailto:[email protected]] On Behalf Of David Barker Sent: Friday, April 30, 2010 11:14 AM To: [email protected] 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 [email protected], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
