SpamAssassin 3.0.4 breaks network checks (?)

[myrem]

I see CP upgraded to Spamassassin 3.0.4-- after which, network tests - dnsbl, dnsuribl, spf - checking seemed to stop. Appears to have been some issue with the Net :: DNS 0.50 pm which was also installed at the same time... I had to roll back to Net :: DNS 0.48 and recompile SA to get the network tests working again.

Anyone else notice similar or was it just me? Thought I would pass this along in case anyone was having issues.

[anup123]

I see CP upgraded to Spamassassin 3.0.4-- after which, network tests - dnsbl, dnsuribl, spf - checking seemed to stop. Appears to have been some issue with the Net :: DNS 0.50 pm which was also installed at the same time... I had to roll back to Net :: DNS 0.48 and recompile SA to get the network tests working again.

Anyone else notice similar or was it just me? Thought I would pass this along in case anyone was having issues.

I confirm this
Don't see few things happening as it was pre upgrade.

Anup

[myrem]

I confirm this
Don't see few things happening as it was pre upgrade.

Anup

It broke (for me) Jun 9 00:17:03 -0400 EDT (just after the nightly upcp)

[anup123]

It broke (for me) Jun 9 00:17:03 -0400 EDT (just after the nightly upcp)

I am watching and i definitely do not see the RBL network tests happening which is just letting few more length enhancers move in

Anup

[dgbaker]

Have you opened a ticket or bugzilla with cPanel to inform them and have them investigate?

[myrem]

Have you opened a ticket or bugzilla with cPanel to inform them and have them investigate?

I have not. And since I've fixed it myself and my license is not direct with CP, I am not going to open one... but i wanted to present the potential issue here so other admins could be on the look-out for it -- and take whatever steps they need to (open the ticket, etc)

[RickG]

It also seems to be a problem with Net::DNS version: 0.51 which I noticed was updated last night. If I run "spamassassin -D --lint" I see the following in the results:

debug: is Net::DNS::Resolver available? yes
debug: Net::DNS version: 0.51
debug: trying (3) ebay.com...
debug: looking up NS for 'ebay.com'
debug: NS lookup of ebay.com failed horribly => Perhaps your resolv.conf isn't pointing at a valid server?
debug: All NS queries failed => DNS unavailable (set dns_available to override)
debug: is DNS available? 0

How does one roll back to Net :: DNS 0.48 ?

Thx -

[anup123]

Waiting still for a bugzilla entry on Features Manager bug wrt catchall and forwarders to be fixed.

--lint -d :

debug: is Net:NS::Resolver available? yes
debug: Net:NS version: 0.50
debug: trying (3) sun.com...
debug: looking up NS for 'sun.com'
debug: NS lookup of sun.com failed horribly => Perhaps your resolv.conf isn't pointing at a valid server?
debug: All NS queries failed => DNS unavailable (set dns_available to override)

Anup

[myrem]

It also seems to be a problem with Net:NS version: 0.51 which I noticed was updated last night. If I run "spamassassin -D --lint" I see the following in the results:

debug: is Net:NS::Resolver available? yes
debug: Net:NS version: 0.51
debug: trying (3) ebay.com...
debug: looking up NS for 'ebay.com'
debug: NS lookup of ebay.com failed horribly => Perhaps your resolv.conf isn't pointing at a valid server?
debug: All NS queries failed => DNS unavailable (set dns_available to override)
debug: is DNS available? 0

How does one roll back to Net :: DNS 0.48 ?

Thx -

I confirm 0.51 also does not work, which is why I went back to 0.48

You can grab it here: http://search.cpan.org/~crein/Net-DNS-0.48/
(I did a manual download/make/install)

[anup123]

rollback to 0.48 gets everything firing up again.

debug: Net:NS version: 0.48
debug: trying (3) yahoo.com...
debug: looking up NS for 'yahoo.com'
debug: NS lookup of yahoo.com succeeded => Dns available (set dns_available to hardcode)
debug: is DNS available? 1

running upcp would again upgrade Net:NS?

Anup

[SageBrian]

so that explains the extra spams getting through. I'm getting a lot more "Spam Assassin Time Outs" since the update. I hadn't had time to track down the cause, so not sure if it's related, but likely is.

[myrem]

running upcp would again upgrade Net:NS?

Anup

I believe it very well may. I turned off automatic update for "cPanel Package Updates" to prevent it from breaking me on the next run just to be safe.

I have non-web hosting clients who use me for mail filtering services only, so SA being a primary tool for that segment of business, I can't afford to have it breaking.

[anup123]

I believe it very well may. I turned off automatic update for "cPanel Package Updates" to prevent it from breaking me on the next run just to be safe.

I have non-web hosting clients who use me for mail filtering services only, so SA being a primary tool for that segment of business, I can't afford to have it breaking.

Very much in the same scenario as yours.
Have had auto updates off eversince one night it brought my server down long back. So wouldn't do a upcp for quite sometime now

Anup

[chirpy]

Just been looking at this in the SpamAssassin code. Haven't nailed it down yet, but if you are desperate for a quick and dirty (very dirty) workaorund, you can:

Edit /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Dns.pm (sub your version of perl in to the path as appropriate) and change line 1264 from:

      $IS_DNS_AVAILABLE = 0; # should already be 0, but let's be sure.

to:

      $IS_DNS_AVAILABLE = 1; # should already be 0, but let's be sure.

The subsequent URIDNSBL checks will then be done. As I said, this is not a fix, just a way of getting it working until the problem can be found.

[chirpy]

Scratch that, the prettier workaround is to edit /etc/mail/spamassassin/local.cf and add:

dns_available yes

SpamAssassin will then skip the NS record test and continue on working.