Users

Thread Start a new thread

Download

[email protected]

March 2016

2 participants
2 discussions

Re: [Exim4U] Facing a problem with false positives using uribl.com Blacklisting?
by Gordon Dickens 31 Mar '16

31 Mar '16

1 0

Facing a problem with false positives using uribl.com Blacklisting?
by valki＠valki.com 30 Mar '16

30 Mar '16

Hi there! I just upgraded to exim4u 3 weeks ago and seem to have a problem regarding false positives when using uribl within exim4u. After some reading through the docs I found a topic regarding the problem when the mailserver is using a "big" public nameserver and therefore the requests may be blocked. So I installed quickly a forwarding bind99 - but still the problem persists. As an example: Incoming Email: 2016-03-29 14:42:57 1aksz2-000JNC-RN H=mx.bmi.gv.at [78.41.149.30] X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no F= rejected during MIME ACL checks: Blacklisted URL in message. (polizei.gv.at) in. See http://lookup.uribl.com. It claims that polizei.gv.at (austrian authority for racecontrol for autobahns) should be on a blacklist? Dont think so... [root(a)mail /]# nslookup polizei.gv.at.multi.uribl.com Server: 144.76.161.138 Address: 144.76.161.138#53 Non-authoritative answer: Name: polizei.gv.at.multi.uribl.com Address: 127.0.0.1 As far as I learned this should mean that its on the "gold" list eg. NOT on the blacklist. And as there is no 127.0.0.255 I assume that my local bind is doing its job well. So how can I find out why that email is being refused? kind regards, Valki

3 6