Re: draft-ietf-imapext-thread
Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Wed, 13 June 2001 08:42 UTC
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.3/8.11.3) id f5D8gni28084 for ietf-imapext-bks; Wed, 13 Jun 2001 01:42:49 -0700 (PDT)
Received: from melkebalanse.troll.no (bluegrass.camelot.de [217.19.165.66]) by above.proper.com (8.11.3/8.11.3) with ESMTP id f5D8gVJ28052 for <ietf-imapext@imc.org>; Wed, 13 Jun 2001 01:42:46 -0700 (PDT)
Received: (from arnt@localhost) by melkebalanse.troll.no (8.9.3/8.8.5) id KAA02686; Wed, 13 Jun 2001 10:48:24 +0200
Date: Wed, 13 Jun 2001 10:48:24 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Ken Murchison <ken@oceana.com>
Cc: Mark Crispin <MRC@cac.washington.edu>, ietf-imapext@imc.org
Subject: Re: draft-ietf-imapext-thread
Message-ID: <20010613104824.C2664@melkebalanse.troll.no>
References: <20010529223543.E26574@melkebalanse.troll.no> <MailManager.991169858.2809.mrc@Tomobiki-Cho.CAC.Washington.EDU> <20010530111859.A26726@melkebalanse.troll.no> <3B26CE21.415319DE@oceana.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <3B26CE21.415319DE@oceana.com>
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>
Ken Murchison <ken@oceana.com> > Arnt Gulbrandsen wrote: > > Actually, subsetting would help with the cases I'm most interested in, > > particularly if the server is permitted to also return answers outside the > > requested set: "Show me all the threads where there's new mail", "show me > > all the messages from mumble@gargle.com, and the threads to which those > > messages belong", "show me all discussion in our department-wide archive > > where the subject included 'fumble'" and so on. > > If I understand what you are looking for here, you want to filter the > messages AFTER they have been threaded. Yes; that's one way of looking at it. > Mark and I have discussed this > in the past, and other algorithms which are derivatives of REFERENCES > are possible. For instance, a REFERENCES.UNSEEN algorithm would return > only those threads which contain at least one \Unseen message (similar > to Netscape's "Threads with Unread"). But isn't that really duplicating the fourth argument in the second? You're suggesting that thread references.unseen utf-8 unseen should return what I think thread references utf-8 unseen should. > To do something like your last two examples, we would have to come up > with a way, either with the (upcoming?) VIEW/WINDOW extension or an > extension to THREAD, to provide generic post-thread filtering. If the server's permitted to return MSNs/UIDs for an entire thread when at least one message in the thread matches the search criteria for that thread command, that should do it. --Arnt
- Re: draft-ietf-imapext-thread Mark Crispin
- Re: draft-ietf-imapext-thread Arnt Gulbrandsen
- re: draft-ietf-imapext-thread Mark Crispin
- draft-ietf-imapext-thread Arnt Gulbrandsen
- Re: draft-ietf-imapext-thread Mark Crispin
- Re: draft-ietf-imapext-thread Arnt Gulbrandsen
- Re: draft-ietf-imapext-thread Cyrus Daboo
- Re: draft-ietf-imapext-thread Arnt Gulbrandsen
- Re: draft-ietf-imapext-thread Ken Murchison
- Re: draft-ietf-imapext-thread Arnt Gulbrandsen
- Re: draft-ietf-imapext-thread Ken Murchison