https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6988
Bug ID: 6988
Summary: __HAS_MIMEOLE triggers FP on legitimate message with
non-Microsoft X-MimeOLE header
Product: Spamassassin
Version: 3.3.2
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Rules
Assignee: [email protected]
Reporter: [email protected]
Created attachment 5177
--> https://issues.apache.org/SpamAssassin/attachment.cgi?id=5177&action=edit
Lightly anonymized header demonstrating the FP
A message reported mistagged as spam hit on TO_NO_BRKTS_MSFT. Digging down
through the meta parts I found overlapping subrules __HAS_MIMEOLE and
__MIMEOLE_MS. __HAS_MIMEOLE will always fire if __MIMEOLE_MS does, but in this
case a third party appears to be legitimately putting their own mailer info in
the X-MimeOLE header.
I suggest removing __HAS_MIMEOLE from __TO_NO_BRKTS_MSFT to narrow the focus to
messages that really were (supposedly) generated by Microsoft mail clients
instead of any mailer that uses an X-MimeOLE header.
--
You are receiving this mail because:
You are the assignee for the bug.
