MBOX-Line: From tss at iki.fi  Wed Dec 20 01:05:04 2006
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:38 2018
Subject: [Imap-protocol] REFERENCES2 threading
In-Reply-To: <15222.1166603835.091995@peirce.dave.cridland.net>
References: <1166586540.22214.282.camel@hurina>
	<15222.1166603835.091995@peirce.dave.cridland.net>
Message-ID: <1166605504.22214.313.camel@hurina>

On Wed, 2006-12-20 at 08:37 +0000, Dave Cridland wrote:
> On Wed Dec 20 03:49:00 2006, Timo Sirainen wrote:
> > There are two annoying things with the standard REFERENCES 
> > threading:
> > 
> > 1. I think base subject merging is nowadays more annoying than it is
> > helpful. Pretty much all the clients generate References headers
> > properly.
> > 
> > 2. Root nodes should be sorted by the newest message in the thread, 
> > not
> > by the root node's date. The new messages should be easily found, 
> > not
> > lost somewhere among old messages.
> > 
> > I've now implemented these as X-REFERENCES2 to Dovecot. Is anyone 
> > else
> > interested in getting this standardized?
> > 
> > 
> I think what you're describing is close to the REFS algorithm found 
> in Arnt Gulbrandsen's INTHREAD draft (which, I might add, would be 
> very useful to me as a client developer).

Ah. That looks like a nice extension. I guess I could comment it as well
in here:

    Open Issue 1: Should THREAD=REFS use In-Reply-To if there is no
    References?

Yes. I don't see what's the benefit of not doing it. I think the
algorithm should be kept as close to REFERENCES as possible. My
X-REFERENCES2 required pretty minimal code changes.

Also it drops Date header. How is it going to sort the messages then? By
the UID? Maybe sorting with UIDs would be OK too. Or as a user I think
I'd like sorting with INTERNALDATEs the most, but as an implementor I'd
rather not do that..
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20061220/1a31f776/attachment.sig>
