Vince Littler <suse@archipelago.eclipse.co.uk> writes:
On Wednesday 23 April 2003 8:59 pm, James Mohr wrote:
Similarly with threading. If there was a _published_ standard [with broad agreement and enough wrinkles ironed out to be broadly beneficial], I would want a client to support that standard. I would want SuSE to provide clients which complied [presuming on the broadness of SuSE's shoulders!]
There *is* a published standard - RFC2822. The following extract expands When creating a reply to a message, the "In-Reply-To:" and "References:" fields of the resultant message are constructed as follows: The "In-Reply-To:" field will contain the contents of the "Message- ID:" field of the message to which this one is a reply (the "parent message"). If there is more than one parent message, then the "In- Reply-To:" field will contain the contents of all of the parents' "Message-ID:" fields. If there is no "Message-ID:" field in any of the parent messages, then the new message will have no "In-Reply-To:" field. The "References:" field will contain the contents of the parent's "References:" field (if any) followed by the contents of the parent's "Message-ID:" field (if any). If the parent message does not contain a "References:" field but does have an "In-Reply-To:" field containing a single message identifier, then the "References:" field will contain the contents of the parent's "In-Reply-To:" field followed by the contents of the parent's "Message-ID:" field (if any). If the parent has none of the "References:", "In-Reply-To:", or "Message-ID:" fields, then the new message will have no "References:" field.