SA Bugzilla – Bug 6347
GMX and In-Reply-To / References headers
Last modified: 2010-02-24 19:29:42 UTC
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: <20100224181659.42210@gmx.net> 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.camel@monkey> Message-ID: <20091125205041.12850@gmx.net> References: <1259161689.5006.2.camel@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.