[Bug 4144] FORGED_IMS_HTML and FORGED_IMS_TAGS false-positive.

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=4144


Bob@Menschel.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|Undefined                   |3.1.1




------- Additional Comments From Bob@Menschel.net  2005-04-28 23:08 -------
Ran the attached email against 3.0.3 and 3.1 svn.  Results: 
X-Spam-Status: No, score=0.5 required=5.0 tests=ALL_TRUSTED,AWL,
  FORGED_IMS_TAGS,HTML_60_70,HTML_MESSAGE autolearn=ham version=3.0.3

So FORGED_IMS_HTML is fixed. FORGED_IMS_TAGS remains.

debug: tests=ALL_TRUSTED,AWL,FORGED_IMS_TAGS,HTML_60_70,HTML_MESSAGE
debug: subtests=__ANY_IMS_MUA, __COMMENT_EXISTS, __CT, __CTYPE_HAS_BOUNDARY,
__CTYPE_MULTIPART_ALT, __HAS_MIMEOLE, __HAS_MSGID, __HAS_SUBJECT,
__HAS_X_MAILER, __IMS_MSGID, __IMS_MUA, __JS_DOCWRITE, __MIME_HTML, __MIME_QP,
__MIME_VERSION, __MSGID_OK_DIGITS, __NEXTPART_ALL, __NEXTPART_NORMAL,
__SANE_MSGID, __TAG_EXISTS_BODY, __TAG_EXISTS_HTML, __UNUSABLE_MSGID

By the definition of FORGED_IMS_TAGS, this email is flagged such because
__TAG_EXISTS_HEAD and __TAG_EXISTS_META didn't fire. 

X-Mailer: Internet Mail Service (5.5.2655.55)

The question then becomes, can this version of IMS really generate such emails? 

Given that FORGED_IMS_HTML and this email therefore falls well under the spam
threshold, I don't see any need to fix this in crisis mode before 3.1.0. So I'm
setting a provisional target threshold of 3.1.1. 



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.