On Thu 03/Mar/2016 13:17:49 +0100 Christopher Rüprich wrote: (On Thu 03/Mar/2016 02:18:12 +0100 Sam Varshavchik wrote:) > >> Appending >> >> ALLOW_0=BLOCK2 >> >> to the esmtpd configuration file, and restarting, should end up with >> this stuff getting recorded in the headers. > > Thank you. This is working for now, but the resulting header is quite > misleading: > > Authentication-Results: mail.con-data.net; > dnswl=pass dns.zone=pbl.spamhaus.org > policy.ip=127.0.0.10 > policy.txt="https://www.spamhaus.org/query/ip/79.203.70.161";
Yes, it is misleading. Courier believes you're allowing the IP, as if whitelisted. In fact you are allowing it, but not that way. > Also the name of the variable (in my case BLOCK2) is not mentioned. That > makes it hard to distinguish between whitelist and blacklist Exactly. Consumers of the result are supposed to know the list name, PBL in this case. Failure to distinguish Black from white impedes using "allowok", which is one of the good reasons to use -allow, as it is a deliverance for SPF -all. I have no idea how many people, if any, are using that config item. Perhaps it could be easily fixed by introducing a "-tolerate" (better name?) along with "-block" and "-allow". Thoughts? Ale -- ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
