https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6347
Summary: GMX and In-Reply-To / References headers
Product: Spamassassin
Version: 3.2.5
Platform: Other
OS/Version: All
Status: NEW
Severity: minor
Priority: P5
Component: Rules
AssignedTo: [email protected]
ReportedBy: [email protected]
For now, this is mostly documentary so I don't forget to look into this again.
Needs further review and investigation.
(a) I just came across a mail that triggered FAKE_REPLY_C, due to a missing
References header. The message appears to be indeed a reply, composed and sent
via the GMX web-frontend, submitted from a gmx.de user.
This message actually has neither an In-Reply-To nor References header.
Message-ID: <[email protected]>
X-Mailer: WWW-Mail 6100 (Global Message Exchange)
(b) Cross-checked with another previously received message. Also a reply, also
via the web-frontend, also from a gmx.de user (though a different one).
This message *does* have both In-Reply-To and References header.
In-Reply-To: <1259161689.5006.2.ca...@monkey>
Message-ID: <[email protected]>
References: <1259161689.5006.2.ca...@monkey>
X-Mailer: WWW-Mail 6100 (Global Message Exchange)
Kind of puzzling to find that kind of discrepancy. According to
__NO_INR_YES_REF *both* of the above are deemed incorrect. Although only case
(a) is being actively punished.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
