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_PERMERROR returned a lot, not just for spoofs of my own domains, but plenty of other domains. Oddly enough, the spfquery tool it provides works fine. I have since switched to the much older Mail::SPF::Query. Its build tests fail as well. (looks like they test a domain that is no longer registered). I am having good success using Mail::SPF::Query with spamassassin The spfquery tool also appears to work. This bug report from 2014 reflects my experience. Bug #99890 for Mail-SPF: Mail-SPF-v2.9.0 fails Build test https://rt.cpan.org/Public/Bug/Display.html?id=99890 My guess for the cause of the failure is other newer perl modules that have been maintained beyond Mail::SPF, or maybe the dns resolver that SA passes to the spf function is somehow different than the resolver that the spfquery tool is using. On Mon, 05 Jun 2017 23:31:58 +0200, you wrote: >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 > >but it also disable whitelist in dnswl for that forwarding ip > >not all maillists have spf, and spf does generic not being breaked on >maillists since envelope sender changes > >what part fails then ?
