Re: Last Call: draft-ietf-imapext-sort (INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS) to Proposed Standard
Mark Crispin <mrc@Washington.EDU> Mon, 03 March 2008 18:44 UTC
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id m23IihkW057912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Mar 2008 11:44:43 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id m23IihdX057911; Mon, 3 Mar 2008 11:44:43 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id m23Iif5L057903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-imapext@imc.org>; Mon, 3 Mar 2008 11:44:42 -0700 (MST) (envelope-from mrc@Washington.EDU)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9] (may be forged)) by mxout4.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id m23Iibch012866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 3 Mar 2008 10:44:37 -0800
X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id m23IiZj5032058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 3 Mar 2008 10:44:36 -0800
Date: Mon, 03 Mar 2008 10:44:35 -0800
From: Mark Crispin <mrc@Washington.EDU>
To: Alexey Melnikov <alexey.melnikov@isode.com>
cc: Dave Cridland <dave@cridland.net>, Cyrus Daboo <cyrus@daboo.name>, ietf-imapext@imc.org, IETF Discussion <ietf@ietf.org>, Dan Karp <dkarp@zimbra.com>
Subject: Re: Last Call: draft-ietf-imapext-sort (INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS) to Proposed Standard
In-Reply-To: <47CC25E5.3060906@isode.com>
Message-ID: <alpine.OSX.1.00.0803031029180.18870@pangtzu.panda.com>
References: <308708312.105681204528070348.JavaMail.root@dogfood.zimbra.com> <39C27EE6CA7A1E19A496AFF8@caldav.corp.apple.com> <2684.1204560897.167053@peirce.dave.cridland.net> <47CC25E5.3060906@isode.com>
User-Agent: Alpine 1.00 (OSX 938 2008-02-29)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.3.3.103427
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0'
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>
On Mon, 3 Mar 2008, Alexey Melnikov wrote: >> (In some >> clients, the sorted list is scrolled to whichever message was previously >> selected, so it's a fast way of finding other messages by the same >> person). > Yea, I do this frequently in Thunderbird. As do I. Note that an address sort that collates all "mrc" messages together is more likely to do the right thing that one that collates by name and has to figure out that "Mark Crispin", "Mark R. Crispin", "Crispin, Mark", "M Crispin", "Mr. Mark Crispin", "IMAP Support", etc. are all the same. > I frequently sort by subject, because many clients still don't support proper > threading (threads can become broken due to lack of the References header). I also sort by Subject (although more commonly ORDERSUBJECT threading than direct SUBJECT sorting) in cases where the thread tree has become so complex that it has lost value. A classic example is when a new thread is started by replying to a message in a thread that has little or no relationship to the thread. Think USENET. > I also sort by IMAP flags (i.e. I want to see all important messages), size > and rarely by date. Usually for flags I would do a filter rather than a SORT, but it seems reasonable to me to add such a thing in the first round of extensions. Date sorting seems to be pretty common with our users. Some people who prefer their mail "in order" use it instead of sequence order in the mailbox (no sort) which tends to be an INTERNALDATE sort. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote.
- Re: Use of IMAP SORT in Lemonade Profile Bis Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Use of IMAP SORT in Lemonade Profile Bis Alexey Melnikov
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Alexey Melnikov
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Cyrus Daboo
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Alexey Melnikov
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Alexey Melnikov
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Alexey Melnikov
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Pete Resnick
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dan Karp
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dan Karp
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dan Karp
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Cyrus Daboo
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dan Karp
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Timo Sirainen
- Last Call: draft-ietf-imapext-sort (INTERNET MESS… The IESG
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Arnt Gulbrandsen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Stephane Bortzmeyer
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dave Cridland
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Alexey Melnikov
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dave Cridland
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Cyrus Daboo
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Alexey Melnikov
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Arnt Gulbrandsen
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Mark Crispin
- Re: Last Call: draft-ietf-imapext-sort (INTERNET … Dan Karp