You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2007/10/08 17:55:20 UTC
Re: SSO's RHSBL
Giampaolo Tomassoni writes:
> > -----Original Message-----
> > From: ram [mailto:ram@netcore.co.in]
> > Sent: Monday, October 08, 2007 5:30 PM
> >
> > On Mon, 2007-10-08 at 14:40 +0200, Giampaolo Tomassoni wrote:
> > > I'm getting this stuff from named in my log files during message
> > scanning.
> > >
> > > Oct 8 14:36:40 ns2 named[6541]: unexpected RCODE (SERVFAIL)
> > > resolving 'xxxx.xxx.blackhole.securitysage.com/A/IN': a.b.c.d#53
> > > Oct 8 14:36:40 ns2 named[6541]: unexpected RCODE (SERVFAIL)
> > > resolving 'xxxx.xxx.blackhole.securitysage.com/A/IN': a.b.c.d#53
> > > Oct 8 14:36:40 ns2 named[6541]: unexpected RCODE (SERVFAIL)
> > > resolving 'xxxx.xxx.blackhole.securitysage.com/A/IN': a.b.c.d#53
> > >
> > > Is there any problem with securitysage.com?
> > >
> >
> > the rhsbl has been down for months now
>
> Well, it may be, but I believe it is not more than a week I'm getting these
> log entries.
>
> Anybody knows if there is this need a bug report? It seems to me there is no
> one about this matter.
yes, please open one -- if the RHSBL is down, we need to remove
the DNS_FROM_SECURITYSAGE rule asap.
--j.