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.
--
View this message in context:
http://www.nabble.com/So-you-wanted-to-firewall-your-mail-server
On Fri, May 11, 2007 at 01:34:06PM -0700, Ernie Dunbar wrote:
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
-to-firewall-your-mail-server...-tf3729493.html#a10439456
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
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,
. I've googled this error message and other people are similarly
confused. DNS lookup failed would be a good one.
--
View this message in context:
http://www.nabble.com/So-you-wanted-to-firewall-your-mail-server...-tf3729493.html#a10439995
Sent from the SpamAssassin - Users mailing list archive
-to-firewall-your-mail-server...-tf3729493.html#a10440500
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
