
From nobody Thu Mar  6 02:42:22 2014
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF6B11A020D for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 02:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvfkgB25DVt9 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 02:42:19 -0800 (PST)
Received: from mail-ve0-x22f.google.com (mail-ve0-x22f.google.com [IPv6:2607:f8b0:400c:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 563A71A01C8 for <imapext@ietf.org>; Thu,  6 Mar 2014 02:42:19 -0800 (PST)
Received: by mail-ve0-f175.google.com with SMTP id oz11so2391446veb.20 for <imapext@ietf.org>; Thu, 06 Mar 2014 02:42:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=OTlORF/pjDr4FIQlPMAV6KJgx/O80sQE5G92H+tCLrQ=; b=X3g0+avnql9Isi2tx2cDupLODntpeC3wYbzs5yMrVZl4vJ5/cbszceoNvL6kSXtVHr cdVrknGCBS3PlBspEaq/PO6BghRIm1bVZrNeJjJt/kC5saAv7K9U7DmZSqoWLEP9PMBI g3KDiJklQYnTLbLS3EC+tkT8/SYJjzHwZ1FqFJ/p/vUhL1bcWNj5KCJdctpUfLE7YiaJ IKb2+4cfdF5fudjJzipjhgwLAutNykKhJZ4ORRBp5ULr4KnygrfMyRHM8PbHXDkDh2Xd QpEnSjWVFLndQyhjIvy+XbmhSRsY/BH+519XmMWNyWOKu8NtZWkijOw+fQDn8WvHv+ym Zrng==
MIME-Version: 1.0
X-Received: by 10.220.161.132 with SMTP id r4mr270658vcx.29.1394102535306; Thu, 06 Mar 2014 02:42:15 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.19.104 with HTTP; Thu, 6 Mar 2014 02:42:15 -0800 (PST)
Date: Thu, 6 Mar 2014 10:42:15 +0000
X-Google-Sender-Auth: 1IekoNwPQQr4YgS-1fNdPED_WYk
Message-ID: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "imapext@ietf.org" <imapext@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/hHZrhyrb8EfVcj88woQDrtg8GjI
Subject: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 10:42:21 -0000

IMAP denizens...

Chris Newman has asked that we consider moving the Multimailbox Search
extension to Standards Track (it was published as RFC 6237 as
Experimental).  Appsawg is handling that:

http://datatracker.ietf.org/doc/draft-ietf-appsawg-multimailbox-search/

I'd like to ask the IMAP crowd to do two things:

1. Review the document and post comments to apps-discuss@ietf.org

2. Tell us, in your review or separately here, if you (a) have
implemented it and/or (b) have interest in implementing it (and
specify client, server, or both).

Please take a few minutes to do this -- the document isn't long, and
we very much need the reviews to move this ahead.

Thanks,
Barry


From nobody Thu Mar  6 02:58:00 2014
Return-Path: <brong@fastmail.fm>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DCC41A01C9 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 02:57:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.801
X-Spam-Level: 
X-Spam-Status: No, score=-0.801 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IEvA2CIce0Xp for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 02:57:57 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 53BF11A01C8 for <imapext@ietf.org>; Thu,  6 Mar 2014 02:57:57 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 7383520D79 for <imapext@ietf.org>; Thu,  6 Mar 2014 05:57:53 -0500 (EST)
Received: from web5 ([10.202.2.215]) by compute5.internal (MEProxy); Thu, 06 Mar 2014 05:57:53 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:in-reply-to:references:subject:date; s=mesmtp; bh= MuuDWgsDPlJG07V3tv7Sw+2pzMw=; b=Vjw9mlcA39v7icZZrE80XBa+qs4Igq3p 6vD/nGQTHFE0RcDh+5I3QfJQKv83USeX/9azaNViYASX6QFUZJN3BQ5BHy1lIbzu NSzcCjjiKBLEehpAYZUM6z/2F2OvQU52EaeFjVCzk2ujsYI0krJ3MQoo93xpbyEn dky6SzwI8YE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=MuuDWgsDPlJG07V3tv7Sw+2pzMw=; b=b48 BRDwKkiATSJ2VAa3YC6cVj9Qrd/KO6PDMmtPZMgncQYyQZfQQyXaiTiBdGxNXP0R Vr90DXFvxycrzzZsaos4PyxAsAikhkBEYAET296gtyPgUnG9wQeis4Yd/opfmpW5 RZGwmnHQRQQvLn6qjFEDhml7zwdvRqLO4eU8qfp0=
Received: by web5.nyi.mail.srv.osa (Postfix, from userid 99) id 4EE15B0593F; Thu,  6 Mar 2014 05:57:53 -0500 (EST)
Message-Id: <1394103473.14059.91258445.054B3082@webmail.messagingengine.com>
X-Sasl-Enc: /2Uw4UVqHZ+FH5TB6pTsw9m3hjfWmF/poe8YAnYhqLxo 1394103473
From: Bron Gondwana <brong@fastmail.fm>
To: imapext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-4527a23f
In-Reply-To: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com>
References: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com>
Date: Thu, 06 Mar 2014 21:57:53 +1100
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/hmOOxmOYUdihIdtDD9HXfTNXLJY
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 10:57:59 -0000

On Thu, Mar 6, 2014, at 09:42 PM, Barry Leiba wrote:
> IMAP denizens...
> 
> Chris Newman has asked that we consider moving the Multimailbox Search
> extension to Standards Track (it was published as RFC 6237 as
> Experimental).  Appsawg is handling that:
> 
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-multimailbox-search/
> 
> I'd like to ask the IMAP crowd to do two things:
> 
> 1. Review the document and post comments to apps-discuss@ietf.org
> 
> 2. Tell us, in your review or separately here, if you (a) have
> implemented it and/or (b) have interest in implementing it (and
> specify client, server, or both).

We didn't implement it because it wasn't possible to track the results
over time - instead we have a command xconvmultisearch (yes, I know,
ugly name) which:

a) only works within single users, because:
b) we keep a single highestmodseq value across all mailboxes within a single
   user, so we can
c) lock the entire user from modifications while we run the search, and
   hence ensure a consistent read, and
d) return the highestmodseq of that read, so that further requests can
   ask for updates since the previous modseq - and they'll get a list of
   anything added, removed or just touched.

This also handles the folding of related (roughly thread=references, with
some trickyness) messages into a single "exemplar".

So we're strayed quite a long way from IMAP to get what we need.

Anyway - my main problem with it is that users don't just want search - they
want sort.  Running the search across multiple mailboxes means you still need
to fetch all the data for all the matches before you can get a meaningful sort
by any parameter other than mailbox name as the first sort index.  And that
can be a lot of download to the client if you searched a common term.]

I'm not signed up for apps-discuss.  Guess I'd better go do that.

Cheers,

Bron.


-- 
  Bron Gondwana
  brong@fastmail.fm


From nobody Thu Mar  6 06:30:50 2014
Return-Path: <cyrus@daboo.name>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECCD31A03E3 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 06:30:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rHyL8X5aUehH for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 06:30:46 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 36E5D1A00DC for <imapext@ietf.org>; Thu,  6 Mar 2014 06:30:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 7A0F95EAA7EF for <imapext@ietf.org>; Thu,  6 Mar 2014 09:30:44 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZjwSaubg1g5V for <imapext@ietf.org>; Thu,  6 Mar 2014 09:30:42 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id B0FCC5EAA7E3 for <imapext@ietf.org>; Thu,  6 Mar 2014 09:30:41 -0500 (EST)
Date: Thu, 06 Mar 2014 09:30:17 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: imapext@ietf.org
Message-ID: <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com>
In-Reply-To: <1394103473.14059.91258445.054B3082@webmail.messagingengine.com>
References: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com> <1394103473.14059.91258445.054B3082@webmail.messagingengine.com>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1251
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/RJAKiFkBmIgtyYWhS9wuNzkje7k
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 14:30:49 -0000

Hi,

--On March 6, 2014 at 10:42:15 AM +0000 Barry Leiba 
<barryleiba@computer.org> wrote:

> Chris Newman has asked that we consider moving the Multimailbox Search
> extension to Standards Track (it was published as RFC 6237 as
> Experimental).  Appsawg is handling that:

If sufficient servers AND clients have bothered to implement 
multimailbox-search and they have proven to be interoperable then I see no 
objection to moving to standards track (i.e, the experiment was a success 
so lets move forward) - but can we see evidence of that first?

--On March 6, 2014 at 9:57:53 PM +1100 Bron Gondwana <brong@fastmail.fm> 
wrote:

> Anyway - my main problem with it is that users don't just want search -
> they want sort.  Running the search across multiple mailboxes means you
> still need to fetch all the data for all the matches before you can get a
> meaningful sort by any parameter other than mailbox name as the first
> sort index.  And that can be a lot of download to the client if you
> searched a common term.]

On Bron's point - yes what is really needed is an extension that does away 
with the single selected mailbox model and allows searching, sorting, 
sync'ing, message access across all mailboxes all the time.

-- 
Cyrus Daboo


From nobody Thu Mar  6 06:36:49 2014
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 603241A038C for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 06:36:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ggZoWcz3_rWy for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 06:36:41 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) by ietfa.amsl.com (Postfix) with ESMTP id 838671A02CA for <imapext@ietf.org>; Thu,  6 Mar 2014 06:36:40 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 6623EFA0097; Thu,  6 Mar 2014 14:36:35 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1394116594-12153-12153/11/11; Thu, 6 Mar 2014 14:36:34 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Cyrus Daboo <cyrus@daboo.name>
Date: Thu, 6 Mar 2014 15:36:33 +0100
User-Agent: Trojita/v0.3.96-176-g713fcbb; Qt/4.8.4; X11; Linux; Ubuntu 13.10
Mime-Version: 1.0
Message-Id: <b5d0bbd9-ffa7-4a2c-b0de-075e03694adf@gulbrandsen.priv.no>
In-Reply-To: <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com>
References: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com> <1394103473.14059.91258445.054B3082@webmail.messagingengine.com> <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/Nfw4Z1X98iBYtt_PYic7LLNAS3A
Cc: imapext@ietf.org
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 14:36:46 -0000

On Thursday, March 6, 2014 3:30:17 PM CEST, Cyrus Daboo wrote:
> If sufficient servers AND clients have bothered to implement 
> multimailbox-search and they have proven to be interoperable 
> then I see no objection to moving to standards track (i.e, the 
> experiment was a success so lets move forward) - but can we see 
> evidence of that first?

Uh. What are some clients that have done this?

AFAICT, gmail's way (an "all mail" mailbox) has won in practice, despite 
its problems.

Arnt


From nobody Thu Mar  6 08:30:18 2014
Return-Path: <chris.newman@oracle.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 761151A01D4 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 08:30:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level: 
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M2vYO_fAbpYl for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 08:30:04 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id CF9E81A01BA for <imapext@ietf.org>; Thu,  6 Mar 2014 08:30:03 -0800 (PST)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s26GTope016511 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Mar 2014 16:29:51 GMT
Received: from gotmail.us.oracle.com (gotmail.us.oracle.com [10.133.152.174]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s26GTo5U015367; Thu, 6 Mar 2014 16:29:50 GMT
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [10.175.34.52] (dhcp-uk-twvpn-1-vpnpool-10-175-26-83.vpn.oracle.com [10.175.26.83]) by gotmail.us.oracle.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built Jan 22 2014)) with ESMTPA id <0N2000A05WHNM100@gotmail.us.oracle.com>; Thu, 06 Mar 2014 08:29:49 -0800 (PST)
Date: Thu, 06 Mar 2014 16:29:46 +0000
From: Chris Newman <chris.newman@oracle.com>
To: Cyrus Daboo <cyrus@daboo.name>, imapext@ietf.org
Message-id: <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90>
In-reply-to: <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com>
References: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com> <1394103473.14059.91258445.054B3082@webmail.messagingengine.com> <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/nj7SBI8ZruQXTfu1SsVcvAkOG2c
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 16:30:09 -0000

--On March 6, 2014 9:30:17 -0500 Cyrus Daboo <cyrus@daboo.name> wrote:
> --On March 6, 2014 at 10:42:15 AM +0000 Barry Leiba
> <barryleiba@computer.org> wrote:
>
>> Chris Newman has asked that we consider moving the Multimailbox Search
>> extension to Standards Track (it was published as RFC 6237 as
>> Experimental).  Appsawg is handling that:
>
> If sufficient servers AND clients have bothered to implement
> multimailbox-search and they have proven to be interoperable then I see
> no objection to moving to standards track (i.e, the experiment was a
> success so lets move forward) - but can we see evidence of that first?

I have written a server implementation of MULTISEARCH that is not presently 
released. As a server vendor, I have had two independent requests for this 
feature. At least one of those requests is from a customer that is working 
on a client implementation. I can not name the customer.

> --On March 6, 2014 at 9:57:53 PM +1100 Bron Gondwana <brong@fastmail.fm> 
wrote:
>> Anyway - my main problem with it is that users don't just want search -
>> they want sort.  Running the search across multiple mailboxes means you
>> still need to fetch all the data for all the matches before you can get a
>> meaningful sort by any parameter other than mailbox name as the first
>> sort index.  And that can be a lot of download to the client if you
>> searched a common term.]
>
> On Bron's point - yes what is really needed is an extension that does
> away with the single selected mailbox model and allows searching,
> sorting, sync'ing, message access across all mailboxes all the time.

I have no interest in implementing such an extension at this time. I'm 
going to assert there is not enough interest in such a proposal to get a 
specification written, thus making it not relevant to this discussion. If 
someone were to prove my assertion wrong, then we could have an interesting 
discussion about whether one or both proposals should go to standards track.

For just searching, the current MULTISEARCH design has significant benefits 
for both client and server. It produces concise results (a UID set for each 
mailbox rather than list of UIDs), and the straightforward implementation 
will return results as they are found on a per-mailbox basis in a way that 
clients can display the results as they are found. The straightforward 
implementation of MULTISORT/ALLMSGS has to compute all the results before 
sending anything to the client. There's value to having these be separate 
extensions even if sufficient interest to write a MULTISORT/ALLMSGS 
extension materializes in the future.

		- Chris


From nobody Thu Mar  6 08:43:35 2014
Return-Path: <cyrus@daboo.name>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB0631A00EC for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 08:43:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QwSg4d1beq4r for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 08:43:32 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5FEDF1A00DE for <imapext@ietf.org>; Thu,  6 Mar 2014 08:43:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id A28F05EACE44; Thu,  6 Mar 2014 11:43:30 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PVgtDlXIYmL1; Thu,  6 Mar 2014 11:43:30 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 6167C5EACE38; Thu,  6 Mar 2014 11:43:29 -0500 (EST)
Date: Thu, 06 Mar 2014 11:43:03 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Chris Newman <chris.newman@oracle.com>, imapext@ietf.org
Message-ID: <92EB7004C315F1887BC4A858@caldav.corp.apple.com>
In-Reply-To: <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90>
References: <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1566
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/Wf8Gfj9lKSxdP21AZNr_nK_0F0Q
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 16:43:33 -0000

Hi Chris,

--On March 6, 2014 at 4:29:46 PM +0000 Chris Newman 
<chris.newman@oracle.com> wrote:

>> If sufficient servers AND clients have bothered to implement
>> multimailbox-search and they have proven to be interoperable then I see
>> no objection to moving to standards track (i.e, the experiment was a
>> success so lets move forward) - but can we see evidence of that first?
>
> I have written a server implementation of MULTISEARCH that is not
> presently released. As a server vendor, I have had two independent
> requests for this feature. At least one of those requests is from a
> customer that is working on a client implementation. I can not name the
> customer.

And the current status of experimental matters to them in terms of 
developing an implementation right now?

My point here is that until we have interoperable implementations on both 
client and server and have caught and fixed any issues in the spec, we 
shouldn't advance the status.

Well, Ok that is my interpretation of what "experimental" should mean - 
others may disagree with that...

Now I am happy to take your word for it that your customer has done a 
client implementation and is happy with the spec (or whatever changes are 
being proposed to advance it). It would be nice to hear from some other 
servers/clients as well...

FYI If I were still working on my client, I would be keen to see 
MULTISEARCH supported since it did the equivalent using select/search 
across multiple mailboxes to get results. It would definitely benefitted 
from MULTISEARCH.

-- 
Cyrus Daboo


From nobody Thu Mar  6 08:51:44 2014
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E0D1A00E8 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 08:51:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WCan7VJRptKp for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 08:51:37 -0800 (PST)
Received: from mail-ve0-x22c.google.com (mail-ve0-x22c.google.com [IPv6:2607:f8b0:400c:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1481A00B4 for <imapext@ietf.org>; Thu,  6 Mar 2014 08:51:37 -0800 (PST)
Received: by mail-ve0-f172.google.com with SMTP id jx11so2925697veb.31 for <imapext@ietf.org>; Thu, 06 Mar 2014 08:51:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HKGYm01TUdEvf4PHwLELiNi5prOfV2X6yD4oWfcwAhE=; b=cSyrct7Voo9Ucv+RF+11VElQ9v6PaC8UOJGXpDRiUC1kapn6KIImzWgukvgR+k6Leu AUvQGz3Vxjtw8kKUK0Tp7NvPBCpWa6t/PU0mflpT/55KoIo7krTU09ChF+BLHpdZlFz+ tXdGYusMgb+++Lex39DtbhFEeoU+WyGVNMshuzjyIpiAWgJwAlDVTGhE6h4/90ZMTeG7 nhLsQeJPngg1vSCpqWLaIxtA6AnvYW7qN3b5vY5FvxUNF679/4t69KJaHpVZxdLxpV13 qxDPZsB3weBGmEda3ilEZVAkTJ7yQQkvhvkC2Tyy+PixSUcgUTjyJFKu33ATcWLxudQd 5KZg==
MIME-Version: 1.0
X-Received: by 10.220.68.5 with SMTP id t5mr9418vci.57.1394124693073; Thu, 06 Mar 2014 08:51:33 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.19.104 with HTTP; Thu, 6 Mar 2014 08:51:33 -0800 (PST)
In-Reply-To: <92EB7004C315F1887BC4A858@caldav.corp.apple.com>
References: <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90> <92EB7004C315F1887BC4A858@caldav.corp.apple.com>
Date: Thu, 6 Mar 2014 16:51:33 +0000
X-Google-Sender-Auth: CjYlwcXjwzPoa1d2XMOC3rdT_dU
Message-ID: <CAC4RtVAgNg0vf35JgJ+MqbCNE3UMjQ3MUt9bC1yKBg559qM_Nw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/TRB5DgfoHagZWGdwOUTDdQN5h9M
Cc: Chris Newman <chris.newman@oracle.com>, "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 16:51:39 -0000

> My point here is that until we have interoperable implementations on both
> client and server and have caught and fixed any issues in the spec, we
> shouldn't advance the status.

Why not?  Interoperable implementations aren't required for Proposed
Standard.  Internet Standard, sure, but not PS.  The requirement for
PS is that we think we got it right.

I would like to see more implementation experience -- it's be great to
see.  That's why I asked whether there is any.  But to me, the gating
factor is more about whether there's *interest* in implementing it.

> FYI If I were still working on my client, I would be keen to see MULTISEARCH
> supported since it did the equivalent using select/search across multiple
> mailboxes to get results. It would definitely benefitted from MULTISEARCH.

Exactly.

b


From nobody Thu Mar  6 09:12:33 2014
Return-Path: <tss@iki.fi>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED7DB1A00D3 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 09:12:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Trnq9lOeRsVk for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 09:12:26 -0800 (PST)
Received: from wursti.dovecot.fi (wursti.dovecot.fi [87.106.245.223]) by ietfa.amsl.com (Postfix) with ESMTP id 7A82E1A0083 for <imapext@ietf.org>; Thu,  6 Mar 2014 09:12:26 -0800 (PST)
Received: from [10.217.1.108] (vfw03.dovecot.fi [88.194.145.100]) by wursti.dovecot.fi (Postfix) with ESMTPSA id 4191921AFD for <imapext@ietf.org>; Thu,  6 Mar 2014 18:12:21 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Timo Sirainen <tss@iki.fi>
In-Reply-To: <b5d0bbd9-ffa7-4a2c-b0de-075e03694adf@gulbrandsen.priv.no>
Date: Thu, 6 Mar 2014 19:12:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB4BDD8D-FDEA-4014-B3B7-5040A1EE97A2@iki.fi>
References: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com> <1394103473.14059.91258445.054B3082@webmail.messagingengine.com> <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com> <b5d0bbd9-ffa7-4a2c-b0de-075e03694adf@gulbrandsen.priv.no>
To: imapext@ietf.org
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/kFCzkRfvHWymVDpj_ibnnF34Opw
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 17:12:29 -0000

On 6.3.2014, at 16.36, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> =
wrote:

> AFAICT, gmail's way (an "all mail" mailbox) has won in practice, =
despite its problems.

This is how it's been implemented in Dovecot. There's a virtual "all =
mails" mailbox which the clients can use with (almost) zero =
modifications to their code. Usually this is configured to be a hidden =
mailbox used only by webmails. There are also special FETCH X-MAILBOX =
and X-REAL-UID fields that can be used to access the underlying actual =
mail and SEARCH has X-MAILBOX parameter. Whenever someone has requested =
MULTISEARCH extension for Dovecot and I've pointed out the way to do it =
with virtual mailboxes, they haven't cared about MULTISEARCH anymore. So =
I'm not really interested in implementing it. Adding some =
standardization for the \All mailbox would be useful though.


From nobody Thu Mar  6 09:12:49 2014
Return-Path: <cyrus@daboo.name>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 682BC1A0083 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 09:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ROpuoY-CIRAw for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 09:12:36 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 420FC1A0226 for <imapext@ietf.org>; Thu,  6 Mar 2014 09:12:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 8CED85EAD6C3; Thu,  6 Mar 2014 12:12:34 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KGayrUBG3d61; Thu,  6 Mar 2014 12:12:33 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 3FEF95EAD6A8; Thu,  6 Mar 2014 12:12:32 -0500 (EST)
Date: Thu, 06 Mar 2014 12:12:07 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Barry Leiba <barryleiba@computer.org>
Message-ID: <8C172B0F6A5AC4B62F5C66A3@caldav.corp.apple.com>
In-Reply-To: <CAC4RtVAgNg0vf35JgJ+MqbCNE3UMjQ3MUt9bC1yKBg559qM_Nw@mail.gmail.com>
References: <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90> <92EB7004C315F1887BC4A858@caldav.corp.apple.com> <CAC4RtVAgNg0vf35JgJ+MqbCNE3UMjQ3MUt9bC1yKBg559qM_Nw@mail.gmail.com>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1122
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/xSO3dw4Y6jOhHSdJ_-o-pqg3s0g
Cc: Chris Newman <chris.newman@oracle.com>, imapext@ietf.org
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 17:12:42 -0000

Hi Barry,

--On March 6, 2014 at 4:51:33 PM +0000 Barry Leiba 
<barryleiba@computer.org> wrote:

> I would like to see more implementation experience -- it's be great to
> see.  That's why I asked whether there is any.  But to me, the gating
> factor is more about whether there's *interest* in implementing it.

I am pretty sure people would have raised there hands saying they are 
"interested" in it before the current spec was even written. But it was 
given "experimental" status for a reason back then. Why was that? I hunted 
down the relevant message to the MORG mailing list and saw this 
(<http://www.ietf.org/mail-archive/web/morg/current/msg00507.html>):

> 2. We have changed the target status of this from standards track to
> experimental.  We think there isn't strong enough consensus to go for
> standards track, given the possible interactions with other
> extensions.

At the very least we need to address that point before we should change the 
status. And I do think that means actually having people implement it and 
see what those possible problems might be, and then report back.

-- 
Cyrus Daboo


From nobody Thu Mar  6 09:16:09 2014
Return-Path: <barryleiba@gmail.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E44101A01FD for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 09:16:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J0gxLpre3r0f for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 09:16:05 -0800 (PST)
Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id 738071A0231 for <imapext@ietf.org>; Thu,  6 Mar 2014 09:16:04 -0800 (PST)
Received: by mail-qa0-f53.google.com with SMTP id w8so2763629qac.26 for <imapext@ietf.org>; Thu, 06 Mar 2014 09:16:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=xBG3KPnKk0JOJRu1Rhm8Cmc6TgSlmxM/kvBbmrJzEyQ=; b=RHNFJH9J+2EeCOLfMOp+fz2SJA3+kwDOp5u6qUDyI0EfHM0v5jHtuDDhcH9jaN0JWv 0VUlbRlCtmDDx+TQXmpSc3O45ANXGTIJvffz5sJGbEgFIDVP/c6XubO2NfaxRvxkMS83 s3uuQEG0c2hAICOCZwBaqW9+GTji3vXeYpjS4dAK1vzLjHEm63NkZ0AWqxxTM0MmcbYL tU4SFWuLcKnYTAPMe6CYzcCs/1RfPic/jnRdb+zSECQyrrG9scOLrmZW82IgXzqFEZI6 IMTcMUkG8xwXGah3eTkbOanHQ1HZ6BVrg8b5Z/z0mK4dI1/JTdoyx/fhB/tAj2NkvCpq Pm/Q==
MIME-Version: 1.0
X-Received: by 10.224.75.73 with SMTP id x9mr15906031qaj.36.1394126160280; Thu, 06 Mar 2014 09:16:00 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.224.26.11 with HTTP; Thu, 6 Mar 2014 09:16:00 -0800 (PST)
In-Reply-To: <8C172B0F6A5AC4B62F5C66A3@caldav.corp.apple.com>
References: <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90> <92EB7004C315F1887BC4A858@caldav.corp.apple.com> <CAC4RtVAgNg0vf35JgJ+MqbCNE3UMjQ3MUt9bC1yKBg559qM_Nw@mail.gmail.com> <8C172B0F6A5AC4B62F5C66A3@caldav.corp.apple.com>
Date: Thu, 6 Mar 2014 09:16:00 -0800
X-Google-Sender-Auth: mc2qH-6LQTxmksd0r1aai8YvlLw
Message-ID: <CALaySJ+qsQCBAh09zCd1jVYgKsOqKLoxYaww+o4tQ1Oyx3nikA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/0MHdGSLcn9SamWNg4Izye-Ws-M0
Cc: Chris Newman <chris.newman@oracle.com>, "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 17:16:06 -0000

> given "experimental" status for a reason back then. Why was that?

Because we weren't sure we got it right.

>> 2. We have changed the target status of this from standards track to
>> experimental.  We think there isn't strong enough consensus to go for
>> standards track, given the possible interactions with other
>> extensions.
>
> At the very least we need to address that point before we should change the
> status. And I do think that means actually having people implement it and
> see what those possible problems might be, and then report back.

Chris, please post what you said to me when you asked me to start this
up -- the bit about how we got the interactions right.

Barry


From nobody Thu Mar  6 09:17:07 2014
Return-Path: <cyrus@daboo.name>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E4EF1A0247 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 09:17:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jBegMuqeshmW for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 09:17:03 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5181A01D6 for <imapext@ietf.org>; Thu,  6 Mar 2014 09:17:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 6B2335EAD824; Thu,  6 Mar 2014 12:17:01 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mrRQ2ZzEc4WW; Thu,  6 Mar 2014 12:17:00 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 562175EAD817; Thu,  6 Mar 2014 12:16:59 -0500 (EST)
Date: Thu, 06 Mar 2014 12:16:34 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Barry Leiba <barryleiba@computer.org>
Message-ID: <074B475021C23745B3795CFD@caldav.corp.apple.com>
In-Reply-To: <8C172B0F6A5AC4B62F5C66A3@caldav.corp.apple.com>
References: <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90> <92EB7004C315F1887BC4A858@caldav.corp.apple.com> <CAC4RtVAgNg0vf35JgJ+MqbCNE3UMjQ3MUt9bC1yKBg559qM_Nw@mail.gmail.com> <8C172B0F6A5AC4B62F5C66A3@caldav.corp.apple.com>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=930
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/qSiLkzda0i98Sh3AiwC0AXUcw24
Cc: Chris Newman <chris.newman@oracle.com>, imapext@ietf.org
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 17:17:04 -0000

Hi Barry,

--On March 6, 2014 at 12:12:07 PM -0500 Cyrus Daboo <cyrus@daboo.name> 
wrote:

>> 2. We have changed the target status of this from standards track to
>> experimental.  We think there isn't strong enough consensus to go for
>> standards track, given the possible interactions with other
>> extensions.
>
> At the very least we need to address that point before we should change
> the status. And I do think that means actually having people implement it
> and see what those possible problems might be, and then report back.

I note the new spec does state:

>    This extension was previously published as experimental.  There is
>    now implementation experience, giving confidence in the protocol, so
>    this document puts the extension on the Standards Track, with some
>    minor updates that were informed by the implementation experience.

I guess I am just asking for confirmation of that.

-- 
Cyrus Daboo


From nobody Thu Mar  6 09:45:16 2014
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D625E1A0086 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 09:45:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zRbVVsXbSP4s for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 09:45:12 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE7E1A0040 for <imapext@ietf.org>; Thu,  6 Mar 2014 09:45:11 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 4A599FA00A6; Thu,  6 Mar 2014 17:45:07 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1394127906-12153-12153/11/13; Thu, 6 Mar 2014 17:45:06 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Thu, 6 Mar 2014 18:45:05 +0100
User-Agent: Trojita/v0.3.96-176-g713fcbb; Qt/4.8.4; X11; Linux; Ubuntu 13.10
Mime-Version: 1.0
Message-Id: <9a717e2c-a82f-462e-859a-e30057bc4bc6@gulbrandsen.priv.no>
In-Reply-To: <DB4BDD8D-FDEA-4014-B3B7-5040A1EE97A2@iki.fi>
References: <DB4BDD8D-FDEA-4014-B3B7-5040A1EE97A2@iki.fi>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/W8M6ytKAlFJyq43f-IkqP__dQgw
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 17:45:14 -0000

On Thursday, March 6, 2014 6:12:19 PM CEST, Timo Sirainen wrote:
> So I'm not really 
> interested in implementing it. Adding some standardization for 
> the \All mailbox would be useful though.

Such as? We do have special-use to declare \all, what more do you want?

I'd like to have something like X-GM-MSGID (and X-GM-THRID is great too).

Arnt


From nobody Thu Mar  6 11:33:47 2014
Return-Path: <chris.newman@oracle.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 750FD1A00E9 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 11:33:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level: 
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lty2NXGpInUS for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 11:33:42 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 871B51A0084 for <imapext@ietf.org>; Thu,  6 Mar 2014 11:33:42 -0800 (PST)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s26JXanj021573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Mar 2014 19:33:37 GMT
Received: from gotmail.us.oracle.com (gotmail.us.oracle.com [10.133.152.174]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s26JXZ8b005444; Thu, 6 Mar 2014 19:33:36 GMT
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [10.175.34.52] (dhcp-uk-twvpn-2-vpnpool-10-175-54-176.vpn.oracle.com.175.10.in-addr.arpa [10.175.54.176]) by gotmail.us.oracle.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built Jan 22 2014)) with ESMTPA id <0N2100A174ZWM100@gotmail.us.oracle.com>; Thu, 06 Mar 2014 11:33:34 -0800 (PST)
Date: Thu, 06 Mar 2014 19:33:31 +0000
From: Chris Newman <chris.newman@oracle.com>
To: Cyrus Daboo <cyrus@daboo.name>, imapext@ietf.org
Message-id: <0163EA9F918CF3A41831B299@96B2F16665FF96BAE59E9B90>
In-reply-to: <92EB7004C315F1887BC4A858@caldav.corp.apple.com>
References: <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90> <92EB7004C315F1887BC4A858@caldav.corp.apple.com>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/jvEbCJlDzl2ZfXr3PbOrWC94TdU
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 19:33:44 -0000

--On March 6, 2014 11:43:03 -0500 Cyrus Daboo <cyrus@daboo.name> wrote:
> --On March 6, 2014 at 4:29:46 PM +0000 Chris Newman
> <chris.newman@oracle.com> wrote:
>>> If sufficient servers AND clients have bothered to implement
>>> multimailbox-search and they have proven to be interoperable then I see
>>> no objection to moving to standards track (i.e, the experiment was a
>>> success so lets move forward) - but can we see evidence of that first?
>>
>> I have written a server implementation of MULTISEARCH that is not
>> presently released. As a server vendor, I have had two independent
>> requests for this feature. At least one of those requests is from a
>> customer that is working on a client implementation. I can not name the
>> customer.
>
> And the current status of experimental matters to them in terms of
> developing an implementation right now?

The organization that I believe is implementing a client was uncomfortable 
with the experimental status. I was not given a specific reason. I suspect 
they interpreted "experimental" as meaning "subject to incompatible 
change". While that shouldn't deter implementation (and I do not believe it 
will), that would understandably make someone doing a large deployment 
uncomfortable. That's a legitimate concern and I believe moving it to 
standards track is the right response unless there's evidence the 
specification is immature. After implementing it, I found the protocol well 
designed and complete.

> My point here is that until we have interoperable implementations on both
> client and server and have caught and fixed any issues in the spec, we
> shouldn't advance the status.

That's not required by the process. For this particular proposal, the 
server side is quite complex to implement so waiting for a server 
implementation before going standards track made sense. But the client side 
is just protocol from RFC 4731 (that is deployed in clients already) with 
some minor tweaks.

> Now I am happy to take your word for it that your customer has done a
> client implementation and is happy with the spec (or whatever changes are
> being proposed to advance it). It would be nice to hear from some other
> servers/clients as well...

I agree it would be nice to hear from more implementers.

The two technical issues I raised were minor. I'd like the rules for 
BODY/TEXT in the context of multisearch to be loosened so that 
implementations are not required to do substring search, but could be 
considered compliant if they did a word-based indexed search (actually, I 
wouldn't mind making that change to the IMAP base spac, but that's a 
separate problem). Secondly, I'd like to simply disallow client commands 
that use the same mailbox name in two different source options. To handle 
the source options, it's necessary to build a hash table of mailbox names 
for duplicate elimination. But a source option like "IN (MAILBOXES foo 
subtree foo)" is annoying because the second "foo" can't be subject to 
duplicate elimination until after the subtree is expanded. So that means 
extra server code is needed to handle a special-case that no client ever 
needs to issue. So it's a minor tweak to simplify server implementations.

All the other issues I had were implementation issues, not protocol issues.

> FYI If I were still working on my client, I would be keen to see
> MULTISEARCH supported since it did the equivalent using select/search
> across multiple mailboxes to get results. It would definitely benefitted
> from MULTISEARCH.

Thank you for saying that. I do think evidence of community interest in a 
protocol is a criteria that should be considered for moving to standards 
track. This statement counts to me as additional evidence.

		- Chris


From nobody Thu Mar  6 11:59:35 2014
Return-Path: <chris.newman@oracle.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0FE91A018D for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 11:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level: 
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkD9gtCGGkYa for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 11:59:31 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 329FB1A0177 for <imapext@ietf.org>; Thu,  6 Mar 2014 11:59:31 -0800 (PST)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s26JxKEN019549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Mar 2014 19:59:21 GMT
Received: from gotmail.us.oracle.com (gotmail.us.oracle.com [10.133.152.174]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s26JxJ7n004970; Thu, 6 Mar 2014 19:59:19 GMT
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [10.175.34.52] (dhcp-uk-twvpn-2-vpnpool-10-175-54-176.vpn.oracle.com.175.10.in-addr.arpa [10.175.54.176]) by gotmail.us.oracle.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built Jan 22 2014)) with ESMTPA id <0N2100A1F66RM100@gotmail.us.oracle.com>; Thu, 06 Mar 2014 11:59:18 -0800 (PST)
Date: Thu, 06 Mar 2014 19:59:14 +0000
From: Chris Newman <chris.newman@oracle.com>
To: Cyrus Daboo <cyrus@daboo.name>, Barry Leiba <barryleiba@computer.org>
Message-id: <D420022D9B1DF151DF2697F9@96B2F16665FF96BAE59E9B90>
In-reply-to: <074B475021C23745B3795CFD@caldav.corp.apple.com>
References: <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90> <92EB7004C315F1887BC4A858@caldav.corp.apple.com> <CAC4RtVAgNg0vf35JgJ+MqbCNE3UMjQ3MUt9bC1yKBg559qM_Nw@mail.gmail.com> <8C172B0F6A5AC4B62F5C66A3@caldav.corp.apple.com> <074B475021C23745B3795CFD@caldav.corp.apple.com>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/Ri2OFErWQbS9qH6Iy5xhPaCDBkM
Cc: imapext@ietf.org
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 19:59:33 -0000

--On March 6, 2014 12:16:34 -0500 Cyrus Daboo <cyrus@daboo.name> wrote:
> Hi Barry,
>
> --On March 6, 2014 at 12:12:07 PM -0500 Cyrus Daboo <cyrus@daboo.name>
> wrote:
>
>>> 2. We have changed the target status of this from standards track to
>>> experimental.  We think there isn't strong enough consensus to go for
>>> standards track, given the possible interactions with other
>>> extensions.
>>
>> At the very least we need to address that point before we should change
>> the status. And I do think that means actually having people implement it
>> and see what those possible problems might be, and then report back.
>
> I note the new spec does state:
>
>>    This extension was previously published as experimental.  There is
>>    now implementation experience, giving confidence in the protocol, so
>>    this document puts the extension on the Standards Track, with some
>>    minor updates that were informed by the implementation experience.
>
> I guess I am just asking for confirmation of that.

Fair enough.

The problematic protocol interactions are with UPDATE and reuse search 
result (SAVE). After implementing I can verify that the document's approach 
to that was correct -- it limited those to the selected mailbox only. I 
encountered several complex issues implementing multisearch but they were 
not protocol issues. As far as I know we implement all the ESEARCH return 
options and I didn't have problems with the others.

I can also confirm that the source options model worked. I like it much 
better than the LIST wildcard model. The duplicate elimination was a bit 
annoying, but less annoying than multiple wildcards would be. I actually 
suspect most client use will be IN (personal) or IN (personal subscribed) 
and the latter does require duplicate elimination.

There were a lot of implementation subtleties, but they were not related to 
the protocol. Perhaps it would be helpful to mention the interaction 
between IMAP "INBOX" being case-insensitive and the duplicate elimination 
requirement, as that's an implementation detail that's impacted by the base 
spec's interaction with this.

I don't think the inboxes source option is useful. If a server implements 
sieve fileinto and variables, then inboxes is a synonym for personal. But 
synonyms are easy to implement and keeping it consistent with RFC 5465 is 
good.

I mentioned my suggested changes in a previous email.

		- Chris


From nobody Thu Mar  6 12:54:07 2014
Return-Path: <adrien@qbik.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A14D1A0039 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 12:54:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lsgn13LOblSy for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 12:54:01 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [210.55.214.35]) by ietfa.amsl.com (Postfix) with ESMTP id 759BF1A002B for <imapext@ietf.org>; Thu,  6 Mar 2014 12:54:01 -0800 (PST)
Received: From [192.168.0.38] (unverified [192.168.0.38]) by SMTP Server [192.168.0.1] (WinGate SMTP Receiver v8.1.0 (Build 4653)) with SMTP id <0019972155@smtp.qbik.com>; Fri, 07 Mar 2014 09:53:54 +1300
From: "Adrien de Croy" <adrien@qbik.com>
To: "Cyrus Daboo" <cyrus@daboo.name>, "imapext@ietf.org" <imapext@ietf.org>
Date: Thu, 06 Mar 2014 20:53:54 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format=flowed; charset=utf-8
In-Reply-To: <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com>
Message-Id: <em931c08fa-9a6d-4138-8c1d-e388aa2ff374@bodybag>
Mime-Version: 1.0
User-Agent: eM_Client/6.0.19861.0
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/pl0NGB9JCtZlw3G76UjqejrLFSY
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Adrien de Croy <adrien@qbik.com>
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 20:54:04 -0000

------ Original Message ------
From: "Cyrus Daboo" <cyrus@daboo.name>
>
>On Bron's point - yes what is really needed is an extension that does=20
>away with the single selected mailbox model and allows searching,=20
>sorting, sync'ing, message access across all mailboxes all the time.
+100

actually I did some work on this approach about 9 years ago.  Just an=20
extension (which I called "UNSELECTED"), which once you enter that mode,=
=20
all msgids and UIDs in requests and responses become fully qualified -=20
e.g. include the mailbox name.

I think in practise it would actually be very simple for servers to do,=20
and allow notifications of changes to any message anywhere.  This would=20
solve numerous problems relating to multiple clients accessing the same=20
account with many folders filtering mail.  It would also make=20
server-based filtering a lot more workable.

Currently I now only run 1 copy of mail that does any filtering (my work=
=20
desktop), and remote desktop to that computer to do mail (other than iOS=
=20
client which I don't use much to send, and don't use for filtering). =20
This was because I have over 600 folders, and if one client filtered=20
something, and the other didn't see it, it was effectively deleted to=20
all intents and purposes - gone and unfindable to the client that didn't=
=20
do the filtering.

Adrien


>
>-- Cyrus Daboo
>
>_______________________________________________
>imapext mailing list
>imapext@ietf.org
>https://www.ietf.org/mailman/listinfo/imapext


From nobody Thu Mar  6 13:36:37 2014
Return-Path: <tss@iki.fi>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B37771A00CA for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 13:36:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nuobGn82Cgbn for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 13:36:33 -0800 (PST)
Received: from wursti.dovecot.fi (wursti.dovecot.fi [87.106.245.223]) by ietfa.amsl.com (Postfix) with ESMTP id 4286B1A00E8 for <imapext@ietf.org>; Thu,  6 Mar 2014 13:36:33 -0800 (PST)
Received: from [192.168.10.106] (cs181255018.pp.htv.fi [82.181.255.18]) by wursti.dovecot.fi (Postfix) with ESMTPSA id DF71221AFD; Thu,  6 Mar 2014 22:36:25 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Timo Sirainen <tss@iki.fi>
In-Reply-To: <9a717e2c-a82f-462e-859a-e30057bc4bc6@gulbrandsen.priv.no>
Date: Thu, 6 Mar 2014 23:36:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <298C8F30-AB7A-462C-A1B4-5A861B7E973E@iki.fi>
References: <DB4BDD8D-FDEA-4014-B3B7-5040A1EE97A2@iki.fi> <9a717e2c-a82f-462e-859a-e30057bc4bc6@gulbrandsen.priv.no>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/p10HmNijF2NWOtJ_3UjC6RdxO2s
Cc: imapext@ietf.org
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 21:36:36 -0000

On 6.3.2014, at 19.45, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> =
wrote:

> On Thursday, March 6, 2014 6:12:19 PM CEST, Timo Sirainen wrote:
>> So I'm not really interested in implementing it. Adding some =
standardization for the \All mailbox would be useful though.
>=20
> Such as? We do have special-use to declare \all, what more do you =
want?

1) The \All mailbox isn't necessarily visible. GMail makes it visible, =
but I think it still causes problems with some clients, so in most =
Dovecot installations that use it it's not visible. I'm not sure if =
there's any nice way to fix this though. Maybe adding it as part of the =
capability, such as VIRTUAL=3DVirtualHidden/ (to support not just \All =
but other virtual mailboxes).

2) After virtual mailbox is already selected, ability to SEARCH messages =
by their original mailbox name. Dovecot currently uses X-MAILBOX that =
supports LIST wildcards, but MULTISEARCH's IN parameter would work just =
as well.

3) Ability to FETCH the original mail's mailbox name and UID.

> I'd like to have something like X-GM-MSGID (and X-GM-THRID is great =
too).

Yeah, those would be nice. Also the mailbox GUID if server supports =
those.


From nobody Thu Mar  6 16:19:04 2014
Return-Path: <brong@fastmail.fm>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B02991A00F1 for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 16:19:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7A41dSBynZC for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 16:18:59 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id ADEFB1A014E for <imapext@ietf.org>; Thu,  6 Mar 2014 16:18:59 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 46B0920C07 for <imapext@ietf.org>; Thu,  6 Mar 2014 19:18:55 -0500 (EST)
Received: from web2 ([10.202.2.212]) by compute3.internal (MEProxy); Thu, 06 Mar 2014 19:18:55 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:in-reply-to:references:subject:date; s=mesmtp; bh= tr+5Ff7OqIU2K9YvINZMf9Oa4G0=; b=akDdQzPQQk2kysmVSfhD2eYHzIJmmZns dVza6jGoCw4z5fanf9fKmwdw7Ek+0vdpCEOrmU5VNqoG0bglI4ML/xmb61KWDOlU 1T4WQ/+4cA81YzdO4MFw7BxwwuEfA4RQDVCmQxGMVHmGYVj+um8dKT13FUDNXnoH tfk1LqfTv64=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=tr+5Ff7OqIU2K9YvINZMf9Oa4G0=; b=dDe pNQjiuvB1fwmgClXxngLI2GUmS4bhuu+3yPkR+7vQJqcRzqBERrt3AOZ+lNUZsFD 7sAqHkikMu4HWl0FXkBGQ13HINkj1YZVJNigH0LppMklXO5+DbpIkCKpcpe96hUq cs6yfLfE/rCOnWaqewx+sqwnCXR9aN4I2k3eIXoM=
Received: by web2.nyi.mail.srv.osa (Postfix, from userid 99) id 29ADB5400D3; Thu,  6 Mar 2014 19:18:55 -0500 (EST)
Message-Id: <1394151535.11608.91550173.28801BBD@webmail.messagingengine.com>
X-Sasl-Enc: naPNn16+OIGQKTyF3JlRyw3NhlxBQXCkWRBZRWtZnwz4 1394151535
From: Bron Gondwana <brong@fastmail.fm>
To: imapext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-4527a23f
In-Reply-To: <298C8F30-AB7A-462C-A1B4-5A861B7E973E@iki.fi>
References: <DB4BDD8D-FDEA-4014-B3B7-5040A1EE97A2@iki.fi> <9a717e2c-a82f-462e-859a-e30057bc4bc6@gulbrandsen.priv.no> <298C8F30-AB7A-462C-A1B4-5A861B7E973E@iki.fi>
Date: Fri, 07 Mar 2014 11:18:55 +1100
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/MR7l8YfSg7H3bpLJkpNmS9icxv0
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Mar 2014 00:19:01 -0000

On Fri, Mar 7, 2014, at 08:36 AM, Timo Sirainen wrote:
> > I'd like to have something like X-GM-MSGID (and X-GM-THRID is great too).
> 
> Yeah, those would be nice. Also the mailbox GUID if server supports those.

At the moment we call these DIGEST.SHA1 (the implementation is in the name,
kind of ugly.  It used to be called GUID, and it still is internally),
CID (conversation ID) and we expose the mailbox GUID as a metadata item called
/shared/vendor/cmu/cyrus-imapd/uniqueid (that bit has been upstream for ages)

All these concepts are useful - particularly X-GM-MSGID, which lets a client
discover that a different client has moved thousands of messages between folders
without re-downloading all their contents or making guesses based on message size
and the unfortunately unreliable-in-the-real-world 'Message-Id' header.

Bron.

-- 
  Bron Gondwana
  brong@fastmail.fm


From nobody Thu Mar  6 16:37:59 2014
Return-Path: <brong@fastmail.fm>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BFC01A014E for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 16:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F3mCJbSooulA for <imapext@ietfa.amsl.com>; Thu,  6 Mar 2014 16:37:53 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id AA8EF1A001D for <imapext@ietf.org>; Thu,  6 Mar 2014 16:37:53 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 90F6220A78 for <imapext@ietf.org>; Thu,  6 Mar 2014 19:37:49 -0500 (EST)
Received: from web2 ([10.202.2.212]) by compute3.internal (MEProxy); Thu, 06 Mar 2014 19:37:49 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:in-reply-to:references:subject:date; s=mesmtp; bh= XpM+4XcXCVkcY0u1XlSWCRJ7xPw=; b=A1dkJBlhcIODWmzueoROfXebxdGtNVux Mkp7R71Cp5BadVau5p9VfqmtdzQJ1o09Ymh95tesfbTbK1NwSZ9DChlqz7bh9E/b woa0k+48qWam8GPgu+MVAy1tgwDeTgzsmf/xQmbETIbrV2MSvTbkRpo3ls1iuykz 8NbeDrgr9v8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=XpM+4XcXCVkcY0u1XlSWCRJ7xPw=; b=IsC NPMtzax32auVK6OHD+1J8IIdt7JQ7U8Xjnm3nOFJdgVBVwIDXw8y8jKsWPBN9tvD fpwLu+QtMe+p3WL0LFMMHl3JWFr4BBTDjH9433OetaCDqUw6VkJAfGvLfTPnkc1c QQB+OJN/LyMx7/ETIPe4n7gG7tY/LfW1/2fykwRw=
Received: by web2.nyi.mail.srv.osa (Postfix, from userid 99) id 704B95400D3; Thu,  6 Mar 2014 19:37:49 -0500 (EST)
Message-Id: <1394152669.15703.91551029.06D49A6D@webmail.messagingengine.com>
X-Sasl-Enc: xMNjyPXvf9zkoTw/jrbRR0jlPDDZCcluZ8fAMF6rGxVy 1394152669
From: Bron Gondwana <brong@fastmail.fm>
To: imapext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-4527a23f
In-Reply-To: <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90>
References: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com> <1394103473.14059.91258445.054B3082@webmail.messagingengine.com> <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com> <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90>
Date: Fri, 07 Mar 2014 11:37:49 +1100
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/WeOxVHf5szGvl-yTfe-JrmTglFE
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Mar 2014 00:37:57 -0000

On Fri, Mar 7, 2014, at 03:29 AM, Chris Newman wrote:
> --On March 6, 2014 9:30:17 -0500 Cyrus Daboo <cyrus@daboo.name> wrote:
> > --On March 6, 2014 at 9:57:53 PM +1100 Bron Gondwana <brong@fastmail.fm=
>=20
> wrote:
> >> Anyway - my main problem with it is that users don't just want search -
> >> they want sort.  Running the search across multiple mailboxes means you
> >> still need to fetch all the data for all the matches before you can ge=
t a
> >> meaningful sort by any parameter other than mailbox name as the first
> >> sort index.  And that can be a lot of download to the client if you
> >> searched a common term.]
> >
> > On Bron's point - yes what is really needed is an extension that does
> > away with the single selected mailbox model and allows searching,
> > sorting, sync'ing, message access across all mailboxes all the time.
>=20
> I have no interest in implementing such an extension at this time. I'm=20
> going to assert there is not enough interest in such a proposal to get a=
=20
> specification written, thus making it not relevant to this discussion. If=
=20
> someone were to prove my assertion wrong, then we could have an interesti=
ng=20
> discussion about whether one or both proposals should go to standards tra=
ck.

You're asserting this based on your customer who you can't name - as opposed
to my customers who I (well, I can't really name the actual customers)... bu
the ability to sort by date overall rather than with each mailbox was a com=
monly
requested search feature at FastMail - and we now support it.

We definitely don't have anyone asking us to go back to sorting by mailbox
only - particularly since mailbox name is still a sort key that you can use
in your sort if you want to.

> For just searching, the current MULTISEARCH design has significant benefi=
ts=20
> for both client and server. It produces concise results (a UID set for ea=
ch=20
> mailbox rather than list of UIDs), and the straightforward implementation=
=20
> will return results as they are found on a per-mailbox basis in a way tha=
t=20
> clients can display the results as they are found. The straightforward=20
> implementation of MULTISORT/ALLMSGS has to compute all the results before=
=20
> sending anything to the client. There's value to having these be separate=
=20
> extensions even if sufficient interest to write a MULTISORT/ALLMSGS=20
> extension materializes in the future.

Our result set is still quite concise - though it's tuples:

3 xconvmultisort (reverse arrival) (conversations position (1 30)) utf-8 FU=
ZZY TEXT "chris.newman" not folder "Inbox.Trash" not folder "Inbox.Junk Mai=
l"
* XCONVMULTI (("INBOX" 1148523981) ("INBOX.Archive.Inbox-2011" 1298369152) =
("INBOX.Drafts" 1148523983) ("INBOX.Lists.Cyrus" 1193627117) ("INBOX.Lists.=
Imap5" 1217730348) ("INBOX.Lists.ImapExt" 1198790887) ("INBOX.Lists.fm-cvs"=
 1148523992) ("INBOX.Sent Items" 1148523995)) ((75e35b068901c51b (2 20195) =
(5 5210) (5 5209) (5 5207) (5 5206) (5 5205) (5 5203) (5 5202) (5 5201) (5 =
5199) (5 5198) (7 13690) (5 5197)) (22e8c6bc0c999471 (5 5106) (0 946541) (5=
 5104) (7 13234) (5 5102)) (35f42610ba6324f3 (5 5079)) (42599c237f434f9f (5=
 5078) (5 5077) (5 5076) (5 5074) (5 5073) (5 5072) (5 5071)) (94643209768b=
a85c (5 5070) (5 5069) (5 5068)) (a85bf44cea5ba267 (6 33423)) (8980e46f8cc9=
617e (6 33248)) (7bec218f48a35592 (6 30446)) (f6375654cf52cb5e (6 28692)) (=
0cc65f89dc003eb7 (7 9754)) (df7c52435658163e (1 5246) (1 4990) (1 4987) (1 =
4967)) (14744ad604794672 (1 3190) (4 201) (7 8057) (1 3183)) (77cb8893eeb61=
bb4 (3 13491)) (c613c22cd60fc734 (4 54) (4 53) (4 51) (4 47)) (cd0f24d8cd2d=
a0e3 (4 50) (4 49) (4 48) (4 46)) (8c1c6d50a25d7d75 (4 41)) (aa0a6113c53456=
ea (5 4315)) (da7343dea9a2dd92 (5 4308) (5 4303)) (7f0aa97dba576376 (5 4286=
)) (86631b9c7fd03ba8 (5 4269)) (1dc2b83458b9edb4 (5 4267)) (764d53b27438df5=
d (5 4261)) (4657718a320253b3 (5 1023)) (8216063d1d06d1a2 (5 3801) (5 1857)=
 (5 1649) (5 3605) (5 987) (5 1453) (5 2782) (5 3152) (5 622) (5 707) (5 25=
87) (5 2670) (5 427) (5 2393) (5 3273) (5 1109) (5 511) (5 1395) (5 3359) (=
5 1201) (5 3065) (5 897)) (885c99dc1324a315 (5 3977) (5 1218) (5 3172) (5 1=
006) (5 2960)) (86e821cd553f0665 (3 2228)) (40dec021413028d4 (5 4046)) (d2a=
6ca5cfc0cd33a (5 4098) (5 1939) (5 1280) (5 2153) (5 3885) (5 1726) (5 3542=
) (5 1389)) (5e0e810635ad3ebf (5 793) (5 1666) (5 3624) (5 1470)) (51cbbb00=
a51db66d (5 1383) (5 3348) (5 2384) (5 225) (5 1102) (5 3057) (5 672) (5 15=
58)))
* OK [POSITION 1]
* OK [HIGHESTMODSEQ 295339132831582]
* OK [TOTAL 109]
3 OK Completed (in 0.110 secs)

Which breaks down to:

a list of folder names and uidvalidities.

a list of the first 30 matching conversations, each of which is (CID (tuple=
) (tuple) ...)

each tuple is folder index (from the list above) and UID within that folder=
.  This is used to hilight the matching messages within the conversation wh=
en it is opened.

... and if you scroll past that first 30 item window, you can fetch more.  =
Obviously, there's no need to work in small windows - it's just an option t=
hat we use in our API to avoid getting unbounded amounts of data returned t=
o the client.

4 xconvmultisort (reverse arrival) (conversations multianchor (1383 Inbox.L=
ists.ImapExt 1 30)) utf-8 FUZZY TEXT "chris.newman" not folder "Inbox.Trash=
" not folder "Inbox.Junk Mail"
* XCONVMULTI (("INBOX" 1148523981) ("INBOX.Archive.Inbox-2011" 1298369152) =
("INBOX.Drafts" 1148523983) ("INBOX.Lists.Cyrus" 1193627117) ("INBOX.Lists.=
Imap5" 1217730348) ("INBOX.Lists.ImapExt" 1198790887) ("INBOX.Lists.fm-cvs"=
 1148523992) ("INBOX.Sent Items" 1148523995)) ((a7c22d265a01ae47 (5 1808) (=
5 2682)) (0e7f42859d14064b (5 522)) (18683122949a755f (5 2482)) (839b475574=
88a2f0 (5 2008) (5 2282) (5 111)) (17d7c11d5c313214 (5 3578) (5 650)) (ddf8=
dad81171c58f (5 4005)) (dd20935a4d7b2534 (5 1476)) (b4bbc805e5d88997 (5 811=
)) (d4b09f52f1551e51 (5 1955)) (9d1382e572868684 (5 4025) (5 1865)) (0285ab=
40d0125d6e (5 3534)) (b84d7c33ee0ce08b (5 2772) (5 612)) (2faf629f598823c9 =
(5 2873)) (16c0037968ce0d5d (5 1393) (5 3357)) (320995b4ec6d6c99 (5 1741)) =
(52f526d95c7a85f5 (5 1459) (5 3419)) (a45377efe133440c (5 3500)) (682cd6d68=
615f357 (5 1997)) (cd77fa3872d98167 (5 501) (5 2661) (5 2463) (5 302)) (f6f=
2cd14f1e19e6f (5 2926) (5 1190) (5 3141) (5 975) (5 753) (5 2121)) (f7ff660=
331ebbe9d (5 3053)) (d01b067ac95c0f9d (5 1696)) (24ce7fe1b6913094 (5 1621) =
(5 3577)) (5b5bbd4ce7ce019a (5 3497)) (472840f7906f56a2 (5 1136) (5 1797)) =
(aa51277478e5d2a2 (5 3002) (5 3866)) (dfcd789dbf52d20d (5 3745) (5 2070) (5=
 2728) (5 570) (5 2530)) (780c5432ead295aa (5 1710) (5 3665) (5 1512) (5 34=
69) (5 239)) (d9a39a69640a0151 (5 873)) (d70e71aab74630dd (5 2821)))
* OK [POSITION 31]
* OK [HIGHESTMODSEQ 295339132831585]
* OK [TOTAL 109]
4 OK Completed (in 0.070 secs)


... this is a search run on our production system against my folders, using=
 the xapian FUZZY indexed full-message search over what expands to about 6 =
different backend indexes spread over slow disk (compressed long-term index=
), slow disk (weekly compressed index), ssd (daily index updates) and final=
ly tmpfs (real-time indexing of new messages).

So this is working now... it's insanely non-standard, but it's a much nicer=
 user experience than the alternatives - including multisearch.

It gives me a list of conversations ordered by most recent message.

If you weren't doing conversations, the syntax would simplify to just a lis=
t of folder names that matched (with uidvalidity) and then a list of tuples=
 of (index uid) mapping into that folder listing.

Bron.

--=20
  Bron Gondwana
  brong@fastmail.fm


From nobody Fri Mar  7 00:21:46 2014
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 525A41A0101 for <imapext@ietfa.amsl.com>; Fri,  7 Mar 2014 00:21:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kEXgyHsXGOA6 for <imapext@ietfa.amsl.com>; Fri,  7 Mar 2014 00:21:43 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id A10441A0107 for <imapext@ietf.org>; Fri,  7 Mar 2014 00:21:38 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 3A6EFFA0065; Fri,  7 Mar 2014 08:21:33 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1394180492-20364-20364/11/1; Fri, 7 Mar 2014 08:21:32 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Fri, 7 Mar 2014 09:21:31 +0100
User-Agent: Trojita/v0.3.96-176-g713fcbb; Qt/4.8.4; X11; Linux; Ubuntu 13.10
Mime-Version: 1.0
Message-Id: <eb8a3f2d-c60d-49ab-a8cd-47e7d949f169@gulbrandsen.priv.no>
In-Reply-To: <298C8F30-AB7A-462C-A1B4-5A861B7E973E@iki.fi>
References: <DB4BDD8D-FDEA-4014-B3B7-5040A1EE97A2@iki.fi> <9a717e2c-a82f-462e-859a-e30057bc4bc6@gulbrandsen.priv.no> <298C8F30-AB7A-462C-A1B4-5A861B7E973E@iki.fi>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/BnpXT5vpuHTcgoPUEvBpbPmG0NY
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Mar 2014 08:21:45 -0000

On Thursday, March 6, 2014 10:36:23 PM CEST, Timo Sirainen wrote:
> 1) The \All mailbox isn't necessarily visible. GMail makes it 
> visible, but I think it still causes problems with some clients,

Clients that issue fetch 1:* for all mailboxes.

> I'm not sure if there's any nice way to fix this though.

1. I think there isn't. I know two non-nice ways. I think I'd rather just 
be blunt about it in the document. "If you try to download all the mail, 
you should be aware that about 5% have more than 2GB and 0.01% of users 
have more than 20GB. The percentages are likely higher among those who use 
this extension." (Those numbers are just informed guesses, though.)

2. This is an intrinsic problem, not a feature of \all. If you allow 
clients a way to fetch everything, any way, ones that do fetch everything 
will have problems.

>> I'd like to have something like X-GM-MSGID (and X-GM-THRID is great 
too).
>
> Yeah, those would be nice. Also the mailbox GUID if server supports 
those.

Indeed.

Arnt


From nobody Fri Mar  7 13:46:23 2014
Return-Path: <ned.freed@mrochek.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1892A1A0114 for <imapext@ietfa.amsl.com>; Fri,  7 Mar 2014 13:46:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZ_flNNSuhGo for <imapext@ietfa.amsl.com>; Fri,  7 Mar 2014 13:46:21 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id E5D661A0111 for <imapext@ietf.org>; Fri,  7 Mar 2014 13:46:20 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P55WTX1Q9C001389@mauve.mrochek.com> for imapext@ietf.org; Fri, 7 Mar 2014 13:41:14 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; Format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P54UCTNK9C00004W@mauve.mrochek.com>; Fri, 7 Mar 2014 13:41:11 -0800 (PST)
Message-id: <01P55WTVNHXK00004W@mauve.mrochek.com>
Date: Fri, 07 Mar 2014 13:23:24 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Thu, 06 Mar 2014 15:36:33 +0100" <b5d0bbd9-ffa7-4a2c-b0de-075e03694adf@gulbrandsen.priv.no>
References: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com> <1394103473.14059.91258445.054B3082@webmail.messagingengine.com> <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com> <b5d0bbd9-ffa7-4a2c-b0de-075e03694adf@gulbrandsen.priv.no>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/029hfrL9Sq0uySEMr-uYgZAUDWg
Cc: Cyrus Daboo <cyrus@daboo.name>, imapext@ietf.org
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Mar 2014 21:46:22 -0000

> On Thursday, March 6, 2014 3:30:17 PM CEST, Cyrus Daboo wrote:
> > If sufficient servers AND clients have bothered to implement
> > multimailbox-search and they have proven to be interoperable
> > then I see no objection to moving to standards track (i.e, the
> > experiment was a success so lets move forward) - but can we see
> > evidence of that first?

> Uh. What are some clients that have done this?

> AFAICT, gmail's way (an "all mail" mailbox) has won in practice, despite
> its problems.

I have to say I find this entire conversation to be confusing in the extreme.

We have an experimental RFC, implementation evidence that it qualifies for
standards track status, and a desire for it to have that status.

And the argument against is that there are at least two other ways to do it,
neither of which, AFAICT, is specified anywhere. And if someone has volunteered
to write up either alternative and see it through the standards process, I
missed seeing that offer. (*)

So we're left with something clients have a real need to do, an experimental
specification that provides one way to do it, a willingness to move it to
standards track, and a bunch of ad-hoc deployment. And the response seems to be
to oppose doing anything?

				Ned

(*) And before anyone says that the \All business is "obvious", there have
already been messages in this thread pointing out that it really isn't. And
even if it requires no protocol changes whatsoever, the model needs to be
documented.


From nobody Fri Mar  7 13:54:49 2014
Return-Path: <cyrus@daboo.name>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C52771A0150 for <imapext@ietfa.amsl.com>; Fri,  7 Mar 2014 13:54:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ejZSBE0ne-H8 for <imapext@ietfa.amsl.com>; Fri,  7 Mar 2014 13:54:46 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5CD021A0114 for <imapext@ietf.org>; Fri,  7 Mar 2014 13:54:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id A83A55EC66B1; Fri,  7 Mar 2014 16:54:44 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hcEBR-nWrn6q; Fri,  7 Mar 2014 16:54:44 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 2AF8E5EC66A5; Fri,  7 Mar 2014 16:54:42 -0500 (EST)
Date: Fri, 07 Mar 2014 16:54:08 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Ned Freed <ned.freed@mrochek.com>, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Message-ID: <C58F957337830EBD6784582C@caldav.corp.apple.com>
In-Reply-To: <01P55WTVNHXK00004W@mauve.mrochek.com>
References: <01P55WTVNHXK00004W@mauve.mrochek.com>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1080
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/aX7jBbuxdmr4CG89OK1wBgTG1Ro
Cc: imapext@ietf.org
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Mar 2014 21:54:48 -0000

Hi Ned,

--On March 7, 2014 at 1:23:24 PM -0800 Ned Freed <ned.freed@mrochek.com> 
wrote:

> We have an experimental RFC, implementation evidence that it qualifies for
> standards track status, and a desire for it to have that status.
>
> And the argument against is that there are at least two other ways to do
> it,
> neither of which, AFAICT, is specified anywhere. And if someone has
> volunteered
> to write up either alternative and see it through the standards process, I
> missed seeing that offer. (*)

To clarify my position - whilst I advocated for a more generic "get to all 
mailboxes" extension, I do not want that to be an argument against 
multimailbox search which, as I have said, I consider beneficial. And 
frankly, I do not believe we will ever get the more generic extension 
anyway, and certainly don't have the time or inclination to work on it.

At this point I am satisfied with Chris' technical commentary on 
implementation of multimailbox search. I would still like to hear from 
others, but I have no objection to upping the status.

-- 
Cyrus Daboo


From nobody Fri Mar  7 14:22:27 2014
Return-Path: <ned.freed@mrochek.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E22991A02DE for <imapext@ietfa.amsl.com>; Fri,  7 Mar 2014 14:22:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w6rxv8ic8oJo for <imapext@ietfa.amsl.com>; Fri,  7 Mar 2014 14:22:20 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 444AE1A02E0 for <imapext@ietf.org>; Fri,  7 Mar 2014 14:22:20 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P55Y3IIDSG001DJO@mauve.mrochek.com> for imapext@ietf.org; Fri, 7 Mar 2014 14:17:13 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; Format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P54UCTNK9C00004W@mauve.mrochek.com>; Fri, 7 Mar 2014 14:17:10 -0800 (PST)
Message-id: <01P55Y3GSK8400004W@mauve.mrochek.com>
Date: Fri, 07 Mar 2014 14:16:36 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Fri, 07 Mar 2014 16:54:08 -0500" <C58F957337830EBD6784582C@caldav.corp.apple.com>
References: <01P55WTVNHXK00004W@mauve.mrochek.com> <C58F957337830EBD6784582C@caldav.corp.apple.com>
To: Cyrus Daboo <cyrus@daboo.name>
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/oylf31O8jnUvLVf943BZbWazZYA
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, Ned Freed <ned.freed@mrochek.com>, imapext@ietf.org
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Mar 2014 22:22:23 -0000

> Hi Ned,

> --On March 7, 2014 at 1:23:24 PM -0800 Ned Freed <ned.freed@mrochek.com>
> wrote:

> > We have an experimental RFC, implementation evidence that it qualifies for
> > standards track status, and a desire for it to have that status.
> >
> > And the argument against is that there are at least two other ways to do
> > it,
> > neither of which, AFAICT, is specified anywhere. And if someone has
> > volunteered
> > to write up either alternative and see it through the standards process, I
> > missed seeing that offer. (*)

> To clarify my position - whilst I advocated for a more generic "get to all
> mailboxes" extension, I do not want that to be an argument against
> multimailbox search which, as I have said, I consider beneficial. And
> frankly, I do not believe we will ever get the more generic extension
> anyway, and certainly don't have the time or inclination to work on it.

> At this point I am satisfied with Chris' technical commentary on
> implementation of multimailbox search. I would still like to hear from
> others, but I have no objection to upping the status.

OK, this makes perfect sense to me. Apologies for any misinterprtation I
made of your position in my original message.

				Ned


From nobody Sat Mar  8 00:16:24 2014
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4430E1A01B5 for <imapext@ietfa.amsl.com>; Sat,  8 Mar 2014 00:16:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PWepqrbopEWz for <imapext@ietfa.amsl.com>; Sat,  8 Mar 2014 00:16:19 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id 43EDC1A00BD for <imapext@ietf.org>; Sat,  8 Mar 2014 00:16:19 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 85DD4FA00A6; Sat,  8 Mar 2014 08:16:13 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1394266572-13710-13710/11/1; Sat, 8 Mar 2014 08:16:12 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Sat, 8 Mar 2014 09:16:11 +0100
User-Agent: Trojita/v0.3.96-176-g713fcbb; Qt/4.8.4; X11; Linux; Ubuntu 13.10
Mime-Version: 1.0
Message-Id: <00394695-160d-43b5-9c68-b7e385d26265@gulbrandsen.priv.no>
In-Reply-To: <01P55WTVNHXK00004W@mauve.mrochek.com>
References: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com> <1394103473.14059.91258445.054B3082@webmail.messagingengine.com> <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com> <b5d0bbd9-ffa7-4a2c-b0de-075e03694adf@gulbrandsen.priv.no> <01P55WTVNHXK00004W@mauve.mrochek.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/D1Ick8Avv9Yo5UuUS0pJ3i08WVM
Subject: Re: [imapext] draft-ietf-appsawg-multimailbox-search
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Mar 2014 08:16:21 -0000

Personally speaking, I'm not opposed to advancing multimailbox search. I 
think it's a little bit pointless since dovecot and gmail dominate the 
landscape and both already support \all. But if you want to do it, go 
ahead.

Arnt


From nobody Mon Mar 10 20:43:34 2014
Return-Path: <chris.newman@oracle.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B261A06F8 for <imapext@ietfa.amsl.com>; Mon, 10 Mar 2014 20:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.205
X-Spam-Level: 
X-Spam-Status: No, score=-3.205 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BvpJ5wNZ2EjT for <imapext@ietfa.amsl.com>; Mon, 10 Mar 2014 20:43:29 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 970C51A06F3 for <imapext@ietf.org>; Mon, 10 Mar 2014 20:43:29 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s2B3hHxk023365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Mar 2014 03:43:18 GMT
Received: from gotmail.us.oracle.com (gotmail.us.oracle.com [10.133.152.174]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s2B3hFTs019406; Tue, 11 Mar 2014 03:43:17 GMT
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [10.159.234.198] (dhcp-whq-twvpn-3-vpnpool-10-159-234-198.vpn.oracle.com [10.159.234.198]) by gotmail.us.oracle.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built Jan 22 2014)) with ESMTPA id <0N290013W6BZKC00@gotmail.us.oracle.com>; Mon, 10 Mar 2014 20:43:13 -0700 (PDT)
Date: Mon, 10 Mar 2014 20:43:11 +0000
From: Chris Newman <chris.newman@oracle.com>
To: Bron Gondwana <brong@fastmail.fm>, imapext@ietf.org
Message-id: <F3D5C85995CEFDDB8D22F0A6@96B2F16665FF96BAE59E9B90>
In-reply-to: <1394152669.15703.91551029.06D49A6D@webmail.messagingengine.com>
References: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com> <1394103473.14059.91258445.054B3082@webmail.messagingengine.com> <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com> <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90> <1394152669.15703.91551029.06D49A6D@webmail.messagingengine.com>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/2f9cdD_zDg-Ph_1cHvvUY5NXvKQ
Subject: [imapext] multisort proposals (was Re: draft-ietf-appsawg-multimailbox-search)
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Mar 2014 03:43:31 -0000

It sounds like IMAP cross-folder sort is a big non-interoperable mess right 
now due to lack of standardization.

Have any of you considered writing a specification of your multisort 
protocol? Or maybe arrange a phone call between proponents of the 
"xconvmultisort" proposal, the "X-MAILBOX, X-REAL-UID" and the "\all" 
proposals to see if consensus on a standard approach is possible?

Standards have several benefits for the vendors who participate:

1. If you have an early implementation, that's a key marketing/selling 
point.

2. It gives your customers more choice of the other side when they choose 
your product. (more client options if you're a server vendor, or vice-versa 
if you're a client vendor).

3. It improves your reputation. It shows you care about the future of your 
customers and the future of the Internet.

4. It raises the innovation baseline. Once a standard is written and 
successful, it becomes "common practice" over time. Then there's no more 
need to proselytize that standard, new innovation can start with that 
standard as a baseline.

5. Once a standard is approved, you're much less likely to have to waste 
time and effort implementing two or more ways of doing the same thing to 
interoperate with different implementations.

6. It's one way a smaller vendor can get a leg-up on a bigger vendor who 
ignores standards.

While private IMAP extensions are fine for experiments, they're an 
interoperability problem when more than one for the same purpose show up. 
Why not take the time to write and progress a protocol specification so you 
and your customers reap the benefits and the community's innovation 
baseline is raised?

		- Chris


From nobody Tue Mar 18 19:51:10 2014
Return-Path: <brong@fastmail.fm>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30CFF1A0338 for <imapext@ietfa.amsl.com>; Tue, 18 Mar 2014 19:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TgnxI46fQcEa for <imapext@ietfa.amsl.com>; Tue, 18 Mar 2014 19:51:06 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 0E41D1A0343 for <imapext@ietf.org>; Tue, 18 Mar 2014 19:51:05 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 1789020C05 for <imapext@ietf.org>; Tue, 18 Mar 2014 22:50:55 -0400 (EDT)
Received: from web6 ([10.202.2.216]) by compute5.internal (MEProxy); Tue, 18 Mar 2014 22:50:55 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:subject:date:in-reply-to:references; s=mesmtp; bh= E8TMhx7LmySO2Tcgqpc7pjQSVb4=; b=ZXjkFfSNITq8izhzEML4oRghDcxexTqP 7HndoKpDNLZ3Y0UogMdbY2V0tYwjbuvJcaSoVAwY0nXNEtrggxTpnYhLtJXVZupQ e/juX8UMAr1pEADJpDg7ivute4cegc0eQd32OvJ9MxGBcF8lQmMXkzvNVmXfHG1r V7NMb2RiDk4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=E8TMhx7LmySO2Tcgqpc7pjQSVb4=; b=uJ9xn iCt5sYOHtmySgCTSstFuUp7koQ19MWyySFe+aWpJQu5j/YPbooqlI5iiAh+RFbAi wJZtZ8sFy6tH8fbQqa77nHT1aisq0SksnPEeJ0uK9cXctcZD0cvRqJxebDcI84Yw jNa6w+MlFHy3cOcdVl4KcCbH7YcV1OMh00VOWo=
Received: by web6.nyi.mail.srv.osa (Postfix, from userid 99) id DFD3F2834E3; Tue, 18 Mar 2014 22:50:54 -0400 (EDT)
Message-Id: <1395197454.14596.96179945.074A46ED@webmail.messagingengine.com>
X-Sasl-Enc: l6gNLngvfHm6KIPj3idPAujCWDiWfKKLNuMcjD8VTnOr 1395197454
From: Bron Gondwana <brong@fastmail.fm>
To: imapext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-6e382e84
Date: Wed, 19 Mar 2014 13:50:54 +1100
In-Reply-To: <F3D5C85995CEFDDB8D22F0A6@96B2F16665FF96BAE59E9B90>
References: <CAC4RtVCgLuvpAqEs6Nzz+358dvg4q2YkBNmeq39SYFmnYOLoKw@mail.gmail.com> <1394103473.14059.91258445.054B3082@webmail.messagingengine.com> <06B38F8D7C86FDF50230A07E@caldav.corp.apple.com> <5B508A7BE305AE6FA48093DB@96B2F16665FF96BAE59E9B90> <1394152669.15703.91551029.06D49A6D@webmail.messagingengine.com> <F3D5C85995CEFDDB8D22F0A6@96B2F16665FF96BAE59E9B90>
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/0XNTSWMSh-u0IeD3WxECS8hG0vI
Subject: Re: [imapext] multisort proposals (was Re: draft-ietf-appsawg-multimailbox-search)
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Mar 2014 02:51:09 -0000

On Tue, Mar 11, 2014, at 07:43 AM, Chris Newman wrote:
> It sounds like IMAP cross-folder sort is a big non-interoperable mess
> right now due to lack of standardization.
>
> Have any of you considered writing a specification of your multisort
> protocol? Or maybe arrange a phone call between proponents of the
> "xconvmultisort" proposal, the "X-MAILBOX, X-REAL-UID" and the "\all"
> proposals to see if consensus on a standard approach is possible?

Apologies for the late reply on this - I've been busy dealing with a
nasty server partial-failure which led to corruption, and the associated
cleanup and recovery.  The "joy" of devops.

> Standards have several benefits for the vendors who participate:
>
> 1. If you have an early implementation, that's a key marketing/selling
>    point.
>
> 2. It gives your customers more choice of the other side when they
>    choose your product. (more client options if you're a server
>    vendor, or vice-versa if you're a client vendor).
>
> 3. It improves your reputation. It shows you care about the future of
>    your customers and the future of the Internet.
>
> 4. It raises the innovation baseline. Once a standard is written and
>    successful, it becomes "common practice" over time. Then there's no
>    more need to proselytize that standard, new innovation can start
>    with that standard as a baseline.
>
> 5. Once a standard is approved, you're much less likely to have to
>    waste time and effort implementing two or more ways of doing the
>    same thing to interoperate with different implementations.
>
> 6. It's one way a smaller vendor can get a leg-up on a bigger vendor
>    who ignores standards.
>
> While private IMAP extensions are fine for experiments, they're an
> interoperability problem when more than one for the same purpose show
> up. Why not take the time to write and progress a protocol
> specification so you and your customers reap the benefits and the
> community's innovation baseline is raised?

We have indeed.  Greg Banks (who doesn't work at FastMail any more, but
wrote the initial conversations support) did some initial work towards a
standards proposal for our conversations.  It was paused mainly because
we wanted to iron out the issues which would become obvious with real-
world usage first.

We have also done some work towards a more general mail access protocol
over HTTP, which is shared at http://jmap.io/

My general guiding principle is that the client should be describing
what it wants as clearly as possible, and the language of the protocol
needs to have the facility for it to do so.

The secondary principle is that the server should never do work that the
client has not explicitly requested.

This means that MSGNO by default is out, because that's an MVCC snapshot
of mailbox data.  It's an ordering that existed at a point in time, and
needs to be maintained by the server for an unbounded length of time.
The client can issue commands every 29 minutes which are chosen to not
allow EXPUNGE notifications - and the server can't forget those messages
until the mailbox is unselected.

Also, UNSEEN and RECENT have costs to calculate which aren't required by
many clients.

One thing that really frustrates me is optimisation hacks encoded in the
standard and guidance.  Things like "do a listing with %, then recurse
into each sub mailbox".  It might be more efficient when you're talking
to a server which is storing the folders in a filesystem and doing the
moral equivalent of 'ls' on each directory.

It's significantly less efficient with Cyrus, where the mailboxes database
is quite efficient to iterate in mailbox order (including sub-folders).
You're basically inspecting the sub-folders anyway - at least until you
can generate the \HasChildren or otherwise.

Generally, I would like the client to be able to say "I want the full
folder tree thanks, but limit it to the first 1000 items".

So my ideal protocol for a X-MULTISEARCH would smell a bit more like SQL
I suspect.  The offset / limit or anchor / limit syntaxes are both very
useful ways of describing exactly what you want to the server.

------

It would also be really great to merge the X-GM-MSGID and similar tricks
that various sites are using to uniquely identify messages across copy/move
operations that were performed by a DIFFERENT client.

APPENDUID is all very nice if you're using the client which did the COPY,
but it falls down if a different client did the copy - you wind up having
to fetch the entire message again if you don't trust the BODYSTRUCTURE and
ENVELOPE to uniquely identify the message enough - and most clients don't
due to the fact that Message-Id isn't 100% reliable in this broken age :(

I think those are the two areas.  I've said before that I'm willing to put
the time in to do this - and you're right - I really should stop talking
and start producing!

------

One final thing that we have found insanely useful in Cyrus replication:
checksums all over the place.  This is not so much useful to a traditional
"partial view" client, but many clients seem to synchronise the entire
contents of a mailbox, and a CRC would have value there.

The issue that's kept me from having time to reply for the past week is
documented here:

http://blog.fastmail.fm/2014/03/13/cleaning-up-from-an-imap-server-failure/

Having the sha1 of the spool files in our logs enabled data recovery in a
way that would have otherwise been impossible on an untrusted filesystem.
We could be sure that the emails we recovered were not corrupted.

Having a strong digest available for every message on the server would also
allow clients to consistency-check their local cache without resyncing all
the data.  I used to think that being able to detect mailbox renames that
you didn't do with this client was important (right now if another client
renames a folder, your client needs to fetch all the messages again for
the same reason as message copies) - but I think re-fetching just the flags/
annotations/digest isn't too expensive if you can re-use the cached message
contents.

Bron.


-- 
  Bron Gondwana
  brong@fastmail.fm

