Ernie Dunbar wrote:
We just put our mailserver (with SpamAssassin of course) behind a firewall,
and now we get many many interesting error messages from spamd telling me
that there's no route to some host or other. I tweaked the DnsResolver.pm
module to show what host it was trying to route to, and I got this output:
May 11 12:00:09 pop spamd[47940]: dns: sendto() failed: No route to host
Host: clickboothlnk.com at
/usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/DnsResolver.pm line
340, <GEN1444> line 137.
May 11 12:00:09 pop spamd[47940]: dns: sendto() failed: No route to host
Host: mktexpertise.net.multi.uribl.com. at
/usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/DnsResolver.pm line
340, <GEN1444> line 137.
May 11 12:00:09 pop spamd[47940]: dns: sendto() failed: No route to host
Host: 190.57.78.66.combined.njabl.org. at
/usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/DnsResolver.pm line
340, <GEN1444> line 137.
May 11 12:00:09 pop spamd[47940]: dns: sendto() failed: No route to host
Host: 190.57.78.66.bl.spamcop.net. at
/usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/DnsResolver.pm line
340, <GEN1444> line 137.
Of course, hosts like 190.57.78.66.bl.spamcop.net are DNSBL blacklist
members, and they resolve to nothing at all, which is why there is no route
to host. But why is spamd suddenly spewing these errors now? It didn't do
this before the firewall was in place.
They don't resolve to nothing at all. The response from the DNS server
is usually NXDOMAIN, not 'no route to host'; you get _that_ when you
block the connection to the dns server you are using.
--
Ken Anderson
Pacific.Net
