
From barryleiba.mailing.lists@gmail.com  Thu Jun  3 13:41:50 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 E8F113A68DB; Thu,  3 Jun 2010 13:41:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.086
X-Spam-Level: 
X-Spam-Status: No, score=-3.086 tagged_above=-999 required=5 tests=[AWL=0.913,  BAYES_50=0.001, GB_I_INVITATION=-2, GB_I_LETTER=-2]
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 oul4NLBTFsLz; Thu,  3 Jun 2010 13:41:49 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 8252A3A6781; Thu,  3 Jun 2010 13:41:48 -0700 (PDT)
Received: by fxm6 with SMTP id 6so410142fxm.31 for <multiple recipients>; Thu, 03 Jun 2010 13:41:32 -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 :content-transfer-encoding; bh=yU1z7ZPkm8KzIsS8Z7YmUVhXftzUi4Wp3odRrrUVr+Y=; b=iJogPigFaCulAXu2/gZjNt9gKET9QtTqBcWR89IRLJeCM5OwaOw2qmYQ9UU47pyQFr U0sOqfMZLC/da52q181OZeiZisEm2HV0RF5pbB12az+9Ul9AU4iURoMRQeNKtjip1vEE /j31yYTnX26dGSp0ePfNDc4HQ4s5KogbxTGGA=
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:content-transfer-encoding; b=cXz8W6yIRny5Y93HWxu4IA+FydgbGhgpCCKOA6E5Q+ZY5Co0GjyKJr6ntMQrtN3GwG zCdYtlEVOV7wGfZykXqARhkSY75CMeDFDPJB29gtHGDEhBTTAMch0Ij7ynjiYaxyi5u2 HpsVcPpIybKCko2O+gFl8Wapcn5p7bHvsmHyA=
MIME-Version: 1.0
Received: by 10.223.24.133 with SMTP id v5mr10902935fab.46.1275597691957; Thu,  03 Jun 2010 13:41:31 -0700 (PDT)
Received: by 10.223.122.141 with HTTP; Thu, 3 Jun 2010 13:41:31 -0700 (PDT)
In-Reply-To: <20100603194905.138023A6A09@core3.amsl.com>
References: <20100603194905.138023A6A09@core3.amsl.com>
Date: Thu, 3 Jun 2010 16:41:31 -0400
Message-ID: <AANLkTinayJ5yrFaYas8c8GUw5uZFlIwFaXBbdOQzCv3N@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: vwrap@ietf.org, marf@ietf.org, morg@ietf.org, ietf-dkim@mipassoc.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: [MORG] Fwd: IETF 78 - Meeting and Sponsorship Information
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: Thu, 03 Jun 2010 20:41:51 -0000

Working-group denizens: see the note below, and notice, in particular,
the sponsorship opportunities available at this and other IETF
meetings.  If a company you're associated with might have an interest
in sponsoring IETF activities, please put the appropriate parties in
contact.

And I hope to see many of you in Maastricht.

Barry, as chair, passing on information from above

---------- Forwarded message ----------
From: IETF Secretariat <ietf-secretariat@ietf.org>
Date: Thu, Jun 3, 2010 at 3:49 PM
Subject: IETF 78 - Meeting and Sponsorship Information
To: IETF Announcement list <ietf-announce@ietf.org>


78th IETF Meeting
Maastricht, Netherlands
July 25-30, 2010

1. Sponsorship Opportunities
2. Registration Types
3. Visas and Letters of Invitation
4. Accommodations & Breakfast Information
5. IETF 79 (Beijing) Visa Information

1) Sponsorship Opportunities
There are still sponsorship opportunities and benefits for high profile
company/organizational exposure at the upcoming IETF meeting in
Maastricht, Netherlands from July 25-30, 2010. All sponsorship fees go
directly to fund the operations of the IETF. See the options at:
http://www.ietf.org/meeting/78/index.html =93Sponsorship Opportunities=94
under =93General=94. Each of the sponsorship options provide extended and
repeat exposure at this weeklong meeting.

Please contact Drew Dvorshak, dvorshak@isoc.org, with any questions
and/or to reserve your organization=92s spot. Thanks in advance for
supporting the critical work of the IETF!

2) Register online at: http://www.ietf.org/meetings/78/

3) Letters of Invitation and Visas
Letters of Invitation
After you complete the meeting registration process, you will be given the
option to request a letter of invitation. You can request the Letter of
Invitation as soon as you finish registration, or at a later time by
following the link provided in the confirmation email.

Visas
Please check the Netherlands Ministry of Foreign Affairs site
(http://www.minbuza.nl/en/Services/Consular_Services/Visa) for list of
countries with visa exemptions.

We recommend you give yourself at least one month to complete the visa
process.

4) Accommodations & Breakfast Information
http://www.ietf.org/meeting/78/hotel.html

5) If you want to start planning for your trip to IETF 79 in Beijing, we
have visa information online here:
http://www.ietf.org/meeting/79/visa.html

Only 52 days until IETF 78!


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From cyrus@daboo.name  Fri Jun 11 14:54:18 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 BC0A53A697D for <morg@core3.amsl.com>; Fri, 11 Jun 2010 14:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.359
X-Spam-Level: 
X-Spam-Status: No, score=-4.359 tagged_above=-999 required=5 tests=[AWL=-1.760, 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 NtDCuUYyD3Dt for <morg@core3.amsl.com>; Fri, 11 Jun 2010 14:54:17 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id D1ECB3A6783 for <morg@ietf.org>; Fri, 11 Jun 2010 14:54:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 6FB99173B21C1; Fri, 11 Jun 2010 17:54:17 -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 OOwBi-BiUkMX; Fri, 11 Jun 2010 17:54:12 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id 8A0A3173B21B6; Fri, 11 Jun 2010 17:54:11 -0400 (EDT)
Date: Fri, 11 Jun 2010 17:54:07 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: morg@ietf.org
Message-ID: <952BA2147FD12E9EABAD77E4@caldav.corp.apple.com>
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=1762
Cc: witold.krecicki@firma.o2.pl
Subject: [MORG] I-D Action:draft-krecicki-imap-move-01.txt  (fwd)
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, 11 Jun 2010 21:54:18 -0000

Hi,
I noticed the draft announcement below. Whilst not strictly a work item of 
this working group (though one could argue it fails under the "secondary 
goal" part of the charter), I think it is worth discussing this draft on 
this list (since most of the other imap lists are dormant).

My thoughts: yes it is about time we had such an extension. Minimising 
roundtrips for one of the most common filing operations a client does is a 
good thing - particularly for mobile devices. It would be good to hear what 
server implementors think of this as the burden is really on them to do all 
the work here.

------------ Forwarded Message -----------
Date: June 11, 2010 2:15:02 PM -0700
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-krecicki-imap-move-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title           : Internet Message Access Protocol (IMAP) - MOVE extension
	Author(s)       : W. Krecicki
	Filename        : draft-krecicki-imap-move-01.txt
	Pages           : 5
	Date            : 2010-06-11

The MOVE extension of the Internet Message Access Protocol [IMAP4]
provides a feature intended to reduce the amount of time and
resources used by usual complicated methods of moving messages
between mailboxes by providing the capability of directly moving
messages.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-krecicki-imap-move-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.

---------- End Forwarded Message ----------



-- 
Cyrus Daboo


From cyrus@daboo.name  Fri Jun 11 18:36: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 0F0DD3A67EC for <morg@core3.amsl.com>; Fri, 11 Jun 2010 18:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 QbdxR+v+i-ka for <morg@core3.amsl.com>; Fri, 11 Jun 2010 18:36:38 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id 2554F3A67B7 for <morg@ietf.org>; Fri, 11 Jun 2010 18:36:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 42602173CEF8D; Fri, 11 Jun 2010 21:36:39 -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 T7ihKBKwBg35; Fri, 11 Jun 2010 21:36:38 -0400 (EDT)
Received: from [10.0.1.5] (unknown [10.0.1.1]) by daboo.name (Postfix) with ESMTPSA id 33582173CEF82; Fri, 11 Jun 2010 21:36:38 -0400 (EDT)
Date: Fri, 11 Jun 2010 21:36:36 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: morg@ietf.org
Message-ID: <37AE7A43660AD70735C37F6D@socrates.local>
In-Reply-To: <952BA2147FD12E9EABAD77E4@caldav.corp.apple.com>
References: <952BA2147FD12E9EABAD77E4@caldav.corp.apple.com>
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=516
Cc: witold.krecicki@firma.o2.pl
Subject: Re: [MORG] I-D Action:draft-krecicki-imap-move-01.txt (fwd)
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, 12 Jun 2010 01:36:39 -0000

Hi,

--On June 11, 2010 5:54:07 PM -0400 Cyrus Daboo <cyrus@daboo.name> wrote:

> I noticed the draft announcement below. Whilst not strictly a work item
> of this working group (though one could argue it fails under the
> "secondary goal" part of the charter), I think it is worth discussing
> this draft on this list (since most of the other imap lists are dormant).

Apparently discussion is happening on the imap-protocol list (which I seem 
to not be subscribed to) so ignore my comments here.

-- 
Cyrus Daboo


From dkarp@zimbra.com  Sat Jun 12 09:22:59 2010
Return-Path: <dkarp@zimbra.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 E35A63A6986 for <morg@core3.amsl.com>; Sat, 12 Jun 2010 09:22:58 -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 W2WWf0+yeV9e for <morg@core3.amsl.com>; Sat, 12 Jun 2010 09:22:57 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id E0C7F3A6981 for <morg@ietf.org>; Sat, 12 Jun 2010 09:22:57 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 54A0CC78058; Sat, 12 Jun 2010 09:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VR6Es3tm+-eJ; Sat, 12 Jun 2010 09:21:06 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id C0D90C78054; Sat, 12 Jun 2010 09:21:06 -0700 (PDT)
Date: Sat, 12 Jun 2010 09:22:52 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: Cyrus Daboo <cyrus@daboo.name>
Message-ID: <981716043.1728.1276359772407.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <37AE7A43660AD70735C37F6D@socrates.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.7_GA_2470.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2470.RHEL4_64)
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-krecicki-imap-move-01.txt (fwd)
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, 12 Jun 2010 16:22:59 -0000

> > I noticed the draft announcement below. Whilst not strictly a work
> > item of this working group (though one could argue it fails under
> > the "secondary goal" part of the charter), I think it is worth
> > discussing this draft on this list (since most of the other imap
> > lists are dormant).
> 
> Apparently discussion is happening on the imap-protocol list (which I
> seem to not be subscribed to) so ignore my comments here.

As an aside -- and because I have no desire to get involved with the
discussion on imap-protocol -- I would be willing to implement such
an extension if it were properly formalized.  And I do think it's 
well within the scope of MORG.

From root@core3.amsl.com  Fri Jun 18 13: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 9C5163A6879; Fri, 18 Jun 2010 13:15:02 -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: <20100618201504.9C5163A6879@core3.amsl.com>
Date: Fri, 18 Jun 2010 13:15:02 -0700 (PDT)
Cc: morg@ietf.org
Subject: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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: Fri, 18 Jun 2010 20:15:08 -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           : IMAP4 Multimailbox SEARCH Extension
	Author(s)       : B. Leiba, A. Melnikov
	Filename        : draft-ietf-morg-multimailbox-search-03.txt
	Pages           : 10
	Date            : 2010-06-18

The IMAP4 specification allows the searching only of the selected
mailbox.  A user often wants to search multiple mailboxes, and a
client that wishes to support this must issue a series of SELECT and
SEARCH commands, waiting for each to complete before moving on to the
next.  This extension allows a client to search multiple mailboxes
with one command, limiting the round-trips and waiting for various
searches to complete, and not requiring disruption of the currently
selected mailbox.  This also uses MAILBOX and TAG fields in ESEARCH
responses, allowing a client to pipeline the searches if it chooses.

Note

A revised version of this draft document will be submitted to the RFC
editor as a Proposed Standard for the Internet Community.  Discussion
and suggestions for improvement are requested, and should be sent to
morg@ietf.org.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-morg-multimailbox-search-03.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-multimailbox-search-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From root@core3.amsl.com  Fri Jun 18 13:30:14 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 C91133A6947; Fri, 18 Jun 2010 13:30:02 -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: <20100618203009.C91133A6947@core3.amsl.com>
Date: Fri, 18 Jun 2010 13:30:02 -0700 (PDT)
Cc: morg@ietf.org
Subject: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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: Fri, 18 Jun 2010 20:30:14 -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           : IMAP LIST extension for special-use mailboxes
	Author(s)       : B. Leiba, J. Nicolson
	Filename        : draft-ietf-morg-list-specialuse-02.txt
	Pages           : 9
	Date            : 2010-06-18

Some IMAP message stores include special-use mailboxes, such as those
used to hold draft messages or sent messages.  Many mail clients
allow users to specify where draft or sent messages should be put,
but configuring them requires that the user know which mailboxes the
server has set aside for these purposes.  This extension adds new
mailbox flags that a server MAY include in IMAP LIST command
responses to identify special-use mailboxes to the client, easing
configuration.

Note

A revised version of this draft document will be submitted to the RFC
editor as a Proposed Standard for the Internet Community.  Discussion
and suggestions for improvement are requested, and should be sent to
morg@ietf.org.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-morg-list-specialuse-02.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-list-specialuse-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From barryleiba.mailing.lists@gmail.com  Fri Jun 18 13:34:38 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 3D8E63A6960 for <morg@core3.amsl.com>; Fri, 18 Jun 2010 13:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.732
X-Spam-Level: 
X-Spam-Status: No, score=-1.732 tagged_above=-999 required=5 tests=[AWL=0.867,  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 WZmFYLDUUEAP for <morg@core3.amsl.com>; Fri, 18 Jun 2010 13:34:37 -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 59D983A699D for <morg@ietf.org>; Fri, 18 Jun 2010 13:34:37 -0700 (PDT)
Received: by gyh4 with SMTP id 4so1225347gyh.31 for <morg@ietf.org>; Fri, 18 Jun 2010 13:34:39 -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 :content-transfer-encoding; bh=uVMB+fUjZ26MbVmU9DeOSuUF3Rtz0DVoM93hOf48ObM=; b=NiPTwKPqiP4kyjjmIEh5Vk47eVmFt1kytNBTQUmkB2L92MhlFi5mIPTWCvpE4hWEuL qQcep9OUjxC37/cEZ7T/dxkEz8VHlx4Ld/jmFD505Uaoyo7P7+7VXJnxbGRPjFmnBUsB gqJeJiTWlL4wzrp97hYt5gg3WnX5cxJTxSS5U=
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:content-transfer-encoding; b=TpWLTSraqU5ByO4rTS1EHbdPIVN1xVbl4B22Naf+PFpiMqvEdrusw62fHJj02iuXD+ kg08C/cOswNdiDonfX/OgJWlVzGoIlLEr3O8Z5JoHUFh5IAhgita+kNY0f79N5souIoU H5zVGTAo/QvSFwU182EQfwnkMvgPAJ/v075ts=
MIME-Version: 1.0
Received: by 10.220.126.200 with SMTP id d8mr699064vcs.41.1276893279284; Fri,  18 Jun 2010 13:34:39 -0700 (PDT)
Received: by 10.220.91.40 with HTTP; Fri, 18 Jun 2010 13:34:39 -0700 (PDT)
In-Reply-To: <20100618203009.C91133A6947@core3.amsl.com>
References: <20100618203009.C91133A6947@core3.amsl.com>
Date: Fri, 18 Jun 2010 16:34:39 -0400
Message-ID: <AANLkTinVA20mz9f6Kdr6RxAS7zVbQzin4W80BKzLr4qB@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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: Fri, 18 Jun 2010 20:34:38 -0000

> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Message Organization Working Group of th=
e IETF.
>
> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : IMAP LIST extension for specia=
l-use mailboxes
> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : B. Leiba, J. Nicolson
> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-morg-list-specialuse-=
02.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 9
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-06-18

> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-morg-list-specialuse-02.tx=
t

This draft should now be ready to go.  I'm going to initiate
working-group last call on it now, to finish in two weeks, on 2 July
2010.

Everyone: please review it, and please post to this thread.  Please
post any requested changes here, and be specific about the changes and
the text.  Please also post if you have reviewed it and you think it's
OK.  We need to know how many people have reviewed it and want to move
it ahead.

Again: please review this document and post to this thread by 2 July
2010, WHETHER OR NOT you have any issues.

Barry, as chair

From barryleiba.mailing.lists@gmail.com  Fri Jun 18 13:40:41 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 E4C493A69D1 for <morg@core3.amsl.com>; Fri, 18 Jun 2010 13:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  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 heLFQab6TYJb for <morg@core3.amsl.com>; Fri, 18 Jun 2010 13:40:32 -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 A861E3A695F for <morg@ietf.org>; Fri, 18 Jun 2010 13:40:30 -0700 (PDT)
Received: by gyh4 with SMTP id 4so1230244gyh.31 for <morg@ietf.org>; Fri, 18 Jun 2010 13:40:33 -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 :content-transfer-encoding; bh=Xm1ms5TyHzzvPu1aeQBMY62JhKniSB+xvpRCirUO3X4=; b=Gasj8M8wzP+0k1jrNnhUlS/N5U6XjWFsL/RCeGlodQddXvefx6acyvdIUam8cEB2iV GP1pQdMH0z2Tl3dvo+F+s2i3xtjhqMzhrpXhTkeiLTV57Pyn2eq/cHVPUAt+lhnGTySK dwOT+wg1M4IrW8m6iqrOj4jcwU01FQ07h7I6k=
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:content-transfer-encoding; b=qmfH4abl6i3EPRZWDPHpl67jq0PsCa0gzko9+BldR4brJ7l15FNUK9RYgUCuepm+PE a/MgNa5f0uOIUTUudjViurcxLoDO7vez7a+XPgoTwUeiqrTPaicf3iEPha+0kPVFDDWE xWRilS4cNh183vBMySDjSGBBG8dzP0YKZ08qk=
MIME-Version: 1.0
Received: by 10.220.47.22 with SMTP id l22mr678546vcf.83.1276893632999; Fri,  18 Jun 2010 13:40:32 -0700 (PDT)
Received: by 10.220.91.40 with HTTP; Fri, 18 Jun 2010 13:40:32 -0700 (PDT)
In-Reply-To: <20100618201504.9C5163A6879@core3.amsl.com>
References: <20100618201504.9C5163A6879@core3.amsl.com>
Date: Fri, 18 Jun 2010 16:40:32 -0400
Message-ID: <AANLkTimXlKThnLRtkxdDOhdMv0cvCxKa1s9Nff8J8zuh@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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: Fri, 18 Jun 2010 20:40:42 -0000

On Fri, Jun 18, 2010 at 4:15 PM,  <Internet-Drafts@ietf.org> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Message Organization Working Group of th=
e IETF.
>
> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : IMAP4 Multimailbox SEARCH Exte=
nsion
> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : B. Leiba, A. Melnikov
> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-morg-multimailbox-sea=
rch-03.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 10
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-06-18

> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-morg-multimailbox-search-0=
3.txt

This document is almost done, but still has a few open issues, noted
in the "open issues" section.  Timo responded in February:
   http://www.ietf.org/mail-archive/web/morg/current/msg00308.html
...but there was no discussion of his comments.  I want to finish this
and resolve the open issues, so everyone, please help with this.

>> Interaction with IMAP Contexts [RFC5267] needs to be defined.
>
> I guess server then just has to monitor all matched mailboxes and send
> updates whenever they happen. But should it notice newly created/renamed
> mailboxes? Maybe the answer is no, except if NOTIFY is also used:
>
>>    Suggestion: UPDATE option of IMAP Notify [RFC5465] might have to be
>>    prohibited when both Context and this extension are used.  [Barry:
>>    But why?  Isn't this then the equivalent of doing many SEARCH
>>    commands with the UPDATE option?]
>
> I guess the problem is if NOTIFY's extended UPDATE should be allowed.
> Sending FETCH replies for messages matching in non-selected mailboxes
> wouldn't work. But the solution could be just that the FETCH replies are
> sent only to messages in selected mailbox, whichever it happens to be at
> the time changes happen.

Does anyone have other comments here?  Can anyone suggest text, if
there's text that needs to be added?

>> There's a suggestion to add an EXCLUDE clause (with a nested search
>>    criteria).  For example, one might want to search "personal" but
>>    exclude "mailboxes (Trash Spam)".
>>
>>    Cyrus suggests you can use metadata to tag mailboxes that you do or
>>    don't want to search, and use search criteria to exclude them (good
>>    for mailboxes that you NEVER want searched (as Trash and Spam,
>>    above)).
>
> Dunno. A 3rd possibility would be to make the IN a search-key, but
> perhaps that would make things too complex again. It would anyway allow
> e.g.:
>
> SEARCH unseen IN (personal) NOT IN (mailboxes "Spam" subtree "Trash")

My sense here is that we can (and should) defer this to a future
extension, if it turns out to be needed.  My sense is that it isn't
strongly needed.

>> C: tag1 SEARCH IN ((mailboxes "folder1" subtree "folder2")) unseen
>>    C: tag2 SEARCH IN ((mailboxes "folder1" subtree-one "folder2"))
>
> Double (( )) doesn't seem correct?

Can someone check the formal grammar for me?  I wrote the text based
on what I saw in the grammar, and my eyes are now glazing over on it.
Help, please, to make sure it's right.

Barry, as document editor

From morg@dankeen.com  Fri Jun 18 13:56:02 2010
Return-Path: <morg@dankeen.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 34BE63A6896 for <morg@core3.amsl.com>; Fri, 18 Jun 2010 13:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 7UBPlZ3Zdl0d for <morg@core3.amsl.com>; Fri, 18 Jun 2010 13:56:00 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 3A3EB3A68BE for <morg@ietf.org>; Fri, 18 Jun 2010 13:56:00 -0700 (PDT)
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id 0E2529F5F57A for <morg@ietf.org>; Fri, 18 Jun 2010 13:56:06 -0700 (PDT)
X-AuditID: 11807130-b7cd0ae00000795d-93-4c1bdd65dd50
Received: from browncoat.apple.com (browncoat.apple.com [17.202.32.50]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id 06.29.31069.66DDB1C4; Fri, 18 Jun 2010 13:56:06 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
From: Dan Keen <morg@dankeen.com>
In-Reply-To: <AANLkTinVA20mz9f6Kdr6RxAS7zVbQzin4W80BKzLr4qB@mail.gmail.com>
Date: Fri, 18 Jun 2010 13:56:05 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <99B0FF5A-770F-433E-AE1C-91189B9C5D0A@dankeen.com>
References: <20100618203009.C91133A6947@core3.amsl.com> <AANLkTinVA20mz9f6Kdr6RxAS7zVbQzin4W80BKzLr4qB@mail.gmail.com>
To: morg@ietf.org
X-Mailer: Apple Mail (2.1078)
X-Brightmail-Tracker: AAAAAQAAAZE=
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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: Fri, 18 Jun 2010 20:56:02 -0000

On Jun 18, 2010, at 1:34 PM, Barry Leiba wrote:

>> 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.
>>=20
>>        Title           : IMAP LIST extension for special-use =
mailboxes
>>        Author(s)       : B. Leiba, J. Nicolson
>>        Filename        : draft-ietf-morg-list-specialuse-02.txt
>>        Pages           : 9
>>        Date            : 2010-06-18
>=20
>> A URL for this Internet-Draft is:
>> =
http://www.ietf.org/internet-drafts/draft-ietf-morg-list-specialuse-02.txt=

>=20
> Everyone: please review it, and please post to this thread.  Please
> post any requested changes here, and be specific about the changes and
> the text.  Please also post if you have reviewed it and you think it's
> OK.  We need to know how many people have reviewed it and want to move
> it ahead.

This doesn't seem to cover the request in the room:

> Proposal: leave CREATE option, don't add any non-metadata way to add =
special-use tag, define metadata way (registry) to add or change special =
use tags (if you support METADATA, we will give a reserved item for this =
function).  No objection in room; adopted.

We've left CREATE (good), but there's no way to alter an existent =
mailbox to become special use.

D=

From dkarp@zimbra.com  Fri Jun 18 14:18:36 2010
Return-Path: <dkarp@zimbra.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 349323A696D for <morg@core3.amsl.com>; Fri, 18 Jun 2010 14:18:36 -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 wcSkobGZdzAh for <morg@core3.amsl.com>; Fri, 18 Jun 2010 14:18:35 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id 4817E3A6929 for <morg@ietf.org>; Fri, 18 Jun 2010 14:18:35 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 43C96C78575; Fri, 18 Jun 2010 14:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qG5v6hjABpAh; Fri, 18 Jun 2010 14:16:42 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id B368FC781D8; Fri, 18 Jun 2010 14:16:42 -0700 (PDT)
Date: Fri, 18 Jun 2010 14:18:33 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: barryleiba@computer.org
Message-ID: <654003389.1457.1276895913357.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <AANLkTinVA20mz9f6Kdr6RxAS7zVbQzin4W80BKzLr4qB@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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: Fri, 18 Jun 2010 21:18:36 -0000

> > =C2=A0 =C2=A0 =C2=A0 =C2=A0Title : IMAP LIST extension for special-use =
mailboxes
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0Author(s) : B. Leiba, J. Nicolson
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0Filename : draft-ietf-morg-list-specialuse-0=
2.txt
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0Pages : 9
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0Date : 2010-06-18
>=20
> Everyone: please review it, and please post to this thread. Please
> post any requested changes here, and be specific about the changes and
> the text. Please also post if you have reviewed it and you think it's
> OK. We need to know how many people have reviewed it and want to move
> it ahead.

You need a CAPABILITY string to let clients know that they can issue an
extended LIST command with RETURN (SPECIAL-USE).  RFC 5258 mandates it:

   Both selection and return command options will be defined in this
   document and in approved extension documents; each option will be
   enabled by a capability string (one capability may enable multiple
   options), and a client MUST NOT send an option for which the server
   has not advertised support.  A server MUST respond to options it does
   not recognize with a BAD response.

Also, you've got a typo (missing the I in SPECIAL):

     C: t1 LIST "" "%" RETURN (SPECAL-USE)

From dkarp@zimbra.com  Fri Jun 18 19:27:39 2010
Return-Path: <dkarp@zimbra.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 CC0213A681C for <morg@core3.amsl.com>; Fri, 18 Jun 2010 19:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  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 XuwIdOS3P0Ja for <morg@core3.amsl.com>; Fri, 18 Jun 2010 19:27:39 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id 1173F3A67D9 for <morg@ietf.org>; Fri, 18 Jun 2010 19:27:39 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id B17ACC785B9; Fri, 18 Jun 2010 19:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a7Y5HsQjeD8c; Fri, 18 Jun 2010 19:25:46 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id 33184C7858D; Fri, 18 Jun 2010 19:25:46 -0700 (PDT)
Date: Fri, 18 Jun 2010 19:27:37 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: barryleiba@computer.org
Message-ID: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <654003389.1457.1276895913357.JavaMail.root@dogfood.zimbra.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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: Sat, 19 Jun 2010 02:27:39 -0000

> You need a CAPABILITY string to let clients know that they can
> issue an extended LIST command with RETURN (SPECIAL-USE).

Alternatively, you could have extended LIST work like regular LIST
and always include the special-use flags in the untagged responses.

And what happened to the proposal to have a SPECIAL-USE *selection*
criterion for extended LIST, which would filter the responses to
include only those mailboxes with special-use flags set on them?

From tss@iki.fi  Tue Jun 22 15:49:46 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 6B03528C10E for <morg@core3.amsl.com>; Tue, 22 Jun 2010 15:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 oeb69l5Ch1dN for <morg@core3.amsl.com>; Tue, 22 Jun 2010 15:49:41 -0700 (PDT)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 9434A3A6A0A for <morg@ietf.org>; Tue, 22 Jun 2010 15:49:39 -0700 (PDT)
Received: from omppu.lan (bl4-153-222.dsl.telepac.pt [81.193.153.222]) by dovecot.org (Postfix) with ESMTP id 8D4D9FA89D8; Wed, 23 Jun 2010 01:49:44 +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: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com>
Date: Tue, 22 Jun 2010 23:49:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi>
References: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com>
To: Dan Karp <dkarp@zimbra.com>
X-Mailer: Apple Mail (2.1081)
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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: Tue, 22 Jun 2010 22:49:46 -0000

On 19.6.2010, at 3.27, Dan Karp wrote:

> And what happened to the proposal to have a SPECIAL-USE *selection*
> criterion for extended LIST, which would filter the responses to
> include only those mailboxes with special-use flags set on them?

Yes, I think it's more useful as selection criteria. The return option =
seems a bit pointless to me. A selection criteria would still need a =
capability though.

Also, should a failed CREATE USE have a resp-code, so clients could =
determine if the problem was the mailbox name or the USE flag? Like: "NO =
[NOUSE] \All not supported".

(Maybe with the above change it would be possible to have only a single =
capability for the selection criteria and CREATE? Although could be a =
bit annoying for clients if they didn't know until after CREATE if the =
USE was supported.)

Other than that, it looks ok to me.=

From alexey.melnikov@isode.com  Tue Jun 22 15:53:26 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 7D9AE3A6A12 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 15:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=0.375,  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 9b5TJwK-gygP for <morg@core3.amsl.com>; Tue, 22 Jun 2010 15:53:25 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 7C10A3A68A0 for <morg@ietf.org>; Tue, 22 Jun 2010 15:53:25 -0700 (PDT)
Received: from [188.28.86.64] (188.28.86.64.threembb.co.uk [188.28.86.64])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TCE-5wAJf3hD@rufus.isode.com>; Tue, 22 Jun 2010 23:53:30 +0100
Message-ID: <4C213EC2.60200@isode.com>
Date: Tue, 22 Jun 2010 23:52:50 +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: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com> <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi>
In-Reply-To: <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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: Tue, 22 Jun 2010 22:53:26 -0000

Timo Sirainen wrote:

>On 19.6.2010, at 3.27, Dan Karp wrote:
>  
>
>>And what happened to the proposal to have a SPECIAL-USE *selection*
>>criterion for extended LIST, which would filter the responses to
>>include only those mailboxes with special-use flags set on them?
>>    
>>
>Yes, I think it's more useful as selection criteria. The return option seems a bit pointless to me.
>
It is only useless if the server always returns the new attributes in an 
unextended LIST response.

I think we need both.

>A selection criteria would still need a capability though.
>
>Also, should a failed CREATE USE have a resp-code, so clients could determine if the problem was the mailbox name or the USE flag? Like: "NO [NOUSE] \All not supported".
>  
>
I was about to make the same suggestion.

>(Maybe with the above change it would be possible to have only a single capability for the selection criteria and CREATE?
>
Yes, I think it would be worth just to have 1 capability for both.

>Although could be a bit annoying for clients if they didn't know until after CREATE if the USE was supported.)
>
>Other than that, it looks ok to me.
>  
>


From dkarp@zimbra.com  Tue Jun 22 16:13:49 2010
Return-Path: <dkarp@zimbra.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 7605A3A6A2B for <morg@core3.amsl.com>; Tue, 22 Jun 2010 16:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  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 G5ZMqCGQ2+PY for <morg@core3.amsl.com>; Tue, 22 Jun 2010 16:13:48 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id 373FD3A67AC for <morg@ietf.org>; Tue, 22 Jun 2010 16:13:47 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 8D9CBC78278; Tue, 22 Jun 2010 16:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CcmMByw4Bt3u; Tue, 22 Jun 2010 16:12:02 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id 12D4AC78243; Tue, 22 Jun 2010 16:12:02 -0700 (PDT)
Date: Tue, 22 Jun 2010 16:13:55 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <456821268.5231.1277248435893.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <4C213EC2.60200@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org, barryleiba@computer.org, Timo Sirainen <tss@iki.fi>
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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: Tue, 22 Jun 2010 23:13:49 -0000

> >(Maybe with the above change it would be possible to have only a
> >single capability for the selection criteria and CREATE?
> >
> Yes, I think it would be worth just to have 1 capability for both.

Then how would a client differentiate servers that allow them to
create special-use mailboxes from those that don't?

From barryleiba.mailing.lists@gmail.com  Tue Jun 22 17:22:57 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 45FD63A68C4 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 17:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  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 wP1NItoF2GMq for <morg@core3.amsl.com>; Tue, 22 Jun 2010 17:22:56 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 256943A680F for <morg@ietf.org>; Tue, 22 Jun 2010 17:22:56 -0700 (PDT)
Received: by vws15 with SMTP id 15so113919vws.31 for <morg@ietf.org>; Tue, 22 Jun 2010 17:23: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:content-type; bh=yfwkkCkrjV5D7p8RcPnhshl2wg9QGtdKfKa8q83vDxA=; b=x/0n+8D0rG1COx5dlKwB4d/PvxrFKHj3chLlvt+o+Ss9Th4cC2MI7gU0I67jWZoJFI egjMQA+7mX8GWo2oX+pVB/xbUBQCJaHmHIK8HX3kBv9gPrvrpWA3ud1r4sa80fKkocek SZr67W+WbvUZQ9AHNYsJiguHtiHkKsPhrvCHw=
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=CjNfc6Vu4LzvRY9zYtj0sADSQgLaMYyLZTXPZzQ9SXe7+jqhEhATJMbPaeXynyPZub GWvE4LPwhdGndEz8sIKqE8g+PMgiZjXvcM8veKgRppL5Vy+XSzQum1ihknPVDPwtCsY2 JgB08kQhiOcWWT6d7nkLs+K8zwosIF2hAOorE=
MIME-Version: 1.0
Received: by 10.220.63.203 with SMTP id c11mr3598678vci.94.1277252581105; Tue,  22 Jun 2010 17:23:01 -0700 (PDT)
Received: by 10.220.91.40 with HTTP; Tue, 22 Jun 2010 17:23:01 -0700 (PDT)
In-Reply-To: <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi>
References: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com> <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi>
Date: Tue, 22 Jun 2010 20:23:01 -0400
Message-ID: <AANLkTinL2qLU5RZVrxzfUo2QW3dB80H9SBbmC9axDOpy@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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, 23 Jun 2010 00:22:57 -0000

Dan says...
> You need a CAPABILITY string to let clients know that they can
> issue an extended LIST command with RETURN (SPECIAL-USE).

Yes; I've put that in my latest version.

> Alternatively, you could have extended LIST work like regular LIST
> and always include the special-use flags in the untagged responses.

I don't think there's a lot of value in that.  A main point of LISText
is that you ask for what you want.

> And what happened to the proposal to have a SPECIAL-USE *selection*
> criterion for extended LIST, which would filter the responses to
> include only those mailboxes with special-use flags set on them?

Timo says...

> Yes, I think it's more useful as selection criteria. The return option seems
> a bit pointless to me. A selection criteria would still need a capability though.

As Alexey says, I think we need both.  We can use the same capability
string for both, as well.

> Also, should a failed CREATE USE have a resp-code, so clients could
> determine if the problem was the mailbox name or the USE flag? Like:
> "NO [NOUSE] \All not supported".

Mm, good point.  I can add that.

> (Maybe with the above change it would be possible to have only a single
> capability for the selection criteria and CREATE? Although could be a bit
> annoying for clients if they didn't know until after CREATE if the USE was
> supported.)

I differ from Alexey here: I think we need two capabilities, one for
LISText and one for CREATE.  IMAP has generally been careful NOT to
set things up so you have to try commands to see whether they work.
It's not terribly expensive to have both.  Maybe I'll make the strings
"list-specialuse" and "create-specialuse".

Barry

From dkarp@zimbra.com  Tue Jun 22 18:01:03 2010
Return-Path: <dkarp@zimbra.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 989593A6907 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 18:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325,  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 v1xD92I0WPxg for <morg@core3.amsl.com>; Tue, 22 Jun 2010 18:01:02 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id E90E03A67EA for <morg@ietf.org>; Tue, 22 Jun 2010 18:01:02 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 559DAC7846C; Tue, 22 Jun 2010 17:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ujKacKzi+pV9; Tue, 22 Jun 2010 17:59:08 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id D447BC78296; Tue, 22 Jun 2010 17:59:08 -0700 (PDT)
Date: Tue, 22 Jun 2010 18:01:02 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: barryleiba@computer.org
Message-ID: <193904168.5312.1277254862884.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <AANLkTimXlKThnLRtkxdDOhdMv0cvCxKa1s9Nff8J8zuh@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 01:01:03 -0000

> > =C2=A0 =C2=A0 =C2=A0 =C2=A0Title : IMAP4 Multimailbox SEARCH Extension
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0Author(s) : B. Leiba, A. Melnikov
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0Filename : draft-ietf-morg-multimailbox-sear=
ch-03.txt
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0Pages : 10
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0Date : 2010-06-18

Looking back at the discussion of the previous draft, I'm with Arnt.
I'm really not comfortable with allowing MSNs in the UID SEARCH
criteria of a multimailbox search.  UIDs are designed as persistent
outside the context of a SELECT/EXPUNGE.  MSNs are expressly tied
to a SELECT/EXPUNGE session.  Absent a session, there's no sequence
to reference.

From mrc+ietf@panda.com  Tue Jun 22 18:22:19 2010
Return-Path: <mrc+ietf@panda.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 854F23A67BD for <morg@core3.amsl.com>; Tue, 22 Jun 2010 18:22:19 -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 7aja6dqG3fes for <morg@core3.amsl.com>; Tue, 22 Jun 2010 18:22:18 -0700 (PDT)
Received: from panda.com (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id 1F29A3A68DC for <morg@ietf.org>; Tue, 22 Jun 2010 18:22:18 -0700 (PDT)
Received: from hsinghsing.panda.com ([206.124.149.116]) by Panda.COM ([192.107.14.50]) with ESMTP via TCP; Tue, 22 Jun 2010 18:22:17 -0700
X-MailFrom: mrc+ietf@panda.com
Date: Tue, 22 Jun 2010 18:22:15 -0700 (PDT)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Dan Karp <dkarp@zimbra.com>
In-Reply-To: <193904168.5312.1277254862884.JavaMail.root@dogfood.zimbra.com>
Message-ID: <alpine.OSX.2.00.1006221804200.266@hsinghsing.panda.com>
References: <193904168.5312.1277254862884.JavaMail.root@dogfood.zimbra.com>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed
Content-ID: <alpine.OSX.2.00.1006221804331.266@hsinghsing.panda.com>
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 01:22:19 -0000

On Tue, 22 Jun 2010, Dan Karp wrote:
> Looking back at the discussion of the previous draft, I'm with Arnt.
> I'm really not comfortable with allowing MSNs in the UID SEARCH
> criteria of a multimailbox search.  UIDs are designed as persistent
> outside the context of a SELECT/EXPUNGE.  MSNs are expressly tied
> to a SELECT/EXPUNGE session.  Absent a session, there's no sequence
> to reference.

I'm quite sympathetic to this argument, but...

Actually, there is a (limited) use for MSNs in the UID SEARCH criteria.

An MSN range of 1:100 explicitly limits the results to the first 100
messages.  Note that unlike sequences in FETCH etc. commands, SEARCH
criteria are not syntactically required to respect the EXISTS count.  I
also note that this was the justification for MSNs to be in single-mailbox
SEARCH and UID SEARCH.

I also worry that removing MSNs creates multiple syntax flavors of SEARCH
criteria.  Implementations may have to go to trouble to remove MSN
capability from multi-mailbox search since MSN capability is mandatory to
implement in single mailbox search.

I recommend, instead, that there be a note to the effect that MSNs are not
particularly useful in multi-mailbox search; and that the use for MSNs in
multi-mailbox search, such as it is, is probably in sequence ranges for
limiting.

To summarize, then:

[1] I agree that MSNs in SEARCH criteria are of very limited use.

[2] However, that use is nearly as applicable to multi-mailbox search as
it is to single mailbox search.

[3] Leaving MSNs in multi-mailbox search probably doesn't do any harm, as
the engine already has to support them for single mailbox search.  At
worst, they are useless and harmless.  At best, they are harmless and
largely useless except for a very obscure case.

[4] Removing MSNs requires a new syntax rule that excludes MSN and
consequent greater complexity.  That's a harm.

In my judgment, the harm from [4] outweighs the uselessness of [3].  If
this was a proposal to add MSN support, as opposed to deleting it, I would
take the opposite side.

Thus, leave it in with a note about their limited use case and being in
there to correspond with single-mailbox search.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

From dkarp@zimbra.com  Tue Jun 22 19:50:55 2010
Return-Path: <dkarp@zimbra.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 99A273A6915 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 19:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level: 
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.260,  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 7s2VyrLHInT1 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 19:50:54 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id CEEE13A6886 for <morg@ietf.org>; Tue, 22 Jun 2010 19:50:54 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 29F85C784F0; Tue, 22 Jun 2010 19:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D7DSMMYBlyWz; Tue, 22 Jun 2010 19:49:00 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id 9064BC7846C; Tue, 22 Jun 2010 19:49:00 -0700 (PDT)
Date: Tue, 22 Jun 2010 19:50:54 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: Mark Crispin <mrc+ietf@panda.com>
Message-ID: <1158592451.5372.1277261454713.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <alpine.OSX.2.00.1006221804200.266@hsinghsing.panda.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 02:50:55 -0000

> > Looking back at the discussion of the previous draft, I'm with Arnt.
> > I'm really not comfortable with allowing MSNs in the UID SEARCH
> > criteria of a multimailbox search. UIDs are designed as persistent
> > outside the context of a SELECT/EXPUNGE. MSNs are expressly tied
> > to a SELECT/EXPUNGE session. Absent a session, there's no sequence
> > to reference.
> 
> Actually, there is a (limited) use for MSNs in the UID SEARCH
> criteria.

I've got no problem with MSNs in UID SEARCH queries on the selected
mailbox.  Since the mailbox is selected, there is a sequence.  Since
there's a sequence, you can constrain a search with it.

In the multimailbox search, however, there is no sequence for the
non-selected folders.

> I also worry that removing MSNs creates multiple syntax flavors of
> SEARCH criteria. Implementations may have to go to trouble to remove
> MSN capability from multi-mailbox search since MSN capability is
> mandatory to implement in single mailbox search.

But it's not a given that an IMAP implementation will use the exact
same code path to do multimailbox SEARCH as to do vanilla SEARCH.
And MSNs are the point where the code would likely diverge.

Would it be reasonable to define a command other than UID SEARCH to
represent multimailbox search?  The IN clause would then be defined
on the new command and not on UID SEARCH (probably a plus), and we
could constrain the set of allowable search criteria without
introducing incompatibilities with base SEARCH.

From mrc+ietf@panda.com  Tue Jun 22 20:11:26 2010
Return-Path: <mrc+ietf@panda.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 AD77A3A69F0 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:11:25 -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 r67z7BpaZiTd for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:11:24 -0700 (PDT)
Received: from panda.com (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id A18593A6929 for <morg@ietf.org>; Tue, 22 Jun 2010 20:11:23 -0700 (PDT)
Received: from hsinghsing.panda.com ([206.124.149.116]) by Panda.COM ([192.107.14.50]) with ESMTP via TCP; Tue, 22 Jun 2010 20:11:26 -0700
X-MailFrom: mrc+ietf@panda.com
Date: Tue, 22 Jun 2010 20:11:23 -0700 (PDT)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Dan Karp <dkarp@zimbra.com>
In-Reply-To: <1158592451.5372.1277261454713.JavaMail.root@dogfood.zimbra.com>
Message-ID: <alpine.OSX.2.00.1006222008332.266@hsinghsing.panda.com>
References: <1158592451.5372.1277261454713.JavaMail.root@dogfood.zimbra.com>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 03:11:26 -0000

On Tue, 22 Jun 2010, Dan Karp wrote:
> I've got no problem with MSNs in UID SEARCH queries on the selected
> mailbox.  Since the mailbox is selected, there is a sequence.  Since
> there's a sequence, you can constrain a search with it.
> In the multimailbox search, however, there is no sequence for the
> non-selected folders.

1:100 is a meaningful concept even in multi-mailbox search.  It means
"only consider the first 100 messages in any mailbox".

> But it's not a given that an IMAP implementation will use the exact
> same code path to do multimailbox SEARCH as to do vanilla SEARCH.
> And MSNs are the point where the code would likely diverge.

Why?

> Would it be reasonable to define a command other than UID SEARCH to
> represent multimailbox search?  The IN clause would then be defined
> on the new command and not on UID SEARCH (probably a plus), and we
> could constrain the set of allowable search criteria without
> introducing incompatibilities with base SEARCH.

How much do you want it generally implemented?

Syntax complexity and special rules are not your friend.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

From barryleiba.mailing.lists@gmail.com  Tue Jun 22 20:24:13 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 A9AE83A6A06 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.021
X-Spam-Level: 
X-Spam-Status: No, score=-1.021 tagged_above=-999 required=5 tests=[AWL=-0.836, BAYES_40=-0.185]
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 O6+kxeTipXiH for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:24:12 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 7EAC63A6916 for <morg@ietf.org>; Tue, 22 Jun 2010 20:24:12 -0700 (PDT)
Received: by vws15 with SMTP id 15so304444vws.31 for <morg@ietf.org>; Tue, 22 Jun 2010 20:24:17 -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=hQFvF2cGxFa7LGmVUAvzWi8850Ugbp+VTsDL+/2xbfE=; b=g2lPgQq51XndPI8mTT7Uar4yHJMfVudNr31EnHPCegM4M/ClICZou54EClv8Z258gq /iaWZB7GO8Uh7G5t/XZsRrGNbwSMg2FIswVuj6Q2/TBIIPUBpO2GUuy//OJt9KYiP/YW W+MAKx146EDWfgNiGZ/c28AULJn08f5gqXf28=
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=dWVyUfxmE2mB/VUMkz0Uxw6ml9NwCpfpSc9CIuRzB1lz7yfFUBc1iqc49sdXQCv0jt upX9tAMEYwTjyb/UCDa0KX45BMhh0hi39kI6lwcnzu2pB1tqIKW5ktngjaQ/4QR1pP1q rCr75sMpKPWzxpJdAmV6FVOE5toyYC8XjHaxI=
MIME-Version: 1.0
Received: by 10.220.126.200 with SMTP id d8mr3677646vcs.181.1277263457439;  Tue, 22 Jun 2010 20:24:17 -0700 (PDT)
Received: by 10.220.91.40 with HTTP; Tue, 22 Jun 2010 20:24:17 -0700 (PDT)
In-Reply-To: <1158592451.5372.1277261454713.JavaMail.root@dogfood.zimbra.com>
References: <alpine.OSX.2.00.1006221804200.266@hsinghsing.panda.com> <1158592451.5372.1277261454713.JavaMail.root@dogfood.zimbra.com>
Date: Tue, 22 Jun 2010 23:24:17 -0400
Message-ID: <AANLkTikv6PE5QyBPOhg1cNs-cUV2lk_UEEOEY-rIY19B@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Dan Karp <dkarp@zimbra.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 03:24:13 -0000

>> Actually, there is a (limited) use for MSNs in the UID SEARCH
>> criteria.
>
> In the multimailbox search, however, there is no sequence for the
> non-selected folders.

Well, there is -- it's just that the client doesn't know what messages
correspond to what MSNs, directly.  That makes the utility low, but
not absent.

I think Mark's example is a little weak -- a client would be more
likely to want to limit a search to the 100 newest messages, rather
than the 100 oldest, and "*-100" doesn't work -- but I agree with him
that it's worth some words in the document (to the effect that clients
are likely to find little use for MSNs here) rather than an outright
restriction.

> But it's not a given that an IMAP implementation will use the exact
> same code path to do multimailbox SEARCH as to do vanilla SEARCH.
> And MSNs are the point where the code would likely diverge.

That seems a stretch.  I can't imagine implementing this search as
anything other than multiple applications of a regular search, perhaps
spinning off a few threads to do some in parallel.

> Would it be reasonable to define a command other than UID SEARCH to
> represent multimailbox search?

We did talk about that a long time ago ("MSEARCH", or some such) and
ruled it out.  It's much more likely to be implemented this way, and
it's inviting trouble to have too many similar but not-quite-the-same
commands.

I'm happy to go either way on this if we have consensus to change it,
but my preference would be to leave MSNs in, and to add text
explaining why clients should generally avoid using them with this
extension.

Barry

From dkarp@zimbra.com  Tue Jun 22 20:25:26 2010
Return-Path: <dkarp@zimbra.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 DDA223A6A06 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217,  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 4a2P1YG5y2KS for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:25:26 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id 115193A69F0 for <morg@ietf.org>; Tue, 22 Jun 2010 20:25:25 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 49D30C785B9; Tue, 22 Jun 2010 20:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AMKr3H67S8qM; Tue, 22 Jun 2010 20:23:31 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id B8AA9C784F0; Tue, 22 Jun 2010 20:23:31 -0700 (PDT)
Date: Tue, 22 Jun 2010 20:25:25 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: Mark Crispin <mrc+ietf@panda.com>
Message-ID: <1702760831.5403.1277263525864.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <alpine.OSX.2.00.1006222008332.266@hsinghsing.panda.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 03:25:27 -0000

> > I've got no problem with MSNs in UID SEARCH queries on the selected
> > mailbox. Since the mailbox is selected, there is a sequence. Since
> > there's a sequence, you can constrain a search with it.
> > In the multimailbox search, however, there is no sequence for the
> > non-selected folders.
> 
> 1:100 is a meaningful concept even in multi-mailbox search. It means
> "only consider the first 100 messages in any mailbox".

I'd respectfully disagree.  The sequence is an ordering of the messages
in the currently-selected mailbox.  A sequence for one SELECT may not
match the sequence for a concurrent SELECT from another client due to
expunges.  And, for that reason, "1:100" does not mean the first 100
messages in the selected mailbox; rather, it means the first 100
entries in the sequence.

> > Would it be reasonable to define a command other than UID SEARCH to
> > represent multimailbox search? The IN clause would then be defined
> > on the new command and not on UID SEARCH (probably a plus), and we
> > could constrain the set of allowable search criteria without
> > introducing incompatibilities with base SEARCH.
> 
> How much do you want it generally implemented?
> Syntax complexity and special rules are not your friend.

I think that you're overstating the difficulty here.  If a server
implementor is going to do the heavy lifting required to implement 
multimailbox search, minor differences in parsing rules (like the IN
clause) are going to be the least of their worries.

From dkarp@zimbra.com  Tue Jun 22 20:31:23 2010
Return-Path: <dkarp@zimbra.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 EBDB93A6A06 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:31:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  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 CwSiylAyMS3S for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:31:21 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id E14373A69F0 for <morg@ietf.org>; Tue, 22 Jun 2010 20:31:21 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 7ED85C784F0; Tue, 22 Jun 2010 20:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WrTd99ea-aqy; Tue, 22 Jun 2010 20:29:27 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id EF4C3C7846C; Tue, 22 Jun 2010 20:29:27 -0700 (PDT)
Date: Tue, 22 Jun 2010 20:31:22 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: barryleiba@computer.org
Message-ID: <848230132.5414.1277263881980.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <AANLkTikv6PE5QyBPOhg1cNs-cUV2lk_UEEOEY-rIY19B@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 03:31:23 -0000

> > But it's not a given that an IMAP implementation will use the exact
> > same code path to do multimailbox SEARCH as to do vanilla SEARCH.
> > And MSNs are the point where the code would likely diverge.
> 
> That seems a stretch. I can't imagine implementing this search as
> anything other than multiple applications of a regular search, perhaps
> spinning off a few threads to do some in parallel.

Actually, I can think of a few tricks particular to my server's
implementation that might allow me to write multimailbox search without
loading each target mailbox in turn and running a vanilla UID SEARCH.
I haven't tried coding it up yet, but I *think* I see how it could be
done.

In other words, your mileage may vary.  But it's not a given that
everyone will implement multimailbox search identically.

From barryleiba.mailing.lists@gmail.com  Tue Jun 22 20:33: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 40FB73A6A06 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.123
X-Spam-Level: 
X-Spam-Status: No, score=-2.123 tagged_above=-999 required=5 tests=[AWL=0.476,  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 5Nr+L3Hj-lIr for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:33:38 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 267483A6A30 for <morg@ietf.org>; Tue, 22 Jun 2010 20:33:38 -0700 (PDT)
Received: by vws15 with SMTP id 15so314630vws.31 for <morg@ietf.org>; Tue, 22 Jun 2010 20:33:36 -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 :content-transfer-encoding; bh=z5oL9fcCzMDeZVHZ5g3TKQSHmDDUTbcjYoPDOVMM0Hw=; b=YkjVgNOjZt4UOuJ4j3mYbgE2JhN71Im5KWE41vx70fLBjvvCgqu3h7VALEHko2f9Cj 1OXOEHKA72rNW3SZjTg+axP96Foe7Yijkk8QXvhxeOgNiXkwnPh785gj8ajTkNXGesbw yXb29bZLx97HFspvYlL8h26H8WzXBTImHLAlM=
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:content-transfer-encoding; b=FvYj3xOMS5aufT8EZ0GpYHyvMcssx75SnZgD7SEauBH6nqfNJcnp9dHD82KXqxXQhb i6TCVbsy6copNTgUeSsRX+YoJpPUXWry1yUMvie4wHjziGvx01HewbMtKJxe9FN485hk PPET81rt7ykSvAjnrbESsuxWQZ5cz1F7EPNPQ=
MIME-Version: 1.0
Received: by 10.220.122.88 with SMTP id k24mr3639689vcr.113.1277264016377;  Tue, 22 Jun 2010 20:33:36 -0700 (PDT)
Received: by 10.220.91.40 with HTTP; Tue, 22 Jun 2010 20:33:36 -0700 (PDT)
In-Reply-To: <20100123144502.119303A68E1@core3.amsl.com>
References: <20100123144502.119303A68E1@core3.amsl.com>
Date: Tue, 22 Jun 2010 23:33:36 -0400
Message-ID: <AANLkTilU-D1dAxL6KlxYEdKseQZeRzKzfqqSZw9cjU_y@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [MORG] I-D Action: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, 23 Jun 2010 03:33:39 -0000

> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Message Organization Working Group of th=
e IETF.
>
> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : IMAP4 Extension for Fuzzy Sear=
ch
> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : T. Sirainen
> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-morg-fuzzy-search-02.=
txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 6
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-01-23

> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-morg-fuzzy-search-02.txt

This draft was updated a while ago, and we didn't move on it... but it
should also be ready to go.  I'm going to initiate working-group last
call on it now, to finish in two weeks, on 7 July 2010.

Everyone: please review it, and please post to this thread.  Please
post any requested changes here, and be specific about the changes and
the text.  Please also post if you have reviewed it and you think it's
OK.  We need to know how many people have reviewed it and want to move it a=
head.

Again: please review this document and post to this thread by 7 July
2010, WHETHER OR NOT you have any issues.

Barry, as chair

From mrc+ietf@panda.com  Tue Jun 22 20:36:21 2010
Return-Path: <mrc+ietf@panda.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 5D2273A6768 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.204
X-Spam-Level: 
X-Spam-Status: No, score=-1.204 tagged_above=-999 required=5 tests=[AWL=-0.094, BAYES_05=-1.11]
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 Tmm3FNjLLCJm for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:36:18 -0700 (PDT)
Received: from panda.com (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id D62583A6A06 for <morg@ietf.org>; Tue, 22 Jun 2010 20:36:17 -0700 (PDT)
Received: from hsinghsing.panda.com ([206.124.149.116]) by Panda.COM ([192.107.14.50]) with ESMTP via TCP; Tue, 22 Jun 2010 20:36:19 -0700
X-MailFrom: mrc+ietf@panda.com
Date: Tue, 22 Jun 2010 20:36:18 -0700 (PDT)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Dan Karp <dkarp@zimbra.com>
In-Reply-To: <1702760831.5403.1277263525864.JavaMail.root@dogfood.zimbra.com>
Message-ID: <alpine.OSX.2.00.1006222028310.266@hsinghsing.panda.com>
References: <1702760831.5403.1277263525864.JavaMail.root@dogfood.zimbra.com>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 03:36:21 -0000

On Tue, 22 Jun 2010, Dan Karp wrote:
>> 1:100 is a meaningful concept even in multi-mailbox search. It means
>> "only consider the first 100 messages in any mailbox".
> I'd respectfully disagree.  The sequence is an ordering of the messages
> in the currently-selected mailbox.  A sequence for one SELECT may not
> match the sequence for a concurrent SELECT from another client due to
> expunges.  And, for that reason, "1:100" does not mean the first 100
> messages in the selected mailbox; rather, it means the first 100
> entries in the sequence.

That is not what a sequence means in search.

 	tag SEARCH 1:100
is valid even if there are only 14 messages in the mailbox.

If your implementation does not do this correctly, it is broken.

> I think that you're overstating the difficulty here.  If a server
> implementor is going to do the heavy lifting required to implement
> multimailbox search, minor differences in parsing rules (like the IN
> clause) are going to be the least of their worries.

Hardly anyone implements more than a tiny percentage of the available IMAP
extensions out there.

There are barriers to implementation, and each incremental barrier makes
it worse.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

From dkarp@zimbra.com  Tue Jun 22 20:38:30 2010
Return-Path: <dkarp@zimbra.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 AEDCB3A6A06 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[AWL=0.163,  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 IAvOvDJBzsFh for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:38:29 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id DEAEA3A690E for <morg@ietf.org>; Tue, 22 Jun 2010 20:38:29 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 41BD1C7846C; Tue, 22 Jun 2010 20:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PghuFZeUV8z4; Tue, 22 Jun 2010 20:36:35 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id BF89BC785BF; Tue, 22 Jun 2010 20:36:35 -0700 (PDT)
Date: Tue, 22 Jun 2010 20:38:29 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: Mark Crispin <mrc+ietf@panda.com>
Message-ID: <423400231.5422.1277264309933.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <alpine.OSX.2.00.1006222028310.266@hsinghsing.panda.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 03:38:30 -0000

> > I'd respectfully disagree. The sequence is an ordering of the
> > messages in the currently-selected mailbox. A sequence for one
> > SELECT may not match the sequence for a concurrent SELECT from
> > another client due to expunges. And, for that reason, "1:100"
> > does not mean the first 100 messages in the selected mailbox;
> > rather, it means the first 100 entries in the sequence.
> 
> That is not what a sequence means in search.
>    tag SEARCH 1:100
> is valid even if there are only 14 messages in the mailbox.

I'm not arguing as to whether or not it is *valid*.  I am discussing

From dkarp@zimbra.com  Tue Jun 22 20:44:43 2010
Return-Path: <dkarp@zimbra.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 890283A690E for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.455
X-Spam-Level: 
X-Spam-Status: No, score=-2.455 tagged_above=-999 required=5 tests=[AWL=0.144,  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 mQa8mCMw8iJP for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:44:41 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id 50B9A3A69F0 for <morg@ietf.org>; Tue, 22 Jun 2010 20:44:36 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id DCCE3C784F0; Tue, 22 Jun 2010 20:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M6NCzGwKhPb7; Tue, 22 Jun 2010 20:42:42 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id 57426C7846C; Tue, 22 Jun 2010 20:42:42 -0700 (PDT)
Date: Tue, 22 Jun 2010 20:44:36 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: Mark Crispin <mrc+ietf@panda.com>
Message-ID: <650317272.5428.1277264676480.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <423400231.5422.1277264309933.JavaMail.root@dogfood.zimbra.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 03:44:44 -0000

> > > I'd respectfully disagree. The sequence is an ordering of the
> > > messages in the currently-selected mailbox. A sequence for one
> > > SELECT may not match the sequence for a concurrent SELECT from
> > > another client due to expunges. And, for that reason, "1:100"
> > > does not mean the first 100 messages in the selected mailbox;
> > > rather, it means the first 100 entries in the sequence.
> >
> > That is not what a sequence means in search.
> >    tag SEARCH 1:100
> > is valid even if there are only 14 messages in the mailbox.
> 
> I'm not arguing as to whether or not it is *valid*. I am discussing

Oops.  I accidentally hit the "send" button.  Apologies.

From mrc+ietf@panda.com  Tue Jun 22 20:46:09 2010
Return-Path: <mrc+ietf@panda.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 920AB3A6A09 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level: 
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[AWL=0.682,  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 hwcgcUs9vSay for <morg@core3.amsl.com>; Tue, 22 Jun 2010 20:46:08 -0700 (PDT)
Received: from panda.com (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id 407673A690E for <morg@ietf.org>; Tue, 22 Jun 2010 20:46:08 -0700 (PDT)
Received: from hsinghsing.panda.com ([206.124.149.116]) by Panda.COM ([192.107.14.50]) with ESMTP via TCP; Tue, 22 Jun 2010 20:46:11 -0700
X-MailFrom: mrc+ietf@panda.com
Date: Tue, 22 Jun 2010 20:46:09 -0700 (PDT)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Dan Karp <dkarp@zimbra.com>
In-Reply-To: <423400231.5422.1277264309933.JavaMail.root@dogfood.zimbra.com>
Message-ID: <alpine.OSX.2.00.1006222042250.266@hsinghsing.panda.com>
References: <423400231.5422.1277264309933.JavaMail.root@dogfood.zimbra.com>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 03:46:09 -0000

On Tue, 22 Jun 2010, Dan Karp wrote:
>>> I'd respectfully disagree. The sequence is an ordering of the
>>> messages in the currently-selected mailbox. A sequence for one
>>> SELECT may not match the sequence for a concurrent SELECT from
>>> another client due to expunges. And, for that reason, "1:100"
>>> does not mean the first 100 messages in the selected mailbox;
>>> rather, it means the first 100 entries in the sequence.
>> That is not what a sequence means in search.
>>    tag SEARCH 1:100
>> is valid even if there are only 14 messages in the mailbox.
> I'm not arguing as to whether or not it is *valid*.

It is valid and it means the first 100 messages in the mailbox.

In a multi-mailbox search, it would refers to the first 100 messages in
each mailbox being searched for the same reason that UID 123 refers to a
message with that UID in the mailbox being searched and not UID 123 in the
currently selected mailbox.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

From mrc+ietf@panda.com  Tue Jun 22 21:07:07 2010
Return-Path: <mrc+ietf@panda.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 D93973A6834 for <morg@core3.amsl.com>; Tue, 22 Jun 2010 21:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.158
X-Spam-Level: 
X-Spam-Status: No, score=-1.158 tagged_above=-999 required=5 tests=[AWL=-0.418, 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 9queYFyZwJSx for <morg@core3.amsl.com>; Tue, 22 Jun 2010 21:07:06 -0700 (PDT)
Received: from panda.com (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id 81E803A67D0 for <morg@ietf.org>; Tue, 22 Jun 2010 21:07:06 -0700 (PDT)
Received: from hsinghsing.panda.com ([206.124.149.116]) by Panda.COM ([192.107.14.50]) with ESMTP via TCP; Tue, 22 Jun 2010 21:07:00 -0700
X-MailFrom: mrc+ietf@panda.com
Date: Tue, 22 Jun 2010 21:06:53 -0700 (PDT)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: barryleiba@computer.org
In-Reply-To: <AANLkTikv6PE5QyBPOhg1cNs-cUV2lk_UEEOEY-rIY19B@mail.gmail.com>
Message-ID: <alpine.OSX.2.00.1006222056210.266@hsinghsing.panda.com>
References: <alpine.OSX.2.00.1006221804200.266@hsinghsing.panda.com> <1158592451.5372.1277261454713.JavaMail.root@dogfood.zimbra.com> <AANLkTikv6PE5QyBPOhg1cNs-cUV2lk_UEEOEY-rIY19B@mail.gmail.com>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 04:07:08 -0000

On Tue, 22 Jun 2010, Barry Leiba wrote:
> I think Mark's example is a little weak -- a client would be more
> likely to want to limit a search to the 100 newest messages

Agreed.  But there are some real-life use cases that I have dealt with in
the past where it had use.

These are not enough to argue for inclusion; but we're not arguing
inclusion.  We're arguing exclusion; the path of complexity is to have a
separate syntax that excludes MSN in search.

> but my preference would be to leave MSNs in, and to add text
> explaining why clients should generally avoid using them with this
> extension.

That is my preference as well.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

From alexey.melnikov@isode.com  Wed Jun 23 02:53:24 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 E84F33A659A for <morg@core3.amsl.com>; Wed, 23 Jun 2010 02:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level: 
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[AWL=0.348,  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 ITz8+59i1nmS for <morg@core3.amsl.com>; Wed, 23 Jun 2010 02:53:24 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id D84FC3A682A for <morg@ietf.org>; Wed, 23 Jun 2010 02:53:23 -0700 (PDT)
Received: from [188.28.95.21] (188.28.95.21.threembb.co.uk [188.28.95.21])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TCHZlwAJf752@rufus.isode.com>; Wed, 23 Jun 2010 10:53:29 +0100
Message-ID: <4C21D97F.5050806@isode.com>
Date: Wed, 23 Jun 2010 10:53:03 +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: barryleiba@computer.org
References: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com> <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi> <AANLkTinL2qLU5RZVrxzfUo2QW3dB80H9SBbmC9axDOpy@mail.gmail.com>
In-Reply-To: <AANLkTinL2qLU5RZVrxzfUo2QW3dB80H9SBbmC9axDOpy@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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, 23 Jun 2010 09:53:25 -0000

Barry Leiba wrote:

>>(Maybe with the above change it would be possible to have only a single
>>capability for the selection criteria and CREATE? Although could be a bit
>>annoying for clients if they didn't know until after CREATE if the USE was
>>supported.)
>>    
>>
>
>I differ from Alexey here: I think we need two capabilities, one for
>LISText and one for CREATE.  IMAP has generally been careful NOT to
>set things up so you have to try commands to see whether they work.
>  
>
The second doesn't follow from the first.
The main question is: can you see a case where CREATE (USE) can be used 
without [specialuse-]extended LIST or vice versa? If not, no need to 
have 2 capabilities.

>It's not terribly expensive to have both.  Maybe I'll make the strings
>"list-specialuse" and "create-specialuse".
>  
>
It is always better to have one than to have two.


From barryleiba.mailing.lists@gmail.com  Wed Jun 23 10:14:12 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 81D033A6ACC for <morg@core3.amsl.com>; Wed, 23 Jun 2010 10:14:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.431
X-Spam-Level: 
X-Spam-Status: No, score=-1.431 tagged_above=-999 required=5 tests=[AWL=-0.321, BAYES_05=-1.11]
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 NNXRBH9NHEEi for <morg@core3.amsl.com>; Wed, 23 Jun 2010 10:14:11 -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 A01583A6ACA for <morg@ietf.org>; Wed, 23 Jun 2010 10:14:11 -0700 (PDT)
Received: by gyh4 with SMTP id 4so4050079gyh.31 for <morg@ietf.org>; Wed, 23 Jun 2010 10:14:16 -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 :content-transfer-encoding; bh=T1n/lPEgFNq69oEOp3DXhkZWnbTNsNNNfPCH84teHII=; b=Z/8i03MxTPj8ZEcAbMJM43z2INPl3U5GJ81witILaUuMUcQOGXHtFPomWtm+A2sKf6 CQnPSkYzZYCCIu1okaCmJPnubl0vF86WScaHR/RZtuhN3gGUshaLHfv0MVyb2N50CFaJ 4vT7eH+/f5cc5lYTy5e/LzcCXnfn/BT8fF8dU=
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:content-transfer-encoding; b=IAehd2Pat0LkfNXwr3CPFT+N3b09SvyzOCcnQ0MpRDZXvZF5BUrY8E6rj8EvkpI8Uq oEY/ckBybKuzIhtIJb8zinco3XrfwxjDrciVr+g1jOID82AdzjNPWB66lXPPSxKrltNp rsAwKipWZ8h4C57y96BTIscGkgI8BBZvrPGAU=
MIME-Version: 1.0
Received: by 10.229.235.197 with SMTP id kh5mr4497657qcb.237.1277313256670;  Wed, 23 Jun 2010 10:14:16 -0700 (PDT)
Received: by 10.220.91.40 with HTTP; Wed, 23 Jun 2010 10:14:16 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.00.1006222056210.266@hsinghsing.panda.com>
References: <alpine.OSX.2.00.1006221804200.266@hsinghsing.panda.com> <1158592451.5372.1277261454713.JavaMail.root@dogfood.zimbra.com> <AANLkTikv6PE5QyBPOhg1cNs-cUV2lk_UEEOEY-rIY19B@mail.gmail.com> <alpine.OSX.2.00.1006222056210.266@hsinghsing.panda.com>
Date: Wed, 23 Jun 2010 13:14:16 -0400
Message-ID: <AANLkTilvtaa61yVcto36BjjNYY4disGy9leSKifQIBUF@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 17:14:12 -0000

> These are not enough to argue for inclusion; but we're not arguing
> inclusion. =A0We're arguing exclusion; the path of complexity is to have =
a
> separate syntax that excludes MSN in search.
>
>> but my preference would be to leave MSNs in, and to add text
>> explaining why clients should generally avoid using them with this
>> extension.
>
> That is my preference as well.

Would anyone else like to weigh in, besides Dan, Mark, and me?

Barry

From barryleiba.mailing.lists@gmail.com  Wed Jun 23 10:16:31 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 0A5183A6ADA for <morg@core3.amsl.com>; Wed, 23 Jun 2010 10:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.144
X-Spam-Level: 
X-Spam-Status: No, score=-2.144 tagged_above=-999 required=5 tests=[AWL=0.455,  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 ogezT7G9j4YU for <morg@core3.amsl.com>; Wed, 23 Jun 2010 10:16:29 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 4388B3A6ACB for <morg@ietf.org>; Wed, 23 Jun 2010 10:16:29 -0700 (PDT)
Received: by vws14 with SMTP id 14so720964vws.31 for <morg@ietf.org>; Wed, 23 Jun 2010 10:16:34 -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:content-transfer-encoding; bh=4iKrnfRaW8g+0kh4HlLyROJPyyPnrEVUUlMOwwgpd/U=; b=bLFmXRgjOSy2hFOnDKiCevUQPtYriZEQsJ9rJBkOLlCCcA4hS7hGA47xZ9sAdNJ5iB YerGuQemERSrvtTLhKlnnKTLXMzJIE51w+lbPJPEa9WH+smJi+Ad/Ja/CC5mEyhaBrxZ TaEZ6WgI3KqITVOy6CKuXAz6J/U29LAV19AjE=
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:content-transfer-encoding; b=dLvec1nCSSdU7Skjk48uPDB0QcGWL0AB89E3PLYz6pFb9b0mEb00QFAvNPsRDPzMv1 4GPEX9D7wbS8BYn6Q7G63/HNoznFtZa38pBjYt8sE7jSk2tMpM2Z62CcVcTZI6dgD+4W PQ6vvZoZptSdcr+cO4AHDTg3Oza/P+asNJQT0=
MIME-Version: 1.0
Received: by 10.220.124.67 with SMTP id t3mr4231167vcr.45.1277313392817; Wed,  23 Jun 2010 10:16:32 -0700 (PDT)
Received: by 10.220.91.40 with HTTP; Wed, 23 Jun 2010 10:16:32 -0700 (PDT)
In-Reply-To: <4C21D97F.5050806@isode.com>
References: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com> <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi> <AANLkTinL2qLU5RZVrxzfUo2QW3dB80H9SBbmC9axDOpy@mail.gmail.com> <4C21D97F.5050806@isode.com>
Date: Wed, 23 Jun 2010 13:16:32 -0400
Message-ID: <AANLkTilZSXG0z2ol2PFsNv45Cxry28_Oh_iBGX9efDoo@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
Content-Transfer-Encoding: quoted-printable
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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, 23 Jun 2010 17:16:31 -0000

>> I differ from Alexey here: I think we need two capabilities, one for
>> LISText and one for CREATE. =A0IMAP has generally been careful NOT to
>> set things up so you have to try commands to see whether they work.
>
> The second doesn't follow from the first.
> The main question is: can you see a case where CREATE (USE) can be used
> without [specialuse-]extended LIST or vice versa? If not, no need to have=
 2
> capabilities.

I don't follow this.  The problem is the other way around: we need a
capability for LIST, and we have at least one implementation (Google)
that wants to be able to implement LIST and *not* CREATE.  That gives
us the choice of having a separate capability for CREATE, or making
clients try the CREATE and see if it fails.

How can you resolve this otherwise; what am I missing?

Barry

From alexey.melnikov@isode.com  Wed Jun 23 10:49:46 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 837E23A6AE8 for <morg@core3.amsl.com>; Wed, 23 Jun 2010 10:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 tagged_above=-999 required=5 tests=[AWL=0.402,  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 ZCMyys0oY8oc for <morg@core3.amsl.com>; Wed, 23 Jun 2010 10:49:45 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 3E0BB3A6AE6 for <morg@ietf.org>; Wed, 23 Jun 2010 10:49:45 -0700 (PDT)
Received: from [172.16.2.161] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TCJJPwAJf3Vz@rufus.isode.com>; Wed, 23 Jun 2010 18:49:52 +0100
Message-ID: <4C224914.4070706@isode.com>
Date: Wed, 23 Jun 2010 18:49:08 +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: barryleiba@computer.org
References: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com> <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi> <AANLkTinL2qLU5RZVrxzfUo2QW3dB80H9SBbmC9axDOpy@mail.gmail.com> <4C21D97F.5050806@isode.com> <AANLkTilZSXG0z2ol2PFsNv45Cxry28_Oh_iBGX9efDoo@mail.gmail.com>
In-Reply-To: <AANLkTilZSXG0z2ol2PFsNv45Cxry28_Oh_iBGX9efDoo@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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, 23 Jun 2010 17:49:46 -0000

Barry Leiba wrote:

>>>I differ from Alexey here: I think we need two capabilities, one for
>>>LISText and one for CREATE.  IMAP has generally been careful NOT to
>>>set things up so you have to try commands to see whether they work.
>>>      
>>>
>>The second doesn't follow from the first.
>>The main question is: can you see a case where CREATE (USE) can be used
>>without [specialuse-]extended LIST or vice versa? If not, no need to have 2
>>capabilities.
>>    
>>
>I don't follow this.  The problem is the other way around: we need a
>capability for LIST, and we have at least one implementation (Google)
>that wants to be able to implement LIST and *not* CREATE.  That gives
>us the choice of having a separate capability for CREATE, or making
>clients try the CREATE and see if it fails.
>
>How can you resolve this otherwise; what am I missing?
>  
>
If Google is not planning to implement extended LIST, then we can just 
have 1 capability for both CREATE (USE) and the extended LIST.


From alexey.melnikov@isode.com  Wed Jun 23 10:55:38 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 A44DA3A6AEA for <morg@core3.amsl.com>; Wed, 23 Jun 2010 10:55:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[AWL=0.398,  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 QGTsD07C37PH for <morg@core3.amsl.com>; Wed, 23 Jun 2010 10:55:38 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id AF0F53A6ADE for <morg@ietf.org>; Wed, 23 Jun 2010 10:55:37 -0700 (PDT)
Received: from [172.16.2.161] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TCJKnwAJf0zM@rufus.isode.com>; Wed, 23 Jun 2010 18:55:44 +0100
Message-ID: <4C224A72.3010804@isode.com>
Date: Wed, 23 Jun 2010 18:54:58 +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: barryleiba@computer.org
References: <alpine.OSX.2.00.1006221804200.266@hsinghsing.panda.com> <1158592451.5372.1277261454713.JavaMail.root@dogfood.zimbra.com> <AANLkTikv6PE5QyBPOhg1cNs-cUV2lk_UEEOEY-rIY19B@mail.gmail.com> <alpine.OSX.2.00.1006222056210.266@hsinghsing.panda.com> <AANLkTilvtaa61yVcto36BjjNYY4disGy9leSKifQIBUF@mail.gmail.com>
In-Reply-To: <AANLkTilvtaa61yVcto36BjjNYY4disGy9leSKifQIBUF@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 17:55:38 -0000

Barry Leiba wrote:

>>These are not enough to argue for inclusion; but we're not arguing
>>inclusion.  We're arguing exclusion; the path of complexity is to have a
>>separate syntax that excludes MSN in search.
>>    
>>
>>>but my preference would be to leave MSNs in, and to add text
>>>explaining why clients should generally avoid using them with this
>>>extension.
>>>      
>>>
>>That is my preference as well.    
>>
>Would anyone else like to weigh in, besides Dan, Mark, and me?
>  
>
I am on the fence and can go either way.

But I don't want to have a separate search criteria syntax for MSEARCH 
(or whatever it ends up being called).


From barryleiba.mailing.lists@gmail.com  Wed Jun 23 13:16:55 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 3554A28C105 for <morg@core3.amsl.com>; Wed, 23 Jun 2010 13:16:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.29
X-Spam-Level: 
X-Spam-Status: No, score=-1.29 tagged_above=-999 required=5 tests=[AWL=-0.550,  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 0BKcwk6B860j for <morg@core3.amsl.com>; Wed, 23 Jun 2010 13:16:54 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 4CD9528C104 for <morg@ietf.org>; Wed, 23 Jun 2010 13:16:54 -0700 (PDT)
Received: by vws14 with SMTP id 14so904969vws.31 for <morg@ietf.org>; Wed, 23 Jun 2010 13:16:56 -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:content-transfer-encoding; bh=I1whpJhhtsUKyiGAhJCpMsItXucRUUHKW2lEN9LjN0A=; b=ueAfJpOKrLG6Fi1rFjiZIiV+xQZwQ+UpN0Gfg5Rl4icWfnvRe6Di0AGPjZQ/Or1N4I Du7SOWTs3ugoOZ8f/77HKHFVpaIlMI+/3FC9ui5o+w4vK54ADocqxGPFwc0KMYmMeksA pnbR1GLxf9MCcp2MaBZbtYuCwnzGQCgXlNLTQ=
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:content-transfer-encoding; b=uBuycViqez2aZ0FrcU3CkylhtN8znyKCcNeaW9b4m7QJaOYIyN6QCAPkbz6X2xsCWZ BXBdSSnTmV7dtlqLPotUoLtYLEcc7YO32aIAozjYhgU3Zdx/VfoPxTjG5e7ftcQNGKqx x0b1ALPl3t/Srd1SgUIjld36zQD6jmLrkyw8k=
MIME-Version: 1.0
Received: by 10.220.123.167 with SMTP id p39mr4423881vcr.205.1277324216514;  Wed, 23 Jun 2010 13:16:56 -0700 (PDT)
Received: by 10.220.91.40 with HTTP; Wed, 23 Jun 2010 13:16:56 -0700 (PDT)
In-Reply-To: <4C224914.4070706@isode.com>
References: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com> <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi> <AANLkTinL2qLU5RZVrxzfUo2QW3dB80H9SBbmC9axDOpy@mail.gmail.com> <4C21D97F.5050806@isode.com> <AANLkTilZSXG0z2ol2PFsNv45Cxry28_Oh_iBGX9efDoo@mail.gmail.com> <4C224914.4070706@isode.com>
Date: Wed, 23 Jun 2010 16:16:56 -0400
Message-ID: <AANLkTikPqoNWAVgi-wIY7TAg_l4vaATviqxusUrLiAGh@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
Content-Transfer-Encoding: quoted-printable
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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, 23 Jun 2010 20:16:55 -0000

>> I don't follow this. =A0The problem is the other way around: we need a
>> capability for LIST, and we have at least one implementation (Google)
>> that wants to be able to implement LIST and *not* CREATE. =A0That gives
>> us the choice of having a separate capability for CREATE, or making
>> clients try the CREATE and see if it fails.
>>
>> How can you resolve this otherwise; what am I missing?
>>
>
> If Google is not planning to implement extended LIST, then we can just ha=
ve
> 1 capability for both CREATE (USE) and the extended LIST.

Right now, implementing the CREATE portion is optional.  That is:
* Implementing this extension in LIST (unextended) can happen with no
capability to announce it.
* Implementing this extension in extended LIST requires the capability
to be announced.
* Implementing this extension in CREATE is optional, regardless of
what type of LIST you implement.

You're suggesting that we change it as follows:
* Implementing this extension in LIST (unextended) can happen with no
capability to announce it.
* Implementing this extension in extended LIST requires the capability
to be announced.
* Implementing this extension in CREATE is mandatory if you implement
it in extended LIST.

I oppose that change, and would like to keep CREATE optional.  I don't
want to set up a barrier for doing the extended-LIST implementation.

Do others have opinions?  Jamie, what's your opinion, in particular?

Barry

From alexey.melnikov@isode.com  Wed Jun 23 13:28:01 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 94BF73A68D0 for <morg@core3.amsl.com>; Wed, 23 Jun 2010 13:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.215
X-Spam-Level: 
X-Spam-Status: No, score=-2.215 tagged_above=-999 required=5 tests=[AWL=0.384,  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 huGsyZv8Kb3q for <morg@core3.amsl.com>; Wed, 23 Jun 2010 13:28:00 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 862B23A6821 for <morg@ietf.org>; Wed, 23 Jun 2010 13:28:00 -0700 (PDT)
Received: from [172.16.2.161] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TCJuVgAJf6yt@rufus.isode.com>; Wed, 23 Jun 2010 21:28:07 +0100
Message-ID: <4C226E22.5000007@isode.com>
Date: Wed, 23 Jun 2010 21:27:14 +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: barryleiba@computer.org
References: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com> <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi> <AANLkTinL2qLU5RZVrxzfUo2QW3dB80H9SBbmC9axDOpy@mail.gmail.com> <4C21D97F.5050806@isode.com> <AANLkTilZSXG0z2ol2PFsNv45Cxry28_Oh_iBGX9efDoo@mail.gmail.com> <4C224914.4070706@isode.com> <AANLkTikPqoNWAVgi-wIY7TAg_l4vaATviqxusUrLiAGh@mail.gmail.com>
In-Reply-To: <AANLkTikPqoNWAVgi-wIY7TAg_l4vaATviqxusUrLiAGh@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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, 23 Jun 2010 20:28:01 -0000

Barry Leiba wrote:

>>>I don't follow this.  The problem is the other way around: we need a
>>>capability for LIST, and we have at least one implementation (Google)
>>>that wants to be able to implement LIST and *not* CREATE.  That gives
>>>us the choice of having a separate capability for CREATE, or making
>>>clients try the CREATE and see if it fails.
>>>
>>>How can you resolve this otherwise; what am I missing?
>>>      
>>>
>>If Google is not planning to implement extended LIST, then we can just have
>>1 capability for both CREATE (USE) and the extended LIST.
>>    
>>
>Right now, implementing the CREATE portion is optional.  That is:
>* Implementing this extension in LIST (unextended) can happen with no
>capability to announce it.
>* Implementing this extension in extended LIST requires the capability
>to be announced.
>* Implementing this extension in CREATE is optional, regardless of
>what type of LIST you implement.
>
>You're suggesting that we change it as follows:
>* Implementing this extension in LIST (unextended) can happen with no
>capability to announce it.
>* Implementing this extension in extended LIST requires the capability
>to be announced.
>* Implementing this extension in CREATE is mandatory if you implement
>it in extended LIST.
>
>I oppose that change, and would like to keep CREATE optional.  I don't
>want to set up a barrier for doing the extended-LIST implementation.
>  
>
To be clear: there is no need to implement the whole extended LIST. The 
server can only implement handling of the new select and return options.


From barryleiba.mailing.lists@gmail.com  Wed Jun 23 13:59:42 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 561AF3A68D5 for <morg@core3.amsl.com>; Wed, 23 Jun 2010 13:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.177
X-Spam-Level: 
X-Spam-Status: No, score=-2.177 tagged_above=-999 required=5 tests=[AWL=0.422,  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 e-rVuZgsJIGr for <morg@core3.amsl.com>; Wed, 23 Jun 2010 13:59:41 -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 968933A68CF for <morg@ietf.org>; Wed, 23 Jun 2010 13:59:41 -0700 (PDT)
Received: by gyh4 with SMTP id 4so4247612gyh.31 for <morg@ietf.org>; Wed, 23 Jun 2010 13:59:46 -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:content-transfer-encoding; bh=ugfY3r7cx1QfPxKyW8ClHpMAgH6agVpNFGrBA853WJ0=; b=R/dyCagW5qQYCvOF7xzHQ6uv1pkKOVq9j438CSXEVpGe8MkjWXUOdnnyMYp0PM1LEP 8vvQCj5O0iOuujdF4s4+SRE9T1JHffWMO1xqEzmWQoG6VbGqBw4HhBk+viJnP4REDNp/ oMg7J+11c/dHLrQ0sl5Wg6Pqn4M0JVEomdrs4=
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:content-transfer-encoding; b=nym/2mSu9JgfxIHNJ2nyqUMl4R0fDMxsVb8rg2JmPojA42mhezPqatblN3o+avWErj GyakF8I8rChV7kdz1fgI13lgofdFQnSFwZ1/mPtQ/X8426pYPAog3Cx9luTL7CTxdrXy Oezk/C8j6pY6MekX4Mr7lyyYvpVopbSXmqqw8=
MIME-Version: 1.0
Received: by 10.229.235.210 with SMTP id kh18mr4666146qcb.279.1277326786533;  Wed, 23 Jun 2010 13:59:46 -0700 (PDT)
Received: by 10.220.91.40 with HTTP; Wed, 23 Jun 2010 13:59:46 -0700 (PDT)
In-Reply-To: <4C226E22.5000007@isode.com>
References: <1215224143.1688.1276914456927.JavaMail.root@dogfood.zimbra.com> <C6A55EC7-8489-488C-9FD4-0E0718A8C7BF@iki.fi> <AANLkTinL2qLU5RZVrxzfUo2QW3dB80H9SBbmC9axDOpy@mail.gmail.com> <4C21D97F.5050806@isode.com> <AANLkTilZSXG0z2ol2PFsNv45Cxry28_Oh_iBGX9efDoo@mail.gmail.com> <4C224914.4070706@isode.com> <AANLkTikPqoNWAVgi-wIY7TAg_l4vaATviqxusUrLiAGh@mail.gmail.com> <4C226E22.5000007@isode.com>
Date: Wed, 23 Jun 2010 16:59:46 -0400
Message-ID: <AANLkTimafQgtOSTpKu2E-57jClCcZv9yE7_CbaJRKSTu@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
Content-Transfer-Encoding: quoted-printable
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-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, 23 Jun 2010 20:59:42 -0000

>> I oppose that change, and would like to keep CREATE optional. =A0I don't
>> want to set up a barrier for doing the extended-LIST implementation.
>>
>
> To be clear: there is no need to implement the whole extended LIST. The
> server can only implement handling of the new select and return options.

That's still backward; it's not a question of needing to implement
extended LIST.  The issue is, for a server that *does* implement
extended LIST, whether implementing CREATE becomes mandatory.  I want
it to remain optional, and so I think we need a second capability for
it.

Barry

From morg@dankeen.com  Wed Jun 23 14:09:29 2010
Return-Path: <morg@dankeen.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 6386B28C0FB for <morg@core3.amsl.com>; Wed, 23 Jun 2010 14:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.854
X-Spam-Level: 
X-Spam-Status: No, score=-5.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, 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 qGX3Wj+dFLEm for <morg@core3.amsl.com>; Wed, 23 Jun 2010 14:09:24 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 38D1028C0FA for <morg@ietf.org>; Wed, 23 Jun 2010 14:09:24 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id 22CB5999298D for <morg@ietf.org>; Wed, 23 Jun 2010 14:09:32 -0700 (PDT)
X-AuditID: 11807137-b7b43ae000004f8e-53-4c22780c1597
Received: from browncoat.apple.com (browncoat.apple.com [17.202.32.50]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id DC.57.20366.C08722C4; Wed, 23 Jun 2010 14:09:32 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
From: Dan Keen <morg@dankeen.com>
In-Reply-To: <AANLkTilvtaa61yVcto36BjjNYY4disGy9leSKifQIBUF@mail.gmail.com>
Date: Wed, 23 Jun 2010 14:09:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2285B75-DA67-48F3-9679-C26632214564@dankeen.com>
References: <alpine.OSX.2.00.1006221804200.266@hsinghsing.panda.com> <1158592451.5372.1277261454713.JavaMail.root@dogfood.zimbra.com> <AANLkTikv6PE5QyBPOhg1cNs-cUV2lk_UEEOEY-rIY19B@mail.gmail.com> <alpine.OSX.2.00.1006222056210.266@hsinghsing.panda.com> <AANLkTilvtaa61yVcto36BjjNYY4disGy9leSKifQIBUF@mail.gmail.com>
To: morg@ietf.org
X-Mailer: Apple Mail (2.1081)
X-Brightmail-Tracker: AAAAAQAAAZE=
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 21:09:29 -0000

On Jun 23, 2010, at 10:14 AM, Barry Leiba wrote:

>> These are not enough to argue for inclusion; but we're not arguing
>> inclusion.  We're arguing exclusion; the path of complexity is to =
have a
>> separate syntax that excludes MSN in search.
>>=20
>>> but my preference would be to leave MSNs in, and to add text
>>> explaining why clients should generally avoid using them with this
>>> extension.
>>=20
>> That is my preference as well.
>=20
> Would anyone else like to weigh in, besides Dan, Mark, and me?

I think we should leave them in.  They add arguable value in ranged =
searches.  They don't really hurt anybody.

They may make implementations easier, and they make the language simpler =
by retaining consistency.

I wouldn't personally use them (MSN ranges are the opposite direction =
from user interaction for us), but that's no reason to take a stance =
against them.

D

From barryleiba.mailing.lists@gmail.com  Wed Jun 23 14:22:40 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 0A5B83A682D for <morg@core3.amsl.com>; Wed, 23 Jun 2010 14:22:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.489
X-Spam-Level: 
X-Spam-Status: No, score=-1.489 tagged_above=-999 required=5 tests=[AWL=-0.379, BAYES_05=-1.11]
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 WVUu2m3JYYSB for <morg@core3.amsl.com>; Wed, 23 Jun 2010 14:22:39 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id C8B1C3A67B3 for <morg@ietf.org>; Wed, 23 Jun 2010 14:22:38 -0700 (PDT)
Received: by vws14 with SMTP id 14so972279vws.31 for <morg@ietf.org>; Wed, 23 Jun 2010 14:22:44 -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 :content-transfer-encoding; bh=SLOlw8tgUTeRmfBxvF2Klsc9jLWShJgmwhtWUQxcvyg=; b=qnxQiTUaqsZ4SmVSFAYsMDhVF48mjM5NtZK/fijcwIhmDWlj2jbrM1iUPzyozq4AjZ ojb718LVM/FDfErvve2yDRPPR1r2L6fkMJEgDdZda8reBGp7UP2GbiZj3amCCE/lex9j m+Cim6kmReexwdLp1/EjqTlu0wBpMjnCk3v1U=
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:content-transfer-encoding; b=UoGa3webQM7PahR8C2ae4KesqDjXu2p0fZeQn/VTUmOMYjYdPs94Jpwedvkfqcd0hI etcq4Y3LtqMcLrMuKkvnqQCut8tAR0Q8alcCiv8Fah4EpeNaICpI0T4/5DsQJaPCWm3f 8YNa2B0ZHpa2EO5CBxsz+0Vx0wQRygGiBa83o=
MIME-Version: 1.0
Received: by 10.220.126.131 with SMTP id c3mr4332509vcs.48.1277328163961; Wed,  23 Jun 2010 14:22:43 -0700 (PDT)
Received: by 10.220.91.40 with HTTP; Wed, 23 Jun 2010 14:22:43 -0700 (PDT)
In-Reply-To: <AANLkTimXlKThnLRtkxdDOhdMv0cvCxKa1s9Nff8J8zuh@mail.gmail.com>
References: <20100618201504.9C5163A6879@core3.amsl.com> <AANLkTimXlKThnLRtkxdDOhdMv0cvCxKa1s9Nff8J8zuh@mail.gmail.com>
Date: Wed, 23 Jun 2010 17:22:43 -0400
Message-ID: <AANLkTilyi-WMKERbNirOkzc-WuUdY7KU5gb0A0CFIiSI@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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, 23 Jun 2010 21:22:40 -0000

We've had a good bit of discussion on the MSN issue, and I'm happy to
see it continue.

Unfortunately, there's been no discussion of the to-do list, or of
TImo's comments.  Repeating from my previous note, and changing roles:

> This document is almost done, but still has a few open issues, noted
> in the "open issues" section. =A0Timo responded in February:
> =A0 http://www.ietf.org/mail-archive/web/morg/current/msg00308.html
> ...but there was no discussion of his comments. =A0I want to finish this
> and resolve the open issues, so everyone, please help with this.
>
>>> Interaction with IMAP Contexts [RFC5267] needs to be defined.
>>
>> I guess server then just has to monitor all matched mailboxes and send
>> updates whenever they happen. But should it notice newly created/renamed
>> mailboxes? Maybe the answer is no, except if NOTIFY is also used:
>>
>>> =A0 =A0Suggestion: UPDATE option of IMAP Notify [RFC5465] might have to=
 be
>>> =A0 =A0prohibited when both Context and this extension are used. =A0[Ba=
rry:
>>> =A0 =A0But why? =A0Isn't this then the equivalent of doing many SEARCH
>>> =A0 =A0commands with the UPDATE option?]
>>
>> I guess the problem is if NOTIFY's extended UPDATE should be allowed.
>> Sending FETCH replies for messages matching in non-selected mailboxes
>> wouldn't work. But the solution could be just that the FETCH replies are
>> sent only to messages in selected mailbox, whichever it happens to be at
>> the time changes happen.
>
> Does anyone have other comments here? =A0Can anyone suggest text, if
> there's text that needs to be added?
>
>>> There's a suggestion to add an EXCLUDE clause (with a nested search
>>> =A0 =A0criteria). =A0For example, one might want to search "personal" b=
ut
>>> =A0 =A0exclude "mailboxes (Trash Spam)".
>>>
>>> =A0 =A0Cyrus suggests you can use metadata to tag mailboxes that you do=
 or
>>> =A0 =A0don't want to search, and use search criteria to exclude them (g=
ood
>>> =A0 =A0for mailboxes that you NEVER want searched (as Trash and Spam,
>>> =A0 =A0above)).
>>
>> Dunno. A 3rd possibility would be to make the IN a search-key, but
>> perhaps that would make things too complex again. It would anyway allow
>> e.g.:
>>
>> SEARCH unseen IN (personal) NOT IN (mailboxes "Spam" subtree "Trash")
>
> My sense here is that we can (and should) defer this to a future
> extension, if it turns out to be needed. =A0My sense is that it isn't
> strongly needed.
>
>>> C: tag1 SEARCH IN ((mailboxes "folder1" subtree "folder2")) unseen
>>> =A0 =A0C: tag2 SEARCH IN ((mailboxes "folder1" subtree-one "folder2"))
>>
>> Double (( )) doesn't seem correct?
>
> Can someone check the formal grammar for me? =A0I wrote the text based
> on what I saw in the grammar, and my eyes are now glazing over on it.
> Help, please, to make sure it's right.

We need comments and consensus on this stuff in order to move the
document forward.

Barry, as chair

From dkarp@zimbra.com  Sat Jun 26 12:27:51 2010
Return-Path: <dkarp@zimbra.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 12ED33A6897 for <morg@core3.amsl.com>; Sat, 26 Jun 2010 12:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.169
X-Spam-Level: 
X-Spam-Status: No, score=-1.169 tagged_above=-999 required=5 tests=[AWL=-1.170, 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 h9woKTQ3IGzG for <morg@core3.amsl.com>; Sat, 26 Jun 2010 12:27:49 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id 63A533A68F9 for <morg@ietf.org>; Sat, 26 Jun 2010 12:27:49 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 78E6AC781A2; Sat, 26 Jun 2010 12:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L162CQO4tGvZ; Sat, 26 Jun 2010 12:25:53 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id DC91BC78110; Sat, 26 Jun 2010 12:25:53 -0700 (PDT)
Date: Sat, 26 Jun 2010 12:27:51 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: barryleiba@computer.org
Message-ID: <2014223842.10589.1277580470972.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <AANLkTilyi-WMKERbNirOkzc-WuUdY7KU5gb0A0CFIiSI@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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: Sat, 26 Jun 2010 19:27:51 -0000

>>> C: tag1 SEARCH IN ((mailboxes "folder1" subtree "folder2")) unseen
>>> =C2=A0 =C2=A0C: tag2 SEARCH IN ((mailboxes "folder1" subtree-one "folde=
r2"))
>>
>> Double (( )) doesn't seem correct?
>
> Can someone check the formal grammar for me? I wrote the text based
> on what I saw in the grammar, and my eyes are now glazing over on
> it. Help, please, to make sure it's right.

It's incorrect.  It should have single parens instead.

   search-source-opts =3D  "IN" SP "(" source-mbox [SP
           "(" scope-options ")"] ")"

   source-mbox =3D  filter-mailboxes *(SP filter-mailboxes)

   filter-mailboxes =3D filter-mailboxes-selected /
                   filter-mailboxes-other

   filter-mailboxes-selected =3D  "selected"

   filter-mailboxes-other =3D "inboxes" / "personal" / "subscribed" /
                   ( "subtree" SP one-or-more-mailbox ) /
                   ( "mailboxes" SP one-or-more-mailbox ) /
                   ( "subtree-one" SP one-or-more-mailbox )

   one-or-more-mailbox =3D mailbox / many-mailboxes

   many-mailboxes  =3D "(" mailbox *(SP mailbox) ")"

From dkarp@zimbra.com  Sat Jun 26 17:27:04 2010
Return-Path: <dkarp@zimbra.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 3CDD63A6964; Sat, 26 Jun 2010 17:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.363
X-Spam-Level: 
X-Spam-Status: No, score=-2.363 tagged_above=-999 required=5 tests=[AWL=0.236,  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 6fHQkoVJDAKZ; Sat, 26 Jun 2010 17:27:03 -0700 (PDT)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id 56CF13A6961; Sat, 26 Jun 2010 17:27:03 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 598E5C78127; Sat, 26 Jun 2010 17:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at zimbra.com
Received: from mta02.zimbra.com ([127.0.0.1]) by localhost (mta02.zimbra.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r906QrURAZPR; Sat, 26 Jun 2010 17:25:03 -0700 (PDT)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id 5A53AC78203; Sat, 26 Jun 2010 17:25:03 -0700 (PDT)
Date: Sat, 26 Jun 2010 17:27:00 -0700 (PDT)
From: Dan Karp <dkarp@zimbra.com>
To: Internet-Drafts@ietf.org
Message-ID: <1582024604.10663.1277598420614.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <20100618201504.9C5163A6879@core3.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.7_GA_2473.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: morg@ietf.org, i-d-announce@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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: Sun, 27 Jun 2010 00:27:04 -0000

> Title : IMAP4 Multimailbox SEARCH Extension
> Author(s) : B. Leiba, A. Melnikov
> Filename : draft-ietf-morg-multimailbox-search-03.txt
> Pages : 10
> Date : 2010-06-18
> 
> http://www.ietf.org/internet-drafts/draft-ietf-morg-multimailbox-search-03.txt

There should probably be a note about interaction with the
SEARCHRES extension.  Is it disallowed?  Does it just save
the search results in the currently selected mailbox?

From barryleiba.mailing.lists@gmail.com  Mon Jun 28 13:39:28 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 3B4693A697A for <morg@core3.amsl.com>; Mon, 28 Jun 2010 13:39:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 pReM+M5M2iQ2 for <morg@core3.amsl.com>; Mon, 28 Jun 2010 13:39:27 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by core3.amsl.com (Postfix) with ESMTP id 3D3EF3A68AB for <morg@ietf.org>; Mon, 28 Jun 2010 13:39:24 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id d26so112997eyd.51 for <morg@ietf.org>; Mon, 28 Jun 2010 13:39:31 -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:content-transfer-encoding; bh=WUNXfGtEDcajpZpGPOZfUjpBYzApINAxQJbeJ5iFOoE=; b=brRWLh9ViAmj/eu6RttSdwjHBCHZ8W5z2Rdw3YoaPIw0Iykd9/smVlDmXwny9U7vJ1 rwMDWmb03YH/Qu0wTttC55PGtqCOK3LZCVWC57zLOoEA/rrs+5G0QkRx4hhujkKh77TC spEvDZWtCh966ucg+dQiO9gi5EP8mzAos4eRM=
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:content-transfer-encoding; b=fdTGVIda5cQQuv4w3vinLvyImsNtbMg+IVX1IfEdgQyZRutvI9qrJ41IT6QRa1zpri 0SIoO1m0pBQcPDLMVe9w3FLGDX1NRc4DP0FJpKjBECLCIdbcsymMm5Yzlm6srAaZUY/c KkVVEb6teRXVgbpyAxg66C212q5RwhqCWCCtw=
MIME-Version: 1.0
Received: by 10.213.35.74 with SMTP id o10mr1322576ebd.60.1277757571046; Mon,  28 Jun 2010 13:39:31 -0700 (PDT)
Received: by 10.213.34.197 with HTTP; Mon, 28 Jun 2010 13:39:30 -0700 (PDT)
In-Reply-To: <2014223842.10589.1277580470972.JavaMail.root@dogfood.zimbra.com>
References: <AANLkTilyi-WMKERbNirOkzc-WuUdY7KU5gb0A0CFIiSI@mail.gmail.com> <2014223842.10589.1277580470972.JavaMail.root@dogfood.zimbra.com>
Date: Mon, 28 Jun 2010 16:39:30 -0400
Message-ID: <AANLkTimx8zl8HbNC7GGb4pxnZHkQBLE5J7POw4ZqsbiH@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Dan Karp <dkarp@zimbra.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-03.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: Mon, 28 Jun 2010 20:39:28 -0000

>>>> =A0 =A0C: tag2 SEARCH IN ((mailboxes "folder1" subtree-one "folder2"))
>
> It's incorrect. =A0It should have single parens instead.
>
> =A0 search-source-opts =3D =A0"IN" SP "(" source-mbox [SP
> =A0 =A0 =A0 =A0 =A0 "(" scope-options ")"] ")"
...
> =A0 filter-mailboxes-other =3D "inboxes" / "personal" / "subscribed" /
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ( "subtree" SP one-or-more-mailbox ) =
/
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ( "mailboxes" SP one-or-more-mailbox =
) /
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ( "subtree-one" SP one-or-more-mailbo=
x )
>
> =A0 one-or-more-mailbox =3D mailbox / many-mailboxes
>
> =A0 many-mailboxes =A0=3D "(" mailbox *(SP mailbox) ")"

Thanks.  Yes, it was the "many-mailboxes" specification that confused
me. but that would result in something like this:
 =A0 =A0C: tag2 SEARCH IN (mailboxes ("folder1" "folder2"))
...which still isn't close to what I had.  I'll fix the example.

Barry
