> It shouldn't be hard to distinguish between a whitelist and a > blacklist. If it were a blacklist (BLOCK), the mail would get rejected > by the server. At this point, you no longer see any blacklisted sources. What I meant is: shouldn't BLACKLISTS="-allow=[...],BLOCK" leave a similar header to BLACKLISTS="-block=[...],BLOCK2"? The only way to distinguish them would be a regex that checks dns.zone. > > As far as identifying the variables, you should be able to > conclusively determine which one is which by looking at dns.zone and > policy.ip. It might get hairy when there are multiple entries, which > is possible, but it should be possible to concoct a regular expression > to figure it out. That's exactly what I'm doing at the moment.
One more question: Is there a way to disable blacklist-checking for authenticated users? Currently most mails from one local user to another local user end up in the junk-folder, because they're sent from a dynamic IP. :-( ------------------------------------------------------------------------------ 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
