Skip Menu |

This queue is for tickets about the Net-DNS CPAN distribution.

Report information
The Basics
Id: 110378
Status: resolved
Priority: 0/
Queue: Net-DNS

People
Owner: Nobody in particular
Requestors: iane [...] sussex.ac.uk
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Spamassassin problem
Date: Wed, 16 Dec 2015 16:11:14 +0000
To: "bug-Net-DNS [...] rt.cpan.org" <bug-Net-DNS [...] rt.cpan.org>
From: Ian Eiloart <iane [...] sussex.ac.uk>
Hi, I was running spamassassin with Net::DNS 1.03 and saw SPF errors in the log file. So, I upgraded to 1.04, and now I’m not seeing errors in the log file, but I am seeing incorrect SPF results SPF_NONE or SPF_PERMERROR for almost every lookup made. Snooping traffic on my DNS servers, I see TXT queries being made, and correct information being returned. But that’s it. -- Ian Eiloart Postmaster, University of Sussex +44 (0) 1273 87-3148
From: rwfranks [...] acm.org
On Wed Dec 16 11:31:30 2015, iane@sussex.ac.uk wrote: Show quoted text
> Hi, > > I was running spamassassin with Net::DNS 1.03 and saw SPF errors in > the log file. So, I upgraded to 1.04, and now I’m not seeing errors in > the log file, but I am seeing incorrect SPF results SPF_NONE or > SPF_PERMERROR for almost every lookup made. > > Snooping traffic on my DNS servers, I see TXT queries being made, and > correct information being returned. But that’s it. > -- > Ian Eiloart > Postmaster, University of Sussex > +44 (0) 1273 87-3148 >
SpamAssassin version? Perl version? Platform? Specific query examples?
Subject: Re: [rt.cpan.org #110378] Spamassassin problem
Date: Thu, 17 Dec 2015 16:31:37 +0000
To: "bug-Net-DNS [...] rt.cpan.org" <bug-Net-DNS [...] rt.cpan.org>
From: Ian Eiloart <iane [...] sussex.ac.uk>
Show quoted text
> On 17 Dec 2015, at 15:04, Dick Franks via RT <bug-Net-DNS@rt.cpan.org> wrote: > > <URL: https://rt.cpan.org/Ticket/Display.html?id=110378 > > > On Wed Dec 16 11:31:30 2015, iane@sussex.ac.uk wrote:
>> Hi, >> >> I was running spamassassin with Net::DNS 1.03 and saw SPF errors in >> the log file. So, I upgraded to 1.04, and now I’m not seeing errors in >> the log file, but I am seeing incorrect SPF results SPF_NONE or >> SPF_PERMERROR for almost every lookup made.
Show quoted text
> SpamAssassin version? > Perl version? > Platform?
/opt/local/bin/spamd --version SpamAssassin Server version 3.4.1 running on Perl 5.16.3 with SSL support (IO::Socket::SSL 2.020) with zlib support (Compress::Zlib 2.069) I’m using a MacPorts install (the latest configuration) on OSX Darwin Kernel Version 8.11.0 I think that’s OSX 10.4, so it’s pretty old, but the local resolvers are reliable. In fact, SpamAssassin is making some successful calls, and snooping the traffic, I can see the responses are accurate. So the problem lies in interpretation of the response. Show quoted text
> Specific query examples?
When the file bar, consists of just one message header: Received: from mail-wm0-f53.google.com ([74.125.82.53]) by karpinski.uscs.susx.ac.uk with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <ian@eiloart.com>) id NZEYTP-00019V-NS for iane@sussex.ac.uk; Tue, 15 Dec 2015 19:15:27 +0000 I get these results. But in fact, I get similar results for every one of about 30k inbound emails daily. /opt/local/bin/spamassassin -D 2>&1 < bar|grep -i spf /var/exim/log 16:28 Dec 17 16:28:35.343 [28825] dbg: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC Dec 17 16:28:36.146 [28825] dbg: config: fixed relative path: /opt/local/var/spamassassin/3.004001/updates_spamassassin_org/25_spf.cf Dec 17 16:28:36.146 [28825] dbg: config: using "/opt/local/var/spamassassin/3.004001/updates_spamassassin_org/25_spf.cf" for included file Dec 17 16:28:36.147 [28825] dbg: config: read file /opt/local/var/spamassassin/3.004001/updates_spamassassin_org/25_spf.cf Dec 17 16:28:36.336 [28825] dbg: config: fixed relative path: /opt/local/var/spamassassin/3.004001/updates_spamassassin_org/60_whitelist_spf.cf Dec 17 16:28:36.336 [28825] dbg: config: using "/opt/local/var/spamassassin/3.004001/updates_spamassassin_org/60_whitelist_spf.cf" for included file Dec 17 16:28:36.336 [28825] dbg: config: read file /opt/local/var/spamassassin/3.004001/updates_spamassassin_org/60_whitelist_spf.cf Dec 17 16:28:36.956 [28825] dbg: config: warning: no description set for FROM_MISSP_SPF_FAIL Dec 17 16:28:39.084 [28825] dbg: spf: checking to see if the message has a Received-SPF header that we can use Dec 17 16:28:39.160 [28825] dbg: spf: using Mail::SPF for SPF checks Dec 17 16:28:39.161 [28825] dbg: spf: checking HELO (helo=mail-wm0-f53.google.com, ip=74.125.82.53) Dec 17 16:28:39.193 [28825] dbg: spf: query for /74.125.82.53/mail-wm0-f53.google.com: result: none, comment: , text: No applicable sender policy available Dec 17 16:28:39.270 [28825] dbg: spf: already checked for Received-SPF headers, proceeding with DNS based checks Dec 17 16:28:39.270 [28825] dbg: spf: found Envelope-From in first external Received header Dec 17 16:28:39.271 [28825] dbg: spf: checking EnvelopeFrom (helo=mail-wm0-f53.google.com, ip=74.125.82.53, envfrom=ian@eiloart.com) Dec 17 16:28:39.277 [28825] dbg: spf: query for ian@eiloart.com/74.125.82.53/mail-wm0-f53.google.com: result: none, comment: , text: No applicable sender policy available Dec 17 16:28:39.280 [28825] dbg: rules: ran eval rule SPF_NONE ======> got hit (1) Dec 17 16:28:39.292 [28825] dbg: spf: def_spf_whitelist_from: already checked spf and didn't get pass, skipping whitelist check Dec 17 16:28:39.296 [28825] dbg: spf: whitelist_from_spf: already checked spf and didn't get pass, skipping whitelist check Dec 17 16:28:40.617 [28825] dbg: check: tests=EMPTY_MESSAGE,MISSING_DATE,MISSING_FROM,MISSING_HEADERS,MISSING_MID,MISSING_SUBJECT,SPF_NONE Dec 17 16:28:40.619 [28825] dbg: timing: total 5332 ms - init: 3269 (61.3%), parse: 1.24 (0.0%), extract_message_metadata: 16 (0.3%), get_uri_detail_list: 1.88 (0.0%), tests_pri_-1000: 22 (0.4%), compile_gen: 910 (17.1%), compile_eval: 322 (6.0%), tests_pri_-950: 18 (0.3%), tests_pri_-900: 19 (0.3%), tests_pri_-400: 15 (0.3%), tests_pri_0: 1606 (30.1%), check_spf: 117 (2.2%), poll_dns_idle: 0.13 (0.0%), dkim_load_modules: 70 (1.3%), check_dkim_signature: 1.18 (0.0%), check_pyzor: 1.23 (0.0%), tests_pri_500: 361 (6.8%) MISSING_FROM,MISSING_HEADERS,MISSING_MID,MISSING_SUBJECT,SPF_NONE * 0.0 SPF_NONE SPF: sender does not publish an SPF Record -- Ian Eiloart Postmaster, University of Sussex +44 (0) 1273 87-3148
From: rwfranks [...] acm.org
On Thu Dec 17 11:31:59 2015, iane@sussex.ac.uk wrote: Show quoted text
> >> I was running spamassassin with Net::DNS 1.03 and saw SPF errors in > >> the log file. So, I upgraded to 1.04, and now I’m not seeing errors > >> in > >> the log file, but I am seeing incorrect SPF results SPF_NONE or > >> SPF_PERMERROR for almost every lookup made.
If you are claiming a difference between 1.03 and 1.04, please provide the specific queries to demonstrate that. Show quoted text
> > SpamAssassin version? > > Perl version? > > Platform?
> > /opt/local/bin/spamd --version > SpamAssassin Server version 3.4.1
latest Show quoted text
> running on Perl 5.16.3
ok Show quoted text
>
> > Specific query examples?
Show quoted text
> /opt/local/bin/spamassassin -D 2>&1 < bar|grep -i spf > /var/exim/log 16:28 > Dec 17 16:28:35.343 [28825] dbg: plugin: loading
Please provide specific examples of queries which fail to work as expected.
RT-Send-CC: rwfranks [...] acm.org
In case it's not known yet: there's a bug report at https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7265 regarding Net::DNS 1.03+ and SpamAssassin. Maybe it's related to this problem here, maybe not. On 2015-12-30 14:01:50, rwfranks@acm.org wrote: Show quoted text
> On Thu Dec 17 11:31:59 2015, iane@sussex.ac.uk wrote: >
> > >> I was running spamassassin with Net::DNS 1.03 and saw SPF errors > > >> in > > >> the log file. So, I upgraded to 1.04, and now I’m not seeing > > >> errors > > >> in > > >> the log file, but I am seeing incorrect SPF results SPF_NONE or > > >> SPF_PERMERROR for almost every lookup made.
> > If you are claiming a difference between 1.03 and 1.04, please provide > the specific queries to demonstrate that. > > >
> > > SpamAssassin version? > > > Perl version? > > > Platform?
> > > > /opt/local/bin/spamd --version > > SpamAssassin Server version 3.4.1
> latest >
> > running on Perl 5.16.3
> ok > > >
> >
> > > Specific query examples?
>
> > /opt/local/bin/spamassassin -D 2>&1 < bar|grep -i spf > > /var/exim/log 16:28 > > Dec 17 16:28:35.343 [28825] dbg: plugin: loading
> > Please provide specific examples of queries which fail to work as > expected.
From: rwfranks [...] acm.org
On Wed Dec 30 15:19:44 2015, SREZIC wrote: Show quoted text
> In case it's not known yet: there's a bug report at > https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7265 regarding > Net::DNS 1.03+ and SpamAssassin. Maybe it's related to this problem > here, maybe not. >
No hard evidence in this unfocussed ramble round at least four problems. It seems possible that Net::DNS 1.04 with SA 3.4.1 plus patches from bugs 7223 and 7321 might solve the problem.