Joseph C. Lininger wrote: > I'm thinking, if the address is > whitelisted, all one need do is to set BLOCK to an empty string. This > line should, if I'm not mistaken, refuse mail from anyone listed on > spamhaus while setting BLOCK to the empty string (and allowing the mail > to pass) for anything on dnswl. > > - -block="list.dnswl.org,BLOCK,\"\" zen.spamhaus.org,BLOCK" > > Will this always have the consequences I am intending?
I think you miss the second "-block" option in your syntax above. That should then cause couriertcpd to skip the spamhaus lookup for dnswl hits, as you apparently wish. Specifically, I don't think that's the intended meaning of dnswl. They claim to monitor spamhaus block lists and revoke listing to servers that get caught there. AFAIK, they don't attempt to dig their nose in a mail domain's operations. Therefore, the recommended use of dnswl is just bettering SpamAssassin's score. > If not, what am I doing wrong and how do I fix it? The BLOCK1/BLOCK2 alternative described in the man page allows for more flexibility. E.g., one can block according to users' options. In your case, it would allow to log addresses listed in both lists --in theory, none. You'd need to use courier's whitelisting API, though: It is activated via courier's "maildropfilter" configuration file, usually so as to result in "embedded mode" maildrop invocations, right after RCPT. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
