A) an IP whitelist to match the IP blacklist feature
The idea of a "BLACKLIST" option in the global.cfg file comes up often, but unfortunately doesn't work.
The problem is that whitelisting and blacklisting, although they sound like complete opposites of each other, they are not. Whitelisting is a binary operation -- if an E-mail address is whitelisted, the E-mail goes through unscanned; if it is not whitelisted, it is treated as was planned. Blacklisting, on the other hand, is very complex. For example, does "BLACKLIST IP 192.0.2.25" mean to delete E-mail from that IP address? Quarantine it? Should a weight be applied?
B) a new "PASS" action. Then I could (ab)use the "ipfile" option to define an IP whitelist and define the "PASS" action (to let mail pass), which hopefully would supercede all other actions based on other tests.
That is something that we have been giving some thought to. It may be a bit tricky to implement, but would allow for much more flexibility.
-Scott
--- [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.
