Theo Van Dinter-2 wrote:
>
> 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 the firewall was in place.
>
> You weren't blocking the requests before?
>
> --
> Randomly Selected Tagline:
> "J: Do YOU know who the Spin Doctors are?
> P: Maybe your mother does..." - John West and a Pizza
> Delivery Guy
>
>
>
Heh. Well, when one tries to request anything of an IP address of "",
generally I'd expect you'd go nowhere fast. :) I'm wondering why it's
generating an error at all, rather than 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.
