
From barryleiba.mailing.lists@gmail.com  Mon Feb  1 11:46:37 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 D275E3A6A55 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 11:46:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.155
X-Spam-Level: 
X-Spam-Status: No, score=-3.155 tagged_above=-999 required=5 tests=[AWL=-0.556, 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 4y6KLPtH0GjB for <morg@core3.amsl.com>; Mon,  1 Feb 2010 11:46:37 -0800 (PST)
Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by core3.amsl.com (Postfix) with ESMTP id D0CCB3A6A51 for <morg@ietf.org>; Mon,  1 Feb 2010 11:46:36 -0800 (PST)
Received: by fxm2 with SMTP id 2so503945fxm.29 for <morg@ietf.org>; Mon, 01 Feb 2010 11:47:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=N4SUymWkQnb3o6fhv7CVNZTv/JxGa65mgFyIcv7o+9U=; b=fVigoR6ODmFYP+yM5y/AVYCW/hdKASeViyUuZqDMn6E8bydaloJ3mgkGDqOvcF7SZf KzS9Ov0ZwThczOrApaFYYYSB9FwVBQlqYjvCHaxTEqjfs+31LpIo9a41IluG8NrfNblu YbfQy7zjLitw8re+0hqQXNZLcqkIx9aV665HI=
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=SHF61PT/bifXduNEeKONJkoovyIlW0qgp3sHkmeJUpwZ/sn17iRbRSIcA78sj4MN+e Vai4NR5HkSBqAOLN6KiiUTEjEOpQ+8C2AV32DpXQl5Y8sHRvgscqWeRnOPPFeON98Ql7 Q1nth+H48DbR8EihHMRuCEZJAURANJh4mQfMA=
MIME-Version: 1.0
Received: by 10.223.164.78 with SMTP id d14mr4867904fay.85.1265053627849; Mon,  01 Feb 2010 11:47:07 -0800 (PST)
In-Reply-To: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com>
References: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com>
Date: Mon, 1 Feb 2010 14:47:07 -0500
Message-ID: <6c9fcc2a1002011147w738e87e2l5a629714d411d0ec@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] WGLC on draft-ietf-morg-fuzzy-search-02; respond by 10 Feb 2010
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, 01 Feb 2010 19:46:37 -0000

Here is a reminder that we are a week into WGLC for the subject
document (see details below), and I have not seen any comment on it
yet.  Please comment on the draft, even if it's just to say that you
think it's ready to go.  WGLC ends on 10 February.

> 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 Extension for Fuzzy Search
>        Author(s)       : T. Sirainen
>        Filename        : draft-ietf-morg-fuzzy-search-02.txt
>        Pages           : 6
>        Date            : 2010-01-23
>
> This document describes an IMAP protocol extension enabling server to
> perform searches with inexact matching and assigning relevancy scores
> for matched messages.
...
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-morg-fuzzy-search-02.txt

Barry, MORG secretary

From mrc+ietf@panda.com  Mon Feb  1 12:11:08 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 45BB028C186 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 12:11:08 -0800 (PST)
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 SzamaJ4cN8mE for <morg@core3.amsl.com>; Mon,  1 Feb 2010 12:11:06 -0800 (PST)
Received: from Panda.COM (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id 4D29B28C1C6 for <morg@ietf.org>; Mon,  1 Feb 2010 12:11:04 -0800 (PST)
Received: from hsinghsing.panda.com mrcrispin@Panda.COM [206.124.149.116] by Panda.COM with M+ Extreme Email Engine 2008.3.internal via secured & encrypted transport (TLS); Mon, 01 Feb 2010 12:11:13 -0800
X-MailFrom: mrc+ietf@panda.com
Date: Mon, 1 Feb 2010 12:11:13 -0800 (PST)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: barryleiba@computer.org
In-Reply-To: <6c9fcc2a1002011147w738e87e2l5a629714d411d0ec@mail.gmail.com>
Message-ID: <alpine.OSX.2.00.1002011149010.17411@hsinghsing.panda.com>
References: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com> <6c9fcc2a1002011147w738e87e2l5a629714d411d0ec@mail.gmail.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, iesg@iesg.org
Subject: Re: [MORG] WGLC on draft-ietf-morg-fuzzy-search-02; respond by 10 Feb 2010
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2010 20:11:09 -0000

You want comments?

Here's my comment:

This document, and from what I can tell the other work of MORG, is best 
suited for an April 1 RFC.

It is a solution in search of a problem.

The IMAP Extensions WG was supposed to have ended years ago.  Instead, it 
found a new home in LEMONADE, and now MORG.  I wish that the IESG would 
apply some discipline here!

The ostensible mission of the IETF is to solve problems that need solving. 
It is not to be a sinecure for efforts that have long been overtaken by 
events, and working groups that were long ago supposed to die.

On Mon, 1 Feb 2010, Barry Leiba wrote:
> Here is a reminder that we are a week into WGLC for the subject
> document (see details below), and I have not seen any comment on it
> yet.  Please comment on the draft, even if it's just to say that you
> think it's ready to go.  WGLC ends on 10 February.
>
>> 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 Extension for Fuzzy Search
>>        Author(s)       : T. Sirainen
>>        Filename        : draft-ietf-morg-fuzzy-search-02.txt
>>        Pages           : 6
>>        Date            : 2010-01-23
>>
>> This document describes an IMAP protocol extension enabling server to
>> perform searches with inexact matching and assigning relevancy scores
>> for matched messages.
> ...
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-morg-fuzzy-search-02.txt
>
> Barry, MORG secretary
> _______________________________________________
> MORG mailing list
> MORG@ietf.org
> https://www.ietf.org/mailman/listinfo/morg
> Note Well: http://www.ietf.org/maillist.html
>

-- 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 tss@iki.fi  Mon Feb  1 12:20:51 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 9084928C1D8 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 12:20:51 -0800 (PST)
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 F6t0ZkMlvWzV for <morg@core3.amsl.com>; Mon,  1 Feb 2010 12:20:50 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 9CCE528C1A4 for <morg@ietf.org>; Mon,  1 Feb 2010 12:20:50 -0800 (PST)
Received: from [192.168.10.199] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id 0850DFA89E1; Mon,  1 Feb 2010 22:21:24 +0200 (EET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Timo Sirainen <tss@iki.fi>
In-Reply-To: <alpine.OSX.2.00.1002011149010.17411@hsinghsing.panda.com>
Date: Mon, 1 Feb 2010 22:21:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D2EA52F-A324-4825-9619-1F69B5ED872B@iki.fi>
References: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com> <6c9fcc2a1002011147w738e87e2l5a629714d411d0ec@mail.gmail.com> <alpine.OSX.2.00.1002011149010.17411@hsinghsing.panda.com>
To: Mark Crispin <mrc+ietf@panda.com>
X-Mailer: Apple Mail (2.1077)
Cc: morg@ietf.org, barryleiba@computer.org, iesg@iesg.org
Subject: Re: [MORG] WGLC on draft-ietf-morg-fuzzy-search-02; respond by 10 Feb 2010
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2010 20:20:51 -0000

On 1.2.2010, at 22.11, Mark Crispin wrote:

> This document, and from what I can tell the other work of MORG, is =
best suited for an April 1 RFC.
>=20
> It is a solution in search of a problem.


Many IMAP server implementors' solution to this problem is to just do it =
already and unconditionally, breaking RFC 3501 compatibility. So it is =
already a problem that some people "solved" without the help of this =
document. What this document is trying to do is to make it possible for =
servers that actually care about being RFC 3501 compatible to do what =
users/clients typically want to do, and what some other non-conforming =
servers already do in reality (and providing better user experience for =
typical users).


From barryleiba.mailing.lists@gmail.com  Mon Feb  1 13:01:24 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 AB5F028C13E for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:01:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.125
X-Spam-Level: 
X-Spam-Status: No, score=-3.125 tagged_above=-999 required=5 tests=[AWL=-0.526, 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 7DOTcYB1pQD6 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:01:23 -0800 (PST)
Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by core3.amsl.com (Postfix) with ESMTP id 8994A3A69B2 for <morg@ietf.org>; Mon,  1 Feb 2010 13:01:23 -0800 (PST)
Received: by fxm2 with SMTP id 2so578761fxm.29 for <morg@ietf.org>; Mon, 01 Feb 2010 13:01:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=aG6gLoA8M9ETJviD0D9qMvU4e7ExQ7jVEduoYJhDwaU=; b=TuR3fWxUN5vON+HpfhDaLlq6oJ4AMNh6ZJ2OvWyx1ZHJGvB5o6IRf3Xi77GmJ7kt0s aai2Y+KtTxV0SFqInMUh4xDgmMtJDwNgxNy3EPo9mueABGzQSSyOSkb2Q2S+Vgtdr3jH dftfipLUfF1IAQsTJxH2NauO6yHPccmG5CEcE=
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=jdcqpnVpCB+pYzpAU6+WiaHyRTnBt/yjRr00M+Hi8q4ayBD8vJclt1Uo76lSBk/ZaL WBfvDGigl0XDmjjcZ5kJWRzsP8c2aYqpbTN9/ZIIoZ8EpwxlieZPgGaB6+xULuUp1Kao 9/RNilAllRfjRFz2qHTw2HglXx1qcb13B2ChU=
MIME-Version: 1.0
Received: by 10.223.127.203 with SMTP id h11mr5211900fas.24.1265058114560;  Mon, 01 Feb 2010 13:01:54 -0800 (PST)
In-Reply-To: <1D2EA52F-A324-4825-9619-1F69B5ED872B@iki.fi>
References: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com> <6c9fcc2a1002011147w738e87e2l5a629714d411d0ec@mail.gmail.com> <alpine.OSX.2.00.1002011149010.17411@hsinghsing.panda.com> <1D2EA52F-A324-4825-9619-1F69B5ED872B@iki.fi>
Date: Mon, 1 Feb 2010 16:01:54 -0500
Message-ID: <6c9fcc2a1002011301h605ad484p1e07881bab99264c@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Timo Sirainen <tss@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1
Cc: morg@ietf.org, iesg@iesg.org
Subject: Re: [MORG] WGLC on draft-ietf-morg-fuzzy-search-02; respond by 10 Feb 	2010
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, 01 Feb 2010 21:01:24 -0000

> Many IMAP server implementors' solution to this problem is to just
> do it already and unconditionally, breaking RFC 3501 compatibility.
> So it is already a problem that some people "solved" [...]

[...] in a non-standard way.

To be fair to Mark's comment, it's always been his contention that
"string" searches (as opposed to flag searches, certainly, or date
searches, perhaps) could always be "fuzzy" without violating the
intent of the IMAP spec.  The spec necessarily makes sure that string
searches are well defined, but "violations" of that aren't considered
violations of the protocol.  Lots of reasonable IMAP servers do
creative things with string searches today.

That's a major reason that Mark doesn't see any need for this doc, in
particular.

In general, Mark thinks there are too many extensions that have been
and are being proposed for IMAP, a spec that some think is already too
involved.  He sees little or no value in yet more extensions that'll
be rarely, if ever, implemented.  Mark isn't alone in this opinion.

That's why I've been pushing the question, for each spec that we're
working on, of who will implement it.  We got a good response to that
for fuzzy search, so we're going ahead.  We got a good response for
multimailbox-search, as well.  We haven't had much commitment to
implement some of the other proposals, and I'll continue to ask the
question.

I don't agree with Mark that we should essentially shut off IMAP
extension work.  But I partially agree that we're throwing them out
too readily.  We might think there's no harm in having them, and if
they don't get implemented, "So what?", and we'll just let the market
decide.  The danger with that is that it's like pouring a beachful of
sand on some nice seashells, and then asking collectors (IMAP
implementors) to find the nice shells.  The myriad extensions can get
in the way of clarity.

So, while Mark's being a little abrasive in his manner (he's MARK,
yes?), don't write off his comment out of hand.

Barry, as a participant

From mrc+ietf@Panda.COM  Mon Feb  1 13:06:24 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 017A23A6874 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:06:24 -0800 (PST)
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 e8OO4T5Lef5m for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:06:23 -0800 (PST)
Received: from Panda.COM (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id A70CA3A69AE for <morg@ietf.org>; Mon,  1 Feb 2010 13:06:23 -0800 (PST)
Received: from hsinghsing.panda.com mrcrispin@Panda.COM [206.124.149.116] by Panda.COM with M+ Extreme Email Engine 2008.3.internal via secured & encrypted transport (TLS); Mon, 01 Feb 2010 13:06:35 -0800
X-MailFrom: mrc+ietf@Panda.COM
Date: Mon, 1 Feb 2010 13:06:34 -0800 (PST)
From: Mark Crispin <mrc+ietf@Panda.COM>
Sender: mrc@hsinghsing.panda.com
To: Timo Sirainen <tss@iki.fi>
In-Reply-To: <1D2EA52F-A324-4825-9619-1F69B5ED872B@iki.fi>
Message-ID: <alpine.OSX.2.00.1002011242090.17411@hsinghsing.panda.com>
References: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com> <6c9fcc2a1002011147w738e87e2l5a629714d411d0ec@mail.gmail.com> <alpine.OSX.2.00.1002011149010.17411@hsinghsing.panda.com> <1D2EA52F-A324-4825-9619-1F69B5ED872B@iki.fi>
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, iesg@iesg.org
Subject: Re: [MORG] WGLC on draft-ietf-morg-fuzzy-search-02; respond by 10 Feb 2010
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2010 21:06:24 -0000

On Mon, 1 Feb 2010, Timo Sirainen wrote:
> Many IMAP server implementors' solution to this problem is to just do it 
> already and unconditionally, breaking RFC 3501 compatibility.

At least one of the servers that does this does does not have any 
capability to do any other type of search, and it would be extremely 
difficult to add substring search.

That's OK.

RFC 3501's purpose in specifying substring search was not to prohibit the 
use of a fuzzy search in IMAP SEARCH, but rather to protect against 
someone claiming in the future that substring search is not compliant.

> So it is 
> already a problem that some people "solved" without the help of this 
> document.

That solution was anticipated from the inception of IMAP.

> What this document is trying to do is to make it possible for 
> servers that actually care about being RFC 3501 compatible to do what 
> users/clients typically want to do, and what some other non-conforming 
> servers already do in reality (and providing better user experience for 
> typical users).

This makes two (in my mind) false assumptions.

The first is the assumption that the majority of servers will offer both 
substring and fuzzy searching; or even that the majority of servers that 
have fuzzy searching will offer substring searching.

The second is that clients desire to control this.

-- 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 tss@iki.fi  Mon Feb  1 13:18:12 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 B724428C1CA for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:18:12 -0800 (PST)
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 qjMdMW+3Zs-Y for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:18:11 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 3D59928C1CF for <morg@ietf.org>; Mon,  1 Feb 2010 13:18:11 -0800 (PST)
Received: from [192.168.10.199] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id C23BB16471EC; Mon,  1 Feb 2010 23:18:45 +0200 (EET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Timo Sirainen <tss@iki.fi>
In-Reply-To: <alpine.OSX.2.00.1002011242090.17411@hsinghsing.panda.com>
Date: Mon, 1 Feb 2010 23:18:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3954D958-E9E4-4E90-9D85-D6CB75861F3E@iki.fi>
References: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com> <6c9fcc2a1002011147w738e87e2l5a629714d411d0ec@mail.gmail.com> <alpine.OSX.2.00.1002011149010.17411@hsinghsing.panda.com> <1D2EA52F-A324-4825-9619-1F69B5ED872B@iki.fi> <alpine.OSX.2.00.1002011242090.17411@hsinghsing.panda.com>
To: Mark Crispin <mrc+ietf@panda.com>
X-Mailer: Apple Mail (2.1077)
Cc: morg@ietf.org, barryleiba@computer.org, iesg@iesg.org
Subject: Re: [MORG] WGLC on draft-ietf-morg-fuzzy-search-02; respond by 10 Feb 2010
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2010 21:18:12 -0000

On 1.2.2010, at 23.06, Mark Crispin wrote:

> On Mon, 1 Feb 2010, Timo Sirainen wrote:
>> Many IMAP server implementors' solution to this problem is to just do =
it already and unconditionally, breaking RFC 3501 compatibility.
>=20
> At least one of the servers that does this does does not have any =
capability to do any other type of search, and it would be extremely =
difficult to add substring search.

I know.

> That's OK.
>=20
> RFC 3501's purpose in specifying substring search was not to prohibit =
the use of a fuzzy search in IMAP SEARCH, but rather to protect against =
someone claiming in the future that substring search is not compliant.

Really? You had exactly the opposite opinion 3 years ago:
=
http://mailman2.u.washington.edu/pipermail/imap-protocol/2006-December/000=
328.html


From barryleiba.mailing.lists@gmail.com  Mon Feb  1 13:18:25 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 2E5AC3A6993 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:18:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bqyGOE8+0F9 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:18:24 -0800 (PST)
Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by core3.amsl.com (Postfix) with ESMTP id EB1B33A6972 for <morg@ietf.org>; Mon,  1 Feb 2010 13:18:23 -0800 (PST)
Received: by fxm2 with SMTP id 2so595732fxm.29 for <morg@ietf.org>; Mon, 01 Feb 2010 13:18:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ACVIf/GTujoVldNMB5UyvwceffEqKjYK1v8fc3oEhY4=; b=wrXIyHG6NzCT+gYSBW3jBUrkLGBxqlPj+XZm7XAp4rK1VOuphTFErc8zuJ0zEbDkrK DsYgCI9hlsR6ZnB+T5wU8rDFYvHZA56l7FRAUzmXMpdq7xmHqxa6sVSKY4TjmtRvbOGf tkQPvDzAEbjJBZSb387QIq7RwzFGoOG1UwZ6s=
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=DYqIskHh3QOrBFjXA4gKhnfCTOJ0GOIfvVo894oCAljY4AZWEljbFTFzRCdOcJnu7v modctoATVZf8dqXKcA4KHZ0vqNkTKoDfX9CpLF6gdnB+C9+9671tKYyknOI+Dm2uwL2N /qcYundCjAkjWAylN0fYZxeFbTBFe1LQd/SbQ=
MIME-Version: 1.0
Received: by 10.223.13.209 with SMTP id d17mr5019276faa.100.1265059135299;  Mon, 01 Feb 2010 13:18:55 -0800 (PST)
In-Reply-To: <alpine.OSX.2.00.1002011242090.17411@hsinghsing.panda.com>
References: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com> <6c9fcc2a1002011147w738e87e2l5a629714d411d0ec@mail.gmail.com> <alpine.OSX.2.00.1002011149010.17411@hsinghsing.panda.com> <1D2EA52F-A324-4825-9619-1F69B5ED872B@iki.fi> <alpine.OSX.2.00.1002011242090.17411@hsinghsing.panda.com>
Date: Mon, 1 Feb 2010 16:18:55 -0500
Message-ID: <6c9fcc2a1002011318m13fe9970wab31fa16712637ba@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Mark Crispin <mrc+ietf@panda.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Timo Sirainen <tss@iki.fi>, morg@ietf.org, iesg@iesg.org
Subject: Re: [MORG] WGLC on draft-ietf-morg-fuzzy-search-02; respond by 10 Feb 	2010
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, 01 Feb 2010 21:18:25 -0000

> This makes two (in my mind) false assumptions.
>
> The first is the assumption that the majority of servers will offer both
> substring and fuzzy searching; or even that the majority of servers that
> have fuzzy searching will offer substring searching.
>
> The second is that clients desire to control this.

I don't think anyone thinks clients want to control it; they think
users do.  This user, at least, would certainly like to.  There are
many times when I *do* want to disable the fuzzy search or the
word-bounded search that the server does today.  Very, very much.

But I absolutely agree with Mark's characterization of the first
assumption.  The commercial IMAP server I'm most familiar with, IBM's
Lotus Domino server, does its own style of search that we'd definitely
call "fuzzy".  If you search for "walked", you'll also get matches for
"walk", "walks", and "walking".  And if you search for "tall", you'll
match "taller" but not "tally".  I can not imagine that they will ever
change that, nor that they might offer an alternative.  [I couldn't
speak for them when I worked there, and I certainly can't now, but I
think this is a very safe bet.]

Similarly, I'd be surprised if Google should offer a strict substring
search as an option.  Do we think they plan to?

And, so, however much users might like the option, do we *really*
think they'll get it in practice?

Barry

From barryleiba.mailing.lists@gmail.com  Mon Feb  1 13:22:44 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 33F6C3A69A6 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:22:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.075
X-Spam-Level: 
X-Spam-Status: No, score=-3.075 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 3+WRsvtlcvx5 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:22:37 -0800 (PST)
Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by core3.amsl.com (Postfix) with ESMTP id AE8D33A6765 for <morg@ietf.org>; Mon,  1 Feb 2010 13:22:36 -0800 (PST)
Received: by fxm2 with SMTP id 2so600005fxm.29 for <morg@ietf.org>; Mon, 01 Feb 2010 13:23:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=KTdUdctKw13JIsY/5O8AVndHQbmfaaBH/aoOarXH5pQ=; b=ZKLXYju12QfRfu1PCp2vbESGyJ3IfRuh9IMqZTdaWmbKm4c6bpv4zviOBwxzPxihx+ 8Es615mYSv+GT5vfFHt5BbmYKGjaR1d5a6C/H3OQX4lqo1gvqcbF9Ih9hz3m1NMTTCn2 cX/m6pKGFYQrf1U6l/6uJgcQ25LxoLOQRISpc=
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=QNh5mYDvMYGDUbPLewC81EgKGkXLSxYrntF2pkSue1/NyC0w5WrizCSavKo16dZU3w ECxFZ+j/fm1kVjzN4FAFeNd6HcwZmQ2ktTUg8V05nzBdZ8sX8csoX9BYOiSCuaci+6nk Bj5791V8Fy2LPNPT5IlmwHgOSgsg4CzLPH8J8=
MIME-Version: 1.0
Received: by 10.223.13.209 with SMTP id d17mr5024361faa.100.1265059388309;  Mon, 01 Feb 2010 13:23:08 -0800 (PST)
In-Reply-To: <6c9fcc2a1002011318m13fe9970wab31fa16712637ba@mail.gmail.com>
References: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com> <6c9fcc2a1002011147w738e87e2l5a629714d411d0ec@mail.gmail.com> <alpine.OSX.2.00.1002011149010.17411@hsinghsing.panda.com> <1D2EA52F-A324-4825-9619-1F69B5ED872B@iki.fi> <alpine.OSX.2.00.1002011242090.17411@hsinghsing.panda.com> <6c9fcc2a1002011318m13fe9970wab31fa16712637ba@mail.gmail.com>
Date: Mon, 1 Feb 2010 16:23:08 -0500
Message-ID: <6c9fcc2a1002011323h6480afbfy16bbc9c92b8a8ae7@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Timo Sirainen <tss@iki.fi>, Mark Crispin <mrc+ietf@panda.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: morg <morg@ietf.org>
Subject: Re: [MORG] WGLC on draft-ietf-morg-fuzzy-search-02; respond by 10 Feb 	2010
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, 01 Feb 2010 21:22:44 -0000

By the way; I meant to do it on my last reply, but forgot to: let's
take the IESG off the CC list for the rest of this discussion.  The
point has been made to them, and they don't need the details of our
further conversation.

Barry

From mrc+ietf@Panda.COM  Mon Feb  1 13:29:02 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 36B7128C1E8 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:29:02 -0800 (PST)
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 1IWVTAiGwXrj for <morg@core3.amsl.com>; Mon,  1 Feb 2010 13:29:01 -0800 (PST)
Received: from Panda.COM (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id 0E1133A6999 for <morg@ietf.org>; Mon,  1 Feb 2010 13:28:14 -0800 (PST)
Received: from hsinghsing.panda.com mrcrispin@Panda.COM [206.124.149.116] by Panda.COM with M+ Extreme Email Engine 2008.3.internal via secured & encrypted transport (TLS); Mon, 01 Feb 2010 13:28:25 -0800
X-MailFrom: mrc+ietf@Panda.COM
Date: Mon, 1 Feb 2010 13:28:25 -0800 (PST)
From: Mark Crispin <mrc+ietf@Panda.COM>
Sender: mrc@hsinghsing.panda.com
To: barryleiba@computer.org
In-Reply-To: <6c9fcc2a1002011301h605ad484p1e07881bab99264c@mail.gmail.com>
Message-ID: <alpine.OSX.2.00.1002011314350.17411@hsinghsing.panda.com>
References: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com> <6c9fcc2a1002011147w738e87e2l5a629714d411d0ec@mail.gmail.com> <alpine.OSX.2.00.1002011149010.17411@hsinghsing.panda.com> <1D2EA52F-A324-4825-9619-1F69B5ED872B@iki.fi> <6c9fcc2a1002011301h605ad484p1e07881bab99264c@mail.gmail.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: Timo Sirainen <tss@iki.fi>, morg@ietf.org, iesg@iesg.org
Subject: Re: [MORG] WGLC on draft-ietf-morg-fuzzy-search-02; respond by 10 Feb  2010
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2010 21:29:02 -0000

On Mon, 1 Feb 2010, Barry Leiba wrote:
> In general, Mark thinks there are too many extensions that have been
> and are being proposed for IMAP, a spec that some think is already too
> involved.  He sees little or no value in yet more extensions that'll
> be rarely, if ever, implemented.  Mark isn't alone in this opinion.

Apropos to this, I refer you to all to my seminal work RFC 748; and to 
ponder its true meaning.

There were only a handful of important TELNET options.  Opinions vary, but 
I number them as three; and one of these was to disable a mandatory TELNET 
facility that served no purpose unless your terminal was an IBM 2741.

TELNET already had an order of magnitude more options at the time RFC 748 
was written.

The last time that I actively followed the IETF follies, there was a 
working group dedicated to improving TELNET long after ssh replaced it. 
That, along with the recent publication of the USEFOR and NNTP 
specifications, is a stirling example of the IETF solving problems that 
were long overtaken by events.

-- 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  Mon Feb  1 14:53:56 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 86A523A6869 for <morg@core3.amsl.com>; Mon,  1 Feb 2010 14:53:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.054
X-Spam-Level: 
X-Spam-Status: No, score=-3.054 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 RRvMkyr0XBna for <morg@core3.amsl.com>; Mon,  1 Feb 2010 14:53:55 -0800 (PST)
Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by core3.amsl.com (Postfix) with ESMTP id 6C79D3A689D for <morg@ietf.org>; Mon,  1 Feb 2010 14:53:55 -0800 (PST)
Received: by fxm2 with SMTP id 2so682360fxm.29 for <morg@ietf.org>; Mon, 01 Feb 2010 14:54:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=4rX5vFANnfxwTpjns1TNveTXSKKywnOgL8BwmJ8QnQc=; b=BW/xIobuFeku6lAAvEDLPf/IJbyQPTzA4ZtOJtvPNqeahffrGGY+BDZoBuCWUbgQ1x P2kHaLMbezEPllr4pEpZdz9/RKBwUwk+vaLBuRwFyd3QG4Q16coyuy3yVQSvPUfqGeIP P60CQZYIbHFfcCNqVlSTiu1S8DroA/6FicAvA=
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=Q3YXC3bbP9GRNYFtEpRvYmyjaTIQug+F7R8uhq8g2YjoBWdRxvK12ZmayyMyAXolmN 7SZ5sna+WmW1K8NnFHg1Sx8uqUSZsUnQbbjDtlTD9R5JslxN72hQJVdvnXsU8+WoNBnH 1GjaQvceuZCim3PmcW9VXTgs84EQnd9xUs/pk=
MIME-Version: 1.0
Received: by 10.223.4.135 with SMTP id 7mr463084far.42.1265064866922; Mon, 01  Feb 2010 14:54:26 -0800 (PST)
In-Reply-To: <6c9fcc2a1001211052h624abbf1h171f6ec19bef20e5@mail.gmail.com>
References: <6c9fcc2a1001211052h624abbf1h171f6ec19bef20e5@mail.gmail.com>
Date: Mon, 1 Feb 2010 17:54:26 -0500
Message-ID: <6c9fcc2a1002011454p296ece05pff6a5fb422882474@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg <morg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [MORG] Getting MORG moving
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, 01 Feb 2010 22:53:56 -0000

> + I need status reports on the following docs from the authors:
>
> =A0- Address Search (Arnt)
> =A0 =A0http://tools.ietf.org/html/draft-ietf-morg-address-search
>
> =A0- In Thread (Arnt)
> =A0 =A0http://tools.ietf.org/html/draft-ietf-morg-inthread
>
> =A0- Collations (Alexey)
> =A0 =A0http://tools.ietf.org/html/draft-ietf-morg-collations

I've discussed the first two with Arnt, and we think that the main
question for all three of these is the one we've been discussing with
Mark on the other thread:

Does the working group think these are important and worth proceeding
with?  Will there be enough implementation of them for it to be worth
putting them through?  Or are we just writing them because they're
plausible, but they'll wind up sitting on the shelf in a list of
seldom-implemented IMAP extensions.

Let's please start a discussion here (in this thread) about these
three documents.  If there's enough detailed discussion about any of
them, we can split that off.  Please, all the active participants
should come out of the woodwork here, scurry around, and answer this
question for the three (expired) drafts noted above.  (Mark: You
needn't comment unless you specifically want to; your opinion is
already noted.)

If there's not a significant base of support for these, and commitment
to implement them, I recommend to the chairs that we drop any or all
of these three.

Barry, MORG secretary

From tss@iki.fi  Mon Feb  1 15:08:36 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 6FAEF3A69AE for <morg@core3.amsl.com>; Mon,  1 Feb 2010 15:08:36 -0800 (PST)
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 WldPTelpPLaq for <morg@core3.amsl.com>; Mon,  1 Feb 2010 15:08:35 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 87E303A68DB for <morg@ietf.org>; Mon,  1 Feb 2010 15:08:35 -0800 (PST)
Received: from [192.168.10.199] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id 81D78FA8C53; Tue,  2 Feb 2010 01:09:10 +0200 (EET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Timo Sirainen <tss@iki.fi>
In-Reply-To: <6c9fcc2a1002011454p296ece05pff6a5fb422882474@mail.gmail.com>
Date: Tue, 2 Feb 2010 01:09:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <44BF2901-0048-4342-A52B-F7E6E698F4DA@iki.fi>
References: <6c9fcc2a1001211052h624abbf1h171f6ec19bef20e5@mail.gmail.com> <6c9fcc2a1002011454p296ece05pff6a5fb422882474@mail.gmail.com>
To: barryleiba@computer.org
X-Mailer: Apple Mail (2.1077)
Cc: morg <morg@ietf.org>
Subject: Re: [MORG] Getting MORG moving
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2010 23:08:36 -0000

On 2.2.2010, at 0.54, Barry Leiba wrote:

> Does the working group think these are important and worth proceeding
> with?  Will there be enough implementation of them for it to be worth
> putting them through?  Or are we just writing them because they're
> plausible, but they'll wind up sitting on the shelf in a list of
> seldom-implemented IMAP extensions.

>>  - Address Search (Arnt)
>>    http://tools.ietf.org/html/draft-ietf-morg-address-search

=46rom server point of view this is easy enough, so I could implement =
this for Dovecot. But I can't speak for client implementors.

>>  - In Thread (Arnt)
>>    http://tools.ietf.org/html/draft-ietf-morg-inthread

This is useful internally for Dovecot (for virtual mailboxes) and I've =
already implemented the actual SEARCH INTHREAD part of this. Whether =
it's useful to actual IMAP clients, again, I don't know.

>>  - Collations (Alexey)
>>    http://tools.ietf.org/html/draft-ietf-morg-collations

I thought we already agreed that we don't know (or don't agree) what the =
important collations are and this was put on hold.


From arnt@gulbrandsen.priv.no  Tue Feb  2 00:42:54 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F312228C1F6 for <morg@core3.amsl.com>; Tue,  2 Feb 2010 00:42:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bw3quXRitlzl for <morg@core3.amsl.com>; Tue,  2 Feb 2010 00:42:53 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id D71D128C154 for <morg@ietf.org>; Tue,  2 Feb 2010 00:42:52 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 54AAAFA0641; Tue,  2 Feb 2010 08:43:28 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO libertango.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1265100010-14604-14603/5/9 for morg@ietf.org; Tue, 2 Feb 2010 09:40:10 +0100
Message-Id: <4B67E717.1060107@gulbrandsen.priv.no>
Date: Tue, 2 Feb 2010 09:49:27 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
References: <6c9fcc2a1001211052h624abbf1h171f6ec19bef20e5@mail.gmail.com> <6c9fcc2a1002011454p296ece05pff6a5fb422882474@mail.gmail.com> <44BF2901-0048-4342-A52B-F7E6E698F4DA@iki.fi>
In-Reply-To: <44BF2901-0048-4342-A52B-F7E6E698F4DA@iki.fi>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [MORG] Getting MORG moving
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, 02 Feb 2010 08:42:54 -0000

I agree entirely with Timo, and will happily work on "my" two. But I 
will NOT discuss whether they're worth pursuing.

We can drop them now, or we can take them to RFC. If we take them to 
RFC, then the RFC can sink or swim. All three outcomes are fine with me. 
What's NOT fine is replying to new-draft announcements by telling me I 
should stop.

Someone sent me mail the other day about C=D saying his client now 
supports it, and it was a name I knew. I let that draft expire because 
several people told me it was worthless and/or harmful, and revived it 
later. Now it's the widest-implemented lemonade document, isn't it? I 
wouldn't have predicted that outcome, so I'm not going to any prediction 
about the MORG documents.

Arnt

From alexey.melnikov@isode.com  Tue Feb  2 02:41:00 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 5C37F28C273 for <morg@core3.amsl.com>; Tue,  2 Feb 2010 02:41:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level: 
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[AWL=0.141,  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 3jYfaOknukCR for <morg@core3.amsl.com>; Tue,  2 Feb 2010 02:40:59 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id E6D5628C271 for <morg@ietf.org>; Tue,  2 Feb 2010 02:40:58 -0800 (PST)
Received: from [92.40.26.171] (92.40.26.171.sub.mbb.three.co.uk [92.40.26.171])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <S2gBWQBCzhYo@rufus.isode.com>; Tue, 2 Feb 2010 10:41:35 +0000
Message-ID: <4B68014B.7090505@isode.com>
Date: Tue, 02 Feb 2010 10:41:15 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Timo Sirainen <tss@iki.fi>
References: <6c9fcc2a1001211052h624abbf1h171f6ec19bef20e5@mail.gmail.com> <6c9fcc2a1002011454p296ece05pff6a5fb422882474@mail.gmail.com> <44BF2901-0048-4342-A52B-F7E6E698F4DA@iki.fi>
In-Reply-To: <44BF2901-0048-4342-A52B-F7E6E698F4DA@iki.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: morg <morg@ietf.org>, barryleiba@computer.org
Subject: Re: [MORG] Getting MORG moving
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, 02 Feb 2010 10:41:00 -0000

Timo Sirainen wrote:

>On 2.2.2010, at 0.54, Barry Leiba wrote:
>  
>
>>Does the working group think these are important and worth proceeding
>>with?  Will there be enough implementation of them for it to be worth
>>putting them through?  Or are we just writing them because they're
>>plausible, but they'll wind up sitting on the shelf in a list of
>>seldom-implemented IMAP extensions.
>>    
>>
>>> - Address Search (Arnt)
>>>   http://tools.ietf.org/html/draft-ietf-morg-address-search
>>>      
>>>
>From server point of view this is easy enough, so I could implement this for Dovecot. But I can't speak for client implementors.
>  
>
I think this would make writing clients easier, especially if they 
require such extension.
How practical the latter assumption - I don't know.

>>> - In Thread (Arnt)
>>>   http://tools.ietf.org/html/draft-ietf-morg-inthread
>>>      
>>>
>This is useful internally for Dovecot (for virtual mailboxes) and I've already implemented the actual SEARCH INTHREAD part of this.
>
As a server implementor I find this useful

>Whether it's useful to actual IMAP clients, again, I don't know.
>  
>
Same here.

>>> - Collations (Alexey)
>>>   http://tools.ietf.org/html/draft-ietf-morg-collations
>>>      
>>>
>I thought we already agreed that we don't know (or don't agree) what the important collations are and this was put on hold.
>
Yes. There was some talk about working on a space ignore collation instead.


From root@core3.amsl.com  Fri Feb  5 09:00:01 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 C67143A6F51; Fri,  5 Feb 2010 09:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100205170001.C67143A6F51@core3.amsl.com>
Date: Fri,  5 Feb 2010 09:00:01 -0800 (PST)
Cc: morg@ietf.org
Subject: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2010 17:00:02 -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-02.txt
	Pages           : 10
	Date            : 2010-02-05

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-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-multimailbox-search-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From barryleiba.mailing.lists@gmail.com  Fri Feb  5 11:15: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 C496628C176 for <morg@core3.amsl.com>; Fri,  5 Feb 2010 11:15:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.969
X-Spam-Level: 
X-Spam-Status: No, score=-2.969 tagged_above=-999 required=5 tests=[AWL=-0.370, 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 jTmU75fu6xcg for <morg@core3.amsl.com>; Fri,  5 Feb 2010 11:15:28 -0800 (PST)
Received: from mail-fx0-f225.google.com (mail-fx0-f225.google.com [209.85.220.225]) by core3.amsl.com (Postfix) with ESMTP id 7A53428C16C for <morg@ietf.org>; Fri,  5 Feb 2010 11:15:27 -0800 (PST)
Received: by fxm25 with SMTP id 25so1208214fxm.32 for <morg@ietf.org>; Fri, 05 Feb 2010 11:16:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=wj8f6W2ikBmdPeXkkB2lSJOn5FtbiiKrkRdKTM9q6eA=; b=b847alUbcR0i5bSOsITAYbpZUSRRa3vtcqLZ/VhkpJiULlI10KVKlBKTPllNfwuR7m WTY5hc+F4ZTXRPHyY96IbkXxXQz4lQ919X0kV6yY7PcBMR7714sw+B9kVPuYWfcOFE9R dlvVT4NLSN42jYllQ7W6pNwoj6zIEH+Tp9S+0=
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=Il3y90cBK47DFCVezSBk3yS7xr2CfDafhQ25nYcB4jBq4E7i/LpP3fvQBbDxeXAvWa hwhXpP8krPbGFrBkjGq+kJ0CutlAExSkuX0kw5ijKycxzfmMcvHHS6dWZXuQN4AP+tD5 P47HVHCgffjNrCuvhSM3HRR56IJ54LhwcNoP8=
MIME-Version: 1.0
Received: by 10.223.77.141 with SMTP id g13mr3424330fak.95.1265397372735; Fri,  05 Feb 2010 11:16:12 -0800 (PST)
In-Reply-To: <20100205170001.C67143A6F51@core3.amsl.com>
References: <20100205170001.C67143A6F51@core3.amsl.com>
Date: Fri, 5 Feb 2010 14:16:12 -0500
Message-ID: <6c9fcc2a1002051116r64b9e75ay99d5b07a588cfbe0@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-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, 05 Feb 2010 19:15:38 -0000

I have updated the multimailbox-search draft, filling in some of the
gaps.  There's still a list of to-do items, so, folks: please review
this draft and help fill them in.  We need a general review of what's
there, and also a particular look at the "open issues" section to
resolve those issues.

I'll appreciate, as we discuss the open issues, suggestions for text
to resolve them (for those we think need text in the document).

Barry

On Fri, Feb 5, 2010 at 12:00 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-02.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 10
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-02-05
>
> The IMAP4 specification allows the searching only of the selected
> mailbox. =A0A 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. =A0This 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. =A0This also uses MAILBOX and TAG fields in ESEARCH
> responses, allowing a client to pipeline the searches if it chooses.
...
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-morg-multimailbox-search-0=
2.txt

From root@core3.amsl.com  Tue Feb  9 17:45:01 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 E7DEA3A764B; Tue,  9 Feb 2010 17:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100210014501.E7DEA3A764B@core3.amsl.com>
Date: Tue,  9 Feb 2010 17:45:01 -0800 (PST)
Cc: morg@ietf.org
Subject: [MORG] I-D Action:draft-ietf-morg-list-specialuse-01.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 01:45:02 -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-01.txt
	Pages           : 10
	Date            : 2010-02-09

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-01.txt

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

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

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

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


--NextPart--

From barryleiba.mailing.lists@gmail.com  Tue Feb  9 17:47:16 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 1140428C15C for <morg@core3.amsl.com>; Tue,  9 Feb 2010 17:47:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.875
X-Spam-Level: 
X-Spam-Status: No, score=-2.875 tagged_above=-999 required=5 tests=[AWL=-0.276, 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 99yu7KXpWPYx for <morg@core3.amsl.com>; Tue,  9 Feb 2010 17:47:15 -0800 (PST)
Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by core3.amsl.com (Postfix) with ESMTP id 18F293A764C for <morg@ietf.org>; Tue,  9 Feb 2010 17:47:14 -0800 (PST)
Received: by fxm10 with SMTP id 10so3281188fxm.29 for <morg@ietf.org>; Tue, 09 Feb 2010 17:48:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=LFE6GRKNx8e8KQBkZtaUbqo6nZarm8oK/7y1FMkZiAQ=; b=hG5fUUJVsktszR92DP0WbEWLozX0ctHRF+uySuahMIEbZdQR5ht2nPtv675YdsdanM OL1SdyjJS7FSyUy+rk+ajECgAWQq03Q5xD1E4a21QvwlqilOeR4SCOOWvHHiiDG5yKiS k0BMnkPo8FL3LkQ7cwsGbZwAmgIlDA34DYVzQ=
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=Grge7Xtp/ZmovJ/zwloF3TyWM/v08i3zT6BzMTjPH2lQb1fTRa3OfJbrHJDClQwEos phij9Lkbinqz92khyr3b/fXFauJnqZMeDsSN+cYUX28NI4HEMUKCqah7YkkyTL0pWKyo x5gWuc1PagPZZrKsNDtZCBQwHsOLXvL4lnh78=
MIME-Version: 1.0
Received: by 10.223.77.85 with SMTP id f21mr3291953fak.40.1265766498755; Tue,  09 Feb 2010 17:48:18 -0800 (PST)
In-Reply-To: <4B5F6E0A.7090709@isode.com>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com>
Date: Tue, 9 Feb 2010 20:48:18 -0500
Message-ID: <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@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] New WG document:draft-ietf-morg-list-specialuse-00
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, 10 Feb 2010 01:47:16 -0000

I've updated the draft with everything that's been discussed so far:
http://www.ietf.org/internet-drafts/draft-ietf-morg-list-specialuse-01.txt

Please review and comment further.

Barry

From barryleiba.mailing.lists@gmail.com  Tue Feb  9 17:48:32 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 9448D3A6991 for <morg@core3.amsl.com>; Tue,  9 Feb 2010 17:48:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.868
X-Spam-Level: 
X-Spam-Status: No, score=-2.868 tagged_above=-999 required=5 tests=[AWL=-0.269, 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 Jrl8Kgk46eBA for <morg@core3.amsl.com>; Tue,  9 Feb 2010 17:48:32 -0800 (PST)
Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by core3.amsl.com (Postfix) with ESMTP id A40423A764C for <morg@ietf.org>; Tue,  9 Feb 2010 17:48:31 -0800 (PST)
Received: by fxm10 with SMTP id 10so3281785fxm.29 for <morg@ietf.org>; Tue, 09 Feb 2010 17:49:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=LtLqm5HBPuuIozxPzonBWfT/Edp5owdPmYTIOkLwk6s=; b=m8RfMeAVY7GnHyMFV7leQ8IDs3Iyd++a4SUQAbd42eCrQ0HA1lq3V64pPpwb75zLue 2FBMr0tJ++HTOXQ1Gd7lW6C1Jwy880fPTjhog31IZuNo0WcbPiFTGTudQD726oW6kOBd 3esLwiQ5gUMsNIP605tjge7qcdOtUBGeM/WKs=
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=Outy+WXOSonLMZuLWyThggGoxGx11cNhRy1lKF8kv6LSrEPk2RV5M8Yk/9uvt5X/9o daRmXOJlC8+eX24zXbTgM3XPtyONoYB7sfRF52V4ln3dDkFyg4nbXKKLeRhkksDS45wx kPO0tPb1XICHR8pZQ7DR58Zb6knf+w75/ngRg=
MIME-Version: 1.0
Received: by 10.223.127.201 with SMTP id h9mr2220578fas.56.1265766577043; Tue,  09 Feb 2010 17:49:37 -0800 (PST)
In-Reply-To: <6c9fcc2a1002051116r64b9e75ay99d5b07a588cfbe0@mail.gmail.com>
References: <20100205170001.C67143A6F51@core3.amsl.com> <6c9fcc2a1002051116r64b9e75ay99d5b07a588cfbe0@mail.gmail.com>
Date: Tue, 9 Feb 2010 20:49:36 -0500
Message-ID: <6c9fcc2a1002091749p2e6815b8v1e8d2cb9aa188d1e@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-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, 10 Feb 2010 01:48:32 -0000

> I have updated the multimailbox-search draft, filling in some of the
> gaps. =A0There's still a list of to-do items, so, folks: please review
> this draft and help fill them in. =A0We need a general review of what's
> there, and also a particular look at the "open issues" section to
> resolve those issues.
>
> I'll appreciate, as we discuss the open issues, suggestions for text
> to resolve them (for those we think need text in the document).

Comments, please.  The open issues need to be resolved.

Barry

From dkarp@zimbra.com  Tue Feb  9 18:24: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 104A73A74F4 for <morg@core3.amsl.com>; Tue,  9 Feb 2010 18:24:03 -0800 (PST)
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 KBuhsZLUIlAf for <morg@core3.amsl.com>; Tue,  9 Feb 2010 18:24:02 -0800 (PST)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id 606863A67A4 for <morg@ietf.org>; Tue,  9 Feb 2010 18:24:02 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id D7A32C78140; Tue,  9 Feb 2010 18:25:07 -0800 (PST)
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 YNKGwwl1bwLc; Tue,  9 Feb 2010 18:24:54 -0800 (PST)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id 81785C7812D; Tue,  9 Feb 2010 18:24:54 -0800 (PST)
Date: Tue, 9 Feb 2010 18:24:58 -0800 (PST)
From: Dan Karp <dkarp@zimbra.com>
To: barryleiba@computer.org
Message-ID: <1069664565.4136.1265768698792.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.5_GA_2213.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.5_GA_2213.RHEL4_64)
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
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, 10 Feb 2010 02:24:03 -0000

> I've updated the draft with everything that's been discussed so far:
> http://www.ietf.org/internet-drafts/draft-ietf-morg-list-specialuse-01.txt
> 
> Please review and comment further.

I don't see any win with RETURN (SPECIAL-USE).  Why not just return the 
extra flags in all cases?

From nicolson@google.com  Tue Feb  9 19:06:51 2010
Return-Path: <nicolson@google.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 1113F28C15F for <morg@core3.amsl.com>; Tue,  9 Feb 2010 19:06:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.6
X-Spam-Level: 
X-Spam-Status: No, score=-104.6 tagged_above=-999 required=5 tests=[AWL=1.076,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 lHQQTuC5jV+G for <morg@core3.amsl.com>; Tue,  9 Feb 2010 19:06:50 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 35FD428C14D for <morg@ietf.org>; Tue,  9 Feb 2010 19:06:49 -0800 (PST)
Received: from spaceape14.eur.corp.google.com (spaceape14.eur.corp.google.com [172.28.16.148]) by smtp-out.google.com with ESMTP id o1A37uCw012224 for <morg@ietf.org>; Tue, 9 Feb 2010 19:07:56 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1265771277; bh=HcYx3D4xKxQmGgOkOsj1kow1xUY=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=LjxIR8KeQI5Jl1al2Cn/imu8oClcTEF6srkTx50Obs3UkCq5UKuQ6NJCrIRDWe4tt 2xehtSBeADZK1qAXj1S4g==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=ctj8U02EpPnmPPQQdYlkKcBh3/Sa2OVi2veRaC4nSae4vmNXBc+tMndyrGbPZAh/O hZOZIXeMcLu+RR3qVGt7Q==
Received: from yxe41 (yxe41.prod.google.com [10.190.2.41]) by spaceape14.eur.corp.google.com with ESMTP id o1A37qCu013487 for <morg@ietf.org>; Tue, 9 Feb 2010 19:07:55 -0800
Received: by yxe41 with SMTP id 41so11472961yxe.30 for <morg@ietf.org>; Tue, 09 Feb 2010 19:07:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.248.24 with SMTP id v24mr1433313ybh.148.1265771272298;  Tue, 09 Feb 2010 19:07:52 -0800 (PST)
In-Reply-To: <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com>  <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com>  <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com>
From: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Date: Tue, 9 Feb 2010 19:07:32 -0800
Message-ID: <f4edc8df1002091907q17b63e5bv4dcae5e19f735813@mail.gmail.com>
To: barryleiba@computer.org
Content-Type: multipart/alternative; boundary=000e0cd6a5e00d63ff047f3657a4
X-System-Of-Record: true
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
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, 10 Feb 2010 03:06:51 -0000

--000e0cd6a5e00d63ff047f3657a4
Content-Type: text/plain; charset=ISO-8859-1

I see the \Archive flag added. It seemed that its justification was to offer
functionality like Gmail, but I wanted to clarify that Gmail won't support
\Archive. "Archiving" in Gmail just means removal of the Inbox label, which
is accomplished in IMAP by deleting the message from the \Inbox mailbox.

On Tue, Feb 9, 2010 at 17:48, Barry Leiba <
barryleiba.mailing.lists@gmail.com> wrote:

> I've updated the draft with everything that's been discussed so far:
> http://www.ietf.org/internet-drafts/draft-ietf-morg-list-specialuse-01.txt
>
> Please review and comment further.
>
> Barry
> _______________________________________________
> MORG mailing list
> MORG@ietf.org
> https://www.ietf.org/mailman/listinfo/morg
> Note Well: http://www.ietf.org/maillist.html
>

--000e0cd6a5e00d63ff047f3657a4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I see the \Archive flag added. It seemed that its justification was to offe=
r functionality like Gmail, but I wanted to clarify that Gmail won&#39;t su=
pport \Archive. &quot;Archiving&quot; in Gmail just means removal of the In=
box label, which is accomplished in IMAP by deleting the message from the \=
Inbox mailbox.<br>

<br><div class=3D"gmail_quote">On Tue, Feb 9, 2010 at 17:48, Barry Leiba <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:barryleiba.mailing.lists@gmail.com">b=
arryleiba.mailing.lists@gmail.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex;">

I&#39;ve updated the draft with everything that&#39;s been discussed so far=
:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-morg-list-special=
use-01.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-iet=
f-morg-list-specialuse-01.txt</a><br>
<br>
Please review and comment further.<br>
<font color=3D"#888888"><br>
Barry<br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<br>
MORG mailing list<br>
<a href=3D"mailto:MORG@ietf.org">MORG@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/morg" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/morg</a><br>
Note Well: <a href=3D"http://www.ietf.org/maillist.html" target=3D"_blank">=
http://www.ietf.org/maillist.html</a><br>
</div></div></blockquote></div><br>

--000e0cd6a5e00d63ff047f3657a4--

From barryleiba.mailing.lists@gmail.com  Tue Feb  9 19:14:16 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 C43A228C1CF for <morg@core3.amsl.com>; Tue,  9 Feb 2010 19:14:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.862
X-Spam-Level: 
X-Spam-Status: No, score=-2.862 tagged_above=-999 required=5 tests=[AWL=-0.263, 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 Iq+YTY9Krp5E for <morg@core3.amsl.com>; Tue,  9 Feb 2010 19:14:15 -0800 (PST)
Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by core3.amsl.com (Postfix) with ESMTP id 9265528C15F for <morg@ietf.org>; Tue,  9 Feb 2010 19:14:15 -0800 (PST)
Received: by fxm10 with SMTP id 10so3319649fxm.29 for <morg@ietf.org>; Tue, 09 Feb 2010 19:15:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=vsQ/Zr07wnwmS99rYCMDLhH+mr5S4drwMkgN7cn/Nf4=; b=gN1eGY6fpKsQLcpDTGKFaaRVFRgkEkQhft0Ok2X1/+2AElswUCd6xueFy15fiAXiZ3 3IbCzmBqJu6P/wvnvcALtNs3ctRJP+5ETFwcuIhgQyalCEeeiWEZniEN5tepnXSMCNgo +gco37x09aoKZqKf9sPrjlxP1hFT/oNga9lEs=
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=YZrjGVzscFRtZ0RiXLR3yMydBIvg98vuQUbseldbVf+0cPIp8D4x9f2VzfGk9rSlbm Es4K2KVykMa9dIUt2pp+7H5nXqSqu5qXS08EnNuzR0aKuF03tgtl9/IukAEnkr/2lWGb r2vnf7aYEMOsDHDWd/9omfJ/8Vc6TydWKNW20=
MIME-Version: 1.0
Received: by 10.223.14.194 with SMTP id h2mr4641069faa.14.1265771720394; Tue,  09 Feb 2010 19:15:20 -0800 (PST)
In-Reply-To: <f4edc8df1002091907q17b63e5bv4dcae5e19f735813@mail.gmail.com>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <f4edc8df1002091907q17b63e5bv4dcae5e19f735813@mail.gmail.com>
Date: Tue, 9 Feb 2010 22:15:20 -0500
Message-ID: <6c9fcc2a1002091915y7d20eba4tfba26c5c45147fdc@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] New WG document:draft-ietf-morg-list-specialuse-00
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, 10 Feb 2010 03:14:16 -0000

Jamie says...
> I see the \Archive flag added. It seemed that its justification was to offer
> functionality like Gmail, but I wanted to clarify that Gmail won't support
> \Archive. "Archiving" in Gmail just means removal of the Inbox label, which
> is accomplished in IMAP by deleting the message from the \Inbox mailbox.

Right; actually, \Archive was suggested by Filip Navara as a feature
that could be used by systems that handled archiving *differently* to
Gmail.  So, actually, it's a good thing to have another non-Gmail
feature that way.

Dan says...
> I don't see any win with RETURN (SPECIAL-USE).  Why not just return
> the extra flags in all cases?

It's there to be parallel to the CHILDREN case (and it was suggested
by Timo), but you're probably right: computing children *might* be
expensive, but I can't imagine that retrieving mailbox use flags would
be expensive enough that it might be avoided if the client doesn't
care.

Does anyone else have an opinion on this?  Should I pull that out of
the next (final?) version, or should we leave it in?

Barry

From tss@iki.fi  Tue Feb  9 19:45:27 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 BFDFF28C273 for <morg@core3.amsl.com>; Tue,  9 Feb 2010 19:45:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.358
X-Spam-Level: 
X-Spam-Status: No, score=-6.358 tagged_above=-999 required=5 tests=[AWL=0.241,  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 AIUDskc+WTqr for <morg@core3.amsl.com>; Tue,  9 Feb 2010 19:45:27 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id A9E3328C26A for <morg@ietf.org>; Tue,  9 Feb 2010 19:45:26 -0800 (PST)
Received: from [192.168.10.199] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id C6C0916471E5; Wed, 10 Feb 2010 05:46:32 +0200 (EET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Timo Sirainen <tss@iki.fi>
In-Reply-To: <6c9fcc2a1002091915y7d20eba4tfba26c5c45147fdc@mail.gmail.com>
Date: Wed, 10 Feb 2010 05:46:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7A6CC53-AEB8-455D-B32F-E46543DAED42@iki.fi>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <f4edc8df1002091907q17b63e5bv4dcae5e19f735813@mail.gmail.com> <6c9fcc2a1002091915y7d20eba4tfba26c5c45147fdc@mail.gmail.com>
To: barryleiba@computer.org
X-Mailer: Apple Mail (2.1077)
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
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, 10 Feb 2010 03:45:27 -0000

On 10.2.2010, at 5.15, Barry Leiba wrote:

> Dan says...
>> I don't see any win with RETURN (SPECIAL-USE).  Why not just return
>> the extra flags in all cases?
>=20
> It's there to be parallel to the CHILDREN case (and it was suggested
> by Timo),

"Suggested" is a bit strong word :) "Wondering" was what I originally =
used.

> but you're probably right: computing children *might* be
> expensive, but I can't imagine that retrieving mailbox use flags would
> be expensive enough that it might be avoided if the client doesn't
> care.

Yes, I didn't think of the cost of computing children flags. The only =
difference would be reduction of network traffic, but that's quite a =
tiny amount.

> Does anyone else have an opinion on this?  Should I pull that out of
> the next (final?) version, or should we leave it in?

Removing it reduces complexity at least.


From filip.navara@gmail.com  Wed Feb 10 00:25:35 2010
Return-Path: <filip.navara@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 45B943A74F4 for <morg@core3.amsl.com>; Wed, 10 Feb 2010 00:25:35 -0800 (PST)
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 Qaz3u20oYr78 for <morg@core3.amsl.com>; Wed, 10 Feb 2010 00:25:34 -0800 (PST)
Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id 3F08A3A754E for <morg@ietf.org>; Wed, 10 Feb 2010 00:25:33 -0800 (PST)
Received: by bwz19 with SMTP id 19so1657066bwz.28 for <morg@ietf.org>; Wed, 10 Feb 2010 00:26:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=So77gcUS1mSC+222968a24sFyeYkbXXcI9jX4slaSRc=; b=jLX3D1GO8jOJRXo3ve475Gzbe1FBwkZAlEFqaWOWLui1pzzW1tbU3tLHxBFoQfWZPK zI4JGcQ52upkXmY7Wvgb3QZ7wbkaL2/xLDTltgMMYhOBViEIhGVK/NwdYo1dmIPN4uQz 540mvyZNG36ZgRGTTz4CvyNQ1SrY3nCcRlgVI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=q4WlCa6ddAywDMEZDDbPJmxIK3DiuJ/MUiSKdsvxyTkDoYoAEKP8WlU5gTHpWxepjM yaKZfD8hMpaLcSF1AMPAcpnu+c/LxeNHoQSkX7HWk7VGHqiJvSqCHlxQVeg5zJ+NnIa0 1sAS5ZK4/DpHekT8kJ28gRlM2Wyg+ZXXUBq6s=
MIME-Version: 1.0
Received: by 10.204.33.196 with SMTP id i4mr4628094bkd.155.1265790399581; Wed,  10 Feb 2010 00:26:39 -0800 (PST)
In-Reply-To: <20100210014501.E7DEA3A764B@core3.amsl.com>
References: <20100210014501.E7DEA3A764B@core3.amsl.com>
Date: Wed, 10 Feb 2010 09:26:39 +0100
Message-ID: <5b31733c1002100026r38eb57f9p73a687794bbd36e4@mail.gmail.com>
From: Filip Navara <filip.navara@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-01.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 08:25:35 -0000

On Wed, Feb 10, 2010 at 2:45 AM,  <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 : 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-=
01.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 10
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-02-09
>
> Some IMAP message stores include special-use mailboxes, such as those
> used to hold draft messages or sent messages. =A0Many 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. =A0This 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. =A0Discussion
> 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-01.tx=
t
>
> 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.
>
>
> _______________________________________________
> MORG mailing list
> MORG@ietf.org
> https://www.ietf.org/mailman/listinfo/morg
> Note Well: http://www.ietf.org/maillist.html
>
>


In section "4.1.  Example of an IMAP LIST command" - shouldn't the
following line

    S: * LIST (\Marked \HasNoChildren) "/" Inbox

be

    S: * LIST (\Marked \HasNoChildren \Inbox) "/" Inbox

?

I don't know if the \Inbox flag is way too useful since the regular
LIST command has to use the "INBOX" reserved name anyway. XLIST used
to return localized name for Inbox, which was a justification for the
flag, but you can't do that for regular LIST.

Best regards,
Filip Navara

From barryleiba.mailing.lists@gmail.com  Wed Feb 10 10:38:06 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 DA74528C211 for <morg@core3.amsl.com>; Wed, 10 Feb 2010 10:38:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.857
X-Spam-Level: 
X-Spam-Status: No, score=-2.857 tagged_above=-999 required=5 tests=[AWL=-0.258, 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 rq7al85nFI4I for <morg@core3.amsl.com>; Wed, 10 Feb 2010 10:38:06 -0800 (PST)
Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by core3.amsl.com (Postfix) with ESMTP id C04A928C224 for <morg@ietf.org>; Wed, 10 Feb 2010 10:38:05 -0800 (PST)
Received: by fxm10 with SMTP id 10so332792fxm.29 for <morg@ietf.org>; Wed, 10 Feb 2010 10:39:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=zbmf0ueYVkmJmw9rOdJCXiLAd8LfIMXccDX6RMpm02c=; b=TOYAuNTA0CRWu2CSuPgevYW9Q8LBZ96cVyUYaNauAC5gQdJhNog7lZdMPR7WDB/WBA wsXsbjgjOeM+yMMyox9XoWRb0ddfgyw3I/HX4P0Spy2B9p/7jHErAdwVU/E6RKe32ZrO GUBkt7XH06TUD2kLMLACky93Lk4Tln4Jd946U=
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=sztKAmbJllGNuCouUmLUZNKqWFoe1LCmn+sloB8zttly/3NQH4sASS+FqYjrzU9aGA kS2nKrrefBaH+HfoZqZhE6kitfnApzxLv3gF/BBWXMNL7xbAgZ6q+uSBMk/69HlkFM3Z lYP5TG0ZlmTivhKiaELBygKHAouG8Yp+VTj3w=
MIME-Version: 1.0
Received: by 10.223.16.199 with SMTP id p7mr737888faa.88.1265827153530; Wed,  10 Feb 2010 10:39:13 -0800 (PST)
In-Reply-To: <5b31733c1002100026r38eb57f9p73a687794bbd36e4@mail.gmail.com>
References: <20100210014501.E7DEA3A764B@core3.amsl.com> <5b31733c1002100026r38eb57f9p73a687794bbd36e4@mail.gmail.com>
Date: Wed, 10 Feb 2010 13:39:13 -0500
Message-ID: <6c9fcc2a1002101039g749610c4p4aa30a385f7f37d1@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Filip Navara <filip.navara@gmail.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-01.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, 10 Feb 2010 18:38:07 -0000

> In section "4.1. =A0Example of an IMAP LIST command" - shouldn't the
> following line
>
> =A0 =A0S: * LIST (\Marked \HasNoChildren) "/" Inbox
>
> be
>
> =A0 =A0S: * LIST (\Marked \HasNoChildren \Inbox) "/" Inbox

I could always say no, because all of the flags are optional... so
this server simply doesn't support the \Inbox flag.  But actually,
it's an oversight in creating the example.  :-)

But...

> I don't know if the \Inbox flag is way too useful since the regular
> LIST command has to use the "INBOX" reserved name anyway. XLIST used
> to return localized name for Inbox, which was a justification for the
> flag, but you can't do that for regular LIST.

This is a good point.  Should we remove \Inbox ?  Then Gmail will just
use the \Inbox flag in their implementation of XLIST, and in regular
LIST the client will know that the inbox is called "inbox".

Barry

From nicolson@google.com  Wed Feb 10 11:48:11 2010
Return-Path: <nicolson@google.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 C64D528C224 for <morg@core3.amsl.com>; Wed, 10 Feb 2010 11:48:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.959
X-Spam-Level: 
X-Spam-Status: No, score=-104.959 tagged_above=-999 required=5 tests=[AWL=0.717, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Jad90GUn40Zs for <morg@core3.amsl.com>; Wed, 10 Feb 2010 11:48:10 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.33.17]) by core3.amsl.com (Postfix) with ESMTP id 68E4A28C243 for <morg@ietf.org>; Wed, 10 Feb 2010 11:48:09 -0800 (PST)
Received: from wpaz37.hot.corp.google.com (wpaz37.hot.corp.google.com [172.24.198.101]) by smtp-out.google.com with ESMTP id o1AJnH0k002807 for <morg@ietf.org>; Wed, 10 Feb 2010 19:49:17 GMT
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1265831359; bh=xyJWZkW8DG9zeBqbDx0prYWjZ7Q=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=FrsBKzfoxU6lUgOAs53OK3poJMYGzZjD3Rxn/VijXmcwbTY4c925chP0UzehKmRIS rIfFE0f6DzZ0uRuov7Oog==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=WT31VI5ujo+SMP6sJ27C+ULLAP3/8WZPKuas4YZYkhoHv7C38tMyl9WQEeq9fvSUX 4X5UdSDWzwYwPQx+QVhww==
Received: from yxe32 (yxe32.prod.google.com [10.190.2.32]) by wpaz37.hot.corp.google.com with ESMTP id o1AJnGnn001678 for <morg@ietf.org>; Wed, 10 Feb 2010 11:49:16 -0800
Received: by yxe32 with SMTP id 32so546875yxe.0 for <morg@ietf.org>; Wed, 10 Feb 2010 11:49:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.240.13 with SMTP id n13mr3062107ybh.333.1265831356245;  Wed, 10 Feb 2010 11:49:16 -0800 (PST)
In-Reply-To: <6c9fcc2a1002101039g749610c4p4aa30a385f7f37d1@mail.gmail.com>
References: <20100210014501.E7DEA3A764B@core3.amsl.com> <5b31733c1002100026r38eb57f9p73a687794bbd36e4@mail.gmail.com>  <6c9fcc2a1002101039g749610c4p4aa30a385f7f37d1@mail.gmail.com>
From: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Date: Wed, 10 Feb 2010 11:48:56 -0800
Message-ID: <f4edc8df1002101148p7febf342jac96221152727ca1@mail.gmail.com>
To: barryleiba@computer.org
Content-Type: multipart/alternative; boundary=000e0cd355a655ae77047f445495
X-System-Of-Record: true
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-list-specialuse-01.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 19:48:11 -0000

--000e0cd355a655ae77047f445495
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Feb 10, 2010 at 10:39, Barry Leiba <
barryleiba.mailing.lists@gmail.com> wrote:

> > In section "4.1.  Example of an IMAP LIST command" - shouldn't the
> > following line
> >
> >    S: * LIST (\Marked \HasNoChildren) "/" Inbox
> >
> > be
> >
> >    S: * LIST (\Marked \HasNoChildren \Inbox) "/" Inbox
>
> I could always say no, because all of the flags are optional... so
> this server simply doesn't support the \Inbox flag.  But actually,
> it's an oversight in creating the example.  :-)
>
> But...
>
> > I don't know if the \Inbox flag is way too useful since the regular
> > LIST command has to use the "INBOX" reserved name anyway. XLIST used
> > to return localized name for Inbox, which was a justification for the
> > flag, but you can't do that for regular LIST.
>
> This is a good point.  Should we remove \Inbox ?  Then Gmail will just
> use the \Inbox flag in their implementation of XLIST, and in regular
> LIST the client will know that the inbox is called "inbox".
>

This works for Gmail.

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

--000e0cd355a655ae77047f445495
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Wed, Feb 10, 2010 at 10:39, Barry Lei=
ba <span dir=3D"ltr">&lt;<a href=3D"mailto:barryleiba.mailing.lists@gmail.c=
om">barryleiba.mailing.lists@gmail.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex;">

<div class=3D"im">&gt; In section &quot;4.1. =A0Example of an IMAP LIST com=
mand&quot; - shouldn&#39;t the<br>
&gt; following line<br>
&gt;<br>
&gt; =A0 =A0S: * LIST (\Marked \HasNoChildren) &quot;/&quot; Inbox<br>
&gt;<br>
&gt; be<br>
&gt;<br>
&gt; =A0 =A0S: * LIST (\Marked \HasNoChildren \Inbox) &quot;/&quot; Inbox<b=
r>
<br>
</div>I could always say no, because all of the flags are optional... so<br=
>
this server simply doesn&#39;t support the \Inbox flag. =A0But actually,<br=
>
it&#39;s an oversight in creating the example. =A0:-)<br>
<br>
But...<br>
<div class=3D"im"><br>
&gt; I don&#39;t know if the \Inbox flag is way too useful since the regula=
r<br>
&gt; LIST command has to use the &quot;INBOX&quot; reserved name anyway. XL=
IST used<br>
&gt; to return localized name for Inbox, which was a justification for the<=
br>
&gt; flag, but you can&#39;t do that for regular LIST.<br>
<br>
</div>This is a good point. =A0Should we remove \Inbox ? =A0Then Gmail will=
 just<br>
use the \Inbox flag in their implementation of XLIST, and in regular<br>
LIST the client will know that the inbox is called &quot;inbox&quot;.<br></=
blockquote><div><br></div><div>This works for Gmail.=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex;">


<font color=3D"#888888"><br>
Barry<br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<br>
MORG mailing list<br>
<a href=3D"mailto:MORG@ietf.org">MORG@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/morg" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/morg</a><br>
Note Well: <a href=3D"http://www.ietf.org/maillist.html" target=3D"_blank">=
http://www.ietf.org/maillist.html</a><br>
</div></div></blockquote></div><br>

--000e0cd355a655ae77047f445495--

From filip.navara@gmail.com  Thu Feb 11 07:27:04 2010
Return-Path: <filip.navara@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 A353F3A7244 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 07:27:04 -0800 (PST)
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 HJTS4-VQ6c4s for <morg@core3.amsl.com>; Thu, 11 Feb 2010 07:27:03 -0800 (PST)
Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id 7495D3A70A0 for <morg@ietf.org>; Thu, 11 Feb 2010 07:27:03 -0800 (PST)
Received: by bwz19 with SMTP id 19so486138bwz.28 for <morg@ietf.org>; Thu, 11 Feb 2010 07:28:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=6IZJ8oeUSy2uiFRy0Pt6229zGnekzMlkt+QTW32FuOs=; b=YQb0Znxeni0rALw4u+/gtARfw1Los3+om8tJP8cz7vTgQkCS2r4smKZ27mghwl8iOp 2Ymkp5TkxC1x1PhwtAtPI49vrHSP6i6MBU7JGo3uqi27e9wjmtTWOdARvjmD4LjpzFr+ IOZz/FPnSVDePkyVapj3f17aoXzCEQ9ANbFHs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=NXUtViW8uxeZlFhEZQpQMjwG5oKL2OGoFARl0hxu834u1xK7p6J7d5rCLt15bGPf2y FpNCEUTac7G38qApzhNl1uGK8nWigiUVYbehUNUyTqcy/oPj6KEV9/xQNeEmTpjnWppn 5YFINvbmDz3zavE+0cx1IJpRTlmiaOUS9KQxw=
MIME-Version: 1.0
Received: by 10.204.144.86 with SMTP id y22mr11704bku.43.1265902093704; Thu,  11 Feb 2010 07:28:13 -0800 (PST)
In-Reply-To: <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com>
Date: Thu, 11 Feb 2010 16:28:13 +0100
Message-ID: <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com>
From: Filip Navara <filip.navara@gmail.com>
To: barryleiba@computer.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 15:27:04 -0000

On Wed, Feb 10, 2010 at 2:48 AM, Barry Leiba
<barryleiba.mailing.lists@gmail.com> wrote:
> I've updated the draft with everything that's been discussed so far:
> http://www.ietf.org/internet-drafts/draft-ietf-morg-list-specialuse-01.txt
>
> Please review and comment further.
>
> Barry

Ok, one more nitpick. How do I know, as a client writer, to which
level do I need to enumerate the folders in order to detect the
special ones? Most servers have them at the root level, so LIST "" "%"
will list them all. Google has them at second level, so I need to do
the LIST at least two levels deep (eg. LIST "" "%/%" or LIST ""
"[Gmail]/%"). With XLIST I knew that based on the capability I need to
list the folders at least two levels deep (given all the known
implementations) in order to detect the special ones. Using LIST ""
"*" is discouraged and without a capability I will never know how deep
do I need to list the folders. I'd certainly appreciate a guideline
for client writers in regard to this...

Best regards,
Filip Navara

From tss@iki.fi  Thu Feb 11 07:48:57 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 0632C3A76F6 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 07:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.398
X-Spam-Level: 
X-Spam-Status: No, score=-6.398 tagged_above=-999 required=5 tests=[AWL=0.201,  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 UeYHh01-B+Qu for <morg@core3.amsl.com>; Thu, 11 Feb 2010 07:48:56 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 195503A7592 for <morg@ietf.org>; Thu, 11 Feb 2010 07:48:56 -0800 (PST)
Received: from [192.168.10.2] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id BCFFAFA8B22; Thu, 11 Feb 2010 17:50:08 +0200 (EET)
From: Timo Sirainen <tss@iki.fi>
To: Filip Navara <filip.navara@gmail.com>
In-Reply-To: <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-45HH8B467wKE6Z4IAikx"
Date: Thu, 11 Feb 2010 17:50:04 +0200
Message-ID: <1265903404.21277.6.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.2 
Cc: morg@ietf.org, barryleiba@computer.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 15:48:57 -0000

--=-45HH8B467wKE6Z4IAikx
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable

On Thu, 2010-02-11 at 16:28 +0100, Filip Navara wrote:
> Ok, one more nitpick. How do I know, as a client writer, to which
> level do I need to enumerate the folders in order to detect the
> special ones? Most servers have them at the root level, so LIST "" "%"
> will list them all. Google has them at second level, so I need to do
> the LIST at least two levels deep (eg. LIST "" "%/%" or LIST ""
> "[Gmail]/%").

First thought that comes to my mind: Add yet another flag, such as
\HasSpecialChildren.


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

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

iEYEABECAAYFAkt0JysACgkQyUhSUUBVisnSFgCfcocrEZJMQ0yvsp9kCzcb++2+
DC0An0K3adexK39TooYvnC+NQnRZ8Iyj
=7C2A
-----END PGP SIGNATURE-----

--=-45HH8B467wKE6Z4IAikx--


From arnt@gulbrandsen.priv.no  Thu Feb 11 07:57:17 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A77D53A784A for <morg@core3.amsl.com>; Thu, 11 Feb 2010 07:57:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.461
X-Spam-Level: 
X-Spam-Status: No, score=-2.461 tagged_above=-999 required=5 tests=[AWL=0.137,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFreh6Z+KhW3 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 07:57:17 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id D0E043A7847 for <morg@ietf.org>; Thu, 11 Feb 2010 07:57:16 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id BEF88FA071D; Thu, 11 Feb 2010 15:58:29 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO libertango.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1265903907-22960-22959/5/17 (2 recipients); Thu, 11 Feb 2010 16:58:27 +0100
Message-Id: <4B742A88.1050206@gulbrandsen.priv.no>
Date: Thu, 11 Feb 2010 17:04:24 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina>
In-Reply-To: <1265903404.21277.6.camel@hurina>
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 15:57:17 -0000

On 02/11/2010 04:50 PM, Timo Sirainen wrote:
> First thought that comes to my mind: Add yet another flag, such as
> \HasSpecialChildren.

Listext added "selection options" for such things. Is there any reason 
to avoid that?

Arnt

From tss@iki.fi  Thu Feb 11 08:22:08 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 78E363A6EAE for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:22:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.427
X-Spam-Level: 
X-Spam-Status: No, score=-6.427 tagged_above=-999 required=5 tests=[AWL=0.172,  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 TZwWUeTbZHeD for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:22:07 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 0B54428C1E0 for <morg@ietf.org>; Thu, 11 Feb 2010 08:22:06 -0800 (PST)
Received: from [192.168.10.2] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id DAD23FA8C2B; Thu, 11 Feb 2010 18:23:20 +0200 (EET)
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
In-Reply-To: <4B742A88.1050206@gulbrandsen.priv.no>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina> <4B742A88.1050206@gulbrandsen.priv.no>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-zgRUhei197Trb5ZJ5g8h"
Date: Thu, 11 Feb 2010 18:23:20 +0200
Message-ID: <1265905400.21277.30.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.2 
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 16:22:08 -0000

--=-zgRUhei197Trb5ZJ5g8h
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable

On Thu, 2010-02-11 at 17:04 +0100, Arnt Gulbrandsen wrote:
> On 02/11/2010 04:50 PM, Timo Sirainen wrote:
> > First thought that comes to my mind: Add yet another flag, such as
> > \HasSpecialChildren.
>=20
> Listext added "selection options" for such things. Is there any reason=20
> to avoid that?

Well, I thought of two ways, neither one really seems much better:

a)

C: C04 LIST (SPECIAL-USE RECURSIVEMATCH) "" "%"
S: * LIST (\Noselect \HasChildren) "/" "[Gmail]" ("CHILDINFO" ("SPECIAL-USE=
"))
..
S: C04 OK done

But RECURSIVEMATCH seems to be described in a way that it's used only
when some other option otherwise filters out mailboxes. So the above
would mean more like "show only special-use mailboxes", and the LIST
would give only the one [Gmail] mailbox reply.

b)=20

C: C04 LIST (SPECIAL-CHILDREN) "" "%"=20
S: * LIST (\Noselect \HasChildren) "/" "[Gmail]" ("SPECIAL-CHILDREN" "1")
..
S: C04 OK done

Or something like that .. This seems pretty horrible though.

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

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

iEYEABECAAYFAkt0LvcACgkQyUhSUUBVisnONwCeJVvDqlHQwr9fotM14mJtQbML
ZvEAn2NVzq6HR7vmKH4EVImrnQ01z96/
=86bh
-----END PGP SIGNATURE-----

--=-zgRUhei197Trb5ZJ5g8h--


From arnt@gulbrandsen.priv.no  Thu Feb 11 08:37:11 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E36B93A7763 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:37:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.473
X-Spam-Level: 
X-Spam-Status: No, score=-2.473 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xuHasrtUs19s for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:37:11 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 094313A7756 for <morg@ietf.org>; Thu, 11 Feb 2010 08:37:11 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id B3694FA0723; Thu, 11 Feb 2010 16:38:24 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO lochnagar.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1265906302-22960-22959/5/18 for morg@ietf.org; Thu, 11 Feb 2010 17:38:22 +0100
Message-Id: <GFolqi66YIKYfXwiWfJAwg.md5@lochnagar.gulbrandsen.priv.no>
Date: Thu, 11 Feb 2010 17:38:37 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: morg@ietf.org
Organization: http://arnt.gulbrandsen.priv.no
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina> <4B742A88.1050206@gulbrandsen.priv.no> <1265905400.21277.30.camel@hurina>
In-Reply-To: <1265905400.21277.30.camel@hurina>
Content-Type: text/plain; format=flowed
Mime-Version: 1.0
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 16:37:12 -0000

Timo Sirainen writes:
> Well, I thought of two ways, neither one really seems much better:

Why would anyone bother with %? There are only a few special-use 
mailboxes, so just get all of them at once:

   a list (special-use) "" "*"

% is fine for progressive discovery, but why should one progressively 
discover four mailboxes?

Arnt

From filip.navara@gmail.com  Thu Feb 11 08:39:50 2010
Return-Path: <filip.navara@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 4FDB13A7734 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:39:50 -0800 (PST)
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 llhdVMAD5CKi for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:39:49 -0800 (PST)
Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id 4F85E3A76D6 for <morg@ietf.org>; Thu, 11 Feb 2010 08:39:49 -0800 (PST)
Received: by bwz19 with SMTP id 19so581163bwz.28 for <morg@ietf.org>; Thu, 11 Feb 2010 08:41:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=eYu1e7imL4I8QoGGDk0u4TWK9gGVBVMM+IDj8CSkVDU=; b=PnwC/c3IJRQjogDK1G971IVfbzbL5iUyVdARMt/bQXa2LuI/APuP6BGtjipO4RzzrA N6q3RWphRdzezN1cnCG/Et+WQ7OJVFBUUr62HSmo+hmafy2w/aSVMYwLKkw0j/9AkyHa ROjrazPv/jX636lMroY+YLuFF7ZKY0eHHA/QA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=gQHGh8WKtA+JX5pTIn7241XiUsksXxy5QBd5MON3SNlEtZFou1KhqfwazrZZcKZ3hY 4vU8uAS3IiSX/Lbliz/FBJMZBk3xbpjuFT5ebU+jyHeat5MGX98kT7ltvbSIspn7R2FN dlDBAB/ieNS6M/duAMDNIu3+ksVIkejyDvpn8=
MIME-Version: 1.0
Received: by 10.204.32.206 with SMTP id e14mr73660bkd.45.1265906460747; Thu,  11 Feb 2010 08:41:00 -0800 (PST)
In-Reply-To: <GFolqi66YIKYfXwiWfJAwg.md5@lochnagar.gulbrandsen.priv.no>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina> <4B742A88.1050206@gulbrandsen.priv.no> <1265905400.21277.30.camel@hurina> <GFolqi66YIKYfXwiWfJAwg.md5@lochnagar.gulbrandsen.priv.no>
Date: Thu, 11 Feb 2010 17:41:00 +0100
Message-ID: <5b31733c1002110841i13cd9fb8m7cf8fca329cf520b@mail.gmail.com>
From: Filip Navara <filip.navara@gmail.com>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 16:39:50 -0000

On Thu, Feb 11, 2010 at 5:38 PM, Arnt Gulbrandsen
<arnt@gulbrandsen.priv.no> wrote:
> Timo Sirainen writes:
>>
>> Well, I thought of two ways, neither one really seems much better:
>
> Why would anyone bother with %? There are only a few special-use mailboxe=
s,
> so just get all of them at once:
>
> =A0a list (special-use) "" "*"
>
> % is fine for progressive discovery, but why should one progressively
> discover four mailboxes?
>
> Arnt

The specification didn't depend on LISTEXT, now it would. I'm fine
with that as long as the server implementers support it.

Filip

From arnt@gulbrandsen.priv.no  Thu Feb 11 08:45:25 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8A2C28C0F8 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:45:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.115,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ayLcAkRzX0nf for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:45:25 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 18E8128C1FE for <morg@ietf.org>; Thu, 11 Feb 2010 08:45:25 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id B84B4FA0720; Thu, 11 Feb 2010 16:46:38 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO lochnagar.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1265906796-22960-22959/5/19 (3 recipients); Thu, 11 Feb 2010 17:46:36 +0100
Message-Id: <n/yQCGZ4AXdJ0nvuWsINcw.md5@lochnagar.gulbrandsen.priv.no>
Date: Thu, 11 Feb 2010 17:46:50 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Filip Navara <filip.navara@gmail.com>
Organization: http://arnt.gulbrandsen.priv.no
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina> <4B742A88.1050206@gulbrandsen.priv.no> <1265905400.21277.30.camel@hurina> <GFolqi66YIKYfXwiWfJAwg.md5@lochnagar.gulbrandsen.priv.no> <5b31733c1002110841i13cd9fb8m7cf8fca329cf520b@mail.gmail.com>
In-Reply-To: <5b31733c1002110841i13cd9fb8m7cf8fca329cf520b@mail.gmail.com>
Content-Type: text/plain; format=flowed
Mime-Version: 1.0
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 16:45:26 -0000

Filip Navara writes:
> The specification didn't depend on LISTEXT, now it would. I'm fine 
> with that as long as the server implementers support it.

Good point. IIRC the usual suspects already have listext 
implementations, but I note that gmail does not. Anyone else? Is it 
acceptable to depend on listext?

Arnt

From filip.navara@gmail.com  Thu Feb 11 08:48:07 2010
Return-Path: <filip.navara@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 BBA2328C209 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:48:07 -0800 (PST)
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 bJHWnUR17eVl for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:48:07 -0800 (PST)
Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id CC6D628C207 for <morg@ietf.org>; Thu, 11 Feb 2010 08:48:06 -0800 (PST)
Received: by bwz19 with SMTP id 19so591609bwz.28 for <morg@ietf.org>; Thu, 11 Feb 2010 08:49:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=iXlSICK9U/7nQlHNII6hieUT3aviR438iqbFNNaFyZg=; b=xKi566K95PpaW5w+rkMIILGPNzwyAbkhK1rL/kxV+qq/Uc2uAiqUSjKhXDFgszsLkt OXmRC357WMiw0Omlj2C643Dl2gZPkJNbR6VwnWvhdua2DsF21TuoHHb4b48SG9Avg5n3 ufmjHnJb8iYNsEBhU+j8+jFr8kujlZM8/GC4U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QlYV8gNTp+H18KqkX+tIfOrwujGLhQuj6lmf8VJVs6SN5bq9YieUGyFXI+YBnSqNfw rqNCXSQSVPY0rXQCnayzVKldK3UAZiow6GGH/Ej1PBW2HtkcX8G/o2whER6WFi9OOAYg Q4try8YSXMVIuHuPn56+zejFx6kTTujYxlHmk=
MIME-Version: 1.0
Received: by 10.204.32.206 with SMTP id e14mr81174bkd.45.1265906955575; Thu,  11 Feb 2010 08:49:15 -0800 (PST)
In-Reply-To: <n/yQCGZ4AXdJ0nvuWsINcw.md5@lochnagar.gulbrandsen.priv.no>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina> <4B742A88.1050206@gulbrandsen.priv.no> <1265905400.21277.30.camel@hurina> <GFolqi66YIKYfXwiWfJAwg.md5@lochnagar.gulbrandsen.priv.no> <5b31733c1002110841i13cd9fb8m7cf8fca329cf520b@mail.gmail.com> <n/yQCGZ4AXdJ0nvuWsINcw.md5@lochnagar.gulbrandsen.priv.no>
Date: Thu, 11 Feb 2010 17:49:15 +0100
Message-ID: <5b31733c1002110849r7383f425x1acb043f1319c5b8@mail.gmail.com>
From: Filip Navara <filip.navara@gmail.com>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Content-Type: text/plain; charset=ISO-8859-1
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 16:48:07 -0000

On Thu, Feb 11, 2010 at 5:46 PM, Arnt Gulbrandsen
<arnt@gulbrandsen.priv.no> wrote:
> Filip Navara writes:
>>
>> The specification didn't depend on LISTEXT, now it would. I'm fine with
>> that as long as the server implementers support it.
>
> Good point. IIRC the usual suspects already have listext implementations,
> but I note that gmail does not. Anyone else? Is it acceptable to depend on
> listext?

Kerio has it, Gmail and IceWarp doesn't. I don't know of anyone else
who implemented XLIST.

Best regards,
Filip Navara

From tss@iki.fi  Thu Feb 11 08:49:31 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 072DA3A7736 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:49:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.448
X-Spam-Level: 
X-Spam-Status: No, score=-6.448 tagged_above=-999 required=5 tests=[AWL=0.151,  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 gspKtsaw5gRX for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:49:30 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 2002D3A7551 for <morg@ietf.org>; Thu, 11 Feb 2010 08:49:30 -0800 (PST)
Received: from [192.168.10.2] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id 66DC5FA8D71; Thu, 11 Feb 2010 18:50:44 +0200 (EET)
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
In-Reply-To: <n/yQCGZ4AXdJ0nvuWsINcw.md5@lochnagar.gulbrandsen.priv.no>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina> <4B742A88.1050206@gulbrandsen.priv.no> <1265905400.21277.30.camel@hurina> <GFolqi66YIKYfXwiWfJAwg.md5@lochnagar.gulbrandsen.priv.no> <5b31733c1002110841i13cd9fb8m7cf8fca329cf520b@mail.gmail.com> <n/yQCGZ4AXdJ0nvuWsINcw.md5@lochnagar.gulbrandsen.priv.no>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-1XOMn04oR6XnIwemXFIt"
Date: Thu, 11 Feb 2010 18:50:44 +0200
Message-ID: <1265907044.21277.42.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.2 
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 16:49:31 -0000

--=-1XOMn04oR6XnIwemXFIt
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable

On Thu, 2010-02-11 at 17:46 +0100, Arnt Gulbrandsen wrote:
> Filip Navara writes:
> > The specification didn't depend on LISTEXT, now it would. I'm fine=20
> > with that as long as the server implementers support it.
>=20
> Good point. IIRC the usual suspects already have listext=20
> implementations, but I note that gmail does not. Anyone else? Is it=20
> acceptable to depend on listext?

I was going to first mention this in my email, but then I thought maybe
you after all meant to use only LISTEXT syntax, not actually depend on
LISTEXT.


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

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

iEYEABECAAYFAkt0NWMACgkQyUhSUUBVisk1sACbBc98bbrp4QJdvKnBVnngSzkk
hOwAni9X/fKU+8uVQ1HZ1Z/IsOWnoSLZ
=hrRt
-----END PGP SIGNATURE-----

--=-1XOMn04oR6XnIwemXFIt--


From arnt@gulbrandsen.priv.no  Thu Feb 11 08:52:57 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E978C28C1D2 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:52:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SpZOVEknTLtd for <morg@core3.amsl.com>; Thu, 11 Feb 2010 08:52:57 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 2C54C3A7752 for <morg@ietf.org>; Thu, 11 Feb 2010 08:52:57 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id C01B4FA0723; Thu, 11 Feb 2010 16:54:10 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO lochnagar.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1265907248-22960-22959/5/20 for morg@ietf.org; Thu, 11 Feb 2010 17:54:08 +0100
Message-Id: <F1XQPEm36rc5h/liSJIpsQ.md5@lochnagar.gulbrandsen.priv.no>
Date: Thu, 11 Feb 2010 17:54:22 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: morg@ietf.org
Organization: http://arnt.gulbrandsen.priv.no
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina> <4B742A88.1050206@gulbrandsen.priv.no> <1265905400.21277.30.camel@hurina> <GFolqi66YIKYfXwiWfJAwg.md5@lochnagar.gulbrandsen.priv.no> <5b31733c1002110841i13cd9fb8m7cf8fca329cf520b@mail.gmail.com> <n/yQCGZ4AXdJ0nvuWsINcw.md5@lochnagar.gulbrandsen.priv.no> <1265907044.21277.42.camel@hurina>
In-Reply-To: <1265907044.21277.42.camel@hurina>
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 16:52:58 -0000

Timo Sirainen writes:
> I was going to first mention this in my email, but then I thought maybe
> you after all meant to use only LISTEXT syntax, not actually depend on
> LISTEXT.

Fine idea, if you ask me.

Arnt

From tss@iki.fi  Thu Feb 11 09:02:41 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 860BE3A7758 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 09:02:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.465
X-Spam-Level: 
X-Spam-Status: No, score=-6.465 tagged_above=-999 required=5 tests=[AWL=0.134,  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 Grczf6BaRx6E for <morg@core3.amsl.com>; Thu, 11 Feb 2010 09:02:40 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 94DFC3A7757 for <morg@ietf.org>; Thu, 11 Feb 2010 09:02:40 -0800 (PST)
Received: from [192.168.10.2] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id DDB38FA8977; Thu, 11 Feb 2010 19:03:54 +0200 (EET)
From: Timo Sirainen <tss@iki.fi>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
In-Reply-To: <GFolqi66YIKYfXwiWfJAwg.md5@lochnagar.gulbrandsen.priv.no>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina> <4B742A88.1050206@gulbrandsen.priv.no> <1265905400.21277.30.camel@hurina> <GFolqi66YIKYfXwiWfJAwg.md5@lochnagar.gulbrandsen.priv.no>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-6yoIdEiv7RfCW/lCvJ3c"
Date: Thu, 11 Feb 2010 19:03:54 +0200
Message-ID: <1265907834.21277.44.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.2 
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 17:02:41 -0000

--=-6yoIdEiv7RfCW/lCvJ3c
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable

On Thu, 2010-02-11 at 17:38 +0100, Arnt Gulbrandsen wrote:
> Timo Sirainen writes:
> > Well, I thought of two ways, neither one really seems much better:
>=20
> Why would anyone bother with %? There are only a few special-use=20
> mailboxes, so just get all of them at once:
>=20
>    a list (special-use) "" "*"
>=20
> % is fine for progressive discovery, but why should one progressively=20
> discover four mailboxes?

Then it would require two LIST commands:

a list (special-use) "" *
b list "" %

Is that a real problem (from client implementers' point of view)?

--=-6yoIdEiv7RfCW/lCvJ3c
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

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

iEYEABECAAYFAkt0OHoACgkQyUhSUUBVisnFqgCdHzV4/OVcrTKKqgOuaf3H/b1w
DU8An1ozJ55By64uzilM5ddQn2eyAy7K
=GjXv
-----END PGP SIGNATURE-----

--=-6yoIdEiv7RfCW/lCvJ3c--


From barryleiba@gmail.com  Thu Feb 11 17:30:20 2010
Return-Path: <barryleiba@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 301183A73B2 for <morg@core3.amsl.com>; Thu, 11 Feb 2010 17:30:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.851
X-Spam-Level: 
X-Spam-Status: No, score=-2.851 tagged_above=-999 required=5 tests=[AWL=-0.252, 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 nNzBfxwijDox for <morg@core3.amsl.com>; Thu, 11 Feb 2010 17:30:17 -0800 (PST)
Received: from mail-px0-f188.google.com (mail-px0-f188.google.com [209.85.216.188]) by core3.amsl.com (Postfix) with ESMTP id 7A4003A726B for <morg@ietf.org>; Thu, 11 Feb 2010 17:30:16 -0800 (PST)
Received: by pxi26 with SMTP id 26so1718258pxi.17 for <morg@ietf.org>; Thu, 11 Feb 2010 17:31:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=Yb0O8hzbiphp/jwpchHfmEyg4EQQ6RtG15wugwKOwQQ=; b=L4LSUEkOesbHDt62T3LNOmyLOKAYp3LdnrBxqYDCEq8rwOaMomi3XAwWf9/sEk1sJn +VRbwrTkiLCipURRLlUKRSs/qt259pUgaHJ9hqfCjRRMPvfMsUUHGJHVEHPg9RlI/ZQi rkB9hw0DMwMeYnwgrDKo8igrUNGEc4pNgHDIs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=hq03/0APtSqLL9KmUnnZcLpBixshBzjYlF7mIusmGFd7lpH+SQbngy6ERFVGscsRgZ M8icNoNSy+tBNHw+G+j8Rh2qpifEAZTCDmP8OBC3WXuPxswjCzBcv1R2bVq/hVaTIZxw Yl1MF8HKk23ymXW4n1oQILSpQ7yUI0FaxeRT4=
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.142.250.18 with SMTP id x18mr442110wfh.169.1265938290535; Thu,  11 Feb 2010 17:31:30 -0800 (PST)
In-Reply-To: <1265903404.21277.6.camel@hurina>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina>
Date: Thu, 11 Feb 2010 20:31:30 -0500
X-Google-Sender-Auth: 7aea7fc54224c2d9
Message-ID: <9abf48a61002111731h2a53e943we5967e0c270fc91e@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Timo Sirainen <tss@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1
Cc: morg@ietf.org
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
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, 12 Feb 2010 01:30:20 -0000

> On Thu, 2010-02-11 at 16:28 +0100, Filip Navara wrote:
>> Ok, one more nitpick. How do I know, as a client writer, to which
>> level do I need to enumerate the folders in order to detect the
>> special ones? Most servers have them at the root level, so LIST "" "%"
>> will list them all. Google has them at second level, so I need to do
>> the LIST at least two levels deep (eg. LIST "" "%/%" or LIST ""
>> "[Gmail]/%").

On Thu, Feb 11, 2010 at 10:50, Timo Sirainen <tss@iki.fi> wrote:
> First thought that comes to my mind: Add yet another flag, such as
> \HasSpecialChildren.

I don't think I like that idea.
I'd rather see a LISText option to list all of the special-use mailboxes:

      C: T1 LIST (SPECIAL) "" "*"
      S: * LIST (\Sent) "/" SentMail
      S: * LIST (\Marked \Drafts) "/" MyDrafts
      S: * LIST (\Trash) "/" Trash
      S: * LIST (\Archive) "/" "Saved/Mail/Archive"
      S: T1 OK done

Barry

From arnt@gulbrandsen.priv.no  Fri Feb 12 06:26:00 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C5EEF3A7559 for <morg@core3.amsl.com>; Fri, 12 Feb 2010 06:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aHlo8QquPDku for <morg@core3.amsl.com>; Fri, 12 Feb 2010 06:25:56 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 84B9C3A738C for <morg@ietf.org>; Fri, 12 Feb 2010 06:25:56 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 789EDFA0727; Fri, 12 Feb 2010 14:27:13 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO libertango.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1265984830-22960-22959/5/36 (2 recipients); Fri, 12 Feb 2010 15:27:10 +0100
Message-Id: <4B7566A3.4090609@gulbrandsen.priv.no>
Date: Fri, 12 Feb 2010 15:33:07 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina> <9abf48a61002111731h2a53e943we5967e0c270fc91e@mail.gmail.com>
In-Reply-To: <9abf48a61002111731h2a53e943we5967e0c270fc91e@mail.gmail.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
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, 12 Feb 2010 14:26:00 -0000

On 02/12/2010 02:31 AM, Barry Leiba wrote:
> I don't think I like that idea.
> I'd rather see a LISText option to list all of the special-use mailboxes:

Would you be happy with something that uses listext syntax, without 
requiring a full listext implementation in the server? (As I can claim 
Timo suggested and Timo can claim I suggested. Good to have plausible 
deniability when bringing up such a hack :-)

Arnt

From tss@iki.fi  Fri Feb 12 20:09:14 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 425FE3A7941 for <morg@core3.amsl.com>; Fri, 12 Feb 2010 20:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.478
X-Spam-Level: 
X-Spam-Status: No, score=-6.478 tagged_above=-999 required=5 tests=[AWL=0.121,  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 nGubrBQuIEK9 for <morg@core3.amsl.com>; Fri, 12 Feb 2010 20:09:13 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 6BD793A7940 for <morg@ietf.org>; Fri, 12 Feb 2010 20:09:13 -0800 (PST)
Received: from [192.168.10.2] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id 8F6BBFA898B for <morg@ietf.org>; Sat, 13 Feb 2010 06:10:32 +0200 (EET)
From: Timo Sirainen <tss@iki.fi>
To: morg@ietf.org
In-Reply-To: <9abf48a61002111731h2a53e943we5967e0c270fc91e@mail.gmail.com>
References: <f4edc8df1001261143x6e81b1f3tdfe45728fa38326a@mail.gmail.com> <4B5F6846.4000102@att.com> <4B5F68B0.1000908@isode.com> <4B5F6E0A.7090709@isode.com> <6c9fcc2a1002091748q340c3d64g6278d23967ec3c41@mail.gmail.com> <5b31733c1002110728i6db8eas505b9920f19a4e69@mail.gmail.com> <1265903404.21277.6.camel@hurina> <9abf48a61002111731h2a53e943we5967e0c270fc91e@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-iywIAjZGWqwBfhEFoxek"
Date: Sat, 13 Feb 2010 06:10:32 +0200
Message-ID: <1266034232.21277.82.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.2 
Subject: Re: [MORG] New WG document:draft-ietf-morg-list-specialuse-00
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, 13 Feb 2010 04:09:14 -0000

--=-iywIAjZGWqwBfhEFoxek
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable

On Thu, 2010-02-11 at 20:31 -0500, Barry Leiba wrote:
> I'd rather see a LISText option to list all of the special-use mailboxes:
>=20
>       C: T1 LIST (SPECIAL) "" "*"
>       S: * LIST (\Sent) "/" SentMail
>       S: * LIST (\Marked \Drafts) "/" MyDrafts
>       S: * LIST (\Trash) "/" Trash
>       S: * LIST (\Archive) "/" "Saved/Mail/Archive"
>       S: T1 OK done

I was also hoping that clients that currently support XLIST might
automatically recognize these \flags even without XLIST
capability/command. That could work only if regular LIST command listed
those flags. But I haven't tested if that actually works.


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

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

iEYEABECAAYFAkt2JjcACgkQyUhSUUBVismGLgCcC5atVhwvP3Nnmo1A8OtlozOj
2sUAn22tkDnrVLSVy52ov2oxxCPBrvcP
=I+tn
-----END PGP SIGNATURE-----

--=-iywIAjZGWqwBfhEFoxek--


From barryleiba.mailing.lists@gmail.com  Thu Feb 18 17:41:24 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 B8F9C3A7F26 for <morg@core3.amsl.com>; Thu, 18 Feb 2010 17:41:24 -0800 (PST)
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 QdrEAXcWC36K for <morg@core3.amsl.com>; Thu, 18 Feb 2010 17:41:24 -0800 (PST)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by core3.amsl.com (Postfix) with ESMTP id B20FF3A7910 for <morg@ietf.org>; Thu, 18 Feb 2010 17:41:23 -0800 (PST)
Received: by fg-out-1718.google.com with SMTP id 22so311020fge.13 for <morg@ietf.org>; Thu, 18 Feb 2010 17:43:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:date:message-id :subject:from:to:content-type; bh=WR2DcaWJQvMrLo/74pxYm+RxG3nG6+ycUPQ4r1IIST8=; b=Qv11XwuVQ5+dTOiuL1jPyv/vkzpU8wqCUAnCR95sWxhjOoM26ziWhIlXYO4jcHhRFl 3tsFyR+nva3H4aQVDhTyvwt6oJqwdnZe7ZYf0Ry3RbI0SriCM6CaTB+7p6RtSydzI97K w6/TTcD/7b4Lkec3whPEjenIizCL7zUEgB4bA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; b=V/1tQx22zSqneZKkX+n6FhE0WXSwMNPLG/s2G3WdvRxPFW08U3eGvnu/HNfJ78kyl2 0XWaFms22I0zb2j0HeiJngaU3GRnHzYrr4+NZmmFYA0eOhKbcMD5QGefKMn4AjK8YAfx o3WG+WKBH/EQgIkEtbkkgjsXbQr+6siUuPuHY=
MIME-Version: 1.0
Received: by 10.223.100.207 with SMTP id z15mr10630235fan.78.1266543782182;  Thu, 18 Feb 2010 17:43:02 -0800 (PST)
Date: Thu, 18 Feb 2010 20:43:02 -0500
Message-ID: <6c9fcc2a1002181743n5ac9b898vc525c6b7359420bb@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg <morg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [MORG] Preliminary MORG agenda for IETF 77
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, 19 Feb 2010 01:41:24 -0000

Here's a preliminary MORG session agenda for IETF 77.  Please bash, as
appropriate.

---------------------------------------------
MORG working group preliminary agenda for IETF 77

xx:00 Introduction, note well, agenda review  (5 min)
xx:05 Review document status  (5 min)
      -- Status In List: in RFC Ed queue
      -- Fuzzy Search: in WGLC
      -- Collations: dropped
xx:10 Discussion of document issues  (25 min)
      -- Special Use Mailboxes: new document
      -- Multimailbox Search: new version posted
      -- SortDisplay: needs update from Dan
      -- Address Search: should we continue with it?
      -- In Thread: should we continue with it?
xx:35 Discussion Message Recall updates  (20 min)
xx:55 Any other business  (5 min)
xx:00 -- adjourn --
---------------------------------------------

Barry, MORG secretary

From barryleiba.mailing.lists@gmail.com  Thu Feb 18 17:46: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 14CE728C125 for <morg@core3.amsl.com>; Thu, 18 Feb 2010 17:46:39 -0800 (PST)
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 MDBdUu3IhXaw for <morg@core3.amsl.com>; Thu, 18 Feb 2010 17:46:38 -0800 (PST)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by core3.amsl.com (Postfix) with ESMTP id 1289428C0E2 for <morg@ietf.org>; Thu, 18 Feb 2010 17:46:37 -0800 (PST)
Received: by fg-out-1718.google.com with SMTP id 22so69444fge.13 for <morg@ietf.org>; Thu, 18 Feb 2010 17:48:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=oCS2w0Hrga0TtJzBychXb3MYHDU9erexsXQznxfMp4s=; b=C6+G3G7Py3QSKYlMQR8fpU8t87OLZsZU5Mq62OTmWOJuYs/iZLhHmApnML6mXN2z1V sJkDVJQVmt3fB91V1XUre2ikUEwrGW9xGyOro+yrQjv5wKTTZeRHvA2+bs4fBAisv3Dc V9JgTlz6y/FTxC5d7xAT2V+la9vCekDS7LSJU=
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=LQSHb90zrM0+VB4/NYjO5gja1W+AJifFgJ7UCppVVE1k/SLs6QL2CsDl2OahE/n0x/ nAOhYvtZcBQnic2nRi0wHw6r3FOZL1+i4hMx0W4VvNmVE2/ms1Xw4RyAE7CHCpylsKWq cDDgs8oPMAW/ZMs94rPsBZDZX4LMkYLh2Q4P0=
MIME-Version: 1.0
Received: by 10.223.77.85 with SMTP id f21mr4110988fak.40.1266544099211; Thu,  18 Feb 2010 17:48:19 -0800 (PST)
In-Reply-To: <6c9fcc2a1002051116r64b9e75ay99d5b07a588cfbe0@mail.gmail.com>
References: <20100205170001.C67143A6F51@core3.amsl.com> <6c9fcc2a1002051116r64b9e75ay99d5b07a588cfbe0@mail.gmail.com>
Date: Thu, 18 Feb 2010 20:48:19 -0500
Message-ID: <6c9fcc2a1002181748ifb752efob8eda5549be02313@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-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, 19 Feb 2010 01:46:39 -0000

On Fri, Feb 5, 2010 at 2:16 PM, Barry Leiba
<barryleiba.mailing.lists@gmail.com> wrote:
> I have updated the multimailbox-search draft, filling in some of the
> gaps. =A0There's still a list of to-do items, so, folks: please review
> this draft and help fill them in. =A0We need a general review of what's
> there, and also a particular look at the "open issues" section to
> resolve those issues.
>
> I'll appreciate, as we discuss the open issues, suggestions for text
> to resolve them (for those we think need text in the document).

Second reminder: Let's please discuss this on the mailing list, so we
can try to resolve some of the open issues before the Anaheim meeting.

Barry

From barryleiba.mailing.lists@gmail.com  Thu Feb 18 17:49:07 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 ADA7428C19E for <morg@core3.amsl.com>; Thu, 18 Feb 2010 17:49:07 -0800 (PST)
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 DoEACD0AkXry for <morg@core3.amsl.com>; Thu, 18 Feb 2010 17:49:06 -0800 (PST)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by core3.amsl.com (Postfix) with ESMTP id 83B1628C0E2 for <morg@ietf.org>; Thu, 18 Feb 2010 17:49:05 -0800 (PST)
Received: by fg-out-1718.google.com with SMTP id 22so70171fge.13 for <morg@ietf.org>; Thu, 18 Feb 2010 17:50:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=HbjimaSlfUykbQ8MG31Xmn0iobjId69roExYR/EGYyU=; b=DGP6PIjEGj4ARuCcgAstRSrEP55ds/99Z1ywgqdJThLOG8PQXnA09xOTENvV4YGbK9 uxKEEf5VZ9Adjv0o8xC3/jok7DEYfzKKPB0t27bNaZD77yh5oPFCjvfva7uGuxwbvn48 HsPA5zPMBdIJs7KIwXhKVOWbxyHWMdPqH/cfc=
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=TKoQHUYZ2qPXGt/kMf4iZ4Sg2M6j9fDGNPPOPdw6piEahnsskyKKUUAvPiB/wIb2u1 uqhYGrR/O+R2Muly6TpAU1zr2K/FLxJJpBXHxvZo6AQuR4ny7XjTYnR9TkuWKTbSKTYX XwzBSIM2h59HO5SxtfL2BNMzIU0YEHm7ZjSgo=
MIME-Version: 1.0
Received: by 10.223.68.143 with SMTP id v15mr2896099fai.62.1266544247064; Thu,  18 Feb 2010 17:50:47 -0800 (PST)
In-Reply-To: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com>
References: <6c9fcc2a1001251734t600329e5m338f2baa0e355a13@mail.gmail.com>
Date: Thu, 18 Feb 2010 20:50:47 -0500
Message-ID: <6c9fcc2a1002181750p3b2daa85l59790f290531768c@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] WGLC on draft-ietf-morg-fuzzy-search-02; respond by 10 Feb 2010
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, 19 Feb 2010 01:49:07 -0000

On Mon, Jan 25, 2010 at 8:34 PM, Barry Leiba
<barryleiba.mailing.lists@gmail.com> wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.
>> This draft is a work item of the Message Organization Working Group of t=
he IETF.
>>
>> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : IMAP4 Extension for Fuzzy Sea=
rch
>> =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
>>
>> This document describes an IMAP protocol extension enabling server to
>> perform searches with inexact matching and assigning relevancy scores
>> for matched messages.
> ...
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-morg-fuzzy-search-02.txt
>
> This message starts working-group last call on this document. =A0Please
> review this version of the draft, even if you have reviewed a previous
> version, and post comments by 10 Feb. =A0Post your comments as a reply
> to this message, and please also respond if you think the document is
> ready for publication -- we need confirmation, as well as issues.

The only last-call comment on this was from Mark.  I'm extending the
WGLC until 3 March.  Let's have some comments on this draft, one way
or another.

Otherwise, if we don't have enough participants to have meaningful
output from this working group, perhaps we should stop work and close
it down.

Barry, MORG secretary

From arnt@gulbrandsen.priv.no  Fri Feb 19 00:54:03 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7E3728C123 for <morg@core3.amsl.com>; Fri, 19 Feb 2010 00:54:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q5umxb3dIzZX for <morg@core3.amsl.com>; Fri, 19 Feb 2010 00:54:03 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id BD0F128C113 for <morg@ietf.org>; Fri, 19 Feb 2010 00:54:02 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 13843FA0018; Fri, 19 Feb 2010 08:55:46 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO libertango.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1266569738-63602-63602/5/31 (2 recipients); Fri, 19 Feb 2010 09:55:38 +0100
Message-Id: <4B7E5371.8010308@gulbrandsen.priv.no>
Date: Fri, 19 Feb 2010 10:01:37 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: Me, http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
References: <20100205170001.C67143A6F51@core3.amsl.com> <6c9fcc2a1002051116r64b9e75ay99d5b07a588cfbe0@mail.gmail.com> <6c9fcc2a1002181748ifb752efob8eda5549be02313@mail.gmail.com>
In-Reply-To: <6c9fcc2a1002181748ifb752efob8eda5549be02313@mail.gmail.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2010 08:54:04 -0000

On 02/19/2010 02:48 AM, Barry Leiba wrote:
> Second reminder: Let's please discuss this on the mailing list, so we
> can try to resolve some of the open issues before the Anaheim meeting.

One open issue.

I raised an issue privately. The solution to that is some informative 
text (which I've offered to write). The issue is: An informative section 
or a separate document?

I couldn't care less.

I'll review the document again, too. Haven't in a while.

Arnt

From tss@iki.fi  Fri Feb 19 03:28:33 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 0317528C1B2 for <morg@core3.amsl.com>; Fri, 19 Feb 2010 03:28:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.489
X-Spam-Level: 
X-Spam-Status: No, score=-6.489 tagged_above=-999 required=5 tests=[AWL=0.110,  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 ioh+ONRTxI7C for <morg@core3.amsl.com>; Fri, 19 Feb 2010 03:28:32 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id AECA928C164 for <morg@ietf.org>; Fri, 19 Feb 2010 03:28:31 -0800 (PST)
Received: from [192.168.10.2] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id DD252FA88FA; Fri, 19 Feb 2010 13:30:15 +0200 (EET)
From: Timo Sirainen <tss@iki.fi>
To: barryleiba@computer.org
In-Reply-To: <6c9fcc2a1002181748ifb752efob8eda5549be02313@mail.gmail.com>
References: <20100205170001.C67143A6F51@core3.amsl.com> <6c9fcc2a1002051116r64b9e75ay99d5b07a588cfbe0@mail.gmail.com> <6c9fcc2a1002181748ifb752efob8eda5549be02313@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-Dbd94xIvaCkqtvXI3FyH"
Date: Fri, 19 Feb 2010 13:30:15 +0200
Message-ID: <1266579015.6990.97.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.2 
Cc: morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2010 11:28:33 -0000

--=-Dbd94xIvaCkqtvXI3FyH
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable

> For each mailbox satisfying the source options, a single ESEARCH
>    response MUST be returned if any messages in that mailbox match the
>    search criteria.  An ESEARCH respoonse SHOULD NOT [[Barry: Why not
>    MUST NOT ?]] be returned for mailboxes that contain no matching
>    messages.  This is true even when result options such as MIN, MAX,

SHOULD NOT seems like the worst possibility. Either it should be MUST or
MUST NOT. MUST might be nice so client knows what mailboxes exactly were
searched, but probably isn't very useful in reality.

> Note that it is now possible for a SEARCH command to return NO
>    untagged responses (no SEARCH nor ESEARCH responses), in the case

The uppercased NO there could be slightly confusing first. First I
thought: "Oh, untagged * NO responses".

> If "subtree" is specified, the server MUST defend against loops in
>    the hierarchy (for example, those caused by recursive file-system
>    links within the message store).  The server SHOULD do this by
>    keeping track of the mailboxes that have been searched, and
>    terminating the hierarchy traversal when a repeat is found.  If it
>    can not do that, it MAY do it by limiting the hierarchy depth.

Well, LIST "" * has exactly the same potential problem..

> If the server supports the ACL [RFC4314] extension, then the logged
>    in user is required to have the 'r' right for each mailbox she wants
>    to search.  Mailboxes matching the source options for which the
>    logged in user has no 'r' right MUST be ignored by a multimailbox
>    search.  In particular, ESEARCH responses MUST NOT be returned for
>    those mailboxes.

Also any mailboxes not explicitly named must have 'l' right.

> 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.

> 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)".
>=20
>    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")

> C: tag1 SEARCH IN ((mailboxes "folder1" subtree "folder2")) unseen
>    C: tag2 SEARCH IN ((mailboxes "folder1" subtree-one "folder2"))

Double (( )) doesn't seem correct?

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

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

iEYEABECAAYFAkt+dkcACgkQyUhSUUBVisnzggCfft5WYeeupr7Y0qqDTie7tQKN
Ef4AnitY3UbG2gBCciU8JkyuUNxw2OOT
=fLhE
-----END PGP SIGNATURE-----

--=-Dbd94xIvaCkqtvXI3FyH--


From alexey.melnikov@isode.com  Sat Feb 20 08:19:53 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 0A0A43A816C for <morg@core3.amsl.com>; Sat, 20 Feb 2010 08:19:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.099, 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 n8E5PICN1vSN for <morg@core3.amsl.com>; Sat, 20 Feb 2010 08:19:51 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 682C528C149 for <morg@ietf.org>; Sat, 20 Feb 2010 08:19:51 -0800 (PST)
Received: from [92.40.167.219] (92.40.167.219.sub.mbb.three.co.uk [92.40.167.219])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <S4AMFABCzltf@rufus.isode.com>; Sat, 20 Feb 2010 16:21:41 +0000
Message-ID: <4B800BFB.8010704@isode.com>
Date: Sat, 20 Feb 2010 16:21:15 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: barryleiba@computer.org
References: <20090525003002.071743A6993@core3.amsl.com> <1247768005.4435.238.camel@timo-desktop> <6c9fcc2a0907171118v3c8a306dg755b2c0d79e13bf9@mail.gmail.com>
In-Reply-To: <6c9fcc2a0907171118v3c8a306dg755b2c0d79e13bf9@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Timo Sirainen <tss@iki.fi>, morg@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-fuzzy-search-01.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Feb 2010 16:19:53 -0000

Barry Leiba wrote:

>>>UIDs, sequences, modification sequences: [[anchor6: TODO: There is
>>>   probably not much point in matching these fuzzily.  Could it be a
>>>   MUST NOT for clients to use them inside FUZZY?]]
>>>      
>>>
>>I don't really have any thoughts on this. Seems pointless, but then
>>again maybe it might make something easier to allow them to be matched
>>(exactly?)
>>    
>>
>
>I think the point is that the server decides what "fuzzy" means, and
>that the decision may vary from search key to search key -- including
>doing an exact match because it thinks that "fuzzy" isn't meaningful
>for that particular key.  I would never want a client to be unable to
>say something like this:
>  SEARCH FUZZY (FROM "siranan" UID 123:217)
>...even though the client could put the UID item outside the FUZZY
>scope.  It's up to the server how to handle it; I don't want the
>client to be trying to second-guess what the server will do.
>
>Maybe a change to the text will help.  How about this?:
>
>OLD
>Fuzzy matching is not limited to just string matching.  All search
>keys SHOULD be matched fuzzily, although what exactly that means for
>different search keys is left up to implementations to decide.  Some
>suggestions are given below.
>
>NEW
>Fuzzy matching is not limited to just string matching.  All search
>keys SHOULD be matched fuzzily, although what exactly that means for
>different search keys is left up to server implementations to decide
>-- including deciding that fuzzy matching is meaningless for a
>particular key, and falling back to exact matching).  Some suggestions
>are given below.
>
+1.

>And then maybe:
>NEW
> UIDs, sequences, modification sequences: These are examples of keys
>for which exact matching is probably what makes sense.  Alternatively,
>a server might choose, for instance, to expand a UID range by 5% on
>each side.
>
That would be fine as well.

>---
>What do you think?
>
>Barry
>_______________________________________________
>MORG mailing list
>MORG@ietf.org
>https://www.ietf.org/mailman/listinfo/morg
>Note Well: http://www.ietf.org/maillist.html
>  
>


-- 
IETF Application Area Director, <http://www.ietf.org/IESGmems.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address


From dkarp@zimbra.com  Sat Feb 20 12:34:40 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 5E13628C14C; Sat, 20 Feb 2010 12:34:40 -0800 (PST)
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 Isq6UD+d8N1F; Sat, 20 Feb 2010 12:34:39 -0800 (PST)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id 7983B28C0DF; Sat, 20 Feb 2010 12:34:39 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 32C30C78152; Sat, 20 Feb 2010 12:36:19 -0800 (PST)
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 KJw4WrNnqbWh; Sat, 20 Feb 2010 12:36:08 -0800 (PST)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id 3E734C7809F; Sat, 20 Feb 2010 12:36:08 -0800 (PST)
Date: Sat, 20 Feb 2010 12:36:21 -0800 (PST)
From: Dan Karp <dkarp@zimbra.com>
To: Internet-Drafts@ietf.org
Message-ID: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <20100205170001.C67143A6F51@core3.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.5_GA_2213.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.5_GA_2213.RHEL4_64)
Cc: morg@ietf.org, i-d-announce@ietf.org
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Feb 2010 20:34:40 -0000

>    Because message numbers are not useful for mailboxes that are not
>    selected, each ESEARCH response MUST return information about UIDs,
>    not message numbers, regardless of whether it is in response to a
>    SEARCH or a UID SEARCH command.  In particular, the responses MUST
>    contain the UID indicator.  This is true even if the source options
>    specify that only the selected mailbox be searched.

Would it be clearer to just require an explicit UID SEARCH when using 
the "IN" multimailbox syntax?  Non-UID SEARCH could just return BAD.

From tss@iki.fi  Tue Feb 23 10:33:39 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 52A5E3A84CF for <morg@core3.amsl.com>; Tue, 23 Feb 2010 10:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.498
X-Spam-Level: 
X-Spam-Status: No, score=-6.498 tagged_above=-999 required=5 tests=[AWL=0.101,  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 H+2GzHqP8Ust for <morg@core3.amsl.com>; Tue, 23 Feb 2010 10:33:38 -0800 (PST)
Received: from dovecot.org (dovecot.org [82.118.211.50]) by core3.amsl.com (Postfix) with ESMTP id 58F523A84C4 for <morg@ietf.org>; Tue, 23 Feb 2010 10:33:38 -0800 (PST)
Received: from [192.168.10.199] (e81-197-71-250.elisa-laajakaista.fi [81.197.71.250]) by dovecot.org (Postfix) with ESMTP id 36724FA8D8B for <morg@ietf.org>; Tue, 23 Feb 2010 20:35:39 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
From: Timo Sirainen <tss@iki.fi>
In-Reply-To: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com>
Date: Tue, 23 Feb 2010 20:35:38 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com>
To: morg <morg@ietf.org>
X-Mailer: Apple Mail (2.1077)
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2010 18:33:39 -0000

On 20.2.2010, at 22.36, Dan Karp wrote:

>>   Because message numbers are not useful for mailboxes that are not
>>   selected, each ESEARCH response MUST return information about UIDs,
>>   not message numbers, regardless of whether it is in response to a
>>   SEARCH or a UID SEARCH command.  In particular, the responses MUST
>>   contain the UID indicator.  This is true even if the source options
>>   specify that only the selected mailbox be searched.
> 
> Would it be clearer to just require an explicit UID SEARCH when using 
> the "IN" multimailbox syntax?  Non-UID SEARCH could just return BAD.

+1


From barryleiba.mailing.lists@gmail.com  Tue Feb 23 10:46:08 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 D64C33A7982 for <morg@core3.amsl.com>; Tue, 23 Feb 2010 10:46:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.865
X-Spam-Level: 
X-Spam-Status: No, score=-2.865 tagged_above=-999 required=5 tests=[AWL=-0.266, 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 chGBWYWj51Nh for <morg@core3.amsl.com>; Tue, 23 Feb 2010 10:46:08 -0800 (PST)
Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id BAB763A8103 for <morg@ietf.org>; Tue, 23 Feb 2010 10:45:46 -0800 (PST)
Received: by fxm5 with SMTP id 5so4328102fxm.29 for <morg@ietf.org>; Tue, 23 Feb 2010 10:47:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hdLGEBzV7RD5IBA673TVxfoQHVZAbkgtLzoBI0JRq/0=; b=vd+Czgp2wvz9wLw9oFBHKXehsj73XUlcglsTE+AiwmCqUWtafHiZyFmMpOEzoXKjGE L+ZjUOUMN6ENxTnr4V/I8ABIgVukdhqF6bhEsAFC8IMx5RFwtr/tWuQNjf+VUPJAlvaJ KiPHDTRtcFGGt23nNhffCjGLvdmjd9j2sTDnA=
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=JOf4HOQrtvZwcYexgS6VXOxtJ97JlZrghYno2IhsRWtQyWDBog54vPzT/WSoKn1apH /3luQGMCtuMKCLIDHm45JRLkADk4yypEQqloYCBKCQgJEsaAuVuob8I87TneauCwyjDR G3o6GDA+658gj99Osk7zDAN3VTzdTvTVXBD0c=
MIME-Version: 1.0
Received: by 10.223.5.211 with SMTP id 19mr74070faw.63.1266950864870; Tue, 23  Feb 2010 10:47:44 -0800 (PST)
In-Reply-To: <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi>
Date: Tue, 23 Feb 2010 13:47:44 -0500
Message-ID: <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Timo Sirainen <tss@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: morg <morg@ietf.org>
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-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: Tue, 23 Feb 2010 18:46:08 -0000

>> Would it be clearer to just require an explicit UID SEARCH when using
>> the "IN" multimailbox syntax? =A0Non-UID SEARCH could just return BAD.
>
> +1

I like this too.  Does anyone object to the change?
I'll put it into my source code for the next version.

Barry

From alexey.melnikov@isode.com  Tue Feb 23 10:48:20 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 64B8728C19F for <morg@core3.amsl.com>; Tue, 23 Feb 2010 10:48:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.471
X-Spam-Level: 
X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[AWL=0.128,  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 fA07-8R3fq+j for <morg@core3.amsl.com>; Tue, 23 Feb 2010 10:48:19 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 8F81F28C130 for <morg@ietf.org>; Tue, 23 Feb 2010 10:48:19 -0800 (PST)
Received: from [172.16.2.169] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <S4QjaQBl=sfW@rufus.isode.com>; Tue, 23 Feb 2010 18:50:19 +0000
Message-ID: <4B842354.7020801@isode.com>
Date: Tue, 23 Feb 2010 18:49:56 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: barryleiba@computer.org
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com>
In-Reply-To: <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Timo Sirainen <tss@iki.fi>, morg <morg@ietf.org>
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2010 18:48:20 -0000

Barry Leiba wrote:

>>>Would it be clearer to just require an explicit UID SEARCH when using
>>>the "IN" multimailbox syntax?  Non-UID SEARCH could just return BAD.
>>>      
>>>
>>+1
>>    
>>
>I like this too.  Does anyone object to the change?
>I'll put it into my source code for the next version.
>  
>
Works for me.


From mrc+ietf@panda.com  Tue Feb 23 10:55:18 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 D184F28C220 for <morg@core3.amsl.com>; Tue, 23 Feb 2010 10:55:18 -0800 (PST)
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 jJM0WBwNEZYW for <morg@core3.amsl.com>; Tue, 23 Feb 2010 10:55:17 -0800 (PST)
Received: from Panda.COM (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id ADE5C28C1CF for <morg@ietf.org>; Tue, 23 Feb 2010 10:55:17 -0800 (PST)
Received: from hsinghsing.panda.com mrcrispin@Panda.COM [206.124.149.116] by Panda.COM with M+ Extreme Email Engine 2008.3.internal via secured & encrypted transport (TLS); Tue, 23 Feb 2010 10:57:17 -0800
X-MailFrom: mrc+ietf@panda.com
Date: Tue, 23 Feb 2010 10:57:17 -0800 (PST)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <4B842354.7020801@isode.com>
Message-ID: <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.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: Timo Sirainen <tss@iki.fi>, barryleiba@computer.org, morg <morg@ietf.org>
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2010 18:55:18 -0000

I have not paid much attention to this discussion, but this caught my eye.

It would be cleaner to have a new command for multimailbox searching that 
always returns UIDs.

That way, all three searches would have the same set of search criteria.

Also, isn't it reasonable to do this command without a mailbox selected? 
In that case, you can't use SEARCH or UID SEARCH since both require a 
mailbox to be selected as a fundamental part of the command.

Arguments to a command should not change its fundamental semantics.

>>>> Would it be clearer to just require an explicit UID SEARCH when using
>>>> the "IN" multimailbox syntax?  Non-UID SEARCH could just return BAD.

-- 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 arnt@gulbrandsen.priv.no  Tue Feb 23 11:57:41 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D51028C130 for <morg@core3.amsl.com>; Tue, 23 Feb 2010 11:57:41 -0800 (PST)
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.235,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LqZr7EFVMQz4 for <morg@core3.amsl.com>; Tue, 23 Feb 2010 11:57:40 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 5F4EC28C0FA for <morg@ietf.org>; Tue, 23 Feb 2010 11:57:40 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 0BBADFA001A; Tue, 23 Feb 2010 19:59:46 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO libertango.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1266955173-13340-13340/5/2 (2 recipients); Tue, 23 Feb 2010 20:59:33 +0100
Message-Id: <4B84350B.4000307@gulbrandsen.priv.no>
Date: Tue, 23 Feb 2010 21:05:31 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: Me, http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com>
In-Reply-To: <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2010 19:57:41 -0000

On 02/23/2010 07:57 PM, Mark Crispin wrote:
> That way, all three searches would have the same set of search criteria.

Not quite; MSN sets are also valid as search keys.

Arnt

From barryleiba.mailing.lists@gmail.com  Tue Feb 23 12:31:30 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 3E8EE28C1E3 for <morg@core3.amsl.com>; Tue, 23 Feb 2010 12:31:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.86
X-Spam-Level: 
X-Spam-Status: No, score=-2.86 tagged_above=-999 required=5 tests=[AWL=-0.261,  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 O8-0kkklQhpJ for <morg@core3.amsl.com>; Tue, 23 Feb 2010 12:31:29 -0800 (PST)
Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id 11B2E28C0FF for <morg@ietf.org>; Tue, 23 Feb 2010 12:31:28 -0800 (PST)
Received: by fxm5 with SMTP id 5so4443195fxm.29 for <morg@ietf.org>; Tue, 23 Feb 2010 12:33:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=7eJ1QEaARY5UnPFeRhFGI4O+4v/j4bkudHSDD+Rmglg=; b=iqE2c0ak9lCISbnubRN9PP2Kue1jsKyP+F9du7Dqh63WSej28+s3azctH/y0pV0cwA 2VkZt4XIOj7wB03aUVvaF6O1LVEo0qa3Og1bNVlelysW7AaHM2dyLcZfIAwRd8O7+rgf slWkt8BAEWm4nW68H6mAZjY6zzQWTju3edunA=
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=Vk64hWIC+UB/kyrEPDRW6rdegaMpHykIuKa+DoUmhF1Zo4Ap/AOZOT88oS7Y/ed+c2 5/KLsXO8dBcYWuyKgKjrFPtKod3f+sHaRVzHqDFQ37PmFTvEXs20hC+/a9FwnLCgaRkz wtcptRHJJCfgrQTsG2IXYmhMGuHmaNlUU07jM=
MIME-Version: 1.0
Received: by 10.223.5.211 with SMTP id 19mr226138faw.63.1266957209074; Tue, 23  Feb 2010 12:33:29 -0800 (PST)
In-Reply-To: <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com>
Date: Tue, 23 Feb 2010 15:33:28 -0500
Message-ID: <6c9fcc2a1002231233m3cece875m70495de3c244e955@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: morg <morg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-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: Tue, 23 Feb 2010 20:31:30 -0000

> It would be cleaner to have a new command for multimailbox searching that
> always returns UIDs.

I have no objection to that: we could make an "ESEARCH" command, to
match the "ESEARCH" response, and that would be OK with me.

I think it's OK to extend UID SEARCH this way, but I agree with Mark
that it's preferable to change the command.  Some servers -- including
mine -- parse the command and check the command against the state
before parsing any options.  If this works with UID SEARCH, it
requires that all UID commands be allowed in authenticated state, and
that another state check be done later.  That's clearly not a terrible
change, but it does alter the server's basic parsing and state-check
logic, and can easily be avoided.

So what do others think of using "ESEARCH" or "MSEARCH" for this?

Barry

From mrc+ietf@panda.com  Tue Feb 23 12:46:56 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 2E8A028C0DE for <morg@core3.amsl.com>; Tue, 23 Feb 2010 12:46:56 -0800 (PST)
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 St4EWrd1WElK for <morg@core3.amsl.com>; Tue, 23 Feb 2010 12:46:55 -0800 (PST)
Received: from Panda.COM (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id 127773A8469 for <morg@ietf.org>; Tue, 23 Feb 2010 12:46:55 -0800 (PST)
Received: from hsinghsing.panda.com mrcrispin@Panda.COM [206.124.149.116] by Panda.COM with M+ Extreme Email Engine 2008.3.internal via secured & encrypted transport (TLS); Tue, 23 Feb 2010 12:48:53 -0800
X-MailFrom: mrc+ietf@panda.com
Date: Tue, 23 Feb 2010 12:48:52 -0800 (PST)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
In-Reply-To: <4B84350B.4000307@gulbrandsen.priv.no>
Message-ID: <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no>
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
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2010 20:46:56 -0000

On Tue, 23 Feb 2010, Arnt Gulbrandsen wrote:
> On 02/23/2010 07:57 PM, Mark Crispin wrote:
>> That way, all three searches would have the same set of search criteria.
> Not quite; MSN sets are also valid as search keys.

And are you saying that there's a problem with an MSN set being provided 
as a search key for this functionality?  I'll grant that it often seems 
silly, but it is not necessary bogus!

Unlike FETCH/STORE/COPY, MSN range validation does not apply to SEARCH set 
arguments.  So it is perfectly reasonable to do things like 1:100 for "the 
first hundred messages in the mailbox", 101:200 for "the second hundred 
messages in the mailbox", etc.

-- 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 Feb 23 12:47:38 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 ABF973A8454 for <morg@core3.amsl.com>; Tue, 23 Feb 2010 12:47:38 -0800 (PST)
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 dCrDhAMsnCKl for <morg@core3.amsl.com>; Tue, 23 Feb 2010 12:47:38 -0800 (PST)
Received: from Panda.COM (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id CD16E3A6811 for <morg@ietf.org>; Tue, 23 Feb 2010 12:47:37 -0800 (PST)
Received: from hsinghsing.panda.com mrcrispin@Panda.COM [206.124.149.116] by Panda.COM with M+ Extreme Email Engine 2008.3.internal via secured & encrypted transport (TLS); Tue, 23 Feb 2010 12:49:38 -0800
X-MailFrom: mrc+ietf@panda.com
Date: Tue, 23 Feb 2010 12:49:37 -0800 (PST)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: barryleiba@computer.org
In-Reply-To: <6c9fcc2a1002231233m3cece875m70495de3c244e955@mail.gmail.com>
Message-ID: <alpine.OSX.2.00.1002231248590.404@hsinghsing.panda.com>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <6c9fcc2a1002231233m3cece875m70495de3c244e955@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 <morg@ietf.org>
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2010 20:47:38 -0000

On Tue, 23 Feb 2010, Barry Leiba wrote:
> Some servers -- including
> mine -- parse the command and check the command against the state
> before parsing any options.  If this works with UID SEARCH, it
> requires that all UID commands be allowed in authenticated state, and
> that another state check be done later.  That's clearly not a terrible
> change, but it does alter the server's basic parsing and state-check
> logic, and can easily be avoided.

I was thinking about this 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 dkarp@zimbra.com  Tue Feb 23 13:06:14 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 5E3AF3A8348 for <morg@core3.amsl.com>; Tue, 23 Feb 2010 13:06:14 -0800 (PST)
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 iBAsFKmxN7Ts for <morg@core3.amsl.com>; Tue, 23 Feb 2010 13:06:13 -0800 (PST)
Received: from mta02.zimbra.com (mta02.zimbra.com [205.140.197.62]) by core3.amsl.com (Postfix) with ESMTP id B81323A739B for <morg@ietf.org>; Tue, 23 Feb 2010 13:06:13 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mta02.zimbra.com (Postfix) with ESMTP id 1A953C7857A; Tue, 23 Feb 2010 13:08:03 -0800 (PST)
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 lVTm8kZNk6XM; Tue, 23 Feb 2010 13:07:46 -0800 (PST)
Received: from dogfood.zimbra.com (dogfood.zimbra.com [10.113.63.59]) by mta02.zimbra.com (Postfix) with ESMTP id E7704C78587; Tue, 23 Feb 2010 13:07:46 -0800 (PST)
Date: Tue, 23 Feb 2010 13:08:03 -0800 (PST)
From: Dan Karp <dkarp@zimbra.com>
To: Mark Crispin <mrc+ietf@panda.com>
Message-ID: <1852174168.18909.1266959283127.JavaMail.root@dogfood.zimbra.com>
In-Reply-To: <832157559.18901.1266959235052.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.5_GA_2213.RHEL4_64 (ZimbraWebClient - SAF3 (Mac)/6.0.5_GA_2213.RHEL4_64)
Cc: Timo Sirainen <tss@iki.fi>, barryleiba@computer.org, morg <morg@ietf.org>
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2010 21:06:14 -0000

> I have not paid much attention to this discussion, but this caught my
> eye.
> 
> It would be cleaner to have a new command for multimailbox searching
> that always returns UIDs.
> 
> That way, all three searches would have the same set of search
> criteria.

Not to take one side or the other regarding a new command for multi-
mailbox search, but the "IN" clause that triggers multimailbox search
is not a search criterion.

   search =  "SEARCH" [SP search-source-opts] [SP search-return-opts]
           SP search-program

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

From mrc+ietf@Panda.COM  Tue Feb 23 13:36:33 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 577033A830F for <morg@core3.amsl.com>; Tue, 23 Feb 2010 13:36:33 -0800 (PST)
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 lQRR6n1SS-Pb for <morg@core3.amsl.com>; Tue, 23 Feb 2010 13:36:32 -0800 (PST)
Received: from Panda.COM (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id 3F8513A7228 for <morg@ietf.org>; Tue, 23 Feb 2010 13:36:30 -0800 (PST)
Received: from hsinghsing.panda.com mrcrispin@Panda.COM [206.124.149.116] by Panda.COM with M+ Extreme Email Engine 2008.3.internal via secured & encrypted transport (TLS); Tue, 23 Feb 2010 13:38:27 -0800
X-MailFrom: mrc+ietf@Panda.COM
Date: Tue, 23 Feb 2010 13:38:26 -0800 (PST)
From: Mark Crispin <mrc+ietf@Panda.COM>
Sender: mrc@hsinghsing.panda.com
To: Dan Karp <dkarp@zimbra.com>
In-Reply-To: <1852174168.18909.1266959283127.JavaMail.root@dogfood.zimbra.com>
Message-ID: <alpine.OSX.2.00.1002231331060.404@hsinghsing.panda.com>
References: <1852174168.18909.1266959283127.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: Timo Sirainen <tss@iki.fi>, barryleiba@computer.org, morg <morg@ietf.org>
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2010 21:36:33 -0000

The less of that syntactical creeping featurism, the better.  CHARSET was 
a mistake; the return-ops a worse one.

On Tue, 23 Feb 2010, Dan Karp wrote:
> Not to take one side or the other regarding a new command for multi-
> mailbox search, but the "IN" clause that triggers multimailbox search
> is not a search criterion.
>
>   search =  "SEARCH" [SP search-source-opts] [SP search-return-opts]
>           SP search-program
>
>   search-source-opts =  "IN" SP "(" source-mbox [SP
>           "(" scope-options ")"] ")"
>

-- 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 arnt@gulbrandsen.priv.no  Wed Feb 24 01:17:03 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 831CE3A6C40 for <morg@core3.amsl.com>; Wed, 24 Feb 2010 01:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.728
X-Spam-Level: 
X-Spam-Status: No, score=-1.728 tagged_above=-999 required=5 tests=[AWL=-0.422, BAYES_00=-2.599, MISSING_HEADERS=1.292, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jajh4au6VQhC for <morg@core3.amsl.com>; Wed, 24 Feb 2010 01:17:02 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 79CDC3A7B1E for <morg@ietf.org>; Wed, 24 Feb 2010 01:17:02 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id A318DFA001B; Wed, 24 Feb 2010 09:19:11 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO lochnagar.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1267003137-13340-13340/5/3 for morg@ietf.org; Wed, 24 Feb 2010 10:18:57 +0100
Message-Id: <HPiL2ZVG2v2FhFR5zN4tXw.md5@lochnagar.gulbrandsen.priv.no>
Date: Wed, 24 Feb 2010 10:19:27 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Cc: morg@ietf.org
Organization: http://arnt.gulbrandsen.priv.no
References: <1852174168.18909.1266959283127.JavaMail.root@dogfood.zimbra.com> <alpine.OSX.2.00.1002231331060.404@hsinghsing.panda.com>
In-Reply-To: <alpine.OSX.2.00.1002231331060.404@hsinghsing.panda.com>
Content-Type: text/plain; format=flowed
Mime-Version: 1.0
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 09:17:03 -0000

Mark Crispin writes:
> The less of that syntactical creeping featurism, the better.

I agree. I think I've said it before, but I'll say it again: By default 
the mailbox stuff should be a search-key. If there's a specific reason 
to do it differently, by all means, but if not, search-key is what 
(almost) everything else is, and there's value in uniformity.

Arnt

From arnt@gulbrandsen.priv.no  Wed Feb 24 01:29:21 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB91F3A7C42 for <morg@core3.amsl.com>; Wed, 24 Feb 2010 01:29:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.355
X-Spam-Level: 
X-Spam-Status: No, score=-2.355 tagged_above=-999 required=5 tests=[AWL=0.243,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0sg+ZJAHPjD for <morg@core3.amsl.com>; Wed, 24 Feb 2010 01:29:21 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id B3C843A8285 for <morg@ietf.org>; Wed, 24 Feb 2010 01:29:20 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id B6A0DFA001B; Wed, 24 Feb 2010 09:31:29 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO lochnagar.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1267003875-13340-13340/5/4 (2 recipients); Wed, 24 Feb 2010 10:31:15 +0100
Message-Id: <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no>
Date: Wed, 24 Feb 2010 10:31:45 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: morg@ietf.org
Organization: http://arnt.gulbrandsen.priv.no
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no> <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com>
In-Reply-To: <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com>
Content-Type: text/plain; format=flowed
Mime-Version: 1.0
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 09:29:21 -0000

Mark Crispin writes:
> And are you saying that there's a problem with an MSN set being 
> provided as a search key for this functionality?  I'll grant that it 
> often seems silly, but it is not necessary bogus!
>
> Unlike FETCH/STORE/COPY, MSN range validation does not apply to SEARCH 
> set arguments.  So it is perfectly reasonable to do things like 1:100 
> for "the first hundred messages in the mailbox", 101:200 for "the 
> second hundred messages in the mailbox", etc.

I'm saying it's just neat to have.

I know at least two clients that use it to get incremental search 
results. I know that because they cause enough load to be noticed.

I can often/usually execute a search quickly, by doing b-tree lookups 
and whatnot. 'search from <a@b>' is a O(log(n)). But if the client 
sends those MSNs ('search 1:100 from <a@b>', then 'search 101:200 from 
<a@b>', then ...), the the b-tree lookup is repeated O(n) times and the 
total cost of the search is O(n*log(n)).

There's some value in incremental search results. Depends on the client. 
But in the case of multimailbox search, I see little or no real value 
in being able to search incrementally _in_that_way_. Base IMAP already 
supports multimailbox incremental search by sending a sequence of 
select and plain search commands.

Arnt

From alexey.melnikov@isode.com  Wed Feb 24 03:34:33 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 ADCC628C105 for <morg@core3.amsl.com>; Wed, 24 Feb 2010 03:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.473
X-Spam-Level: 
X-Spam-Status: No, score=-2.473 tagged_above=-999 required=5 tests=[AWL=0.126,  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 797r0ljAnNMK for <morg@core3.amsl.com>; Wed, 24 Feb 2010 03:34:33 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id C766F28C10A for <morg@ietf.org>; Wed, 24 Feb 2010 03:34:32 -0800 (PST)
Received: from [172.16.2.142] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <S4UPRABl=hRC@rufus.isode.com>; Wed, 24 Feb 2010 11:36:38 +0000
Message-ID: <4B850F34.4070002@isode.com>
Date: Wed, 24 Feb 2010 11:36:20 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: barryleiba@computer.org
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <6c9fcc2a1002231233m3cece875m70495de3c244e955@mail.gmail.com>
In-Reply-To: <6c9fcc2a1002231233m3cece875m70495de3c244e955@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: morg <morg@ietf.org>
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 11:34:33 -0000

Barry Leiba wrote:

>>It would be cleaner to have a new command for multimailbox searching that
>>always returns UIDs.
>>    
>>
>
>I have no objection to that: we could make an "ESEARCH" command, to
>match the "ESEARCH" response, and that would be OK with me.
>
>I think it's OK to extend UID SEARCH this way, but I agree with Mark
>that it's preferable to change the command.  Some servers -- including
>mine -- parse the command and check the command against the state
>before parsing any options.  If this works with UID SEARCH, it
>requires that all UID commands be allowed in authenticated state, and
>that another state check be done later.  That's clearly not a terrible
>change, but it does alter the server's basic parsing and state-check
>logic, and can easily be avoided.
>
>So what do others think of using "ESEARCH" or "MSEARCH" for this?
>  
>
Changing the command name (I slightly prefer ESEARCH) is fine with me.

I would like to keep the untagged ESEARCH response name/structure.


From mrc+ietf@panda.com  Wed Feb 24 06:08:23 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 788EC28C12B for <morg@core3.amsl.com>; Wed, 24 Feb 2010 06:08:23 -0800 (PST)
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 kaD10ePlKKNP for <morg@core3.amsl.com>; Wed, 24 Feb 2010 06:08:22 -0800 (PST)
Received: from panda.com (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id 4CA5628C124 for <morg@ietf.org>; Wed, 24 Feb 2010 06:08:22 -0800 (PST)
Received: from hsinghsing.panda.com [206.124.149.116] by Panda.COM with ESMTP via TCP; Wed, 24 Feb 2010 06:10:24 -0800
X-MailFrom: mrc+ietf@panda.com
Date: Wed, 24 Feb 2010 06:10:23 -0800 (PST)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
In-Reply-To: <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no>
Message-ID: <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no> <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com> <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no>
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-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, 24 Feb 2010 14:08:23 -0000

On Wed, 24 Feb 2010, Arnt Gulbrandsen wrote:
> I can often/usually execute a search quickly, by doing b-tree lookups
> and whatnot. 'search from <a@b>' is a O(log(n)). But if the client
> sends those MSNs ('search 1:100 from <a@b>', then 'search 101:200 from
> <a@b>', then ...), the the b-tree lookup is repeated O(n) times and the
> total cost of the search is O(n*log(n)).

That sounds like a predictable consequence of your implementation choice;
and suggests that you should consider some alternative choices to remove
that cost.

One obvious possibility is to cache the b-tree lookup results for reuse.

> There's some value in incremental search results. Depends on the client.
> But in the case of multimailbox search, I see little or no real value
> in being able to search incrementally _in_that_way_. Base IMAP already
> supports multimailbox incremental search by sending a sequence of
> select and plain search commands.

Client authors would disagree.

I thought that the entire point of the exercise was to do the function
without the additional RTTs.  RTTs are deadly, and it is desirable to
reduce them.

Now it sounds like the sole purpose is to accomodate a single server.

-- 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 arnt@gulbrandsen.priv.no  Wed Feb 24 06:15:18 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9ADBE28C169 for <morg@core3.amsl.com>; Wed, 24 Feb 2010 06:15:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.365
X-Spam-Level: 
X-Spam-Status: No, score=-2.365 tagged_above=-999 required=5 tests=[AWL=0.233,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99gync-eY7bX for <morg@core3.amsl.com>; Wed, 24 Feb 2010 06:15:17 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 44C5228C16E for <morg@ietf.org>; Wed, 24 Feb 2010 06:15:14 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 2CEEDFA001B; Wed, 24 Feb 2010 14:17:25 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO libertango.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1267021030-26496-26495/5/4 (2 recipients); Wed, 24 Feb 2010 15:17:10 +0100
Message-Id: <4B8534ED.3000208@gulbrandsen.priv.no>
Date: Wed, 24 Feb 2010 15:17:17 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: Me, http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no> <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com> <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no> <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com>
In-Reply-To: <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 14:15:18 -0000

On 02/24/2010 03:10 PM, Mark Crispin wrote:
>> There's some value in incremental search results. Depends on the client.
>> But in the case of multimailbox search, I see little or no real value
>> in being able to search incrementally _in_that_way_. Base IMAP already
>> supports multimailbox incremental search by sending a sequence of
>> select and plain search commands.
>
> Client authors would disagree.

Disagree with what?

That there's value in incremental search results?

That I see little or no value in THAT WAY to do incremental multimailbox 
search?

That base IMAP allows sending a sequence of select and search commands?

Arnt

From mrc+ietf@panda.com  Wed Feb 24 06:23:32 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 3DC4A28C187 for <morg@core3.amsl.com>; Wed, 24 Feb 2010 06:23:32 -0800 (PST)
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 ls-UnEmdVo2K for <morg@core3.amsl.com>; Wed, 24 Feb 2010 06:23:31 -0800 (PST)
Received: from panda.com (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id 2E56828C184 for <morg@ietf.org>; Wed, 24 Feb 2010 06:23:28 -0800 (PST)
Received: from hsinghsing.panda.com [206.124.149.116] by Panda.COM with ESMTP via TCP; Wed, 24 Feb 2010 06:25:30 -0800
X-MailFrom: mrc+ietf@panda.com
Date: Wed, 24 Feb 2010 06:25:29 -0800 (PST)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
In-Reply-To: <4B8534ED.3000208@gulbrandsen.priv.no>
Message-ID: <alpine.OSX.2.00.1002240619100.404@hsinghsing.panda.com>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no> <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com> <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no> <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com> <4B8534ED.3000208@gulbrandsen.priv.no>
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-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, 24 Feb 2010 14:23:32 -0000

On Wed, 24 Feb 2010, Arnt Gulbrandsen wrote:
>> Client authors would disagree.
> Disagree with what?
> That there's value in incremental search results?

Considering that I just gave an example of a strategy to do incremental
search, it would make no sense for me to disagree with its value.

> That I see little or no value in THAT WAY to do incremental multimailbox
> search?

It should be obvious, from context, that client authors may want to do
incremental multimailbox search in that way.

> That base IMAP allows sending a sequence of select and search commands?

I see no point for a multimailbox search other than to remove RTTs.

-- 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 arnt@gulbrandsen.priv.no  Wed Feb 24 06:32:59 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5627D28C0E0 for <morg@core3.amsl.com>; Wed, 24 Feb 2010 06:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.375
X-Spam-Level: 
X-Spam-Status: No, score=-2.375 tagged_above=-999 required=5 tests=[AWL=0.223,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ZkdD5FlUDWC for <morg@core3.amsl.com>; Wed, 24 Feb 2010 06:32:58 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id BD3163A82F0 for <morg@ietf.org>; Wed, 24 Feb 2010 06:32:57 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 3A9ADFA001A; Wed, 24 Feb 2010 14:35:07 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO libertango.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1267022091-26496-26495/5/5 (2 recipients); Wed, 24 Feb 2010 15:34:51 +0100
Message-Id: <4B853913.404@gulbrandsen.priv.no>
Date: Wed, 24 Feb 2010 15:34:59 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: Me, http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no> <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com> <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no> <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com> <4B8534ED.3000208@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240619100.404@hsinghsing.panda.com>
In-Reply-To: <alpine.OSX.2.00.1002240619100.404@hsinghsing.panda.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 14:32:59 -0000

On 02/24/2010 03:25 PM, Mark Crispin wrote:
> On Wed, 24 Feb 2010, Arnt Gulbrandsen wrote:
>>> Client authors would disagree.
>> Disagree with what?
>> That there's value in incremental search results?
>
> Considering that I just gave an example of a strategy to do incremental
> search, it would make no sense for me to disagree with its value.
>
>> That I see little or no value in THAT WAY to do incremental multimailbox
>> search?
>
> It should be obvious, from context, that client authors may want to do
> incremental multimailbox search in that way.

Really?

I reviewed the draft when I did multimailbox search for a client a whole 
ago, and ended up with something like this to get incremental search 
results:

  find list of mailboxes to be searched
  if server supports multimailbox search
    send status (messages) for each mailbox
    process the status responses as they come back
    find the highest message count in any relevant mailbox
    loop from 1 to that count by steps of e.g. 256
      send 'search in (...) x+1:x+256 (other criteria)'
    process the search responses that come back
  else
    for each mailbox
      send examine
      send search
    process the search responses that come back
  retrieve some/all of the matching messages

My conclusion was that the whole thing was too much hassle, so it would 
be better to just send a single SEARCH IN. If I overlooked some better 
way, I'd be thrilled to hear what it is.

Arnt

From arnt@gulbrandsen.priv.no  Wed Feb 24 06:50:17 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB5F328C1B8 for <morg@core3.amsl.com>; Wed, 24 Feb 2010 06:50:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.384
X-Spam-Level: 
X-Spam-Status: No, score=-2.384 tagged_above=-999 required=5 tests=[AWL=0.214,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rADmL1jROy0x for <morg@core3.amsl.com>; Wed, 24 Feb 2010 06:50:16 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 506F128C1AF for <morg@ietf.org>; Wed, 24 Feb 2010 06:50:16 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 5110DFA001A; Wed, 24 Feb 2010 14:52:25 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO libertango.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1267023130-27943-27942/5/1 (2 recipients); Wed, 24 Feb 2010 15:52:10 +0100
Message-Id: <4B853D22.2030407@gulbrandsen.priv.no>
Date: Wed, 24 Feb 2010 15:52:18 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: Me, http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no> <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com> <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no> <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com> <4B8534ED.3000208@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240619100.404@hsinghsing.panda.com> <4B853913.404@gulbrandsen.priv.no>
In-Reply-To: <4B853913.404@gulbrandsen.priv.no>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 14:50:17 -0000

Actually, let me rephrase. That was too much of a digression.

On 02/24/2010 03:34 PM, Arnt Gulbrandsen wrote:
> My conclusion was that the whole thing was too much hassle, so it would
> be better to just send a single SEARCH IN. If I overlooked some better
> way, I'd be thrilled to hear what it is.

If I overlooked a better way, then I think the document might do well to 
describe it.

If there is some other use-case for using MSNs in multimailbox search 
commands, then I'd like to hear about that, too.

Arnt

From mrc+ietf@panda.com  Wed Feb 24 07:00:30 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 14F9C28C1B6 for <morg@core3.amsl.com>; Wed, 24 Feb 2010 07:00:30 -0800 (PST)
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 CB9wwG0iw3ec for <morg@core3.amsl.com>; Wed, 24 Feb 2010 07:00:29 -0800 (PST)
Received: from panda.com (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id D85B828C1CC for <morg@ietf.org>; Wed, 24 Feb 2010 07:00:28 -0800 (PST)
Received: from hsinghsing.panda.com [206.124.149.116] by Panda.COM with ESMTP via TCP; Wed, 24 Feb 2010 07:02:31 -0800
X-MailFrom: mrc+ietf@panda.com
Date: Wed, 24 Feb 2010 07:02:30 -0800 (PST)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
In-Reply-To: <4B853D22.2030407@gulbrandsen.priv.no>
Message-ID: <alpine.OSX.2.00.1002240654030.404@hsinghsing.panda.com>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no> <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com> <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no> <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com> <4B8534ED.3000208@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240619100.404@hsinghsing.panda.com> <4B853913.404@gulbrandsen.priv.no> <4B853D22.2030407@gulbrandsen.priv.no>
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-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, 24 Feb 2010 15:00:30 -0000

On Wed, 24 Feb 2010, Arnt Gulbrandsen wrote:
> If I overlooked a better way, then I think the document might do well to
> describe it.

In your quest for the complex you overlooked the simple.

What you overlooked is that many incremental search tasks have no
intention of sweeping the entire space.  All they seek to do is collect
some results.

Hence the loop is to fetch 1:100, 101:200, etc. until "enough" results
have been obtained, and/or a time interval has expired, and/or the user
says stop, etc.  No need to do STATUS commands & etc.

The fact that you can't conceive of a use for something doesn't mean that
nobody else can.

-- 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 arnt@gulbrandsen.priv.no  Wed Feb 24 07:08:03 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 58CE828C1A4 for <morg@core3.amsl.com>; Wed, 24 Feb 2010 07:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.392
X-Spam-Level: 
X-Spam-Status: No, score=-2.392 tagged_above=-999 required=5 tests=[AWL=0.206,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tuaBWHLfzs1n for <morg@core3.amsl.com>; Wed, 24 Feb 2010 07:08:02 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 70D793A6CA1 for <morg@ietf.org>; Wed, 24 Feb 2010 07:08:02 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 56ECDFA001A; Wed, 24 Feb 2010 15:10:13 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO libertango.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1267024198-27943-27942/5/2 (2 recipients); Wed, 24 Feb 2010 16:09:58 +0100
Message-Id: <4B85414E.8060905@gulbrandsen.priv.no>
Date: Wed, 24 Feb 2010 16:10:06 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: Me, http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no> <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com> <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no> <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com> <4B8534ED.3000208@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240619100.404@hsinghsing.panda.com> <4B853913.404@gulbrandsen.priv.no> <4B853D22.2030407@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240654030.404@hsinghsing.panda.com>
In-Reply-To: <alpine.OSX.2.00.1002240654030.404@hsinghsing.panda.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 15:08:03 -0000

On 02/24/2010 04:02 PM, Mark Crispin wrote:
> In your quest for the complex you overlooked the simple.
>
> What you overlooked is that many incremental search tasks have no
> intention of sweeping the entire space. All they seek to do is collect
> some results.
>
> Hence the loop is to fetch 1:100, 101:200, etc. until "enough" results
> have been obtained, and/or a time interval has expired, and/or the user
> says stop, etc. No need to do STATUS commands & etc.

Either you know that there are results so the search will terminate, or 
you run the STATUSes to know when to stop looking, or you loop all the 
way to UINT_MAX. Right?

> The fact that you can't conceive of a use for something doesn't mean that
> nobody else can.

Right. The question is whether this is plausible/simple/useful enough to 
warrant support. IMAP extensions have a habit of making arcane 
taskspossible; I'd rather make the important tasks simple.

Arnt

From mrc+ietf@panda.com  Wed Feb 24 09:04:53 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 164D93A853C for <morg@core3.amsl.com>; Wed, 24 Feb 2010 09:04:53 -0800 (PST)
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 CAgUvOa8BzD7 for <morg@core3.amsl.com>; Wed, 24 Feb 2010 09:04:52 -0800 (PST)
Received: from panda.com (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id C67853A8516 for <morg@ietf.org>; Wed, 24 Feb 2010 09:04:51 -0800 (PST)
Received: from hsinghsing.panda.com [206.124.149.116] by Panda.COM with ESMTP via TCP; Wed, 24 Feb 2010 09:06:54 -0800
X-MailFrom: mrc+ietf@panda.com
Date: Wed, 24 Feb 2010 09:06:53 -0800 (PST)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
In-Reply-To: <4B85414E.8060905@gulbrandsen.priv.no>
Message-ID: <alpine.OSX.2.00.1002240857280.404@hsinghsing.panda.com>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no> <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com> <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no> <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com> <4B8534ED.3000208@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240619100.404@hsinghsing.panda.com> <4B853913.404@gulbrandsen.priv.no> <4B853D22.2030407@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240654030.404@hsinghsing.panda.com> <4B85414E.8060905@gulbrandsen.priv.no>
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-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, 24 Feb 2010 17:04:53 -0000

On Wed, 24 Feb 2010, Arnt Gulbrandsen wrote:
> Either you know that there are results so the search will terminate, or
> you run the STATUSes to know when to stop looking, or you loop all the
> way to UINT_MAX. Right?

No, because the point of that search is to collect some results, not all
results.  You seem to be hung up on what needs to be done to assemble a
complete set of results from pieces.

>> The fact that you can't conceive of a use for something doesn't mean that
>> nobody else can.
> Right. The question is whether this is plausible/simple/useful enough to
> warrant support. IMAP extensions have a habit of making arcane
> taskspossible; I'd rather make the important tasks simple.

No, the question is whether the needs of your server justify adding yet
another special rule to IMAP.  In this case, the burden of proof is on
the proposal for deletion from a standard rule.

Have you considered that implementations might have to go to extra work
NOT to do something that they do in other circumstances?

-- 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 arnt@gulbrandsen.priv.no  Thu Feb 25 00:40:00 2010
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8160628C0E3 for <morg@core3.amsl.com>; Thu, 25 Feb 2010 00:40:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[AWL=0.198, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4wL3qdzbFds9 for <morg@core3.amsl.com>; Thu, 25 Feb 2010 00:39:59 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by core3.amsl.com (Postfix) with ESMTP id 4AEC43A8656 for <morg@ietf.org>; Thu, 25 Feb 2010 00:39:59 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 82DEDFA001B; Thu, 25 Feb 2010 08:42:14 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO libertango.gulbrandsen.priv.no) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.3) with esmtp id 1267087317-42234-42233/5/1 (2 recipients); Thu, 25 Feb 2010 09:41:57 +0100
Message-Id: <4B8637DC.70802@gulbrandsen.priv.no>
Date: Thu, 25 Feb 2010 09:42:04 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Organization: Me, http://arnt.gulbrandsen.priv.no
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
Mime-Version: 1.0
To: morg@ietf.org
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <F7C40486-F40A-45DC-AA38-748B494E9092@iki.fi> <6c9fcc2a1002231047w423fc844ibc3e293adcd74fda@mail.gmail.com> <4B842354.7020801@isode.com> <alpine.OSX.2.00.1002231053150.404@hsinghsing.panda.com> <4B84350B.4000307@gulbrandsen.priv.no> <alpine.OSX.2.00.1002231201140.404@hsinghsing.panda.com> <n5+yDDm2DPQmOxx++Bjlyg.md5@lochnagar.gulbrandsen.priv.no> <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com> <4B8534ED.3000208@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240619100.404@hsinghsing.panda.com> <4B853913.404@gulbrandsen.priv.no> <4B853D22.2030407@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240654030.404@hsinghsing.panda.com> <4B85414E.8060905@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240857280.404@hsinghsing.panda.com>
In-Reply-To: <alpine.OSX.2.00.1002240857280.404@hsinghsing.panda.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [MORG] I-D Action:draft-ietf-morg-multimailbox-search-02.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 08:40:01 -0000

On 02/24/2010 06:06 PM, Mark Crispin wrote:
> On Wed, 24 Feb 2010, Arnt Gulbrandsen wrote:
>> Either you know that there are results so the search will terminate, =
or
>> you run the STATUSes to know when to stop looking, or you loop all the
>> way to UINT_MAX. Right?
>
> No, because the point of that search is to collect some results, not =
all
> results. You seem to be hung up on what needs to be done to assemble a
> complete set of results from pieces.

Not quite; you assume there are some results to collect, I don't assume=20
that. And I have a... semi-rational disposition against the kind of very=20
long loop that would result, due to once having to pay =801769 in =
traffic=20
charges for a similar loop.

>>> The fact that you can't conceive of a use for something doesn't mean
>>> that
>>> nobody else can.
>> Right. The question is whether this is plausible/simple/useful enough =
to
>> warrant support. IMAP extensions have a habit of making arcane
>> taskspossible; I'd rather make the important tasks simple.
>
> No, the question is whether the needs of your server justify adding yet
> another special rule to IMAP. In this case, the burden of proof is on
> the proposal for deletion from a standard rule.

A misunderstanding, perhaps. I'm not arguing to eliminate the existing=20
MSN rule. I'm arguing that the present justification is too weak to=20
extend the rule to OTHER mailboxes. (Find a good use-case and my=20
protests with disappear.)

I think MSNs should be used to refer to messages in the selected=20
mailbox, not extended to unselected mailboxes.

> Have you considered that implementations might have to go to extra work
> NOT to do something that they do in other circumstances?

Yes. So? We all do that. GENURLAUTH and URLFETCH have similar=20
implications in my case, for example: No MSNs, all UIDs.

Arnt

From barryleiba.mailing.lists@gmail.com  Thu Feb 25 12:37:26 2010
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0B1228C243 for <morg@core3.amsl.com>; Thu, 25 Feb 2010 12:37:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.877
X-Spam-Level: 
X-Spam-Status: No, score=-2.877 tagged_above=-999 required=5 tests=[AWL=-0.278, 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 6WTF+0zPHlGo for <morg@core3.amsl.com>; Thu, 25 Feb 2010 12:37:25 -0800 (PST)
Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id 1842E3A8726 for <morg@ietf.org>; Thu, 25 Feb 2010 12:37:24 -0800 (PST)
Received: by fxm5 with SMTP id 5so6887343fxm.29 for <morg@ietf.org>; Thu, 25 Feb 2010 12:39:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=YbBgsxEoKdjSBAfuSH7jCK7OEzhVnBNqr/FHbErn2Cs=; b=ADMkRF0WbD7zHalek2n7uNLq8+lHD/XtR0/9Yfof9ThBKAzlulg0U/DHNgBf3KDFhQ yG/HxslCU20vfcEzcuwJk/+BBGvSk7AQk+KJn78kzo8UoBM1vQYgpF5h5tqQgP7M+vek b6knyOS9QE/Uv8ANJ6U+zmOSeBIEz+yhlp7rI=
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=KPhWUpmNRAroHkFE2fZFL3pmnI7TJ2yuVVJtD41jQHCePoOncXTkOUUZYc+yTwJW7V sBIhBaH8D+lpBGgbuBJTeuFaeOMn40rjFknLI2VsQej6S6/g4gNX1IDKtjwcWV0BITF6 nPn/5cvyopSAddBJTmlk0w4WQiMIXix44JhaM=
MIME-Version: 1.0
Received: by 10.223.5.212 with SMTP id 20mr265778faw.19.1267130372549; Thu, 25  Feb 2010 12:39:32 -0800 (PST)
In-Reply-To: <4B8637DC.70802@gulbrandsen.priv.no>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com> <4B8534ED.3000208@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240619100.404@hsinghsing.panda.com> <4B853913.404@gulbrandsen.priv.no> <4B853D22.2030407@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240654030.404@hsinghsing.panda.com> <4B85414E.8060905@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240857280.404@hsinghsing.panda.com> <4B8637DC.70802@gulbrandsen.priv.no>
Date: Thu, 25 Feb 2010 15:39:32 -0500
Message-ID: <6c9fcc2a1002251239m1e06e98fxca19d2ffaf0c98dc@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-multimailbox-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: Thu, 25 Feb 2010 20:37:26 -0000

Just addressing one point in particular:

> I think MSNs should be used to refer to messages in the selected mailbox,
> not extended to unselected mailboxes.

It would be the opposite of "extending", here; we would have to
*prohibit* a search criterion that's otherwise allowed.  I see no
reason to make such a prohibition.

It's possible that we should, nevertheless, say something about this
in the document, because it might create some confusion.  I'd like to
add a paragraph that explains the use of MSNs as search criteria in
unselected mailboxes.  In particular, I'd like to point out the usage
of only selecting the Nth set of M messages... and I'd like to add
some normative text saying that the server MUST NOT (or SHOULD NOT?
opinions requested) consider it an error for ESEARCH to pass an MSN
set that goes beyond the bounds of valid MSNs for any particular
mailbox.

In other words if there are 53 messages in mailbox Bloog, whether or not

   T0 SELECT Bloog
   T1 SEARCH SINCE 1-Dec-2009 101:200

...returns "T1 BAD - 101:200 out of range"

   T1 ESEARCH IN (mailboxes "Bloog") SINCE 1-Dec-2009 101:200

...MUST NOT (or SHOULD NOT?) return tagged NO or BAD.

Barry

From mrc+ietf@panda.com  Thu Feb 25 13:08:46 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 83B8C28C27F for <morg@core3.amsl.com>; Thu, 25 Feb 2010 13:08:46 -0800 (PST)
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 LCvX+VLf3Gb4 for <morg@core3.amsl.com>; Thu, 25 Feb 2010 13:08:45 -0800 (PST)
Received: from panda.com (panda.com [206.124.149.114]) by core3.amsl.com (Postfix) with ESMTP id 34EC028C150 for <morg@ietf.org>; Thu, 25 Feb 2010 13:08:45 -0800 (PST)
Received: from hsinghsing.panda.com [206.124.149.116] by Panda.COM with ESMTP via TCP; Thu, 25 Feb 2010 13:10:52 -0800
X-MailFrom: mrc+ietf@panda.com
Date: Thu, 25 Feb 2010 13:10:50 -0800 (PST)
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: barryleiba@computer.org
In-Reply-To: <6c9fcc2a1002251239m1e06e98fxca19d2ffaf0c98dc@mail.gmail.com>
Message-ID: <alpine.OSX.2.00.1002251257240.404@hsinghsing.panda.com>
References: <1197163948.15717.1266698181686.JavaMail.root@dogfood.zimbra.com> <alpine.OSX.2.00.1002240605370.404@hsinghsing.panda.com> <4B8534ED.3000208@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240619100.404@hsinghsing.panda.com> <4B853913.404@gulbrandsen.priv.no> <4B853D22.2030407@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240654030.404@hsinghsing.panda.com> <4B85414E.8060905@gulbrandsen.priv.no> <alpine.OSX.2.00.1002240857280.404@hsinghsing.panda.com> <4B8637DC.70802@gulbrandsen.priv.no> <6c9fcc2a1002251239m1e06e98fxca19d2ffaf0c98dc@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-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: Thu, 25 Feb 2010 21:08:46 -0000

On Thu, 25 Feb 2010, Barry Leiba wrote:
> I'd like to add
> some normative text saying that the server MUST NOT (or SHOULD NOT?
> opinions requested) consider it an error for ESEARCH to pass an MSN
> set that goes beyond the bounds of valid MSNs for any particular
> mailbox.

It is not an error in SEARCH or UID SEARCH either.  RFC 3501 could perhaps
be a bit more clear on that point.  The question never really came up
before.

In SEARCH, the MSN search criterion is a searching specifier.  Unlike
FETCH, STORE, COPY, etc., the SEARCH command is not operating on those
MSNs; in fact, it could even be a NOT of those MSNs.

-- 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 root@core3.amsl.com  Thu Feb 25 15:00:01 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 5015E3A870A; Thu, 25 Feb 2010 15:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100225230001.5015E3A870A@core3.amsl.com>
Date: Thu, 25 Feb 2010 15:00:01 -0800 (PST)
Cc: morg@ietf.org
Subject: [MORG] I-D ACTION:draft-ietf-morg-sortdisplay-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: Thu, 25 Feb 2010 23:00:01 -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		: Display-based Address Sorting for the IMAP4 SORT Extension
	Author(s)	: D. Karp
	Filename	: draft-ietf-morg-sortdisplay-03.txt
	Pages		: 6
	Date		: 2010-2-25
	
This document describes an IMAP protocol extension enabling server-
   side message sorting on the commonly-displayed portion of the From
   and To header fields.

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

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


--NextPart--


From wwwrun@core3.amsl.com  Fri Feb 26 09:00:10 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: morg@ietf.org
Delivered-To: morg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id B430028C245; Fri, 26 Feb 2010 09:00:10 -0800 (PST)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20100226170010.B430028C245@core3.amsl.com>
Date: Fri, 26 Feb 2010 09:00:10 -0800 (PST)
Cc: morg@ietf.org
Subject: [MORG] Last Call: draft-ietf-morg-sortdisplay (Display-based Address Sorting for the IMAP4 SORT Extension) to Proposed Standard
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.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, 26 Feb 2010 17:00:10 -0000

The IESG has received a request from the Message Organization WG (morg) 
to consider the following document:

- 'Display-based Address Sorting for the IMAP4 SORT Extension '
   <draft-ietf-morg-sortdisplay-03.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-03-12. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-morg-sortdisplay-03.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18157&rfc_flag=0

