Postfix is a mailer, it needs a lot of help with spf – thats dns, and dkim message signing but email is still reveleant. However one day all our dns lookups stopped, apache (a webserver) was using it but not postfix. It was time to troubleshoot. Nothing had changed in our configurations* and dig lookups to the block list service returned what they should [dig ip.some.blocklist.at.a.tld].
I check the config commands and they are also the same. Its a silly thing, so one evening the thought resolv.cfg pings into my monkey head. and that’s it when next day i update it and discover that network manager changed it knocking out nameserver 127.0.0.1, after some copying of the file to the right place – postfix demands a copy in a non /etc directory and things start looking up in postfix land.
Client host [209.43.22.5] blocked using bl.spamcop.net
Argh well at least postfix was not to blame and network manager was and networking has not changed either. Oddly dkms signing with private keys and a public key in dns kept working so although that’s not part of native postfix dns stuff was working in a manner.
* note plural not singular
Bananas likes linux and runs lots of things with it, 
