You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Sebastian Arcus <s....@open-t.co.uk> on 2018/01/15 14:03:01 UTC

Re: Spamassassin DNS problems

On 10/01/18 12:14, teremy@web.de wrote:
> Hi.
> I found your spamassassin problem while looking for answers to my problem:
> http://spamassassin.1065346.n5.nabble.com/Dns-Blocklists-always-returning-0-records-td124564.html
> 
> It seems the problem you have/had is exactly the problem I have!
> Sadly there is no solution in the thread.
> Did you manage to find a solution?

Hi. I did reply to the list at the time in case others would find the 
information useful. For some strange reason, the SA mailing list archive 
doesn't seem to include my last reply. I've enclosed it below:


On 17/05/17 18:11, Sebastian Arcus wrote:

Just a follow-up and clarification on this issue - after more testing, 
it seems that it was the Spamassassin version which was the problem. I 
have had to upgrade SA on 7 servers running 3.4.1 on Slackware - as the 
dns rbl's weren't working on any of them. The only server I had with SA 
3.4.0 *was* actually working correctly. After upgrading all the boxes to 
4.0.0, the dns rbl's are now working correctly. I have *not* changed any 
configuration options in SA - I left all the servers as they were in 
this respect - so it seems it was not a configuration issue.

I'm afraid I haven't been able to narrow it down further than this. The 
servers were all running various kernels, both x86 and x86_64 
architectures, and several different versions of Perl - so I would guess 
the SA version was the common factor and the likely culprit.