OK more reading ��� more ideas J

Requesting a TXT does the trick and let some light shine on the issue:

[root@mail /]# host -tTXT polizei.gv.at.multi.uribl.com

polizei.gv.at.multi.uribl.com descriptive text "127.0.0.1 -> Query Refused. See http://uribl.com/refused.shtml for more information [Your DNS IP: 188.40.25.2]"

Looks like I misunderstood ���gold entry��� and still a DNS in my Upstream is blocked L

Any better ideas than looking for an external, small DNS Server to point my local caching bind to?

Von: users [mailto:users-bounces@exim4u.org] Im Auftrag von valki@valki.com
Gesendet: Dienstag, 29. M��rz 2016 15:28
An: users@exim4u.org
Betreff: [Exim4U] Facing a problem with false positives using uribl.com Blacklisting?

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=<Oeffentlichkeitsarbeit-V@polizei.gv.at> 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@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