Re: So you wanted to firewall your mail server...

2007-05-11 Thread Ernie Dunbar
e it would actually come out and *tell* the sysadmin which host there is no route to, but I expect that's an entirely different bit of code or even another program entirely that's coming up with that error. -- View this message in context: http://www.nabble.com/So-you-wanted-to-firewall-your-mail-server...-tf3729493.html#a10440500 Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: So you wanted to firewall your mail server...

2007-05-11 Thread Daryl C. W. O'Shea
Ernie Dunbar wrote: Ken A wrote: 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, line 137. It might be a good idea to change DnsResolver.pm to mak

Re: So you wanted to firewall your mail server...

2007-05-11 Thread Ernie Dunbar
d all is well again. Your post was most enlightening. :) It might be a good idea to change DnsResolver.pm to make this error message clearer. I've googled this error message and other people are similarly confused. "DNS lookup failed" would be a good one. -- View this message in con

Re: So you wanted to firewall your mail server...

2007-05-11 Thread Ken A
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, a

Re: So you wanted to firewall your mail server...

2007-05-11 Thread Ernie Dunbar
an failing silently due to the fact that no IP address exists, thus the DNSBL. -- View this message in context: http://www.nabble.com/So-you-wanted-to-firewall-your-mail-server...-tf3729493.html#a10439456 Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: So you wanted to firewall your mail server...

2007-05-11 Thread Theo Van Dinter
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 befo

So you wanted to firewall your mail server...

2007-05-11 Thread Ernie Dunbar
, 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...-tf3729493.html