I never mentioned mailing lists. Here's the another version of my original
post so we're clear:
Latest Mail::SPF (2.9 circa 2013) builds but fails its test suite on my new
system. New linux, perl, perl modules, etc.
After forcing it to install, I later found that spamassassing is getting
T_SPF_PE
spamassas...@nro.ca skrev den 2017-06-05 16:33:
I would guess it is some kind of issue with newer dependencies or dns
resolution. If I wait long enough someone else will figure it out.
if it just fails on forwarded emails eq on maillists, add forwarding ip
to trusted_networks solves spf fails
On 5 Jun 2017, at 12:03, Benny Pedersen wrote:
> Mail::SPF uses SPF first, and failback to TXT if SPF does not exists
Changed in the latest version, almost 4 years ago.
Bill Cole skrev den 2017-06-05 14:53:
Remove your SPF (not TXT) record. The SPF record type is deprecated.
The problem is that srs.bis.na.blackberry.com has no SPF record (only
a TXT) making any SPF record including it invalid.
Mail::SPF::Query uses TXT only
Mail::SPF uses SPF first, and failb
Mail::SPF version 2.009 is package "Mail-SPF-v2.9.0" which is what I
indicated I was using (and had to force install) in my first post.
spfquery works, but whatever perl interface SA is using is not producing
correct results. Not just on my own domains, but on many others as well. My
dns spf reco
And furthermore...
On 2 Jun 2017, at 19:05, spamassas...@nro.ca wrote:
I started reading SPF.pm and saw that I could hack it to avoid using
Mail::SPF and instead use (what seems to be) the less preferred
Mail::SPF::Query
This is a wrong approach. SA will use whichever is installed but prefers
On 2 Jun 2017, at 19:05, spamassas...@nro.ca wrote:
Thanks for the tip! I didn't know how to debug that stuff. Here's what
happens with a spammer faking one of my own domains:
spamd[21654]: spf: query for
isabelle.2...@nro.ca/41.203.191.125/!41.203.191.125!: result:
permerror, comment: , text
Thanks for the tip! I didn't know how to debug that stuff. Here's what
happens with a spammer faking one of my own domains:
>spamd[21654]: spf: query for
>isabelle.2...@nro.ca/41.203.191.125/!41.203.191.125!: result: permerror,
>comment: , text: Included domain 'srs.bis.na.blackberry.com' has no
Thanks for the tip! I didn't know how to debug that stuff. Here's what
happens with a spammer faking one of my own domains:
>spamd[21654]: spf: query for
>isabelle.2...@nro.ca/41.203.191.125/!41.203.191.125!: result: permerror,
>comment: , text: Included domain 'srs.bis.na.blackberry.com' has no
On Fri, 02 Jun 2017 10:33:39 -0400
spamassas...@nro.ca wrote:
> Hi. I'm getting T_SPF_PERMERROR extremely often. Not exclusively, but
> especially when spammers are faking my own domain names.
>
> Here's an example from the good old xerox copier spam:
>
> From cop...@nro.ca Fri May 26 08:26:18
Hi. I'm getting T_SPF_PERMERROR extremely often. Not exclusively, but
especially when spammers are faking my own domain names.
Here's an example from the good old xerox copier spam:
From cop...@nro.ca Fri May 26 08:26:18 2017
Return-Path:
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28)
11 matches
Mail list logo
