34 lines
1.4 KiB
Plaintext
34 lines
1.4 KiB
Plaintext
MBOX-Line: From johannes at sipsolutions.net Mon Apr 9 13:12:37 2007
|
|
To: imap-protocol@u.washington.edu
|
|
From: Johannes Berg <johannes@sipsolutions.net>
|
|
Date: Fri Jun 8 12:34:39 2018
|
|
Subject: [Imap-protocol] thread computation algorithms and Exchange
|
|
In-Reply-To: <07Apr9.093358pdt."57996"@synergy1.parc.xerox.com>
|
|
References: <07Apr9.093358pdt."57996"@synergy1.parc.xerox.com>
|
|
Message-ID: <1176149558.8459.40.camel@johannes.berg>
|
|
|
|
On Mon, 2007-04-09 at 09:33 -0700, Bill Janssen wrote:
|
|
|
|
> I'm looking at a collection of email mostly sent from Exchange
|
|
> servers, and notice that it by and large does not support the
|
|
> "References" or "In-Reply-To" headers, but does always contain headers
|
|
> called "Thread-Topic" and "Thread-Index". The "Thread-Index" field
|
|
> seems to contain a BASE64 string which contains the "Thread-Index" of
|
|
> its parent message as a prefix.
|
|
>
|
|
> Has anyone tried to understand or reverse-engineer this Exchange
|
|
> information to describe a thread computation algorithm that works
|
|
> better for messages with this information?
|
|
|
|
Look at the evolution source code, it contains quite a bit of
|
|
information on this.
|
|
|
|
johannes
|
|
-------------- next part --------------
|
|
A non-text attachment was scrubbed...
|
|
Name: signature.asc
|
|
Type: application/pgp-signature
|
|
Size: 197 bytes
|
|
Desc: This is a digitally signed message part
|
|
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20070409/1fce591f/attachment.sig>
|