That did it. Upgraded to 3.1.3 in backports and the IP does get picked up.
1.0 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
[125.22.64.110 listed in sbl-xbl.spamhaus.org]
Is this a known problem with anything less than 3.0.4?
I also see that AWL is part of the scoring now. It is enabled by default. How
do I
update this list? Will the auto-whitelist db keep growing or does SA trim it
every once
in a while? How do I remove any wrong addresses from there so that the AVG is
not thrown
off?
Thanks,
Dhaval
"Daryl C. W. O'Shea" <[EMAIL PROTECTED]> said:
> Dhaval Patel wrote:
> > Please bare with me while I try to get spamassassin fully tweaked.
> >
> > I received a spam in my inbox which clearly came from an ip that is on
> > blacklists
> > (http://www.dnsstuff.com/tools/ip4r.ch?ip=125.22.64.110) that spamassassin
> > should be
> > searching. Unfortunately spamassassin did not perform these searches for
> > this particular
> > spam. Below is a cut out from debug. Can somebody see why this check was
> > skipped? I
> > setup my trusted_networks last night so this is fixed.
> >
> >
> > debug: is Net::DNS::Resolver available? yes
> > debug: Net::DNS version: 0.48
> > debug: trying (3) doubleclick.com...
> > debug: looking up NS for 'doubleclick.com'
> > debug: NS lookup of doubleclick.com succeeded => Dns available (set
> > dns_available to
> > hardcode)
> > debug: is DNS available? 1
> > debug: IP is reserved, not looking up PTR: 125.22.64.110
>
> Upgrade to 3.0.4+ or 3.1.0+.
>
> Daryl
>
--
