On 06/07/2015 10:29 PM, Lindsay Haisley wrote: > > So, e.g., if I'm using BLOCK2, BLOCK3 and BLOCK4, (but not BLOCK) in the > BLACKLISTS list in /etc/courier/esmtpd (I deal with these in a maildrop > script) and I have "w.x.y.z<tab>access,BLOCK" > in /etc/courier/smtpaccess/webadmin to whitelist w.x.y.z would I not > need instead to set _every_ BLOCKn listed in BLACKLISTS?
You need to set every variable that you want to override. The access file is checked first, and environment variables are set. Later, when a DNS check specified by -block are run, that section of code first checks to see if the environment variable that it might set is already set. If it is already set, the code returns immediately, without checking DNS. > The logic of how this _should_ work is pretty simple. Without filtering > or blocking, courier accepts everything. Adding filtering or blocking > modulates this behavior. Specific exemptions should then easily be able > to trump this filtering or blocking just as a more specific whitelist > will carve out an exception to, say, a /24 group IP address block. I think that's how it works, but the code is easier to read than that description. :) ------------------------------------------------------------------------------ _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
