BODY WHITELIST CONTAINS Declude
If there is a match, the filter will end, and the E-mail will be whitelisted (with no further filters being run).
I'm not sure why this would be approached this way. Why not automatically stop Declude from processing all filters, custom, technical, RBL's, whatever, when something is whitelisted?
That's just the way the code exists now. When Declude JunkMail was originally created, there were no whitelists (they were added about 6 months after Declude JunkMail was first released). When they were added, they were rarely used, and the extra processing wasn't much of a consideration, and ensured that there would not be any unwelcome side-effects (for example, reverse DNS lookups would be skipped, preventing the %REVDNS% variable from working).
Also, order becomes an issue -- from the beginning, users haven't been able to control the order that tests are run in. That means that if a test is to whitelist an E-mail, other tests may already have been run (so it would not be possible to not run them).
Why would we want to have to start coding this information into our individual filters?
That's up to you.
One reason is that it allows more flexibility -- anything that a filter can filter on can now be used for a whitelist. Another reason is that it helps reduce CPU time by ensuring that other filters will not be run.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask about our free 30-day evaluation.
--- [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.
