
From arnt@gulbrandsen.priv.no  Tue Jul  6 06:31:27 2010
Return-Path: <arnt@gulbrandsen.priv.no>
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 282B73A67AE for <morg@core3.amsl.com>; Tue,  6 Jul 2010 06:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 JQHiscw4YlAJ for <morg@core3.amsl.com>; Tue,  6 Jul 2010 06:31:26 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 4CB6C3A67C3 for <morg@ietf.org>; Tue,  6 Jul 2010 06:31:26 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 5E550FA0122; Tue,  6 Jul 2010 13:31:27 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtpsa id 1278423086-42496-42495/8/43; Tue, 6 Jul 2010 15:31:26 +0200
Message-Id: <4C333056.4010703@gulbrandsen.priv.no>
Date: Tue, 6 Jul 2010 15:32:06 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: Me, http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: [MORG] 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/mail-archive/web/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>
X-List-Received-Date: Tue, 06 Jul 2010 13:31:27 -0000

A few seconds ago I decided to not implement more of inthread. Instead I 
shall remove everything from the draft that I haven't implemented (on 
the theory that its need was less than compelling). Expect a new 
revision sometime late tonight.

Arnt

From tss@iki.fi  Tue Jul  6 07:00:23 2010
Return-Path: <tss@iki.fi>
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 DC3583A68FA for <morg@core3.amsl.com>; Tue,  6 Jul 2010 07:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.185
X-Spam-Level: 
X-Spam-Status: No, score=-4.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 m5wJcbw98LFh for <morg@core3.amsl.com>; Tue,  6 Jul 2010 07:00:23 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 13D223A686C for <morg@ietf.org>; Tue,  6 Jul 2010 07:00:23 -0700 (PDT)
Received: from [10.134.134.32] (pickles.tp.telepac.pt [194.65.5.228]) by dovecot.org (Postfix) with ESMTP id 1BC24FA8B6D; Tue,  6 Jul 2010 17:00:23 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
In-Reply-To: <4C333056.4010703@gulbrandsen.priv.no>
References: <4C333056.4010703@gulbrandsen.priv.no>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 06 Jul 2010 15:00:20 +0100
Message-ID: <1278424820.1533.60.camel@kurkku.sapo.corppt.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Content-Transfer-Encoding: 7bit
Cc: morg@ietf.org
Subject: Re: [MORG] 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/mail-archive/web/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>
X-List-Received-Date: Tue, 06 Jul 2010 14:00:23 -0000

On Tue, 2010-07-06 at 15:32 +0200, Arnt Gulbrandsen wrote:
> A few seconds ago I decided to not implement more of inthread. Instead I 
> shall remove everything from the draft that I haven't implemented (on 
> the theory that its need was less than compelling).

So basically the INTHREAD search-key? Yeah, that's what I have also
implemented.



From arnt@gulbrandsen.priv.no  Tue Jul  6 07:01:20 2010
Return-Path: <arnt@gulbrandsen.priv.no>
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 DDF523A691B for <morg@core3.amsl.com>; Tue,  6 Jul 2010 07:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  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 DIRopzH0DNLz for <morg@core3.amsl.com>; Tue,  6 Jul 2010 07:01:20 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id D5DCF3A68F3 for <morg@ietf.org>; Tue,  6 Jul 2010 07:01:19 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 90C32FA0120; Tue,  6 Jul 2010 14:01:21 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtpsa id 1278424880-42496-42495/8/44; Tue, 6 Jul 2010 16:01:20 +0200
Message-Id: <4C333758.8080307@gulbrandsen.priv.no>
Date: Tue, 6 Jul 2010 16:02:00 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: Me, http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: Timo Sirainen <tss@iki.fi>
References: <4C333056.4010703@gulbrandsen.priv.no> <1278424820.1533.60.camel@kurkku.sapo.corppt.com>
In-Reply-To: <1278424820.1533.60.camel@kurkku.sapo.corppt.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Cc: morg@ietf.org
Subject: Re: [MORG] 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/mail-archive/web/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>
X-List-Received-Date: Tue, 06 Jul 2010 14:01:21 -0000

On 07/06/2010 04:00 PM, Timo Sirainen wrote:
> So basically the INTHREAD search-key? Yeah, that's what I have also
> implemented.

+T=R

From arnt@gulbrandsen.priv.no  Thu Jul  8 03:05:00 2010
Return-Path: <arnt@gulbrandsen.priv.no>
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 D6A993A6A0B for <morg@core3.amsl.com>; Thu,  8 Jul 2010 03:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.866
X-Spam-Level: 
X-Spam-Status: No, score=-1.866 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, J_CHICKENPOX_64=0.6]
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 Y7l+7Qx6ExnY for <morg@core3.amsl.com>; Thu,  8 Jul 2010 03:04:57 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id C73B33A6A0E for <morg@ietf.org>; Thu,  8 Jul 2010 03:04:56 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 10B39FA0010; Thu,  8 Jul 2010 10:04:58 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtpsa id 1278583497-74603-74602/8/5; Thu, 8 Jul 2010 12:04:57 +0200
Message-Id: <4C35A2FD.9030304@gulbrandsen.priv.no>
Date: Thu, 8 Jul 2010 12:05:49 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: Me, http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
Content-Type: multipart/mixed; boundary=------------000706050102030601080608
Subject: [MORG] Fwd: New Version Notification for draft-ietf-morg-inthread-01
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/mail-archive/web/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>
X-List-Received-Date: Thu, 08 Jul 2010 10:05:00 -0000

--------------000706050102030601080608
Content-Type: text/plain; charset=utf-8; format=flowed

Sometimes the magic parser is too much for me.

I got the nits count down to zero, but one "Actually Them" is still 
listed as author. OK.

Arnt

--------------000706050102030601080608
Content-Type: message/rfc822;
 name="New Version Notification for draft-ietf-morg-inthread-01.eml"
Content-Disposition: attachment;
 filename="New Version Notification for draft-ietf-morg-inthread-01.eml"

Return-Path: <wwwrun@core3.amsl.com>
Received: from 79.140.39.153 (HELO strange.aox.org) by
 fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with lmtp id
 1278583331-74603-74602/7/49 for arnt@gulbrandsen.priv.no; Thu, 8 Jul
 2010 12:02:11 +0200
Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1890:1112:1::20])
	by strange.aox.org (Postfix) with ESMTP id 10A34FA0010
	for <arnt@gulbrandsen.priv.no>; Thu,  8 Jul 2010 10:02:08 +0000 (UTC)
Received: by core3.amsl.com (Postfix, from userid 30)
	id E88A03A6809; Thu,  8 Jul 2010 03:02:02 -0700 (PDT)
From: IETF I-D Submission Tool <idsubmission@ietf.org>
To: arnt@gulbrandsen.priv.no
Cc: "<foo@bar>"@core3.amsl.com
Subject: New Version Notification for draft-ietf-morg-inthread-01
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0
Message-Id: <20100708100202.E88A03A6809@core3.amsl.com>
Date: Thu, 8 Jul 2010 03:02:02 -0700 (PDT)
Content-Transfer-Encoding: quoted-printable


A new version of I-D, draft-ietf-morg-inthread-01.txt has been successful=
ly submitted by Arnt Gulbrandsen and posted to the IETF repository.

Filename:	 draft-ietf-morg-inthread
Revision:	 01
Title:		 The IMAP SEARCH=3DINTHREAD and THREAD=3DREFS Extensions
Creation_date:	 2010-07-08
WG ID:		 morg
Number_of_pages: 9

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. This allows clients to perform
 searches such as "find all threads that mention schemata", rather
 than just "find all single messages that mention schemata".

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


1.
                                                                         =
        =20


The IETF Secretariat.



--------------000706050102030601080608--

From root@core3.amsl.com  Thu Jul  8 03:15:08 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: morg@ietf.org
Delivered-To: morg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 82A0B3A6970; Thu,  8 Jul 2010 03:15:06 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100708101506.82A0B3A6970@core3.amsl.com>
Date: Thu,  8 Jul 2010 03:15:06 -0700 (PDT)
Cc: morg@ietf.org
Subject: [MORG] I-D Action:draft-ietf-morg-inthread-01.txt
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/mail-archive/web/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>
X-List-Received-Date: Thu, 08 Jul 2010 10:15:11 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Message Organization Working Group of the IETF.


	Title           : The IMAP SEARCH=INTHREAD and THREAD=REFS Extensions
	Author(s)       : A. Gulbrandsen, A. them
	Filename        : draft-ietf-morg-inthread-01.txt
	Pages           : 9
	Date            : 2010-07-08

The SEARCH=INTHREAD extension extends the IMAP SEARCH command to
 operate on threads as well as individual messages. Other commands
 which search are implicitly extended. This allows clients to perform
 searches such as "find all threads that mention schemata", rather
 than just "find all single messages that mention schemata".

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


1.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-morg-inthread-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-morg-inthread-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-08030202.I-D@ietf.org>


--NextPart--

From barryleiba.mailing.lists@gmail.com  Fri Jul  9 10:15:35 2010
Return-Path: <barryleiba.mailing.lists@gmail.com>
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 66F9E3A68F1 for <morg@core3.amsl.com>; Fri,  9 Jul 2010 10:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, 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 rNGHPLqfT0rI for <morg@core3.amsl.com>; Fri,  9 Jul 2010 10:15:27 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 3F1503A69EC for <morg@ietf.org>; Fri,  9 Jul 2010 10:15:22 -0700 (PDT)
Received: by gxk3 with SMTP id 3so1520925gxk.31 for <morg@ietf.org>; Fri, 09 Jul 2010 10:15:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to:date :message-id:subject:from:to:content-type; bh=GT9EF0tt72PAG7IbqS81dWVDFrVlhlWgTuMqwsfuwIo=; b=mQ+Q74fSlCjgXyEpGmKNKHPq+Aw5piU4Ox/qZ2vv5JG3S+RO8TotdZ1vbQTKuai4cc m0AGqWJB4H4nJljq8ObrsD84WBzsbrSxVpjroGhtKWUMAljHj5xXGVx7fGNwhDLtHW8f 7+xEenbKQv281Il5NEldLH5EmfYJjhplnAd+c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; b=x07quqJgu60N5N7TLzrCawnNZTteD/BVENWn7QexY+FIVZwdvahNHEs+dHi8TaaCDL f9XKVGTKXgV1Xz31D0pNaJ6WF++xex6GtOnnxDOrS9kH0Mxy9uPPMJozO78ZjwtiwVqh 7bn0UvJwRvB2c4crATMwE1IjpVhgGtv0bGT3c=
MIME-Version: 1.0
Received: by 10.90.62.7 with SMTP id k7mr572223aga.31.1278695723678; Fri, 09  Jul 2010 10:15:23 -0700 (PDT)
Received: by 10.42.5.212 with HTTP; Fri, 9 Jul 2010 10:15:23 -0700 (PDT)
Date: Fri, 9 Jul 2010 13:15:23 -0400
Message-ID: <AANLkTimOFDprZg7eH5qARWPnxSj13MGiPLIs401YLurJ@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg <morg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [MORG] Agenda for IETF 78, Maastricht
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: barryleiba@computer.org
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/mail-archive/web/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>
X-List-Received-Date: Fri, 09 Jul 2010 17:15:35 -0000

The chairs need to make up an agenda for the WG meeting in Maastricht.
 We're scheduled to meet for 1 hour, on Tuesday afternoon (27 July)
from 17:10 to 18:10 CET (15:10 to 16:10 UTC).

I'm including a skeleton agenda, below.  I'd like to hear about other
agenda items people have to propose, or any other comments about the
skeleton agenda.  I'd also like a sort of "show of hands" to let me
know who's going to be attending in person, and who will participate
remotely, using the audio stream or jabber.  Please reply to this
thread with answers to these questions, and other issues directly
related to the Maastricht meeting.  (Please take any other discussion
to a separate thread.)

Here's a skeleton agenda, with no times on it yet:
1. Welcome and announcements.
2. Working group status.
3. Document discussions...
   a. Fuzzy search[1], in WGLC
   b. Special-use mailboxes[2], in WGLC
   c. Multimailbox search[3], outstanding items
   d. Search inthread[4], new draft posted
   e. Address search[5], dropped by WG
4. What to do about draft-leiba-morg-message-recall,[6] expired ?
5. What to do about draft-krecicki-imap-move,[7] new ?
6. The future of the MORG working group.
7. Any other business.

Barry, as chair

[1] http://tools.ietf.org/html/draft-ietf-morg-fuzzy-search
[2] http://tools.ietf.org/html/draft-ietf-morg-list-specialuse
[3] http://tools.ietf.org/html/draft-ietf-morg-multimailbox-search
[4] http://tools.ietf.org/html/draft-ietf-morg-inthread
[5] http://tools.ietf.org/html/draft-ietf-morg-address-search
[6] http://tools.ietf.org/html/draft-leiba-morg-message-recall
[7] http://tools.ietf.org/html/draft-krecicki-imap-move

From tss@iki.fi  Mon Jul 12 07:05:23 2010
Return-Path: <tss@iki.fi>
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 774A43A693B for <morg@core3.amsl.com>; Mon, 12 Jul 2010 07:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.392
X-Spam-Level: 
X-Spam-Status: No, score=-5.392 tagged_above=-999 required=5 tests=[AWL=1.207,  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 O1WxxU+hemfi for <morg@core3.amsl.com>; Mon, 12 Jul 2010 07:05:19 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 857A73A6870 for <morg@ietf.org>; Mon, 12 Jul 2010 07:05:19 -0700 (PDT)
Received: from [10.134.134.32] (pickles.tp.telepac.pt [194.65.5.228]) by dovecot.org (Postfix) with ESMTP id EF2A5FA8AD8; Mon, 12 Jul 2010 17:05:24 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: barryleiba@computer.org
In-Reply-To: <AANLkTimOFDprZg7eH5qARWPnxSj13MGiPLIs401YLurJ@mail.gmail.com>
References: <AANLkTimOFDprZg7eH5qARWPnxSj13MGiPLIs401YLurJ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 12 Jul 2010 15:05:23 +0100
Message-ID: <1278943523.5768.37.camel@kurkku.sapo.corppt.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Content-Transfer-Encoding: 7bit
Cc: morg <morg@ietf.org>
Subject: Re: [MORG] Agenda for IETF 78, Maastricht
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/mail-archive/web/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>
X-List-Received-Date: Mon, 12 Jul 2010 14:05:23 -0000

On Fri, 2010-07-09 at 13:15 -0400, Barry Leiba wrote:
> I'm including a skeleton agenda, below.  I'd like to hear about other
> agenda items people have to propose, or any other comments about the
> skeleton agenda.  

It looks ok to me.

> I'd also like a sort of "show of hands" to let me
> know who's going to be attending in person, 

I'll be there.

> Here's a skeleton agenda, with no times on it yet:

My guess it that things will go pretty quickly, except for imap-move and
maybe message-recall and multimailbox.



From barryleiba.mailing.lists@gmail.com  Fri Jul 23 07:07:26 2010
Return-Path: <barryleiba.mailing.lists@gmail.com>
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 B66AB3A67F2 for <morg@core3.amsl.com>; Fri, 23 Jul 2010 07:07:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.776
X-Spam-Level: 
X-Spam-Status: No, score=-2.776 tagged_above=-999 required=5 tests=[AWL=-0.177, 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 U8YEy6PBoTUl for <morg@core3.amsl.com>; Fri, 23 Jul 2010 07:07:25 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 8ECB13A67EA for <morg@ietf.org>; Fri, 23 Jul 2010 07:07:25 -0700 (PDT)
Received: by yxj4 with SMTP id 4so3576814yxj.31 for <morg@ietf.org>; Fri, 23 Jul 2010 07:07:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:content-type; bh=3qRvjsVCOX1bhfKxF/LsiQYaLXC91vi/0SsOWWCVs8w=; b=x6ZDVJOP4BzaQpi5Pcs/VFSmbFbvIbVtPBlKymUo174WyvBXVbFF2e/NB8cJfXlUZb oBiag7UGr1usamKC/fbBGw9WbyPvTMwebzN23rTzlyi6Wa+R2EwQWhI9y8qdsyUvhLad LUzEy28unezejhjIkpkLcjgjMJCQW9ylK9MIY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=yCRxWKcymRq6S7lL/EQXDlixXxxy8wQwMj0hfYRB0wcV62tgkzoUIeByTZbAgooU+0 YFwIrjXhYUVyYxwIAEXVdjtuwjUre19yAjbEzplkfDhDcY+EJCLS0SxOBdTWag+8RmXZ 3KreG0bTlETvkz5gscHoaCzh3uER5Kd4EOq9A=
MIME-Version: 1.0
Received: by 10.150.7.4 with SMTP id 4mr362784ybg.11.1279894063266; Fri, 23  Jul 2010 07:07:43 -0700 (PDT)
Received: by 10.42.1.136 with HTTP; Fri, 23 Jul 2010 07:07:43 -0700 (PDT)
In-Reply-To: <AANLkTimOFDprZg7eH5qARWPnxSj13MGiPLIs401YLurJ@mail.gmail.com>
References: <AANLkTimOFDprZg7eH5qARWPnxSj13MGiPLIs401YLurJ@mail.gmail.com>
Date: Fri, 23 Jul 2010 10:07:43 -0400
Message-ID: <AANLkTintcOeH+4A2DdoMefPKaMb4WN19KU3bMMbKzq5z@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg <morg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [MORG] Agenda for IETF 78, Maastricht
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: barryleiba@computer.org
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/mail-archive/web/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>
X-List-Received-Date: Fri, 23 Jul 2010 14:07:26 -0000

I have updated the agenda on the meeting materials site with some sketchy times:
https://datatracker.ietf.org/meeting/78/materials.html

I am not planning to use slides for this meeting, so remote
participants will mostly not have to worry about following slides. The
agenda and our voices will be the order of the day.  That said, if
anyone does have slides they want to present, please get them to me by
email <barryleiba@computer.org> by the end of day on Monday.  I will
close submissions hard on Monday evening, and I will really appreciate
it if people can get them to me as early as possible.

Barry, as chair

From wwwrun@rfc-editor.org  Sun Jul 25 02:15:19 2010
Return-Path: <wwwrun@rfc-editor.org>
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 7C0063A67E3; Sun, 25 Jul 2010 02:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.125
X-Spam-Level: 
X-Spam-Status: No, score=-2.125 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-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 dMNKvIPq91gL; Sun, 25 Jul 2010 02:15:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id C55383A68DF; Sun, 25 Jul 2010 02:15:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 63562E06A6; Sun, 25 Jul 2010 02:15:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100725091537.63562E06A6@rfc-editor.org>
Date: Sun, 25 Jul 2010 02:15:37 -0700 (PDT)
Cc: morg@ietf.org, rfc-editor@rfc-editor.org
Subject: [MORG] RFC 5957 on Display-Based Address Sorting for the IMAP4 SORT Extension
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/mail-archive/web/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>
X-List-Received-Date: Sun, 25 Jul 2010 09:15:19 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5957

        Title:      Display-Based Address Sorting for the 
                    IMAP4 SORT Extension 
        Author:     D. Karp
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2010
        Mailbox:    dkarp@zimbra.com
        Pages:      5
        Characters: 8709
        Updates:    RFC5256

        I-D Tag:    draft-ietf-morg-sortdisplay-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5957.txt

This document describes an IMAP protocol extension enabling server-
side message sorting on the commonly displayed portion of the From
and To header fields.  [STANDARDS TRACK]

This document is a product of the Message Organization Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From alexey.melnikov@isode.com  Wed Jul 28 05:26:04 2010
Return-Path: <alexey.melnikov@isode.com>
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 8B8413A68F6 for <morg@core3.amsl.com>; Wed, 28 Jul 2010 05:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.384
X-Spam-Level: 
X-Spam-Status: No, score=-2.384 tagged_above=-999 required=5 tests=[AWL=-0.385, BAYES_00=-2.599, J_CHICKENPOX_65=0.6]
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 FH2Agm0pI2tZ for <morg@core3.amsl.com>; Wed, 28 Jul 2010 05:26:03 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 6D85928C0F0 for <morg@ietf.org>; Wed, 28 Jul 2010 05:26:03 -0700 (PDT)
Received: from [192.168.49.3] ((unknown) [130.129.80.30])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TFAh7gADG4A7@rufus.isode.com>; Wed, 28 Jul 2010 13:26:24 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4C5021F0.5020002@isode.com>
Date: Wed, 28 Jul 2010 14:26:24 +0200
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090303 SeaMonkey/1.1.15
To: morg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [MORG] Review of draft-ietf-morg-fuzzy-search-02.txt
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/mail-archive/web/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>
X-List-Received-Date: Wed, 28 Jul 2010 12:26:04 -0000

I think the document is basically fine, but I have a couple of minor 
comments:

In Section 4:
>    If server advertises the ESEARCH capability as defined by [ESEARCH <http://tools.ietf.org/html/draft-ietf-morg-fuzzy-search-02#ref-ESEARCH>],
>   
This is probably minor, but I would say "If server *also* advertises 
....". Because this is in addition to SEARCH=FUZZY.
>    the relevancy scores can be retrieved using the new RELEVANCY return
>    option for SEARCH:
In Section 8 (Security Considerations):
>    This document is believed not to have any security implications.
>   
This is not a proper text for this section, as I don't think this is 
true. It would be better to say that this document doesn't add 
additional security considerations not already present in 
implementations of ESEARCH, SORT, etc.

But maybe we should think harder about this in the case of this document.

From alexey.melnikov@isode.com  Wed Jul 28 05:36:10 2010
Return-Path: <alexey.melnikov@isode.com>
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 D4BA128C10A for <morg@core3.amsl.com>; Wed, 28 Jul 2010 05:36:07 -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.053, 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 f-zLQl+HJpew for <morg@core3.amsl.com>; Wed, 28 Jul 2010 05:36:05 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id E729628C0E8 for <morg@ietf.org>; Wed, 28 Jul 2010 05:36:04 -0700 (PDT)
Received: from [192.168.49.3] ((unknown) [130.129.80.30])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TFAkSgADG5Xt@rufus.isode.com>; Wed, 28 Jul 2010 13:36:27 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4C50244C.8010401@isode.com>
Date: Wed, 28 Jul 2010 14:36:28 +0200
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090303 SeaMonkey/1.1.15
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: morg@ietf.org
Subject: [MORG] THREAD= search return option in draft-ietf-morg-inthread-01.txt
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/mail-archive/web/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>
X-List-Received-Date: Wed, 28 Jul 2010 12:36:10 -0000

Hi Arnt,
> 11. Open Issues
>
>     I left the THREAD= search return option, but I haven't implemented
>     it either. I don't see any use cases for anything other than the
>     default. (At the moment there isn't an example, which is really
>     another way of saying "no use cases".) I want to drop it.
I think this is useful, as it affects outcome of an INTHREAD search. 
However section 3.3 is lacking any example. In particular, it is not 
clear if this option is going to result in an ESEARCH response.


From barryleiba.mailing.lists@gmail.com  Wed Jul 28 07:44:39 2010
Return-Path: <barryleiba.mailing.lists@gmail.com>
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 3DCF828C154 for <morg@core3.amsl.com>; Wed, 28 Jul 2010 07:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.821
X-Spam-Level: 
X-Spam-Status: No, score=-2.821 tagged_above=-999 required=5 tests=[AWL=-0.222, 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 2MVFJAhxqnTN for <morg@core3.amsl.com>; Wed, 28 Jul 2010 07:44:38 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id 090CB28C140 for <morg@ietf.org>; Wed, 28 Jul 2010 07:44:38 -0700 (PDT)
Received: by pzk6 with SMTP id 6so2465234pzk.31 for <morg@ietf.org>; Wed, 28 Jul 2010 07:45:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=1OX+IAziw3+J5H+UEzm/MQodRluoNPCWKkbbUDdbTnU=; b=hDCNebTump6Zhd5I8RpPHLe8oKV6I6wYtfNpRDIOUTDeA2S49yDCIzX7K1A9sS8FjF /QPQD7kFr40W3F+xhzVnmCPPq9Th+1iLUQiFiAkE+EQFYXX7SVEq8vCJjbkZJKBHH2DS LbBRXe6eJS4JbDpjgKDaXibYZVjrOEAizEFWc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=fryXbuNK4TSUCRIequebE8qMbfelDJzLBXSVRBj0w4o3L0lPoYVst5l3I5H9CwqEHY 5E868eUdtYeh84kC7Hfkw+Y8eu3o5bEgInp1oVLryazCpTPiHaJ8gAiJtoizpjgJwGZW FNkSOvfR2UE5T+NLztLzLoMpDtdcRqe8Uyzjc=
MIME-Version: 1.0
Received: by 10.114.122.13 with SMTP id u13mr12757305wac.93.1280328300677;  Wed, 28 Jul 2010 07:45:00 -0700 (PDT)
Received: by 10.42.1.136 with HTTP; Wed, 28 Jul 2010 07:45:00 -0700 (PDT)
In-Reply-To: <4C5021F0.5020002@isode.com>
References: <4C5021F0.5020002@isode.com>
Date: Wed, 28 Jul 2010 10:45:00 -0400
Message-ID: <AANLkTik3ayOVth5v5gVowi8ybtj=k99n=evgt7YZQYzw@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: morg@ietf.org
Subject: Re: [MORG] Review of draft-ietf-morg-fuzzy-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: barryleiba@computer.org
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/mail-archive/web/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>
X-List-Received-Date: Wed, 28 Jul 2010 14:44:39 -0000

> This is not a proper text for this section, as I don't think this is true.
> It would be better to say that this document doesn't add additional security
> considerations not already present in implementations of ESEARCH, SORT, etc.

I agree.

> But maybe we should think harder about this in the case of this document.

We did think about it, and we think it's correct that it doesn't add
additional ones.

Did you have anything specific in mind?

Barry

From cyrus@daboo.name  Fri Jul 30 01:44:39 2010
Return-Path: <cyrus@daboo.name>
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 438EF3A67F9 for <morg@core3.amsl.com>; Fri, 30 Jul 2010 01:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level: 
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[AWL=-0.827, BAYES_20=-0.74]
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 0niavNu1b7Tg for <morg@core3.amsl.com>; Fri, 30 Jul 2010 01:44:36 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id DEDB73A69AA for <morg@ietf.org>; Fri, 30 Jul 2010 01:44:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 05C6C18BB64C9 for <morg@ietf.org>; Fri, 30 Jul 2010 04:44:59 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o9xGUcLNcBtw for <morg@ietf.org>; Fri, 30 Jul 2010 04:44:58 -0400 (EDT)
Received: from dhcp-63f1.meeting.ietf.org (dhcp-63f1.meeting.ietf.org [130.129.99.241]) by daboo.name (Postfix) with ESMTPSA id 0A0ED18BB64BE for <morg@ietf.org>; Fri, 30 Jul 2010 04:44:57 -0400 (EDT)
Date: Fri, 30 Jul 2010 10:44:54 +0200
From: Cyrus Daboo <cyrus@daboo.name>
To: morg@ietf.org
Message-ID: <A199F09978CEADEC3697D0DA@dhcp-63f1.meeting.ietf.org>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1245
Subject: [MORG] Review: draft-ietf-morg-fuzzy-search-02
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/mail-archive/web/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>
X-List-Received-Date: Fri, 30 Jul 2010 08:44:39 -0000

Hi,
I have looked at this document. Some comments:

1) I would like to see an example of a mixed fuzzy/non-fuzzy search, just 
to emphasize that such a thing can happen. e.g.:

C: A01 SEARCH FUZZY SUBJECT "Mulberry" FROM cyrus@daboo.name

FROM - precise match, SUBJECT - fuzzy match

2) I would like it t be clear, that for a "plain" SEARCH response (i.e. no 
relevancy results) that the order of returned results is arbitrary (i.e. 
NOT ordered by relevancy) - I am assuming that that is the intent, but I 
would like it to be clear to client implementors.

3) Security: there should be some discussion about how relevancy rankings 
can be "poisoned" by smart attackers using certain keywords or hidden 
markup in their messages to boost the rankings.

4) Given RFC5255's comparator stuff, is the active comparator expected to 
have any influence on the fuzzy behavior? I am guess not, but it might be 
worth a mention.

5) How are rankings determined when more than one FUZZY is used? I assume 
the server has to use its own logic for aggregating the rankings.

6) Do clients need to care that the FUZZY search key is not distributive, 
e.g.:

FUZZY OR SUBJECT x SUBJECT y != OR FUZZY SUBJECT x FUZZY SUBJECT y

Otherwise OK.

-- 
Cyrus Daboo


From cyrus@daboo.name  Fri Jul 30 02:14:22 2010
Return-Path: <cyrus@daboo.name>
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 9C37F28C27E for <morg@core3.amsl.com>; Fri, 30 Jul 2010 02:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level: 
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[AWL=0.268,  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 Ei2+kHEjoOYZ for <morg@core3.amsl.com>; Fri, 30 Jul 2010 02:14:21 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id 3665F28C268 for <morg@ietf.org>; Fri, 30 Jul 2010 02:14:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id C4DCE18BB6692 for <morg@ietf.org>; Fri, 30 Jul 2010 05:14:45 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43feVx-1dkji for <morg@ietf.org>; Fri, 30 Jul 2010 05:14:45 -0400 (EDT)
Received: from dhcp-63f1.meeting.ietf.org (dhcp-63f1.meeting.ietf.org [130.129.99.241]) by daboo.name (Postfix) with ESMTPSA id 0B5B818BB6683 for <morg@ietf.org>; Fri, 30 Jul 2010 05:14:44 -0400 (EDT)
Date: Fri, 30 Jul 2010 11:14:42 +0200
From: Cyrus Daboo <cyrus@daboo.name>
To: morg@ietf.org
Message-ID: <647A30D3C16706CC3FB27874@dhcp-63f1.meeting.ietf.org>
In-Reply-To: <A199F09978CEADEC3697D0DA@dhcp-63f1.meeting.ietf.org>
References: <A199F09978CEADEC3697D0DA@dhcp-63f1.meeting.ietf.org>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=625
Subject: Re: [MORG] Review: draft-ietf-morg-fuzzy-search-02
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/mail-archive/web/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>
X-List-Received-Date: Fri, 30 Jul 2010 09:14:22 -0000

Hi,
One more issue: how many results should a server return? We allow relevancy 
from 1 to 100, and in theory every message in a mailbox could have a 
ranking of 1 or more. Isn't the typical client use case that it wants just 
the top few rankings? If so, we need to specify how the PARTIAL search 
result code (defined in RFC5267) interacts with RELEVANCY. i.e.:

A02 SEARCH RETURN (RELEVANCY PARTIAL 1:10) FUZZY TEXT "Helo"

means return the top 10 relevant results. So the combination of RELEVANCY 
and PARTIAL would require the server to order the result set before 
applying the partial range matching.

-- 
Cyrus Daboo


From barryleiba.mailing.lists@gmail.com  Fri Jul 30 04:53:17 2010
Return-Path: <barryleiba.mailing.lists@gmail.com>
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 3BF753A692B for <morg@core3.amsl.com>; Fri, 30 Jul 2010 04:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.811
X-Spam-Level: 
X-Spam-Status: No, score=-2.811 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 n1soGYoTCrfK for <morg@core3.amsl.com>; Fri, 30 Jul 2010 04:53:16 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id BF7593A68E8 for <morg@ietf.org>; Fri, 30 Jul 2010 04:53:15 -0700 (PDT)
Received: by gyg8 with SMTP id 8so682269gyg.31 for <morg@ietf.org>; Fri, 30 Jul 2010 04:53:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=F6hpIJ0g3jFWqbatxaDPKI+FRcfoTYB8k6r/Nhv2Ow4=; b=m1z4gMMzQRlnix3SYapTat5UJ/mtXUQu2aUtRkxeSh7LiUVOcXgOpWc65dxPp8IAFJ LUN4pcm2d0J/4UxbBDYKzkpmwTPWKZjow9VpmOhbK9lYkIf/Kadr4oEOXIobjyG1qd/y BHrHCn8pwA0DOrlTIWMOO6mY19i3a+489/Kgo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=njrA5Bglab0OkLxrUit5DPax8llTAABbKxIaXVfCLMyJyNPVvELznGdhFjHvyAbPEg fccBG6azZCwq09N1zIF41SRm2mJh7Y9UmiSbWw/BjDtm/u+J3bCjLucZ0bNLrOQhJH89 Dh926Ka4GjcgFmP0V6RaZY5oiKAJVHFe0p7dI=
MIME-Version: 1.0
Received: by 10.90.101.12 with SMTP id y12mr2099664agb.116.1280490819604; Fri,  30 Jul 2010 04:53:39 -0700 (PDT)
Received: by 10.42.1.136 with HTTP; Fri, 30 Jul 2010 04:53:39 -0700 (PDT)
In-Reply-To: <A199F09978CEADEC3697D0DA@dhcp-63f1.meeting.ietf.org>
References: <A199F09978CEADEC3697D0DA@dhcp-63f1.meeting.ietf.org>
Date: Fri, 30 Jul 2010 07:53:39 -0400
Message-ID: <AANLkTikpxj788+WaFstG_-9+Uu4rmuhzQSfFqUnR_psg@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: text/plain; charset=ISO-8859-1
Cc: morg@ietf.org
Subject: Re: [MORG] Review: draft-ietf-morg-fuzzy-search-02
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: barryleiba@computer.org
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/mail-archive/web/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>
X-List-Received-Date: Fri, 30 Jul 2010 11:53:17 -0000

> 4) Given RFC5255's comparator stuff, is the active comparator expected to
> have any influence on the fuzzy behavior? I am guess not, but it might be
> worth a mention.

I suppose it would be possible for ascii-numeric to have an effect.
< fuzzy header "special-field" "50" > would have different fuzz,
depending upon whether you used ascii-casemap or ascii-numeric.  On
the other hand, I imagine that any fuzzy string search would ignore
case, so specifying ascii-casemap would be unnecessary.

But we already say the server can do anything it wants, so do we
really need to mention this?  I suppose we could add something to that
paragraph, like "including ignoring the comparator".

> 6) Do clients need to care that the FUZZY search key is not distributive,
> e.g.:
>
> FUZZY OR SUBJECT x SUBJECT y != OR FUZZY SUBJECT x FUZZY SUBJECT y

I disagree with your example; I think they are the same, because fuzzy
applies to "OR", so I think it applies to the whole OR clause.

> Isn't the typical client use case that it wants just the top
> few rankings? If so, we need to specify how the PARTIAL search result code
> (defined in RFC5267) interacts with RELEVANCY. i.e.:
>
> A02 SEARCH RETURN (RELEVANCY PARTIAL 1:10) FUZZY TEXT "Helo"
>
> means return the top 10 relevant results. So the combination of RELEVANCY
> and PARTIAL would require the server to order the result set before applying
> the partial range matching.

I'm not sure I like that requirement.  Maybe you have to use SORT if
you want that.  What happens in the general case of PARTIAL?  Might a
client that wants the *newest* 10 results be unhappy if it got the
OLDEST 10?

Barry

From tss@iki.fi  Sat Jul 31 12:32:28 2010
Return-Path: <tss@iki.fi>
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 68D8F3A6A40 for <morg@core3.amsl.com>; Sat, 31 Jul 2010 12:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 9AmCI+qkgLZg for <morg@core3.amsl.com>; Sat, 31 Jul 2010 12:32:24 -0700 (PDT)
Received: from dovecot.org (dovecot.org [62.236.108.70]) by core3.amsl.com (Postfix) with ESMTP id 7DB7E3A69B1 for <morg@ietf.org>; Sat, 31 Jul 2010 12:32:22 -0700 (PDT)
Received: from omppu.lan (bl9-130-60.dsl.telepac.pt [85.242.130.60]) by dovecot.org (Postfix) with ESMTP id CD6C5FA89B5; Sat, 31 Jul 2010 22:32:43 +0300 (EEST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Timo Sirainen <tss@iki.fi>
In-Reply-To: <A199F09978CEADEC3697D0DA@dhcp-63f1.meeting.ietf.org>
Date: Sat, 31 Jul 2010 20:32:41 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA8B3A3A-5450-4D4D-AEE3-970403B2256F@iki.fi>
References: <A199F09978CEADEC3697D0DA@dhcp-63f1.meeting.ietf.org>
To: Cyrus Daboo <cyrus@daboo.name>
X-Mailer: Apple Mail (2.1081)
Cc: morg@ietf.org
Subject: Re: [MORG] Review: draft-ietf-morg-fuzzy-search-02
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/mail-archive/web/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>
X-List-Received-Date: Sat, 31 Jul 2010 19:32:28 -0000

On 30.7.2010, at 9.44, Cyrus Daboo wrote:

> 1) I would like to see an example of a mixed fuzzy/non-fuzzy search, =
just to emphasize that such a thing can happen. e.g.:
>=20
> C: A01 SEARCH FUZZY SUBJECT "Mulberry" FROM cyrus@daboo.name
>=20
> FROM - precise match, SUBJECT - fuzzy match

Added.

> 2) I would like it t be clear, that for a "plain" SEARCH response =
(i.e. no relevancy results) that the order of returned results is =
arbitrary (i.e. NOT ordered by relevancy) - I am assuming that that is =
the intent, but I would like it to be clear to client implementors.

Added the second sentence here:

"The RELEVANCY return option MUST NOT be used unless FUZZY search key is =
also given. Note that SEARCH results aren't sorted by relevancy, SORT is =
needed for that."

(Kind of ugly and bad place, but I just can't figure out anything =
better.)

> 3) Security: there should be some discussion about how relevancy =
rankings can be "poisoned" by smart attackers using certain keywords or =
hidden markup in their messages to boost the rankings.

I'll try to figure out some text about this later..

> 4) Given RFC5255's comparator stuff, is the active comparator expected =
to have any influence on the fuzzy behavior? I am guess not, but it =
might be worth a mention.

Added as suggested by Barry:

"FUZZY search key takes another search key as its argument. Server is =
allowed to perform all matching in an implementation-defined manner for =
this search key, including ignoring the active comparator as defined by =
[RFC5255]. Typically this would be used to search for strings, for =
example:"

> 5) How are rankings determined when more than one FUZZY is used? I =
assume the server has to use its own logic for aggregating the rankings.

Added: "When multiple search keys are matched fuzzily, it's =
server-dependent on how the relevancy score is calculated."

> 6) Do clients need to care that the FUZZY search key is not =
distributive, e.g.:
>=20
> FUZZY OR SUBJECT x SUBJECT y !=3D OR FUZZY SUBJECT x FUZZY SUBJECT y

I agree with Barry, those are the same. Added example:

FUZZY is applied to all search keys when parenthesis or OR is used. For =
example in this search query everything is matched fuzzily:

 C: A03 SEARCH FUZZY OR (SUBJECT work FROM user@example.com) SUBJECT =
home
 S: * SEARCH 2 5
 S: A03 OK Search completed.

From tss@iki.fi  Sat Jul 31 12:38:35 2010
Return-Path: <tss@iki.fi>
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 DB9863A68B9 for <morg@core3.amsl.com>; Sat, 31 Jul 2010 12:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level: 
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=0.930,  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 CQ9PpOhoStP6 for <morg@core3.amsl.com>; Sat, 31 Jul 2010 12:38:35 -0700 (PDT)
Received: from dovecot.org (dovecot.org [62.236.108.70]) by core3.amsl.com (Postfix) with ESMTP id EB4BD3A6873 for <morg@ietf.org>; Sat, 31 Jul 2010 12:38:34 -0700 (PDT)
Received: from omppu.lan (bl9-130-60.dsl.telepac.pt [85.242.130.60]) by dovecot.org (Postfix) with ESMTP id 43768FA8A3A; Sat, 31 Jul 2010 22:39:00 +0300 (EEST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Timo Sirainen <tss@iki.fi>
In-Reply-To: <AANLkTikpxj788+WaFstG_-9+Uu4rmuhzQSfFqUnR_psg@mail.gmail.com>
Date: Sat, 31 Jul 2010 20:38:59 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C80B2463-5A2E-465D-A800-79EA009131AB@iki.fi>
References: <A199F09978CEADEC3697D0DA@dhcp-63f1.meeting.ietf.org> <AANLkTikpxj788+WaFstG_-9+Uu4rmuhzQSfFqUnR_psg@mail.gmail.com>
To: barryleiba@computer.org
X-Mailer: Apple Mail (2.1081)
Cc: morg@ietf.org
Subject: Re: [MORG] Review: draft-ietf-morg-fuzzy-search-02
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/mail-archive/web/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>
X-List-Received-Date: Sat, 31 Jul 2010 19:38:36 -0000

On 30.7.2010, at 12.53, Barry Leiba wrote:

>> Isn't the typical client use case that it wants just the top
>> few rankings? If so, we need to specify how the PARTIAL search result =
code
>> (defined in RFC5267) interacts with RELEVANCY. i.e.:
>>=20
>> A02 SEARCH RETURN (RELEVANCY PARTIAL 1:10) FUZZY TEXT "Helo"
>>=20
>> means return the top 10 relevant results. So the combination of =
RELEVANCY
>> and PARTIAL would require the server to order the result set before =
applying
>> the partial range matching.
>=20
> I'm not sure I like that requirement.  Maybe you have to use SORT if
> you want that.  What happens in the general case of PARTIAL?  Might a
> client that wants the *newest* 10 results be unhappy if it got the
> OLDEST 10?

Yes, I think SORT (RELEVANCY) should be required for that.  RFC 5267 =
isn't super clear on if SORT supports PARTIAL, but I guess it should =
according to ABNF.=
