From morg-bounces@ietf.org  Sat Oct 18 14:59:40 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D48563A68A4;
	Sat, 18 Oct 2008 14:59:40 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5168E3A68A4
	for <morg@core3.amsl.com>; Sat, 18 Oct 2008 14:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.387
X-Spam-Level: 
X-Spam-Status: No, score=-2.387 tagged_above=-999 required=5 tests=[AWL=0.212, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 91-Ks8AAnpmJ for <morg@core3.amsl.com>;
	Sat, 18 Oct 2008 14:59:38 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 4FB393A67E2
	for <morg@ietf.org>; Sat, 18 Oct 2008 14:59:38 -0700 (PDT)
Received: from [92.40.179.137] (92.40.179.137.sub.mbb.three.co.uk
	[92.40.179.137]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SPpciQBpDCEW@rufus.isode.com>; Sat, 18 Oct 2008 23:00:43 +0100
Message-ID: <48FA5C7E.4070008@isode.com>
Date: Sat, 18 Oct 2008 23:00:30 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
	Gecko/20050915
X-Accept-Language: en-us, en
To: morg@ietf.org
MIME-Version: 1.0
Subject: [MORG] Initial set of documents to work on
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Hi,
 From the BOF in Dublin and discussions I had with various people after 
that it seems there is a desire to form a WG. In order to get the 
process started I would like to first discuss documents that would be 
worked on first. Speaking as an individual, I would like to propose the 
following set of documents (to be worked on in the specified order)

1). draft-karp-morg-sortdisplay-00.txt
2). draft-melnikov-imapext-status-in-list-00.txt and possibly status 
counts per message context (Peter Coates has a draft)
3). New collations - space ignore, numeric ignoring punctuation, etc. (me)
4). Sorting by relevancy (Timo)
5). draft-gulbrandsen-imap-inthread-02.txt
6). draft-melnikov-imapext-multimailbox-search-03.txt

Comments?

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue Oct 21 03:47:17 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3FD253A6B4E;
	Tue, 21 Oct 2008 03:47:17 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C3EFB3A6B4F
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 03:47:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6fiGR0ycJCPZ for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 03:47:15 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id C2C4A3A6B4E
	for <morg@ietf.org>; Tue, 21 Oct 2008 03:47:14 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id 331C54AC9D;
	Tue, 21 Oct 2008 12:48:20 +0200 (CEST)
Received: from arnt@oryx.com (client address 195.30.37.40) (HELO
	lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with
	esmtp id 1224586099-66249-6781 for morg@ietf.org; Tue, 21 Oct 2008
	12:48:19 +0200
Message-Id: <yoDKeqV08PWDxmQGeuslQw.md5@lochnagar.oryx.com>
Date: Tue, 21 Oct 2008 12:46:55 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: morg@ietf.org
References: <48FA5C7E.4070008@isode.com>
In-Reply-To: <48FA5C7E.4070008@isode.com>
Mime-Version: 1.0
Subject: Re: [MORG] Initial set of documents to work on
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Excuse my late reply; it was difficult to find something to say.

Alexey Melnikov writes:
> Hi,
> From the BOF in Dublin and discussions I had with various people after 
> that it seems there is a desire to form a WG. In order to get the 
> process started I would like to first discuss documents that would be 
> worked on first. Speaking as an individual, I would like to propose 
> the following set of documents (to be worked on in the specified 
> order)

And the only thing I can say is that I don't understand the list.

This list ought to be a set of tools to reach some vision, right? But I 
don't understand how these documents combine to work towards something, 
and what vision that something is.

My lack of understanding may be because I wasn't in Dublin. (I couldn't 
even join via jabber, I was blocked except at that exact time.) Still, 
some background for the list would help me to understand.

> 1). draft-karp-morg-sortdisplay-00.txt
> 2). draft-melnikov-imapext-status-in-list-00.txt and possibly status 
> counts per message context (Peter Coates has a draft)
> 3). New collations - space ignore, numeric ignoring punctuation, etc. (me)
> 4). Sorting by relevancy (Timo)
> 5). draft-gulbrandsen-imap-inthread-02.txt
> 6). draft-melnikov-imapext-multimailbox-search-03.txt

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue Oct 21 03:58:23 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 913373A6A5D;
	Tue, 21 Oct 2008 03:58:23 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D1B683A6901
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 03:58:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level: 
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[AWL=0.031, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yWkEi1z8+XeO for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 03:58:21 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id E53943A68D6
	for <morg@ietf.org>; Tue, 21 Oct 2008 03:58:20 -0700 (PDT)
Received: from [192.168.0.2] ((unknown) [62.3.217.253]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SP22FgBpDEyM@rufus.isode.com>; Tue, 21 Oct 2008 11:59:34 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <48FDB610.7000701@isode.com>
Date: Tue, 21 Oct 2008 11:59:28 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
	Gecko/20050915
X-Accept-Language: en-us, en
To: Arnt Gulbrandsen <arnt@oryx.com>
References: <48FA5C7E.4070008@isode.com>
	<yoDKeqV08PWDxmQGeuslQw.md5@lochnagar.oryx.com>
In-Reply-To: <yoDKeqV08PWDxmQGeuslQw.md5@lochnagar.oryx.com>
MIME-Version: 1.0
Cc: morg@ietf.org
Subject: Re: [MORG] Initial set of documents to work on
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Arnt Gulbrandsen wrote:

> Excuse my late reply; it was difficult to find something to say.
>
> Alexey Melnikov writes:
>
>> Hi,
>> From the BOF in Dublin and discussions I had with various people 
>> after that it seems there is a desire to form a WG. In order to get 
>> the process started I would like to first discuss documents that 
>> would be worked on first. Speaking as an individual, I would like to 
>> propose the following set of documents (to be worked on in the 
>> specified order)
>
> And the only thing I can say is that I don't understand the list.
>
> This list ought to be a set of tools to reach some vision, right? But 
> I don't understand how these documents combine to work towards 
> something, and what vision that something is.
>
> My lack of understanding may be because I wasn't in Dublin. (I 
> couldn't even join via jabber, I was blocked except at that exact 
> time.) Still, some background for the list would help me to understand.

 From my slides for the MORG BOF in Dublin:

Goals:
improve ability to find messages in an IMAP mailstore
1) Don't make things worse while doing that (think about extension 
interaction)
2) Should work for diverse clients
3) Mobile devices, web clients, desktop clients

And this is the updated list of drafts for the original charter I 
proposed <http://www.ietf.org/mail-archive/web/morg/current/msg00024.html>

Does this help?

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue Oct 21 04:50:20 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1AAF63A6B3C;
	Tue, 21 Oct 2008 04:50:20 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F71A3A6B0B
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 04:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wIUr+DucONjp for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 04:50:17 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 0B4DC3A691F
	for <morg@ietf.org>; Tue, 21 Oct 2008 04:50:16 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id 04C0D4AC93;
	Tue, 21 Oct 2008 13:51:16 +0200 (CEST)
Received: from arnt@oryx.com (client address 195.30.37.40) (HELO
	lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with
	esmtp id 1224589876-66249-6828 for morg@ietf.org; Tue, 21 Oct 2008
	13:51:16 +0200
Message-Id: <k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
Date: Tue, 21 Oct 2008 13:49:52 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: morg@ietf.org
References: <48FA5C7E.4070008@isode.com>
In-Reply-To: <48FA5C7E.4070008@isode.com>
Mime-Version: 1.0
Subject: Re: [MORG] Initial set of documents to work on
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

In view of Alexey's response just now.

Alexey Melnikov wrote, weeks ago:
> 1). draft-karp-morg-sortdisplay-00.txt

A fine draft and I'll commit to implementing it if Dan gets it to RFC, 
but it's not clear to me how it improves the ability to find messages.

> 2). draft-melnikov-imapext-status-in-list-00.txt and possibly status 
> counts per message context (Peter Coates has a draft)

Again, not clear to me, etc.

> 3). New collations - space ignore, numeric ignoring punctuation, etc. (me)

Ditto.

> 4). Sorting by relevancy (Timo)

This is about returning an ordered list of search responses, rather than 
an unordered set? That sounds like a good idea.

> 5). draft-gulbrandsen-imap-inthread-02.txt

Hm, I have updated that, but not published, and it expired. Expect a revision.

I think this helps, in so far as it provides tools to perform some 
really common searches.

> 6). draft-melnikov-imapext-multimailbox-search-03.txt

Multimailbox search is obviously a great help with finding things. Of 
course it interacts with 4) above. Solvable.

Overall, I'd say that 4-6 could solve two of the four big findability 
problems. The other two are:

1. Searching for messages whose address fields contain a specific 
address or domain.

2. Searching for messages by word instead of substring. Substring 
serches are easy to implement, but IMO fairly useless. Prefix searches 
would be better, word searches even better, and IMO perfection would be 
word searches where the server may stem.

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue Oct 21 07:12:05 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4FEBD3A6950;
	Tue, 21 Oct 2008 07:12:05 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D67F28C101
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 07:12:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zi5tL6zyRdTv for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 07:12:03 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 4F3163A697A
	for <morg@ietf.org>; Tue, 21 Oct 2008 07:12:03 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id 8379C4AC94;
	Tue, 21 Oct 2008 16:12:51 +0200 (CEST)
Received: from arnt@oryx.com (client address 195.30.37.40) (HELO
	lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with
	esmtp id 1224598371-66249-6891 for morg@ietf.org; Tue, 21 Oct 2008
	16:12:51 +0200
Message-Id: <ucHgGpllrvbukbaHRlZCxA.md5@lochnagar.oryx.com>
Date: Tue, 21 Oct 2008 16:11:26 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: morg@ietf.org
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<1210667945.9518.576.camel@hurina>
In-Reply-To: <1210667945.9518.576.camel@hurina>
Mime-Version: 1.0
Subject: Re: [MORG] SEARCH=INTHREAD
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Timo Sirainen writes:
> I can think of a couple of use cases for THREADROOT, but is THREADLEAF 
> actually useful for something?

I included it because Dave argued that it was a natural part of the 
parcel, which I think is a desirable property and sufficient 
justification as long as it's easy to implement.

Later I've found an example use case: Suppose you want to make sure 
threads aren't forgotten. So you do "THREADLEAF NOT FROM <me> UNKEYWORD 
considered" to find all unconsidered leaf messages, and for each of 
result, you either answer it or do "STORE +FLAGS considered".

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue Oct 21 07:12:35 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6715E3A6A60;
	Tue, 21 Oct 2008 07:12:35 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4BA373A6916
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 07:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id a8MZbccmoOcN for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 07:12:33 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 46CCA3A67C0
	for <morg@ietf.org>; Tue, 21 Oct 2008 07:12:33 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id B44D14AC93;
	Tue, 21 Oct 2008 16:13:08 +0200 (CEST)
Received: from arnt@oryx.com (client address 195.30.37.40) (HELO
	lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with
	esmtp id 1224598388-66249-6893 for morg@ietf.org; Tue, 21 Oct 2008
	16:13:08 +0200
Message-Id: <s6hNnW4ewirvc/EtY1kpTg.md5@lochnagar.oryx.com>
Date: Tue, 21 Oct 2008 16:11:44 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: morg@ietf.org
References: <1213930530.3904.1577.camel@hurina>
In-Reply-To: <1213930530.3904.1577.camel@hurina>
Mime-Version: 1.0
Subject: Re: [MORG] SEARCH=INTHREAD algorithm selection
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Timo Sirainen writes:
> Ability to specify multiple different thread algorithms for the same 
> search command seems quite pointless and makes its implementation 
> unnecessarily complex. I'd like to avoid doing nested INTHREAD 
> searches, which is possible but only as long as the same algorithm is 
> used everywhere.
>
> How about specifying the algorithm in SEARCH RETURN options?
>
> SEARCH RETURN (THREAD (REFERENCES)) INTHREAD SUBJECT "hello"

Done.

I don't particularly care one way or another. This change doesn't seem 
to affect either benevolent or malevolent users. Malevolent users can 
construct DoSish CPU eaters either way.

> This also fixes the issue of THREADROOT and THREADLEAF not specifying 
> the algorithm currently.

Also fixes the issue of THREADROOT and THREADLEAF having rotten 
definitions. I like that.

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue Oct 21 07:54:25 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 02CF53A6B4F;
	Tue, 21 Oct 2008 07:54:25 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 206743A6B3D
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 07:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cOjV5Pg1N9kM for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 07:54:23 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 17FFE3A6B3C
	for <morg@ietf.org>; Tue, 21 Oct 2008 07:54:23 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id 526C34AC7E;
	Tue, 21 Oct 2008 16:55:01 +0200 (CEST)
Received: from arnt@oryx.com (client address 195.30.37.40) (HELO
	lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with
	esmtp id 1224600900-66249-6917 for morg@ietf.org; Tue, 21 Oct 2008
	16:55:00 +0200
Message-Id: <0NRE1do4ijzB1cUSjb8gLQ.md5@lochnagar.oryx.com>
Date: Tue, 21 Oct 2008 16:53:36 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: Messaging Organization <morg@ietf.org>
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<1210667945.9518.576.camel@hurina>
	<ucHgGpllrvbukbaHRlZCxA.md5@lochnagar.oryx.com>
	<10893.1224600585.247428@peirce.dave.cridland.net>
In-Reply-To: <10893.1224600585.247428@peirce.dave.cridland.net>
Mime-Version: 1.0
Subject: Re: [MORG] SEARCH=INTHREAD
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Dave Cridland writes:
> On Tue Oct 21 15:11:26 2008, Arnt Gulbrandsen wrote:
>> Timo Sirainen writes:
>>> I can think of a couple of use cases for THREADROOT, but is  
>>> THREADLEAF actually useful for something?
>>
>> I included it because Dave argued that it was a natural part of the  
>> parcel, which I think is a desirable property and sufficient  
>> justification as long as it's easy to implement.
>
> My thought was that if you find THREADROOTs, then logically you must  
> be able to find THREADLEAFs. This might be bogus thinking, of course.

I think it was good thinking, because it naturally led to support a use 
case we weren't aware of at the time.

>> Later I've found an example use case: Suppose you want to make sure  
>> threads aren't forgotten. So you do "THREADLEAF NOT FROM <me>  
>> UNKEYWORD considered" to find all unconsidered leaf messages, and  
>> for each of result, you either answer it or do "STORE +FLAGS  
>> considered".
>
> Oh, indeed, although I think you mean:
>
> THREADLEAF NOT FROM <me> UNKEYWORD considered UNANSWERED

No... if I reply the message will stop being a leaf, but it won't 
necessarily acquire an \answered flag.

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue Oct 21 08:04:33 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2868B3A6B3E;
	Tue, 21 Oct 2008 08:04:33 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 65C3F3A6832
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 08:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.613
X-Spam-Level: 
X-Spam-Status: No, score=-1.613 tagged_above=-999 required=5 tests=[AWL=0.986, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Vcyo3C-+ThPB for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 08:04:30 -0700 (PDT)
Received: from turner.dave.cridland.net (turner.dave.cridland.net
	[217.155.137.60])
	by core3.amsl.com (Postfix) with ESMTP id 0FD813A6836
	for <morg@ietf.org>; Tue, 21 Oct 2008 08:04:30 -0700 (PDT)
Received: from peirce.dave.cridland.net ([217.155.137.61]) by
	turner.dave.cridland.net (submission)
	via TCP with ESMTPA id <SP3sCQAS0ayv@turner.dave.cridland.net>;
	Tue, 21 Oct 2008 15:49:46 +0100
References: <1210654151.9518.539.camel@hurina>
	<M36GB7SjVS/ecjHThF/mug.md5@lochnagar.oryx.com>
	<1210667945.9518.576.camel@hurina>
	<ucHgGpllrvbukbaHRlZCxA.md5@lochnagar.oryx.com>
In-Reply-To: <ucHgGpllrvbukbaHRlZCxA.md5@lochnagar.oryx.com>
MIME-Version: 1.0
Message-Id: <10893.1224600585.247428@peirce.dave.cridland.net>
Date: Tue, 21 Oct 2008 15:49:45 +0100
From: Dave Cridland <dave@cridland.net>
To: Arnt Gulbrandsen <arnt@oryx.com>
Cc: Messaging Organization <morg@ietf.org>
Subject: Re: [MORG] SEARCH=INTHREAD
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

On Tue Oct 21 15:11:26 2008, Arnt Gulbrandsen wrote:
> Timo Sirainen writes:
>> I can think of a couple of use cases for THREADROOT, but is  
>> THREADLEAF actually useful for something?
> 
> I included it because Dave argued that it was a natural part of the  
> parcel, which I think is a desirable property and sufficient  
> justification as long as it's easy to implement.
> 
> 
My thought was that if you find THREADROOTs, then logically you must  
be able to find THREADLEAFs. This might be bogus thinking, of course.


> Later I've found an example use case: Suppose you want to make sure  
> threads aren't forgotten. So you do "THREADLEAF NOT FROM <me>  
> UNKEYWORD considered" to find all unconsidered leaf messages, and  
> for each of result, you either answer it or do "STORE +FLAGS  
> considered".

Oh, indeed, although I think you mean:

THREADLEAF NOT FROM <me> UNKEYWORD considered UNANSWERED

You might do the reverse, too:

THREADLEAF FROM <me> TO <minion> UNKEYWORD done

might find all requests to your minion that your minion hadn't yet  
done.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue Oct 21 08:05:34 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 47FCF3A6B44;
	Tue, 21 Oct 2008 08:05:34 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0DF63A6B2F;
	Tue, 21 Oct 2008 08:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_64=0.6,
	UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id na5Z23S3h4j0; Tue, 21 Oct 2008 08:05:31 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 0AC863A6832;
	Tue, 21 Oct 2008 08:05:08 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id 51E694AC93;
	Tue, 21 Oct 2008 17:05:45 +0200 (CEST)
Received: from arnt@oryx.com (client address 195.30.37.40) (HELO
	lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with
	esmtp id 1224601544-66249-6936 (2 recipients); Tue, 21 Oct 2008
	17:05:44 +0200
Message-Id: <tXY1DReqGl1L2yjepIvdig.md5@lochnagar.oryx.com>
Date: Tue, 21 Oct 2008 17:04:20 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: internet-drafts@ietf.org
References: <48FA5C7E.4070008@isode.com>
	<k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
In-Reply-To: <k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
Content-Type: multipart/mixed; boundary=-
Mime-Version: 1.0
Cc: morg@ietf.org
Subject: [MORG] draft-gulbrandsen-imap-inthread
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

---
Content-Type: text/plain; format=flowed

Hi,

please post the appended internet-draft update.

The automatic upload tool has failed for me in the past hour or so; the 
upload suffers from Spinning Cursor Syndrome. I'll leave the web 
browser until it gives up, though. It seems to be remarkably patient.

Arnt

---
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Content-Disposition: attachment; size=13446;
 filename=draft-gulbrandsen-imap-inthread-03.txt

Network Working Group                                   Arnt Gulbrandsen
Internet-Draft                                    Oryx Mail Systems GmbH
Intended Status: Proposed Standard                         November 2008


          The IMAP SEARCH=3DINTHREAD and THREAD=3DREFS Extensions
                 draft-gulbrandsen-imap-inthread-03.txt


Status of this Memo

    By submitting this Internet-Draft, each author represents that any
    applicable patent or other IPR claims of which he or she is aware
    have been or will be disclosed, and any of which he or she becomes
    aware will be disclosed, in accordance with Section 6 of BCP 79.

    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet-
    Drafts.

    Internet-Drafts are draft documents valid for a maximum of six
    months and may be updated, replaced, or obsoleted by other documents
    at any time.  It is inappropriate to use Internet-Drafts as
    reference material or to cite them other than as "work in progress."

    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-
    Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.

    This Internet-Draft expires in April 2009.


Copyright Notice

    Copyright (C) The IETF Trust (2008).


Abstract

    The SEARCH=3DINTHREAD extension extends the IMAP SEARCH command to
    operate on threads as well as individual messages. Other commands
    which search are implicitly extended.

    The THREAD=3DREFS extension provides a threading algorithm using
    (almost) only the References header field for use with the IMAP
    THREAD command.



Gulbrandsen                Expires April 2009                   [Page 1]
=0C
Internet-draft                                              October 2008


1.  Conventions Used in This Document

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
    document are to be interpreted as described in [RFC2119].

    Formal syntax is defined by [RFC5234].

    Example lines prefaced by "C:" are sent by the client and ones
    prefaced by "S:" by the server. The five characters [...] means that
    something has been elided.


2.  Overview

    This document defines two related extensions.

    The THREAD=3DREFS extension defined a fairly pure References-based
    (see [RFC5322] section 3.6.4) threading algorithm for use with the
    THREAD command (see [RFC5256]) and with SEARCH=3DINTHREAD.

    An IMAP server (see [RFC3501]) that supports the THREAD=3DREFS
    extension MUST announce THREAD=3DREFS as capabilities. This extension
    adds no new commands and responses, only a new thread algorithm.

    The SEARCH=3DINTHREAD extension extends the IMAP SEARCH command to
    operate on threads as well as individual messages. Other commands
    which search are implicitly extended. SEARCH=3DINTHREAD requires that
    servers implement THREAD=3DREFS too.

    An IMAP server that supports SEARCH=3DINTHREAD MUST announce both
    SEARCH=3DINTHREAD and THREAD=3DREFS as capabilities. This extension =
adds
    no new commands and responses, but adds four new search-keys,
    INTHREAD, THREADROOT, THREADLEAF and MESSAGEID, and least one search
    return option, THREAD=3DREFS.


3.  New Search Keys

    This document defines three new search keys which operate on
    threads: One to find all messages in a thread where at least one
    message matches another search key, one to find the roots of threads
    and one to find the leaves. It also defines a helper which matches a
    message given its message-id.







Gulbrandsen                Expires April 2009                   [Page 2]
=0C
Internet-draft                                              October 2008


3.1. The INTHREAD Search Key

    INTHREAD takes one argument, which is another search key.

    The INTHREAD search-key matches a message if its subsidiary search-
    key matches at least one message in the same thread as the message.

    This command finds all messages in an entire thread concerning the
    meetings where fizzle was discussed:

         C: a UID SEARCH INTHREAD (SUBJECT meeting BODY fizzle)

    This command threads all threads containing at least one message
    from fred@example.com:

         C: a UID THREAD REFS utf-8 INTHREAD FROM <fred@example.com>


3.2. The THREADROOT Search Key

    The THREADROOT search key matches a message if that message does not
    have any extant parent according to the active threading algorithm
    (see section 3.5).

    This command finds the roots of all threads containing unread
    messages:

         C: a UID SEARCH THREADROOT INTHREAD UNSEEN


3.3. The THREADLEAF Search Key

    The THREADLEAF search key matches a message if that message has no
    extant children in the same mailbox, according to the active
    threading algorithm.

    Note that THEADLEAF interacts badly with THREAD=3DORDEREDSUBJECT.
    THREAD=3DORDEREDSUBJECT is defined such that every message is either =
a
    root or a leaf, there are no intermediate nodes.

    This command finds all messages that were (also) sent to me, and to
    which noone has answered:

         C: a UID SEARCH THREADLEAF OR TO <me@example.com> CC
            <me@example.com>






Gulbrandsen                Expires April 2009                   [Page 3]
=0C
Internet-draft                                              October 2008


3.4. The MESSAGEID Search Key

    The MESSAGEID search key takes a sigle argument, and matches a
    message if that message's normalized nessage-id is the same as the
    argument.

    This command finds all in the same thread as
    <4321.1234321@example.com>:

         C: a UID SEARCH INTHREAD MESSAGEID <4321.1234321@example.com>


3.5. The THREAD=3D* Search Return Option(s)

    The THREAD=3D* search return options enables the client to select
    which threading algorithm the server uses when processing INTHREAD,
    THREADROOT and THREADLEAF as part of a SEARCH command. If THREAD=3D*
    isn't specified, then the default for the SEARCH command is
    THREAD=3DREFS.

    When the server processes a THREAD command, it uses the algorithm
    specified by the client.

    This command sorts the messages by subject and returns the first
    message with each subject, disregarding "fwd", "re" and other
    paraphernalia:

         C: a UID SEARCH RETURN (THREAD=3DORDEREDSUBJECT) THREADROOT


4.  The THREAD=3DREFS Thread Algorithm

    The THREAD=3DREFS thread algorithm is defined as the part of
    THREAD=3DREFERENCES (see [RFC5256]) which concerns itself with the
    References, In-Reply-To, Message-ID and Date fields.  THREAD=3DREFS
    ignores Subject.

    This document defines THREAD=3DREFS because THREAD=3DREFERENCES is =
too
    inclusive for the INTHREAD search key. For example, independent
    threads that happen to have use same subject field (such as "Agenda
    for Friday's meeting", "Web site updated" or "Message delivery
    failed") are grouped into one thread by THREAD=3DREFERENCES.

    It is explicitly permitted for the server to persistently store
    threading information, even if this causes the server to return
    different information than it would otherwise. This can happen if
    the first messages in a thread are deleted, for example.




Gulbrandsen                Expires April 2009                   [Page 4]
=0C
Internet-draft                                              October 2008


5.  Formal Syntax

    The following syntax specification uses the Augmented Backus-Naur
    Form (ABNF) notation as specified in [RFC5234]. [RFC3501] defines
    the non-terminals "capability" and "search-key", [RFC4466] defines
    "search-return-opt", [RFC5256] defines "thread-alg", and [RFC5322]
    defines "id-left" and "id-right".

    Except as noted otherwise, all alphabetic characters are case-
    insensitive.  The use of upper or lower case characters to define
    token strings is for editorial clarity only.  Implementations MUST
    accept these strings in a case-insensitive fashion.

        capability   =3D/ "SEARCH=3DINTHREAD" / "THREAD=3DREFS"

        search-key   =3D/ "INTHREAD" SP search-key / "MESSAGEID" SP "<"
                        id-left "@" id-right ">" / "THREADROOT" /
                        "THREADLEAF"

        thread-alg   =3D/ "REFS"

        search-return-opt =3D/ "THREAD=3D" thread-alg


6.  Security Considerations

    This document is believed not to have any security implications.


7.  IANA Considerations

    The IANA is requested to add SEARCH=3DINTHREAD and THREAD=3DREFS to =
the
    list of IMAP extensions,
    http://www.iana.org/assignments/imap4-capabilities.


8.  Acknowledgements

    The name THREAD=3DREFS was suggested by Cyrus Daboo. Dave Cridland,
    Alexey Menikov and particularly Timo Sirainen have helped with the
    document.


9. Normative References

    [RFC2119]  Bradner, "Key words for use in RFCs to Indicate
               Requirement Levels", RFC 2119, Harvard University, March
               1997.



Gulbrandsen                Expires April 2009                   [Page 5]
=0C
Internet-draft                                              October 2008


    [RFC3501]  Crispin, "Internet Message Access Protocol - Version
               4rev1", RFC 3501, University of Washington, June 2003.

    [RFC4466]  Melnikov, Daboo, "Collected Extensions to IMAP4 ABNF",
               RFC 4466, Isode Ltd., April 2006.

    [RFC5234]   Crocker, D. and P. Overell, "Augmented BNF for Syntax
               Specifications: ABNF", RFC 5234, January 2008.

    [RFC5256]  Crispin, Murchison, "INTERNET MESSAGE ACCESS PROTOCOL -
               SORT AND THREAD EXTENSIONS", RFC 5256, Panda Programming,
               June 2008.

    [RFC5322]  Resnick, "Internet Message Format", RFC 5322, Qualcomm,
               October 2008.


10. Author's Address

    Arnt Gulbrandsen
    Oryx Mail Systems GmbH
    Schweppermannstr. 8
    D-81671 Muenchen
    Germany

    Fax: +49 89 4502 9758

    Email: arnt@oryx.com


Intellectual Property Statement

    The IETF takes no position regarding the validity or scope of any
    Intellectual Property Rights or other rights that might be claimed
    to pertain to the implementation or use of the technology described
    in this document or the extent to which any license under such
    rights might or might not be available; nor does it represent that
    it has made any independent effort to identify any such rights.
    Information on the procedures with respect to rights in RFC
    documents can be found in BCP 78 and BCP 79.

    Copies of IPR disclosures made to the IETF Secretariat and any
    assurances of licenses to be made available, or the result of an
    attempt made to obtain a general license or permission for the use
    of such proprietary rights by implementers or users of this
    specification can be obtained from the IETF on-line IPR repository
    at http://www.ietf.org/ipr.




Gulbrandsen                Expires April 2009                   [Page 6]
=0C
Internet-draft                                              October 2008


    The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at ietf-
    ipr@ietf.org.


Full Copyright Statement

    Copyright (C) The IETF Trust (2008).  This document is subject to
    the rights, licenses and restrictions contained in BCP 78, and
    except as set forth therein, the authors retain all their rights.

    This document and the information contained herein are provided on
    an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
    REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
    IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
    WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
    WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
    ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
    FOR A PARTICULAR PURPOSE.


Acknowledgment

    Funding for the RFC Editor function is currently provided by the
    Internet Society.
























Gulbrandsen                Expires April 2009                   [Page 7]
=0C
Internet-draft                                              October 2008


          (RFC Editor: Please delete everything after this point)


Open Issues

    None.


Changes since -00

    - The IANA asked me to specify the IANA registry exactly

    - Boilerplate updates - IETF Trust and so on.


Changes since -01

    - Added THREADROOT, THREADLEAF and MESSAGEID

    - Fixed the typo


Changes since -02

    - Specified thread algorithm per-command, generally using a search
      return option.

    - Defined THREADROOT and THREADLEAF robustly.

    - Required that the server implement THREAD=3DREFS if it implements
      SEARCH=3DINTHREAD.

    - Use In-Reply-To as THREAD=3DREFERENCES, since Timo prefers that and
      I don't mind.

    - Use Date as T=3DR does. Hm? Good idea?















Gulbrandsen                Expires April 2009                   [Page 8]
=0C

---
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

-----


From morg-bounces@ietf.org  Tue Oct 21 08:21:50 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0C0B3A6A76;
	Tue, 21 Oct 2008 08:21:50 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A41273A6AD9
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 08:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.418
X-Spam-Level: 
X-Spam-Status: No, score=-6.418 tagged_above=-999 required=5 tests=[AWL=0.181, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EgeD7HDRO90a for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 08:21:48 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id BC3DB3A6A3B
	for <morg@ietf.org>; Tue, 21 Oct 2008 08:21:48 -0700 (PDT)
Received: from [192.168.10.2] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id 88040164722A;
	Tue, 21 Oct 2008 18:22:59 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <48FA5C7E.4070008@isode.com>
References: <48FA5C7E.4070008@isode.com>
Date: Tue, 21 Oct 2008 18:22:58 +0300
Message-Id: <1224602578.18283.106.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 
Cc: morg@ietf.org
Subject: Re: [MORG] Initial set of documents to work on
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0406568910=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org


--===============0406568910==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-WSdqRz1okkNxc+rveql3"


--=-WSdqRz1okkNxc+rveql3
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2008-10-18 at 23:00 +0100, Alexey Melnikov wrote:
> Hi,
>  From the BOF in Dublin and discussions I had with various people after=20
> that it seems there is a desire to form a WG. In order to get the=20
> process started I would like to first discuss documents that would be=20
> worked on first. Speaking as an individual, I would like to propose the=20
> following set of documents (to be worked on in the specified order)
>=20
> 1). draft-karp-morg-sortdisplay-00.txt
> 2). draft-melnikov-imapext-status-in-list-00.txt and possibly status=20
> counts per message context (Peter Coates has a draft)

Sounds good. Should status counters also specify interaction with
NOTIFY?

> 3). New collations - space ignore, numeric ignoring punctuation, etc. (me=
)
> 4). Sorting by relevancy (Timo)

4) almost requires having a collation that is free to return search
results in pretty unspecified ways. I think people also want to just
type their search keys and expect the server to magically figure out
what the user really wants to see as results.

So if the server is allowed to perform magic, is there really a use for
3) collations? I doubt many users would change the collation themselves.
Perhaps a few power users with special power clients might, but I don't
really see it happening for "normal" people.

Or is there some use case I'm totally missing?

> 5). draft-gulbrandsen-imap-inthread-02.txt
> 6). draft-melnikov-imapext-multimailbox-search-03.txt

I still think 6) is best to be done with some kind of virtual views, but
it needs more thinking. Good thing it's last on the list. :)

--=-WSdqRz1okkNxc+rveql3
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkj989IACgkQyUhSUUBViskL3gCbB8tBx1Bq9hofZc7UhakcoRoF
Dl0An2GCKuUJCtRzF+K5kC9FGel+SlHl
=KVOt
-----END PGP SIGNATURE-----

--=-WSdqRz1okkNxc+rveql3--


--===============0406568910==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============0406568910==--



From morg-bounces@ietf.org  Tue Oct 21 08:36:35 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 634333A69B9;
	Tue, 21 Oct 2008 08:36:35 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B67A93A67C0
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 08:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.136
X-Spam-Level: 
X-Spam-Status: No, score=-6.136 tagged_above=-999 required=5
	tests=[AWL=-0.137, BAYES_00=-2.599, J_CHICKENPOX_64=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FOF9Y1EnQy4S for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 08:36:30 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id D87F13A6A70
	for <morg@ietf.org>; Tue, 21 Oct 2008 08:36:29 -0700 (PDT)
Received: from [192.168.10.2] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id A271A164722A;
	Tue, 21 Oct 2008 18:37:42 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@oryx.com>
In-Reply-To: <tXY1DReqGl1L2yjepIvdig.md5@lochnagar.oryx.com>
References: <48FA5C7E.4070008@isode.com>
	<k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
	<tXY1DReqGl1L2yjepIvdig.md5@lochnagar.oryx.com>
Date: Tue, 21 Oct 2008 18:37:42 +0300
Message-Id: <1224603462.18283.111.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 
Cc: morg@ietf.org
Subject: Re: [MORG] draft-gulbrandsen-imap-inthread
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1122966649=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org


--===============1122966649==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-10Bqf5W0/IaIje28tOse"


--=-10Bqf5W0/IaIje28tOse
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

How is the thread algorithm selected with SORT? ESORT return option
probably?

THREADROOT should probably say clearly what to do when thread root is a
dummy. I guess that can be considered non-existing and instead all the
dummy's children are returned as roots.

Also I was hoping that THREAD=3DREFS would do the thread root sorting
differently for THREAD command. I wrote this about it before:

Replace step (4) with something like: Initialize each thread root's
sort-date to non-existing. For each (non-dummy) message get its
INTERNALDATE and find its thread root. If the thread root's sort-date is
non-existing or the INTERNALDATE is higher than sort-date, update
sort-date to INTERNALDATE. Finally sort all the thread roots by their
sort-date. (Because all threads have at least one non-dummy message,
there should be no non-existing sort-dates left when sorting.)


--=-10Bqf5W0/IaIje28tOse
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkj990YACgkQyUhSUUBVisnRbwCgmslKBO4ijPUubRet9pim9BbF
fI8AnRHOQtuovZBCzvMY3FpwKrBWACff
=+IYl
-----END PGP SIGNATURE-----

--=-10Bqf5W0/IaIje28tOse--


--===============1122966649==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============1122966649==--



From morg-bounces@ietf.org  Tue Oct 21 08:52:39 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0AF3A3A6953;
	Tue, 21 Oct 2008 08:52:39 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 836AA3A68F0
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 08:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.279
X-Spam-Level: 
X-Spam-Status: No, score=-2.279 tagged_above=-999 required=5
	tests=[AWL=-0.281, BAYES_00=-2.599, J_CHICKENPOX_64=0.6,
	UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ios+vWP053aV for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 08:52:33 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 824773A6AD9
	for <morg@ietf.org>; Tue, 21 Oct 2008 08:52:33 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id C04B24AC7E;
	Tue, 21 Oct 2008 17:53:32 +0200 (CEST)
Received: from arnt@oryx.com (client address 195.30.37.40) (HELO
	lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with
	esmtp id 1224604412-66249-6963 for morg@ietf.org; Tue, 21 Oct 2008
	17:53:32 +0200
Message-Id: <wM5lPJCicpGb8ytwCtHHPg.md5@lochnagar.oryx.com>
Date: Tue, 21 Oct 2008 17:52:08 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: morg@ietf.org
References: <48FA5C7E.4070008@isode.com>
	<k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
	<tXY1DReqGl1L2yjepIvdig.md5@lochnagar.oryx.com>
	<1224603462.18283.111.camel@hurina>
In-Reply-To: <1224603462.18283.111.camel@hurina>
Mime-Version: 1.0
Subject: Re: [MORG] draft-gulbrandsen-imap-inthread
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Timo Sirainen writes:
> How is the thread algorithm selected with SORT? ESORT return option probably?

Dave?

> THREADROOT should probably say clearly what to do when thread root is 
> a dummy. I guess that can be considered non-existing and instead all 
> the dummy's children are returned as roots.

Doesn't it say so? "Has no extant parents" or something?

> Also I was hoping that THREAD=REFS would do the thread root sorting 
> differently for THREAD command. I wrote this about it before:

I agree what THREAD=REFERENCES does isn't optimal. But I also like the 
situation where THREAD=REFS has no code of its own, it's 100% a subset 
of THREAD=REFERENCES.

A show of hands, please? What's best: Sorting a better way, or being 
able to reuse more code?

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Tue Oct 21 09:04:07 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8AEA93A6B41;
	Tue, 21 Oct 2008 09:04:07 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C5063A6B41
	for <morg@core3.amsl.com>; Tue, 21 Oct 2008 09:04:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Z8cxXlrYtrap for <morg@core3.amsl.com>;
	Tue, 21 Oct 2008 09:04:02 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id EA6593A6B3E
	for <morg@ietf.org>; Tue, 21 Oct 2008 09:04:01 -0700 (PDT)
Received: from [172.16.2.162] (shiny.isode.com [62.3.217.250]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SP39uwBpDGSM@rufus.isode.com>; Tue, 21 Oct 2008 17:05:15 +0100
Message-ID: <48FDFDA9.9040809@isode.com>
Date: Tue, 21 Oct 2008 17:04:57 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
	Gecko/20050915
X-Accept-Language: en-us, en
To: Timo Sirainen <tss@iki.fi>
References: <48FA5C7E.4070008@isode.com> <1224602578.18283.106.camel@hurina>
In-Reply-To: <1224602578.18283.106.camel@hurina>
MIME-Version: 1.0
Cc: morg@ietf.org
Subject: Re: [MORG] Initial set of documents to work on
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Timo Sirainen wrote:

>On Sat, 2008-10-18 at 23:00 +0100, Alexey Melnikov wrote:
>  
>
>>Hi,
>> From the BOF in Dublin and discussions I had with various people after 
>>that it seems there is a desire to form a WG. In order to get the 
>>process started I would like to first discuss documents that would be 
>>worked on first. Speaking as an individual, I would like to propose the 
>>following set of documents (to be worked on in the specified order)
>>
>>1). draft-karp-morg-sortdisplay-00.txt
>>2). draft-melnikov-imapext-status-in-list-00.txt and possibly status 
>>counts per message context (Peter Coates has a draft)
>>    
>>
>Sounds good. Should status counters also specify interaction with
>NOTIFY?
>  
>
Yes (but I don't think we need to mention this explicitly).

>>3). New collations - space ignore, numeric ignoring punctuation, etc. (me)
>>4). Sorting by relevancy (Timo)
>>    
>>
>
>4) almost requires having a collation that is free to return search
>results in pretty unspecified ways. I think people also want to just
>type their search keys and expect the server to magically figure out
>what the user really wants to see as results.
>  
>
After our discussion in Dublin I am not convinced that the final result 
of this work is going to be a collation, because relevancy scores are 
also of interest to users.
But we will see.

>So if the server is allowed to perform magic, is there really a use for
>3) collations?
>
I think there is, but not necessarily in IMAP.
However I think I have IMAP specific use cases for each one of them 
(e.g. telephone number search).

>I doubt many users would change the collation themselves.
>Perhaps a few power users with special power clients might, but I don't
>really see it happening for "normal" people.
>
>Or is there some use case I'm totally missing?
>  
>
>>5). draft-gulbrandsen-imap-inthread-02.txt
>>6). draft-melnikov-imapext-multimailbox-search-03.txt
>>    
>>
>
>I still think 6) is best to be done with some kind of virtual views, but
>it needs more thinking. Good thing it's last on the list. :)
>  
>
This is perfectly fine, at this point I am more interested in picking 
workitems rather than specific solutions.

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Wed Oct 22 10:20:46 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0ECB73A6A58;
	Wed, 22 Oct 2008 10:20:46 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2CCCE3A6A58
	for <morg@core3.amsl.com>; Wed, 22 Oct 2008 10:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zunTv96DRgvt for <morg@core3.amsl.com>;
	Wed, 22 Oct 2008 10:20:41 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 9EED428C1AE
	for <morg@ietf.org>; Wed, 22 Oct 2008 10:20:37 -0700 (PDT)
Received: from [172.16.2.186] (shiny.isode.com [62.3.217.250]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SP9hKQAJ3SsI@rufus.isode.com>; Wed, 22 Oct 2008 18:21:45 +0100
Message-ID: <48FF6111.9030602@isode.com>
Date: Wed, 22 Oct 2008 18:21:21 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
	Gecko/20050915
X-Accept-Language: en-us, en
To: Arnt Gulbrandsen <arnt@oryx.com>
References: <48FA5C7E.4070008@isode.com>
	<k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
In-Reply-To: <k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
MIME-Version: 1.0
Cc: morg@ietf.org
Subject: Re: [MORG] Initial set of documents to work on
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Arnt Gulbrandsen wrote:

> In view of Alexey's response just now.
>
> Alexey Melnikov wrote, weeks ago:
>
>> 1). draft-karp-morg-sortdisplay-00.txt
>
> A fine draft and I'll commit to implementing it if Dan gets it to RFC, 
> but it's not clear to me how it improves the ability to find messages.

It makes server side sort usable, so it helps clients to find messages 
(as in they need to do less work).

>> 2). draft-melnikov-imapext-status-in-list-00.txt and possibly status 
>> counts per message context (Peter Coates has a draft)
>
> Again, not clear to me, etc.

This reduces bandwidth and the number of roundtrips, so I think it is in 
scope.

>> 3). New collations - space ignore, numeric ignoring punctuation, etc. 
>> (me)
>
> Ditto.

Better (or rather more suitable) collations improve ability to find 
messages, thus in scope.

>> 4). Sorting by relevancy (Timo)
>
> This is about returning an ordered list of search responses, rather 
> than an unordered set?

I think so, but details are yet to be determined.

> That sounds like a good idea.
>
>> 5). draft-gulbrandsen-imap-inthread-02.txt
>
> Hm, I have updated that, but not published, and it expired. Expect a 
> revision.
>
> I think this helps, in so far as it provides tools to perform some 
> really common searches.
>
>> 6). draft-melnikov-imapext-multimailbox-search-03.txt
>
> Multimailbox search is obviously a great help with finding things. Of 
> course it interacts with 4) above. Solvable.

Sure.

> Overall, I'd say that 4-6 could solve two of the four big findability 
> problems. The other two are:
>
> 1. Searching for messages whose address fields contain a specific 
> address or domain.

It might be late for me, but I am not sure what is missing. Can you give 
an example?

> 2. Searching for messages by word instead of substring. Substring 
> serches are easy to implement, but IMO fairly useless. Prefix searches 
> would be better, word searches even better, and IMO perfection would 
> be word searches where the server may stem.

Speaking as an individual, I am all in favour of considering this for 
inclusion. But I think I need to see more details (not necessarily a draft).

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Wed Oct 22 10:53:49 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67C353A6A0F;
	Wed, 22 Oct 2008 10:53:49 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B9CFB3A6A0F
	for <morg@core3.amsl.com>; Wed, 22 Oct 2008 10:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.74
X-Spam-Level: 
X-Spam-Status: No, score=-5.74 tagged_above=-999 required=5 tests=[AWL=-0.537, 
	BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id REnqfvVMdoy4 for <morg@core3.amsl.com>;
	Wed, 22 Oct 2008 10:53:48 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id D3FAC3A69B2
	for <morg@ietf.org>; Wed, 22 Oct 2008 10:53:47 -0700 (PDT)
Received: from [192.168.10.2] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id D4F061647247;
	Wed, 22 Oct 2008 20:54:56 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <48FF6111.9030602@isode.com>
References: <48FA5C7E.4070008@isode.com>
	<k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
	<48FF6111.9030602@isode.com>
Date: Wed, 22 Oct 2008 20:54:56 +0300
Message-Id: <1224698096.18283.169.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 
Cc: morg@ietf.org
Subject: Re: [MORG] Initial set of documents to work on
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0338561175=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org


--===============0338561175==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-4xPUsRK6G8GbTgNqHXAo"


--=-4xPUsRK6G8GbTgNqHXAo
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2008-10-22 at 18:21 +0100, Alexey Melnikov wrote:
> >> 4). Sorting by relevancy (Timo)
..
> > 2. Searching for messages by word instead of substring. Substring=20
> > serches are easy to implement, but IMO fairly useless. Prefix searches=20
> > would be better, word searches even better, and IMO perfection would=20
> > be word searches where the server may stem.
> Speaking as an individual, I am all in favour of considering this for=20
> inclusion. But I think I need to see more details (not necessarily a draf=
t).

I think this is highly relevant to 4). I'm mainly interested in getting
4) implemented using existing search engines and about none of them can
do substring searches. I also don't know if 4) is really even useful for
other purposes. I wasn't really planning on implementing my own
relevancy scoring algorithm.


--=-4xPUsRK6G8GbTgNqHXAo
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkj/aPAACgkQyUhSUUBVisn6ZACdFCkvCiyoH2mrjKjniuOx/mZA
b+YAoKbgP37Ui6sd0jX54+rs9SiOHcoX
=y0ax
-----END PGP SIGNATURE-----

--=-4xPUsRK6G8GbTgNqHXAo--


--===============0338561175==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============0338561175==--



From morg-bounces@ietf.org  Wed Oct 22 15:41:33 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9FE4F3A6B93;
	Wed, 22 Oct 2008 15:41:33 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B60F3A6B8D
	for <morg@core3.amsl.com>; Wed, 22 Oct 2008 15:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.332
X-Spam-Level: 
X-Spam-Status: No, score=-1.332 tagged_above=-999 required=5 tests=[AWL=0.048, 
	BAYES_00=-2.599, DATE_IN_PAST_24_48=1.219]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kvbvwWrVIwZ0 for <morg@core3.amsl.com>;
	Wed, 22 Oct 2008 15:41:31 -0700 (PDT)
Received: from turner.dave.cridland.net (turner.dave.cridland.net
	[217.155.137.60])
	by core3.amsl.com (Postfix) with ESMTP id 0E0A33A67CC
	for <morg@ietf.org>; Wed, 22 Oct 2008 15:41:30 -0700 (PDT)
Received: from peirce.dave.cridland.net ([217.155.137.61]) by
	turner.dave.cridland.net (submission)
	via TCP with ESMTPA id <SP3-fwAS0TPQ@turner.dave.cridland.net>;
	Tue, 21 Oct 2008 17:08:31 +0100
References: <48FA5C7E.4070008@isode.com>
	<k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
	<tXY1DReqGl1L2yjepIvdig.md5@lochnagar.oryx.com>
	<1224603462.18283.111.camel@hurina>
	<wM5lPJCicpGb8ytwCtHHPg.md5@lochnagar.oryx.com>
In-Reply-To: <wM5lPJCicpGb8ytwCtHHPg.md5@lochnagar.oryx.com>
MIME-Version: 1.0
Message-Id: <10893.1224605311.025164@peirce.dave.cridland.net>
Date: Tue, 21 Oct 2008 17:08:31 +0100
From: Dave Cridland <dave@cridland.net>
To: Arnt Gulbrandsen <arnt@oryx.com>
Cc: Messaging Organization <morg@ietf.org>
Subject: Re: [MORG] draft-gulbrandsen-imap-inthread
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

On Tue Oct 21 16:52:08 2008, Arnt Gulbrandsen wrote:
> Timo Sirainen writes:
>> How is the thread algorithm selected with SORT? ESORT return  
>> option probably?
> 
> Dave?
> 
> 
It could do, I suppose, although that means a normative dependency on  
the CONTEXT document, unless ESORT is extracted from it. Means that  
you'd emit ESEARCH responses, of course.

I'm easy, but I'd note that if we are to head this route, it seems  
odd that selection of thread algorithms is different in SORT and  
SEARCH than in THREAD itself, and moreover it's also different to  
comparator selection.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Thu Oct 23 05:30:49 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4099F3A6BE8;
	Thu, 23 Oct 2008 05:30:49 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91E803A6806
	for <morg@core3.amsl.com>; Thu, 23 Oct 2008 05:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.025, 
	BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GP8RUAxZ288R for <morg@core3.amsl.com>;
	Thu, 23 Oct 2008 05:30:41 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30])
	by core3.amsl.com (Postfix) with ESMTP id 3B4363A6BE8
	for <morg@ietf.org>; Thu, 23 Oct 2008 05:30:41 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1])
	by kalyani.oryx.com (Postfix) with ESMTP id E5A2C4AC78;
	Thu, 23 Oct 2008 14:31:51 +0200 (CEST)
Received: from arnt@oryx.com (client address 195.30.37.40) (HELO
	lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with
	esmtp id 1224765111-66249-7767 for morg@ietf.org; Thu, 23 Oct 2008
	14:31:51 +0200
Message-Id: </89fkU+i7/ylQfgIf9dxbQ.md5@lochnagar.oryx.com>
Date: Thu, 23 Oct 2008 14:30:30 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: morg@ietf.org
References: <48FA5C7E.4070008@isode.com>
	<k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
	<48FF6111.9030602@isode.com>
In-Reply-To: <48FF6111.9030602@isode.com>
Mime-Version: 1.0
Subject: Re: [MORG] Initial set of documents to work on
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

Alexey Melnikov writes:
>>> 1). draft-karp-morg-sortdisplay-00.txt
>>
>> A fine draft and I'll commit to implementing it if Dan gets it to =

>> RFC, but it's not clear to me how it improves the ability to find =

>> messages.
>
> It makes server side sort usable, so it helps clients to find messages =

> (as in they need to do less work).

OK. Fine argument.

>>> 2). draft-melnikov-imapext-status-in-list-00.txt and possibly status =

>>> counts per message context (Peter Coates has a draft)
>>
>> Again, not clear to me, etc.
>
> This reduces bandwidth and the number of roundtrips, so I think it is =

> in scope.

Reducing bandwidth usage and number of roundtrips are surely fine goals, =

but they seem to be orthogonal to finding messages.

Unless you think _any_ performance improvement helps people find stuff fast=
er?

>>> 3). New collations - space ignore, numeric ignoring punctuation, etc. (=
me)
>>
>> Ditto.
>
> Better (or rather more suitable) collations improve ability to find =

> messages, thus in scope.

I don't agree, but we don't have enough detail to argue usefully. Write =

something about these collations we can argue more usefully.

>> Overall, I'd say that 4-6 could solve two of the four big findability =

>> problems. The other two are:
>>
>> 1. Searching for messages whose address fields contain a specific =

>> address or domain.
>
> It might be late for me, but I am not sure what is missing. Can you =

> give an example?

Compare with Sieve. Sieve has =ABaddress :localpart :is "arnt"=BB. IMAP onl=
y =

has the equivalent of =ABheader :contains "arnt"=BB, =ABfrom arnt=BB.

If you take a small risk, you can say =ABfrom arnt@=BB, but that may or may =

not match messages =ABFrom: arnt (Arnt Gulbrandsen)=BB. If you take a =

bigger risk, you can say =ABfrom <arnt@=BB, but you can't trust that to =

match =ABFrom: arnt@oryx.com=BB on all servers.

I can write a draft for this, if desired, based on my code. I would add =

two or three search keys. Exact address, exact domain and =

domain-or-subdomain. (Exact localpart would be a possibility too and =

perhaps easy to implement along with the rest, but there doesn't seem =

to be much demand for that.)

>> 2. Searching for messages by word instead of substring. Substring =

>> serches are easy to implement, but IMO fairly useless. Prefix =

>> searches would be better, word searches even better, and IMO =

>> perfection would be word searches where the server may stem.
>
> Speaking as an individual, I am all in favour of considering this for =

> inclusion. But I think I need to see more details (not necessarily a =

> draft).

I suggest that Timo write the introduction to a draft and post on the list.

Arnt
_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html


From morg-bounces@ietf.org  Sun Oct 26 13:17:59 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB46C3A6AD4;
	Sun, 26 Oct 2008 13:17:59 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F00853A69B5
	for <morg@core3.amsl.com>; Sun, 26 Oct 2008 13:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.652
X-Spam-Level: 
X-Spam-Status: No, score=-2.652 tagged_above=-999 required=5
	tests=[AWL=-0.054, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JBVH4lfZz6Uc for <morg@core3.amsl.com>;
	Sun, 26 Oct 2008 13:17:57 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251])
	by core3.amsl.com (Postfix) with ESMTP id 4F83E3A6A96
	for <morg@ietf.org>; Sun, 26 Oct 2008 13:17:57 -0700 (PDT)
Received: from [92.40.206.35] (92.40.206.35.sub.mbb.three.co.uk
	[92.40.206.35]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <SQTQxABEUVE3@rufus.isode.com>; Sun, 26 Oct 2008 20:19:18 +0000
Message-ID: <4904B972.4060408@isode.com>
Date: Sun, 26 Oct 2008 18:39:46 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
	Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@oryx.com>
References: <48FA5C7E.4070008@isode.com>
	<k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
	<48FF6111.9030602@isode.com>
	</89fkU+i7/ylQfgIf9dxbQ.md5@lochnagar.oryx.com>
In-Reply-To: </89fkU+i7/ylQfgIf9dxbQ.md5@lochnagar.oryx.com>
Cc: morg@ietf.org
Subject: Re: [MORG] Initial set of documents to work on
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0829262608=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

--===============0829262608==
Content-Type: multipart/alternative;
              boundary="------------050700000009030904000205"

--------------050700000009030904000205
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: quoted-printable

Arnt Gulbrandsen wrote:

> Alexey Melnikov writes:
>
>>>> 1). draft-karp-morg-sortdisplay-00.txt
>>>
>>> A fine draft and I'll commit to implementing it if Dan gets it to=20
>>> RFC, but it's not clear to me how it improves the ability to find=20
>>> messages.
>>
>> It makes server side sort usable, so it helps clients to find=20
>> messages (as in they need to do less work).
>
> OK. Fine argument.
>
>>>> 2). draft-melnikov-imapext-status-in-list-00.txt and possibly=20
>>>> status counts per message context (Peter Coates has a draft)
>>>
>>> Again, not clear to me, etc.
>>
>> This reduces bandwidth and the number of roundtrips, so I think it is=20
>> in scope.
>
> Reducing bandwidth usage and number of roundtrips are surely fine=20
> goals, but they seem to be orthogonal to finding messages.
>
> Unless you think _any_ performance improvement helps people find stuff=20
> faster?

I meant improving "ability to find", which includes both new ways to=20
limit search results, as well as to transfer them quicker ;-).

>>>> 3). New collations - space ignore, numeric ignoring punctuation,=20
>>>> etc. (me)
>>>
>>> Ditto.
>>
>> Better (or rather more suitable) collations improve ability to find=20
>> messages, thus in scope.
>
> I don't agree, but we don't have enough detail to argue usefully.=20
> Write something about these collations we can argue more usefully.

Ok, after Minneapolis perhaps. Too busy at the moment.

>>> Overall, I'd say that 4-6 could solve two of the four big=20
>>> findability problems. The other two are:
>>>
>>> 1. Searching for messages whose address fields contain a specific=20
>>> address or domain.
>>
>> It might be late for me, but I am not sure what is missing. Can you=20
>> give an example?
>
> Compare with Sieve. Sieve has =ABaddress :localpart :is "arnt"=BB. IMAP=20
> only has the equivalent of =ABheader :contains "arnt"=BB, =ABfrom arnt=BB.
>
> If you take a small risk, you can say =ABfrom arnt@=BB, but that may or=20
> may not match messages =ABFrom: arnt (Arnt Gulbrandsen)=BB. If you take a=
=20
> bigger risk, you can say =ABfrom <arnt@=BB, but you can't trust that to=20
> match =ABFrom: arnt@oryx.com=BB on all servers.
>
> I can write a draft for this, if desired, based on my code. I would=20
> add two or three search keys. Exact address, exact domain and=20
> domain-or-subdomain. (Exact localpart would be a possibility too and=20
> perhaps easy to implement along with the rest, but there doesn't seem=20
> to be much demand for that.)

Sure.

>>> 2. Searching for messages by word instead of substring. Substring=20
>>> serches are easy to implement, but IMO fairly useless. Prefix=20
>>> searches would be better, word searches even better, and IMO=20
>>> perfection would be word searches where the server may stem.
>>
>> Speaking as an individual, I am all in favour of considering this for=20
>> inclusion. But I think I need to see more details (not necessarily a=20
>> draft).
>
> I suggest that Timo write the introduction to a draft and post on the=20
> list.

I agree.


--------------050700000009030904000205
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
Arnt Gulbrandsen wrote:<br>
<blockquote cite="mid%2F89fkU+i7%2FylQfgIf9dxbQ.md5@lochnagar.oryx.com"
 type="cite">Alexey Melnikov writes: <br>
  <blockquote type="cite">
    <blockquote type="cite">
      <blockquote type="cite">1). draft-karp-morg-sortdisplay-00.txt <br>
      </blockquote>
A fine draft and I'll commit to implementing it if Dan gets it to RFC,
but it's not clear to me how it improves the ability to find messages. <br>
    </blockquote>
It makes server side sort usable, so it helps clients to find messages
(as in they need to do less work). <br>
  </blockquote>
OK. Fine argument. <br>
  <blockquote type="cite">
    <blockquote type="cite">
      <blockquote type="cite">2).
draft-melnikov-imapext-status-in-list-00.txt and possibly status counts
per message context (Peter Coates has a draft) <br>
      </blockquote>
Again, not clear to me, etc. <br>
    </blockquote>
This reduces bandwidth and the number of roundtrips, so I think it is
in scope. <br>
  </blockquote>
Reducing bandwidth usage and number of roundtrips are surely fine
goals, but they seem to be orthogonal to finding messages. <br>
  <br>
Unless you think _any_ performance improvement helps people
find stuff faster? <br>
</blockquote>
I meant improving "ability to find", which includes both new ways to
limit search results, as well as to transfer them quicker ;-).<br>
<blockquote cite="mid%2F89fkU+i7%2FylQfgIf9dxbQ.md5@lochnagar.oryx.com"
 type="cite">
  <blockquote type="cite">
    <blockquote type="cite">
      <blockquote type="cite">3). New collations - space ignore,
numeric ignoring punctuation, etc. (me) <br>
      </blockquote>
Ditto. <br>
    </blockquote>
Better (or rather more suitable) collations improve ability to find
messages, thus in scope. <br>
  </blockquote>
I don't agree, but we don't have enough detail to argue usefully.
Write something about these collations we can argue more usefully. <br>
</blockquote>
Ok, after Minneapolis perhaps. Too busy at the moment.<br>
<blockquote cite="mid%2F89fkU+i7%2FylQfgIf9dxbQ.md5@lochnagar.oryx.com"
 type="cite">
  <blockquote type="cite">
    <blockquote type="cite">Overall, I'd say that 4-6 could solve two
of the four big findability problems. The other two are: <br>
      <br>
1. Searching for messages whose address fields contain a specific
address or domain. <br>
    </blockquote>
It might be late for me, but I am not sure what is missing. Can you
give an example? <br>
  </blockquote>
Compare with Sieve. Sieve has &laquo;address :localpart :is "arnt"&raquo;. IMAP
only has the equivalent of &laquo;header :contains "arnt"&raquo;, &laquo;from arnt&raquo;. <br>
  <br>
If you take a small risk, you can say &laquo;from arnt@&raquo;, but that may or may
not match messages &laquo;From: arnt (Arnt Gulbrandsen)&raquo;. If you take a
bigger risk, you can say &laquo;from &lt;arnt@&raquo;, but you can't trust that to
match &laquo;From: <span class="moz-txt-link-abbreviated"><a class="moz-txt-link-abbreviated" href="mailto:arnt@oryx.com">arnt@oryx.com</a></span>&raquo;
on all servers. <br>
  <br>
I can write a draft for this, if desired, based on my code. I would add
two or three search keys. Exact address, exact domain and
domain-or-subdomain. (Exact localpart would be a possibility too and
perhaps easy to implement along with the rest, but there doesn't seem
to be much demand for that.) <br>
</blockquote>
Sure.<br>
<blockquote cite="mid%2F89fkU+i7%2FylQfgIf9dxbQ.md5@lochnagar.oryx.com"
 type="cite">
  <blockquote type="cite">
    <blockquote type="cite">2. Searching for messages by word instead
of substring. Substring serches are easy to implement, but IMO fairly
useless. Prefix searches would be better, word searches even better,
and IMO perfection would be word searches where the server may stem. <br>
    </blockquote>
Speaking as an individual, I am all in favour of considering this for
inclusion. But I think I need to see more details (not necessarily a
draft). <br>
  </blockquote>
I suggest that Timo write the introduction to a draft and post on the
list. <br>
</blockquote>
I agree.<br>
<br>
</body>
</html>

--------------050700000009030904000205--

--===============0829262608==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============0829262608==--


From morg-bounces@ietf.org  Sun Oct 26 15:03:10 2008
Return-Path: <morg-bounces@ietf.org>
X-Original-To: morg-archive@optimus.ietf.org
Delivered-To: ietfarch-morg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D19233A6901;
	Sun, 26 Oct 2008 15:03:10 -0700 (PDT)
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A066E3A6901
	for <morg@core3.amsl.com>; Sun, 26 Oct 2008 15:03:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.4
X-Spam-Level: 
X-Spam-Status: No, score=-3.4 tagged_above=-999 required=5
	tests=[J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ct3VsCTmVAJu for <morg@core3.amsl.com>;
	Sun, 26 Oct 2008 15:03:09 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50])
	by core3.amsl.com (Postfix) with ESMTP id 9B6933A683E
	for <morg@ietf.org>; Sun, 26 Oct 2008 15:03:05 -0700 (PDT)
Received: from [192.168.10.200] (xdsl-177-118.nblnetworks.fi [217.30.177.118])
	by dovecot.org (Postfix) with ESMTP id 609A01647239
	for <morg@ietf.org>; Mon, 27 Oct 2008 00:03:01 +0200 (EET)
Message-Id: <CF2060FE-6B87-4C99-B829-456D90F02041@iki.fi>
From: Timo Sirainen <tss@iki.fi>
To: morg@ietf.org
In-Reply-To: <wM5lPJCicpGb8ytwCtHHPg.md5@lochnagar.oryx.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 00:03:00 +0200
References: <48FA5C7E.4070008@isode.com>
	<k4IJ8MqyWVb6OYjFr+JsPA.md5@lochnagar.oryx.com>
	<tXY1DReqGl1L2yjepIvdig.md5@lochnagar.oryx.com>
	<1224603462.18283.111.camel@hurina>
	<wM5lPJCicpGb8ytwCtHHPg.md5@lochnagar.oryx.com>
X-Pgp-Agent: GPGMail d51 (Leopard)
X-Mailer: Apple Mail (2.929.2)
Subject: [MORG] THREAD=REFS sorting
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>,
	<mailto:morg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1591310312=="
Sender: morg-bounces@ietf.org
Errors-To: morg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1591310312==
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-47--209238498"
Content-Transfer-Encoding: 7bit

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-47--209238498
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On Oct 21, 2008, at 6:52 PM, Arnt Gulbrandsen wrote:

>> Also I was hoping that THREAD=REFS would do the thread root sorting  
>> differently for THREAD command. I wrote this about it before:
>
> I agree what THREAD=REFERENCES does isn't optimal. But I also like  
> the situation where THREAD=REFS has no code of its own, it's 100% a  
> subset of THREAD=REFERENCES.
>
> A show of hands, please? What's best: Sorting a better way, or being  
> able to reuse more code?

Anyone?

I use two IMAP clients: Evolution and Apple Mail. Both sort the thread  
roots by their latest received message, not by the sent-date of the  
thread root. I'm guessing many (most? all?) other clients do the same.  
I've received bug reports about Dovecot's THREAD=REFERENCES  
implementation because it doesn't sort by the latest received message  
and users think they're not receiving new messages because they show  
up in the middle of the mailbox. So this sorting is something users  
really want and I'll have to do it one way or another, currently it's  
THREAD=X-REFERENCES2 but I'd prefer to make it a standard.

I also don't think the code reuse issue is all that big of a deal.  
It's replacing a single step in the threading algorithm. Dovecot  
needed less than 40 lines more to implement it (although that'll  
increase if I add some optimizations).


--Apple-Mail-47--209238498
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkkE6RQACgkQyUhSUUBVislcPQCbBLS0iasLrmUlMsj7ds2D2mqI
X7oAnjML/BX2P8BBV2XSTMsUihWovoYV
=ogrQ
-----END PGP SIGNATURE-----

--Apple-Mail-47--209238498--

--===============1591310312==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MORG mailing list
MORG@ietf.org
https://www.ietf.org/mailman/listinfo/morg
Note Well: http://www.ietf.org/maillist.html

--===============1591310312==--


