SpamAssassin version 3.3.0 has not had a rule update since 2017-06-24.
SpamAssassin version 3.3.1 has not had a rule update since 2017-06-24.
SpamAssassin version 3.3.2 has not had a rule update since 2017-06-24.
20170805: Spam and ham are above threshold of 150,000:
http://ruleqa.spamassassin.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7446
--- Comment #9 from Karsten Bräckelmann ---
*** Bug 7440 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7440
Karsten Bräckelmann changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7446
Karsten Bräckelmann changed:
What|Removed |Added
Summary|DKIM-Signature increases|DKIM-Signature increases
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7446
--- Comment #11 from Karsten Bräckelmann ---
(In reply to documentation quote from comment #10)
> alongside URIs found in the body with some rules and moduels", see
> M::SA::Conf.
Typo in the documentation fixed: revision 1804259 trunk and
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7304
--- Comment #1 from Karsten Bräckelmann ---
Thanks Hanno for the report. However, I believe the described issue to not be a
problem.
First of all, the memcmp function does not "read all bytes of both variables",
but compares the source stri