spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Prei├čler <tho...@preissler.me>
Subject Re: spf: lookup failed: addr is not a string
Date Mon, 27 Oct 2014 16:22:57 GMT
Hey Kam,

thanks for getting back!
I nailed it down a bit.

If I use Google DNS (8.8.8.8) I don't get the message, whereas when 
using other DNS servers (e.g. 156.154.70.1) spamassassin reports the spf 
lookup failure. But using 'dig @ip SPF mail.sys4.de' shows pretty much 
the same result.

I've attached two files which contain the output of spamassassin -D.
  - ok.log shows the output when using 8.8.8.8
  - failed.log shows the output when using 156.154.70.1

I tried unbound as a local DNS resolver, but it produces the spf lookup 
failure as well.

Are you able to reproduce this issue?

Thanks!
Thomas



On 2014-10-27 15:30, Kevin A. McGrail wrote:
> On 10/26/2014 6:04 PM, Thomas Prei├čler wrote:
>> I use SpamAssassin version 3.4.0 from wheezy-backports. Unfortunately, 
>> I get the following line sometimes in mail.log:
>> 
>> warn: spf: lookup failed: addr is not a string at 
>> /usr/share/perl5/IO/Socket/IP.pm line 646.
>> 
>> Attached you'll find a mail.eml and the output of spamassassin -D 
>> which shows the warning.
>> 
>> Any ideas how to solve this issue? Thomas, are you seeing the issue 
>> still because I could not replicate:
> 
> Oct 27 10:28:38.031 [8662] dbg: spf: checking to see if the message
> has a Received-SPF header that we can use
> Oct 27 10:28:38.177 [8662] dbg: spf: using Mail::SPF for SPF checks
> Oct 27 10:28:38.177 [8662] dbg: spf: checking HELO (helo=mail.sys4.de,
> ip=194.126.158.139)
> Oct 27 10:28:38.184 [8662] dbg: dns: providing a callback for id:
> 19578/IN/SPF/mail.sys4.de
> Oct 27 10:28:38.304 [8662] dbg: spf: query for
> /194.126.158.139/mail.sys4.de: result: none, comment: , text: No
> applicable sender policy available
> Oct 27 10:28:38.325 [8662] dbg: spf: already checked for Received-SPF
> headers, proceeding with DNS based checks
> Oct 27 10:28:38.326 [8662] dbg: spf: relayed through one or more
> trusted relays, cannot use header-based Envelope-From, skipping
> Oct 27 10:28:38.355 [8662] dbg: spf: def_spf_whitelist_from: already
> checked spf and didn't get pass, skipping whitelist check
> Oct 27 10:28:38.363 [8662] dbg: spf: whitelist_from_spf: already
> checked spf and didn't get pass, skipping whitelist check
> 
> My thoughts are perhaps they fixed their SPF record or you had a
> temporary DNS issue?
> 
> regards,
> KAM
Mime
View raw message