Hello, well I also didn't read the RFCs, but I raised the issue on [EMAIL PROTECTED]:
http://sourceforge.net/mailarchive/message.php?msg_id=38050510 (thread view on sourceforge webpage is not yet available, the answers of my posts are missing, probably takes a while to update) From Bill Yerazunis I got the following explaination: --------------------------------------------------------------------- The reason for hiding the reavercache in two places is because some mail reader programs trash (or at least refuse to forward) any header they don't understand. If that happens to the X-CRM114-CacheID, then there's still a chance that training can happen because the sfid is *also* in the Message-Id. --------------------------------------------------------------------- And Paolo stated: --------------------------------------------------------------------- if such X-* and/or the MSG-ID (comment) breaks threading in such MUAs, it's definitely a bug in those MUA and we need not take extra care - sfid are all strictly RFC-compliants and better let it breaks, MUA-devs get bugrep and hopely fix them. Fix the broken part, don't break the good one. --------------------------------------------------------------------- Bill wants to add an option for disable the behavior of adding a Message-Id only if there is a justification and it really breaks something. JFYI. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
