Am 22.09.2016 um 21:40 schrieb Thomas Barth:
URIBL_BLOCKED shows you are using still a dns-forwarder and so won't get
results from a lot of blacklists
http://uribl.com/refused.shtml
fix that - use a local caching resolver with *no forwarding* and if you
are using dnsmasq just don't do that for a inbound mailserver
I found an instruction here for a debian system
https://manageacloud.com/configuration/local_dns_caching
/etc/resolv.conf
nameserver 127.0.0.1
/etc/resolv.dnsmasq
nameserver 208.67.222.222
nameserver 208.67.220.220
nameserver 208.67.222.220
nameserver 208.67.220.222
/etc/default/dnsmasq
DNSMASQ_OPTS="-r /etc/resolv.dnsmasq"
But it is using dnsmasq for local dns caching. I ve configured it, but I
still see URIBL_BLOCKED=0.001 in a mail header
because it is nonsense
the point is not that you use 127.0.0.1 as dsn server - the point is
that *nobody else* is using that dns server - i doubt that you are the
only person on this plant using the 208.67.xx.xx opendns servers
frankly - get the basics!
