I'm not sure I'm following you... but I think what you might need is an additional license. Suppose you create one rulebase that will contain only your white rules. Then leave the normal sniffer rulebase alone. The small rulebase with the white rules will be so small as to require nearly no additional processing power. You would have your white rules, and you would retain any black rules that matched as well.

An alternative while still using a single rulebase is to parse the log file for the details with an additional utility. Message Sniffer can only return a single numeric result, but it records all of the rules that matched.

Hope this helps,
_M

At 02:02 PM 12/5/2003, you wrote:
Hello David,

Friday, December 5, 2003, 11:44:41 AM, you wrote:

DS> 3. Anyone see any problems with this scenario?

Ok, I'll answer my own question.  In thinking about this more, this
isn't going to work.

If I recode my rule base to return a 1 instead of 0 on whitelist, then
the original sniffer test will interpret the 1 as a spam, then the
externalplus test will interpret the 1 as whitelist and override the
sniffer external test.

So, I still lose the original reason for sniffer failure since sniffer
will always be returning a 1, right?




-- Best regards, David mailto:[EMAIL PROTECTED]

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

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