Hi, thanks for your really fast responses! These led me into the right direction.
The problem is, the name server I'm using is blocked. I'm using a name server of a big hosting provider. ______________________________________________________________________ $ dig -t txt amiblocked.dnswl.org ; <<>> DiG 9.9.5-3ubuntu0.2-Ubuntu <<>> -t txt amiblocked.dnswl.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65311 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;amiblocked.dnswl.org. IN TXT ;; ANSWER SECTION: amiblocked.dnswl.org. 172382 IN TXT "Yes" ;; Query time: 1 msec ;; SERVER: 213.133.100.100#53(213.133.100.100) ;; WHEN: Thu Mar 05 10:10:06 CET 2015 ;; MSG SIZE rcvd: 65 ______________________________________________________________________ I think I'll need to set up my own caching name server... Michael On 05.03.2015 09:53, Viktor Dukhovni wrote: > On Thu, Mar 05, 2015 at 09:37:26AM +0100, Michael wrote: > >> permit_dnswl_client list.dnswl.org, >> >> Mar 5 09:18:14 mx0 postfix/smtpd[25201]: warning: >> 144.252.10.85.list.dnswl.org: RBL lookup error: Host or domain name not >> found. Name service error for name=144.252.10.85.list.dnswl.org type=A: >> Host not found, try again >> >> Did I miss something in my config? > > Looks like you have a DNS resolver issue, or perhaps your access > to this list is blocked by policy. Test with "dig": > > $ dig +noall +comment +ans -t a 144.252.10.85.list.dnswl.org > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17429 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 4096 > ;; ANSWER SECTION: > 144.252.10.85.list.dnswl.org. 28692 IN A 127.0.15.0 > > Nothing in your Postfix configuration is likely to break DNS in > this way, the problem is outside Postfix. Note that the dnswl.org > nameservers have IPv6 addresses, if your caching resolver is trying > to use IPv6 to reach them, but your IPv6 connectivity is broken > that could be part of the problem. > > There are other potential issues. Start by looking in your > /etc/resolv.conf file (make sure smtpd(8) is not chrooted, > or that the resolv.conf file in the jail is correct). Then > understand why the resolver is having trouble. >
