43 lines
2.0 KiB
Plaintext
43 lines
2.0 KiB
Plaintext
MBOX-Line: From janssen at parc.com Mon Apr 9 10:41:26 2007
|
|
To: imap-protocol@u.washington.edu
|
|
From: Bill Janssen <janssen@parc.com>
|
|
Date: Fri Jun 8 12:34:39 2018
|
|
Subject: [Imap-protocol] thread computation algorithms and Exchange
|
|
In-Reply-To: <alpine.OSX.0.98.0704091015270.11423@pangtzu.panda.com>
|
|
References: <07Apr9.093358pdt."57996"@synergy1.parc.xerox.com>
|
|
<alpine.OSX.0.98.0704090939120.11423@pangtzu.panda.com>
|
|
<07Apr9.101403pdt."57996"@synergy1.parc.xerox.com>
|
|
<alpine.OSX.0.98.0704091015270.11423@pangtzu.panda.com>
|
|
Message-ID: <07Apr9.104129pdt."57996"@synergy1.parc.xerox.com>
|
|
|
|
> On Mon, 9 Apr 2007, Bill Janssen wrote:
|
|
> >> I strongly urge you to focus on standards, and disregard
|
|
> >> non-standards.
|
|
> > Ah, but identifying what's really a standard is the hard part. :-)
|
|
>
|
|
> Actually, it is not difficult at all within the Internet context.
|
|
|
|
Yeah, but... The (expired?) document at
|
|
http://tools.ietf.org/html/draft-ietf-imapext-sort-19 is attempting to
|
|
standardize two hacks that let possessors of a quantity of mail
|
|
organize it into threads that a human may recognize. While both of
|
|
these hacks are reasonable given the kinds of information usually
|
|
found in email headers in non-corporate environments, they are also
|
|
unreasonably fragile to the extent they are based on comparison of
|
|
"Subject" header strings, which are typically presented in an MUA in
|
|
an edit window for the responder to mung at will.
|
|
|
|
However, in many email messages, there is additional machine-injected
|
|
information, not exposed to the whim of the human user, which may aid
|
|
in the determination of threads which actually make sense to the human
|
|
user. In particular, it may be possible to exploit this information
|
|
in order to correct for some of the fragility introduced by comparing
|
|
the "Subject" header. It doesn't seem out of the question for someone
|
|
to try to standardize a third or fourth or fifth hack based on this
|
|
information to add to the THREAD extension. Given that vast amounts
|
|
of corporate email may include these headers, might be worth looking
|
|
into.
|
|
|
|
Bill
|
|
|