Description of problem: After I updated perl-Net-DNS to the latest version (perl-Net-DNS-0.76-1.fc20.x86_64.rpm), spamassassin shows the following errors: Jun 19 10:36:41 main spamd[10551]: spamd: connection from localhost [::1]:43706 to port 783, fd 6 Jun 19 10:36:41 main spamd[10551]: spamd: setuid to sa-milt succeeded Jun 19 10:36:41 main spamd[10551]: spamd: processing message <C5717E7C2B9EDA49A81164B48D20472642F0B9.root> for sa-milt:997 Jun 19 10:36:41 main spamd[10551]: plugin: eval failed: available_nameservers: No DNS servers available! Jun 19 10:36:41 main spamd[10551]: rules: failed to run NO_DNS_FOR_FROM RBL test, skipping: Jun 19 10:36:41 main spamd[10551]: (available_nameservers: [...] No DNS servers available!) Jun 19 10:36:41 main spamd[10551]: spf: lookup failed: available_nameservers: No DNS servers available! Jun 19 10:36:41 main spamd[10551]: spf: lookup failed: available_nameservers: No DNS servers available! To fix this issue, I had to downgrade perl-Net-DNS to this version: perl-Net-DNS-0.75-1.fc20.x86_64 This happens on two different, unrelated servers.
I have worked around this locally by explicitly configuring my nameserver in /etc/mail/spamassassin/local.cf: # https://mailman.archlinux.org/pipermail/arch-general/2014-June/036479.html # work around inability to find nameservers dns_server 127.0.0.1
Thank you. I can confirm that it works when adding the DNS servers in local.cf
Sadly, 0.76 wasn't just a bugfix release. Apparently, there was an API change, too. Spamassassin will need a fix (already upstream) to work to work with 0.76+.
I've already fixed f20 (see bug 1111586) I'll push a f19 build soon... *** This bug has been marked as a duplicate of bug 1112003 ***