On 2022-05-26 at 11:05:59 UTC-0400 (Thu, 26 May 2022 11:05:59 -0400)
Alex <mysqlstud...@gmail.com>
is rumored to have said:
Hi,
no matter if you have Mail::SpamAssassin::Plugin::DMARC loaded or
not.
Latest trunk has fix for DMARC waiting for SPF and DKIM results.
Might
be
relevant to this thread.
according to:
https://github.com/apache/spamassassin/commit/63fa58d814837f5d12b5d587ab4b72fa3c7501c3
it should fix the problem.
Okay, wait, it doesn't appear that I have those changes.
Don't be confused: the GitHub repo is a read-only replica of the
in-house Subversion repo, which obviously uses different commit/revision
identifiers than git.
$ spamassassin --version
SpamAssassin version 4.0.0-r1900857
That's the last change (in the Subversion repo) to the
Mail::SpamAssassin module.
running on Perl version 5.34.1
I built SA using the following:
$ svn checkout http://svn.apache.org/repos/asf/spamassassin/trunk
Mail-SpamAssassin-4.0.0
This gave me revision 1901294.
Is that not the proper trunk?
That's the correct way to get our trunk.
Right now we are at r1901296, because automated ruleQA/update jobs
generate changes in trunk.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
