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
Mail::SPF because it is not broken on modern Perl and is maintained,
whereas Mail::SPF hasn't been right since Perl 5.10.1 and never will be,
as it has not been touched since 2006.
Installing Mail::SPF::Query had to be forced because most of its tests
fail
but it looks like it is returning correct SPF evaluations.
Forcing installation of abandoned Perl modules that fail most of their
tests is not a wise practice.
It's recognizing mail sent via blackberry trusted relays, and giving
me fail
results on spammers as it should.
If I get the time I'll look into the guts of Mail::SPF and try to
figure out
where it's going wrong.
Mail::SPF v2.009 is documented as having exactly one change:
--- 2.009 (2013-07-21 03:30)
Mail::SPF:
* Default to querying only TXT type RRs (query_rr_types =
Mail::SPF::Server->
query_rr_type_txt). Experience has shown that querying SPF type
RRs is
impractical.
If you update to 2.009, your local issue may vanish even without
removing your SPF record. However, anyone else still checking SPF
records instead of or in preference to TXT records will still break on
your record because it includes the Blackberry record which no longer
exists (SOA implies that it may have been removed last week.)
