https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8214
Bill Cole <billcole@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |FIXED
--- Comment #8 from Bill Cole <billcole@apache.org> ---
(In reply to Jared from comment #6)
[...]
>
> DMARC reports from Google, Amazon, Mail.ru, KDD, Docomo all hit the rule:
> SCC_BODY_URI_ONLY. Prior to Dec 24, this False Positive NEVER occurred in
> these messages. Now it is ubiquitous.
That's a concrete issue that can be addressed.
> I'll zero out the score for SCC_BODY_URI_ONLY
That is one way to address it. It sacrifices an otherwise useful (according to
the automated re-scoring process) correlation to spam.
I have just committed a less drastic approach: adding some direct FP-prevention
to it specifically for avoiding catching DMARC reports. It properly identifies
your sample and many that I have handy (which I had never noticed hitting
SCC_BODY_URI_ONLY because none ever went over threshold.)
The change should be reflected in the active channel Sunday or Monday.
--
You are receiving this mail because:
You are the assignee for the bug.
Bill Cole <billcole@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |FIXED
--- Comment #8 from Bill Cole <billcole@apache.org> ---
(In reply to Jared from comment #6)
[...]
>
> DMARC reports from Google, Amazon, Mail.ru, KDD, Docomo all hit the rule:
> SCC_BODY_URI_ONLY. Prior to Dec 24, this False Positive NEVER occurred in
> these messages. Now it is ubiquitous.
That's a concrete issue that can be addressed.
> I'll zero out the score for SCC_BODY_URI_ONLY
That is one way to address it. It sacrifices an otherwise useful (according to
the automated re-scoring process) correlation to spam.
I have just committed a less drastic approach: adding some direct FP-prevention
to it specifically for avoiding catching DMARC reports. It properly identifies
your sample and many that I have handy (which I had never noticed hitting
SCC_BODY_URI_ONLY because none ever went over threshold.)
The change should be reflected in the active channel Sunday or Monday.
--
You are receiving this mail because:
You are the assignee for the bug.