
From nobody Mon Dec  1 22:39:21 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 E298A1A00EB for <imapext@ietfa.amsl.com>; Mon,  1 Dec 2014 22:39:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.279
X-Spam-Level: 
X-Spam-Status: No, score=0.279 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_NEUTRAL=0.779] 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 iOM1VQbUMmxz for <imapext@ietfa.amsl.com>; Mon,  1 Dec 2014 22:39:18 -0800 (PST)
Received: from wursti.dovecot.fi (wursti.dovecot.fi [87.106.245.223]) by ietfa.amsl.com (Postfix) with ESMTP id 438051A0055 for <imapext@ietf.org>; Mon,  1 Dec 2014 22:39:18 -0800 (PST)
Received: from [192.168.2.5] (c-24-6-218-211.hsd1.ca.comcast.net [24.6.218.211]) by wursti.dovecot.fi (Postfix) with ESMTPSA id 7506422577 for <imapext@ietf.org>; Tue,  2 Dec 2014 07:39:16 +0100 (CET)
From: Timo Sirainen <tss@iki.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi>
Date: Mon, 1 Dec 2014 22:39:13 -0800
To: "imapext@ietf.org" <imapext@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/HB0byDrQ_XGFKmWmCm54G0DM0xQ
Subject: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 06:39:20 -0000

Nowadays many mail clients want to show about 100 chars of the beginning =
of mail, so there should be a nice and efficient way for clients to =
request this. I'm now wondering what would be a nice IMAP way of =
implementing this. Does anyone have some suggestions? There's what I've =
come up with so far:

a) FETCH n (SNIPPET)
 - Would require writing a new RFC (or just use X-SNIPPET for internal =
use)

b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))
 - Would require implementing ANNOTATE, which is a lot of work. But it =
could also be implemented just minimally for this specific command.
 - Standardizing vendor.dovecot.snippet would probably require new RFC

c) CONVERT n ("text/vnd.dovecot.snippet" ("length" "100")) BINARY[BODY]
 - Would require implementing CONVERT, which is a lot of work. But it =
could also be implemented just minimally for this specific command.
 - Standardizing vnd.dovecot.snippet would probably require new RFC

d) CONVERT n ("text/plain") BINARY[BODY]<0.100>
 - CONVERT RFC says it's legal to convert entire multiparts, but doesn't =
say exactly what should be done with them. This is probably a valid use =
case though.
 - Downside to this compared to others is that this always fetches the =
first 100 chars, while the others could also be smarter and skip over =
quoted text and such.

I think I'm leaning towards b)


From nobody Mon Dec  1 23:04:49 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 5CEBC1A0103 for <imapext@ietfa.amsl.com>; Mon,  1 Dec 2014 23:04:47 -0800 (PST)
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 0YtfLQlxprrY for <imapext@ietfa.amsl.com>; Mon,  1 Dec 2014 23:04:44 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAF381A00FC for <imapext@ietf.org>; Mon,  1 Dec 2014 23:04:44 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 35ABD206ED for <imapext@ietf.org>; Tue,  2 Dec 2014 02:04:44 -0500 (EST)
Received: from betaweb1 ([10.202.2.10]) by compute1.internal (MEProxy); Tue, 02 Dec 2014 02:04:44 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:x-sasl-enc:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=mesmtp; bh=L4mAvQ5v+BixqrNEqnwGrH9fi6I=; b=IbvSAG thQBQM3Q5GS/bDAe0qSRigVrA3dffBgNuo5IXIvhj3ZqdvhkA6Bjzt4XueoyaWqk dzSNOZ/IVOZ43Cu/t0DxzftenQmEjoEcZlZt3/BCnrQ+pewmSVoPYRqS8aTIowpZ iHSV1YQ8FwAeSSKGQwNI4EJgJFA5LbMybiH14=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:subject :date:in-reply-to:references; s=smtpout; bh=L4mAvQ5v+BixqrNEqnwG rH9fi6I=; b=Bn7EbE5vJetx1MCnm93VCTcIwB4p8bIVTm4Zt0PgmfzSDsYwSKBB Jwwym9ZVcL6NeWxkglzZWUSYQPVlDThbT2SdNTYJOH6a2/j4Pjyveww6ryTd73jR lriuY2fKUiVfkg1vMeP8TaJCe06JgbUyf9yma96ocbYW2/GifZmQ1+A=
Received: by betaweb1.nyi.internal (Postfix, from userid 99) id EFAD874BAC0; Tue,  2 Dec 2014 02:04:43 -0500 (EST)
Message-Id: <1417503883.1500659.197680913.1FD3441E@webmail.messagingengine.com>
X-Sasl-Enc: 7YZzi2FRUCa99oFqnxA3vMQg8McLRWlQJw9gOT5/VQ0V 1417503883
From: Bron Gondwana <brong@fastmail.fm>
To: imapext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
Date: Tue, 02 Dec 2014 18:04:43 +1100
In-Reply-To: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi>
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/CQNlYFcDOvwxspr9mjz94wYDbKs
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 07:04:47 -0000

On phone, excuse short form response.

We do b at Fastmail, because we have annotations in Cyrus. We call it preview. Our snippet is a highlighted search fragment.

The preview is generated by a callout to an external program which adds the preview, a couple of flags calculated from the headers and body structure, and a flag to say what version of the annotator code did it. This is why all Fastmail messages have a $X-ME-ANNOT-2 flag right now!

The downside with b is standard preview name. Of we can standardize /preview or /htmlpreview or something then I am all for it.

Bron.

On Tue, Dec 2, 2014, at 05:39 PM, Timo Sirainen wrote:
> Nowadays many mail clients want to show about 100 chars of the beginning of mail, so there should be a nice and efficient way for clients to request this. I'm now wondering what would be a nice IMAP way of implementing this. Does anyone have some suggestions? There's what I've come up with so far:
> 
> a) FETCH n (SNIPPET)
>  - Would require writing a new RFC (or just use X-SNIPPET for internal use)
> 
> b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))
>  - Would require implementing ANNOTATE, which is a lot of work. But it could also be implemented just minimally for this specific command.
>  - Standardizing vendor.dovecot.snippet would probably require new RFC
> 
> c) CONVERT n ("text/vnd.dovecot.snippet" ("length" "100")) BINARY[BODY]
>  - Would require implementing CONVERT, which is a lot of work. But it could also be implemented just minimally for this specific command.
>  - Standardizing vnd.dovecot.snippet would probably require new RFC
> 
> d) CONVERT n ("text/plain") BINARY[BODY]<0.100>
>  - CONVERT RFC says it's legal to convert entire multiparts, but doesn't say exactly what should be done with them. This is probably a valid use case though.
>  - Downside to this compared to others is that this always fetches the first 100 chars, while the others could also be smarter and skip over quoted text and such.
> 
> I think I'm leaning towards b)
> 
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext


-- 
  Bron Gondwana
  brong@fastmail.fm


From nobody Tue Dec  2 02:37:43 2014
Return-Path: <dave@cridland.net>
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 B70C01A1A75 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 02:37:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 DI6k6Avm2SFU for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 02:37:38 -0800 (PST)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80F5F1A1A6A for <imapext@ietf.org>; Tue,  2 Dec 2014 02:37:38 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id wp4so9324869obc.25 for <imapext@ietf.org>; Tue, 02 Dec 2014 02:37:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=seegmhy+sA1MKoYgCsQejdfL294LNJRjOp6qjGPCOjM=; b=gnivveHjtZ1+oh0h/TZVBnJ5ovuCusCSPkbm7EpFN2ocL2L8G04UJ4jRac5q/yiGMY t0aTZmS8RJ6GO41uz/llJZ+pRBasexWhRjboMPuFvzSfIt7ykwMQlZ01d+aIGHgJmb+W /qIYd1/PXyE5b1hFTLV9IEzPFzW9q9ImEPmGk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=seegmhy+sA1MKoYgCsQejdfL294LNJRjOp6qjGPCOjM=; b=lvh+Bb283csYo63OMocaSh/x9QaGMeNmP72bzk7Mxucpzz0RfjnSIrYHYmR80V4cB+ IcnCH5CsW/n70ks7ITmldRpkFNVudkBdZAEbfHQnxyHWIhSIz7CS8/4OxYnVqc5a87cr oeQ3Z902esAlLtYn5mt9ofEL9y/6lS3Evc9QOOZpTa/yjuqECZfHkmRuKupSkK5UXAVc gDEP6bQMWU4psJoKcVSI0zGFZKfqYLhwORzsbzCNpHS4YXkZFDnovOccFYcfuXs4K4lM 91aNHLP72dNFlmYblsRDKNFjS21Bk8iggsH10fIQm0cyukRmEd7OTV9ieBnol0ivNBnq zR1g==
X-Gm-Message-State: ALoCoQnlaSCoBsGaH7aeqTIsoOE32jk/vsBQ6KGuzmw3bmh3Fl3A++SoXQpTMfGzDDEkZZR1Zsgu
MIME-Version: 1.0
X-Received: by 10.202.223.193 with SMTP id w184mr36959611oig.110.1417516657680;  Tue, 02 Dec 2014 02:37:37 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Tue, 2 Dec 2014 02:37:37 -0800 (PST)
In-Reply-To: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi>
Date: Tue, 2 Dec 2014 10:37:37 +0000
Message-ID: <CAKHUCzz6JjQ9o7T8Nx5f6zOEExCyX-J9VNVXDAnze=2Dmoxxqg@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Timo Sirainen <tss@iki.fi>
Content-Type: multipart/alternative; boundary=001a113d4fecd83a1205093950a0
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/EPcxPmWDccC5XmiVoaIWfpXyWfs
Cc: "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 10:37:39 -0000

--001a113d4fecd83a1205093950a0
Content-Type: text/plain; charset=UTF-8

On 2 December 2014 at 06:39, Timo Sirainen <tss@iki.fi> wrote:

> Nowadays many mail clients want to show about 100 chars of the beginning
> of mail, so there should be a nice and efficient way for clients to request
> this. I'm now wondering what would be a nice IMAP way of implementing this.
> Does anyone have some suggestions? There's what I've come up with so far:
>
> a) FETCH n (SNIPPET)
>  - Would require writing a new RFC (or just use X-SNIPPET for internal use)
>
> b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))
>  - Would require implementing ANNOTATE, which is a lot of work. But it
> could also be implemented just minimally for this specific command.
>  - Standardizing vendor.dovecot.snippet would probably require new RFC
>

One of these two.

I also wonder about making this more generic, as a THUMBNAIL, since
thumbnailing/snippeting seems a fairly generic action on any body part,
leaf or not. There's part of me wondering if it's worthwhile having this as
a BODYSTRUCTURE extension, since having this info at that stage seems more
useful.

It'd need an ENABLE, and probably mandatory BINARY, but it'd allow things
like thumbnailing image attachments, showing an image preview of a PDF, or
whatever.

I admit this is vastly more complex than 100 chars of text, though that's
not as simple as a substring anyway.

Dave.

--001a113d4fecd83a1205093950a0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 2=
 December 2014 at 06:39, Timo Sirainen <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:tss@iki.fi" target=3D"_blank">tss@iki.fi</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">Nowadays many mail clients want to show about 100=
 chars of the beginning of mail, so there should be a nice and efficient wa=
y for clients to request this. I&#39;m now wondering what would be a nice I=
MAP way of implementing this. Does anyone have some suggestions? There&#39;=
s what I&#39;ve come up with so far:<br>
<br>
a) FETCH n (SNIPPET)<br>
=C2=A0- Would require writing a new RFC (or just use X-SNIPPET for internal=
 use)<br>
<br>
b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))<br>
=C2=A0- Would require implementing ANNOTATE, which is a lot of work. But it=
 could also be implemented just minimally for this specific command.<br>
=C2=A0- Standardizing vendor.dovecot.snippet would probably require new RFC=
<br></blockquote><div><br></div><div>One of these two.</div><div><br></div>=
<div>I also wonder about making this more generic, as a THUMBNAIL, since th=
umbnailing/snippeting seems a fairly generic action on any body part, leaf =
or not. There&#39;s part of me wondering if it&#39;s worthwhile having this=
 as a BODYSTRUCTURE extension, since having this info at that stage seems m=
ore useful.</div><div><br></div><div>It&#39;d need an ENABLE, and probably =
mandatory BINARY, but it&#39;d allow things like thumbnailing image attachm=
ents, showing an image preview of a PDF, or whatever.</div><div><br></div><=
div>I admit this is vastly more complex than 100 chars of text, though that=
&#39;s not as simple as a substring anyway.</div><div><br></div><div>Dave.<=
/div></div></div></div>

--001a113d4fecd83a1205093950a0--


From nobody Tue Dec  2 03:37:12 2014
Return-Path: <jkt@flaska.net>
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 221A71A1A9F for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 03:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.289
X-Spam-Level: 
X-Spam-Status: No, score=0.289 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 lVvHs8GlWbjs for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 03:37:08 -0800 (PST)
Received: from latimerie.flaska.net (latimerie.flaska.net [IPv6:2a02:2b88:2:1::4a7:333]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A7B11A1A4C for <imapext@ietf.org>; Tue,  2 Dec 2014 03:37:08 -0800 (PST)
Received: by latimerie.flaska.net (Postfix, from userid 1000) id 6E097613B5; Tue,  2 Dec 2014 12:37:03 +0100 (CET)
From: =?iso-8859-1?Q?Jan_Kundr=E1t?= <jkt@flaska.net>
To: <imapext@ietf.org>
Date: Tue, 02 Dec 2014 12:37:03 +0100
User-Agent: Trojita/v0.4.1-408-g93d28e6; Qt/4.8.5; X11; Linux; 
MIME-Version: 1.0
Message-ID: <88b853db-cdbd-457b-8212-096b5dd48a14@flaska.net>
In-Reply-To: <CAKHUCzz6JjQ9o7T8Nx5f6zOEExCyX-J9VNVXDAnze=2Dmoxxqg@mail.gmail.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <CAKHUCzz6JjQ9o7T8Nx5f6zOEExCyX-J9VNVXDAnze=2Dmoxxqg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/DDyLvUrwUPT4UIVlaCVDsGopVjU
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 11:37:10 -0000

On Tuesday, 2 December 2014 11:37:37 CEST, Dave Cridland wrote:
> I also wonder about making this more generic, as a THUMBNAIL

That's exactly what CONVERT is doing. There's probably a reason nobody=20
implements CONVERT, so I suggest not to make this proposal any more=20
generic.

With kind regards,
Jan

--=20
Trojit=C3=A1, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/


From nobody Tue Dec  2 04:25:56 2014
Return-Path: <alexey.melnikov@isode.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 9327F1A1B19 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 04:25:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 5g2Swq85MmcH for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 04:25:51 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 50C8B1A1B0B for <imapext@ietf.org>; Tue,  2 Dec 2014 04:25:51 -0800 (PST)
Received: from [172.22.17.106] ((unknown) [217.34.220.158])  by waldorf.isode.com (smtp internal) via TCP with ESMTPA  id <VH2vxwBH1aug@waldorf.isode.com>; Tue, 2 Dec 2014 12:25:49 +0000
X-SMTP-Protocol-Errors: NORDNS
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <CAKHUCzz6JjQ9o7T8Nx5f6zOEExCyX-J9VNVXDAnze=2Dmoxxqg@mail.gmail.com>
In-Reply-To: <CAKHUCzz6JjQ9o7T8Nx5f6zOEExCyX-J9VNVXDAnze=2Dmoxxqg@mail.gmail.com>
Message-Id: <27897A8C-B2E5-4F1E-B04C-78E0DDC00E76@isode.com>
X-Mailer: iPhone Mail (11B651)
From: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Tue, 2 Dec 2014 12:30:08 +0000
To: Dave Cridland <dave@cridland.net>, Timo Sirainen <tss@iki.fi>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-12B3C206-2780-45D1-9937-571F5176AB4F
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/Gk8CyoewJplw-JXRAWViICfiehk
Cc: "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 12:25:53 -0000

--Apple-Mail-12B3C206-2780-45D1-9937-571F5176AB4F
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

On 2 Dec 2014, at 10:37, Dave Cridland <dave@cridland.net> wrote:

>> On 2 December 2014 at 06:39, Timo Sirainen <tss@iki.fi> wrote:
>> Nowadays many mail clients want to show about 100 chars of the beginning o=
f mail, so there should be a nice and efficient way for clients to request t=
his. I'm now wondering what would be a nice IMAP way of implementing this. D=
oes anyone have some suggestions? There's what I've come up with so far:
>>=20
>> a) FETCH n (SNIPPET)
>>  - Would require writing a new RFC (or just use X-SNIPPET for internal us=
e)
>>=20
>> b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))
>>  - Would require implementing ANNOTATE, which is a lot of work. But it co=
uld also be implemented just minimally for this specific command.
>>  - Standardizing vendor.dovecot.snippet would probably require new RFC
>=20
> One of these two.

What is snippet? Is it a piece of text or is it an image? This looks like CO=
NVERT.


--Apple-Mail-12B3C206-2780-45D1-9937-571F5176AB4F
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>On 2 Dec 2014, at 10:37, Dave Cridland &lt;<a href="mailto:dave@cridland.net">dave@cridland.net</a>&gt; wrote:</div><div><br></div><blockquote type="cite"><blockquote type="cite">On 2 December 2014 at 06:39, Timo Sirainen <span dir="ltr">&lt;<a href="mailto:tss@iki.fi" target="_blank">tss@iki.fi</a>&gt;</span> wrote:<br></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nowadays many mail clients want to show about 100 chars of the beginning of mail, so there should be a nice and efficient way for clients to request this. I'm now wondering what would be a nice IMAP way of implementing this. Does anyone have some suggestions? There's what I've come up with so far:<br>
<br>
a) FETCH n (SNIPPET)<br>
&nbsp;- Would require writing a new RFC (or just use X-SNIPPET for internal use)<br>
<br>
b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))<br>
&nbsp;- Would require implementing ANNOTATE, which is a lot of work. But it could also be implemented just minimally for this specific command.<br>
&nbsp;- Standardizing vendor.dovecot.snippet would probably require new RFC<div style="display: none;"><br></div></blockquote><div><br></div><div>One of these two.</div></blockquote><br><div>What is snippet? Is it a piece of text or is it an image? This looks like CONVERT.</div><div><br></div></body></html>
--Apple-Mail-12B3C206-2780-45D1-9937-571F5176AB4F--


From nobody Tue Dec  2 04:32:55 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 73D691A1AF2 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 04:32:52 -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 RS5WqPP9DMO4 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 04:32:50 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0A551A0030 for <imapext@ietf.org>; Tue,  2 Dec 2014 04:32:50 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 0F42AFA001D; Tue,  2 Dec 2014 12:32:48 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1417523567-22718-22717/12/3; Tue, 2 Dec 2014 12:32:47 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Tue, 2 Dec 2014 13:32:47 +0100
User-Agent: Trojita/v0.4.1-243-g4a74770; Qt/4.8.6; X11; Linux; Ubuntu 14.04.1 LTS
Mime-Version: 1.0
Message-Id: <e0fae8bb-c569-4be6-b488-62173289832f@gulbrandsen.priv.no>
In-Reply-To: <27897A8C-B2E5-4F1E-B04C-78E0DDC00E76@isode.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <CAKHUCzz6JjQ9o7T8Nx5f6zOEExCyX-J9VNVXDAnze=2Dmoxxqg@mail.gmail.com> <27897A8C-B2E5-4F1E-B04C-78E0DDC00E76@isode.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/Z87AF2CWeH5C27lpJwSP3MRFPp4
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 12:32:52 -0000

On Tuesday, December 2, 2014 1:30:08 PM CEST, Alexey Melnikov wrote:
> What is snippet? Is it a piece of text or is it an image? This 
> looks like CONVERT.

It's a piece of text. You've seen it: Modern mobile clients display 
30-200-byte extracts of the message even before you tap the message to read 
it.

The algorithm to extract the proper text is a bit like BASESUBJECT in 
spirit, but can be rather complex if one wants good results.

Arnt


From nobody Tue Dec  2 05:35:40 2014
Return-Path: <dave@cridland.net>
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 EC50B1A8967 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 05:35:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 pyDheskmXbUe for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 05:35:36 -0800 (PST)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82FA61A1B49 for <imapext@ietf.org>; Tue,  2 Dec 2014 05:35:36 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id nt9so2726415obb.33 for <imapext@ietf.org>; Tue, 02 Dec 2014 05:35:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=seoNPGt4IS1I3wtsBTwR2RAZQWBdDKiiaX5MNLzuyhE=; b=V1wXqy9Jfja8J24DWJC4Qt5GXRbr44N0/FckH1s6velI+w8jGO/FntftrY0ateUlx8 MsayBzAbns3nypg6GPR/FA9+4vtGt14aRqhDA4xP77J1BOOAsZ59EjFwXvyEw95THi7u b3egpZ0QXIMCh7vx6uhw347duen9oZ7WnA3ec=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=seoNPGt4IS1I3wtsBTwR2RAZQWBdDKiiaX5MNLzuyhE=; b=UCj1EnlJhB+c/pZtIq0L+uhGWoYf/9pPJtka4FZ4d11ZJ6e23Bx9c1exs+4njRWEtE G6WoxHl4Y2/0pJZoAqDyY+FPX/wI8SqyMYKw2eDofPUGYNmE97a9nASMz75uOPNa3U3J zwXDT9V+nL4O6tUb6jH2G8A4FwmrIELEwNO2+0DU8D7tbuGpl9077Rd8xFKy7JCBs/JT LdoGCneIKSlpzX+80AU75RSm0HKAQMjQX4kfKEvt9H5mWtGOBVZKLzB4RMjIff+8MCe+ 1wPypVVde/kCiEaQdsGPlHPyCAkCjg60ptaaFqwpCgf6AOSkaFX7QO8KQST1XP5wjviG vhTw==
X-Gm-Message-State: ALoCoQkmghjmeBSCfN8OX503dIu/IiEXQPhlziwvebHox7bbOqe/gRIbGs/sytO+XmiS5PaHJLKX
MIME-Version: 1.0
X-Received: by 10.202.220.87 with SMTP id t84mr31961436oig.86.1417527335775; Tue, 02 Dec 2014 05:35:35 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Tue, 2 Dec 2014 05:35:35 -0800 (PST)
In-Reply-To: <27897A8C-B2E5-4F1E-B04C-78E0DDC00E76@isode.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <CAKHUCzz6JjQ9o7T8Nx5f6zOEExCyX-J9VNVXDAnze=2Dmoxxqg@mail.gmail.com> <27897A8C-B2E5-4F1E-B04C-78E0DDC00E76@isode.com>
Date: Tue, 2 Dec 2014 13:35:35 +0000
Message-ID: <CAKHUCzwxnW2q0cntM0+VbQaB=WzZn6t2WEDzKRj6RRexg1P-Lg@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: multipart/alternative; boundary=001a113d30b24f093d05093bcd11
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/yHPe_284WMxoxyVMvpMwrgkd8Lc
Cc: Timo Sirainen <tss@iki.fi>, "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 13:35:38 -0000

--001a113d30b24f093d05093bcd11
Content-Type: text/plain; charset=UTF-8

On 2 December 2014 at 12:30, Alexey Melnikov <alexey.melnikov@isode.com>
wrote:

> On 2 Dec 2014, at 10:37, Dave Cridland <dave@cridland.net> wrote:
>
> On 2 December 2014 at 06:39, Timo Sirainen <tss@iki.fi> wrote:
>
> Nowadays many mail clients want to show about 100 chars of the beginning
>> of mail, so there should be a nice and efficient way for clients to request
>> this. I'm now wondering what would be a nice IMAP way of implementing this.
>> Does anyone have some suggestions? There's what I've come up with so far:
>>
>> a) FETCH n (SNIPPET)
>>  - Would require writing a new RFC (or just use X-SNIPPET for internal
>> use)
>>
>> b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))
>>  - Would require implementing ANNOTATE, which is a lot of work. But it
>> could also be implemented just minimally for this specific command.
>>  - Standardizing vendor.dovecot.snippet would probably require new RFC
>>
>>
> One of these two.
>
>
> What is snippet? Is it a piece of text or is it an image? This looks like
> CONVERT.
>
>
Yeah, well, everything looks like CONVERT or ANNOTATE. I think that's the
problem with CONVERT and ANNOTATE - they're just so wide-ranging and
generic.

This is an extract or smaller version for a specific purpose (preview), and
if having a specific, standalone mechanism for it means more people will
implement it, that's good.

Also, as Arnt implies, the quality and representativeness (yes, I know) of
the thumbnail/preview/snippet can vary between implementations, and becomes
a differentiating factor in user experience. Differentiating factors that
are comfortingly well within a simple wire protocol, but are clearly
visible to the end-user, feel like a fine thing to me.

Dave.

--001a113d30b24f093d05093bcd11
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 2=
 December 2014 at 12:30, Alexey Melnikov <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:alexey.melnikov@isode.com" target=3D"_blank">alexey.melnikov@isode.co=
m</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"=
><span class=3D""><div>On 2 Dec 2014, at 10:37, Dave Cridland &lt;<a href=
=3D"mailto:dave@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt; w=
rote:</div><div><br></div><blockquote type=3D"cite"><blockquote type=3D"cit=
e">On 2 December 2014 at 06:39, Timo Sirainen <span dir=3D"ltr">&lt;<a href=
=3D"mailto:tss@iki.fi" target=3D"_blank">tss@iki.fi</a>&gt;</span> wrote:<b=
r></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Nowadays many mail clients wa=
nt to show about 100 chars of the beginning of mail, so there should be a n=
ice and efficient way for clients to request this. I&#39;m now wondering wh=
at would be a nice IMAP way of implementing this. Does anyone have some sug=
gestions? There&#39;s what I&#39;ve come up with so far:<br>
<br>
a) FETCH n (SNIPPET)<br>
=C2=A0- Would require writing a new RFC (or just use X-SNIPPET for internal=
 use)<br>
<br>
b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))<br>
=C2=A0- Would require implementing ANNOTATE, which is a lot of work. But it=
 could also be implemented just minimally for this specific command.<br>
=C2=A0- Standardizing vendor.dovecot.snippet would probably require new RFC=
<div><br></div></blockquote><div><br></div><div>One of these two.</div></bl=
ockquote><br></span><div>What is snippet? Is it a piece of text or is it an=
 image? This looks like CONVERT.</div><div><br></div></div></blockquote></d=
iv><br></div><div class=3D"gmail_extra">Yeah, well, everything looks like C=
ONVERT or ANNOTATE. I think that&#39;s the problem with CONVERT and ANNOTAT=
E - they&#39;re just so wide-ranging and generic.</div><div class=3D"gmail_=
extra"><br></div><div class=3D"gmail_extra">This is an extract or smaller v=
ersion for a specific purpose (preview), and if having a specific, standalo=
ne mechanism for it means more people will implement it, that&#39;s good.</=
div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Also, a=
s Arnt implies, the quality and representativeness (yes, I know) of the thu=
mbnail/preview/snippet can vary between implementations, and becomes a diff=
erentiating factor in user experience. Differentiating factors that are com=
fortingly well within a simple wire protocol, but are clearly visible to th=
e end-user, feel like a fine thing to me.</div><div class=3D"gmail_extra"><=
br></div><div class=3D"gmail_extra">Dave.</div></div>

--001a113d30b24f093d05093bcd11--


From nobody Tue Dec  2 08:23:03 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 5664F1A1BD4 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 08:23:01 -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 eX2Uqq5v1xGm for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 08:22:59 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EBBC1A026F for <imapext@ietf.org>; Tue,  2 Dec 2014 08:22:59 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 61A65FA001D; Tue,  2 Dec 2014 16:22:57 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1417537376-22718-22717/12/7; Tue, 2 Dec 2014 16:22:56 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Timo Sirainen <tss@iki.fi>, imapext@ietf.org, Dave Cridland <dave@cridland.net>
Message-Id: <1de1f39c6ee20d8e3afe31a7fa8bf9e094e60fee41a5977e6eff6074c51220cf.sha-256@android.antelope.email>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <CAKHUCzz6JjQ9o7T8Nx5f6zOEExCyX-J9VNVXDAnze=2Dmoxxqg@mail.gmail.com> <27897A8C-B2E5-4F1E-B04C-78E0DDC00E76@isode.com> <CAKHUCzwxnW2q0cntM0+VbQaB=WzZn6t2WEDzKRj6RRexg1P-Lg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Date: Tue, 2 Dec 2014 16:22:56 +0000
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/93L8hy2F6QIKNinfpQNLcRe59CY
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 16:23:01 -0000

IMO, the extensions people implement are the ones that are readily =
described over coffee. Something that builds on annotate or convert is =
not, something that adds two lines to the ABNF may be.

That said, I cannot muster much enthusiasm for this proposal. Or against.

Army


From nobody Tue Dec  2 08:37:44 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 434BE1A1EF4 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 08:37:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 yoY3nHJ5yMSJ for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 08:37:38 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55E841A1BF3 for <imapext@ietf.org>; Tue,  2 Dec 2014 08:37:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 8D71C4F9732; Tue,  2 Dec 2014 11:37:37 -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 sbYfK5K1xJNi; Tue,  2 Dec 2014 11:37:37 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 11E684F9723; Tue,  2 Dec 2014 11:37:35 -0500 (EST)
Date: Tue, 02 Dec 2014 11:37:31 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Timo Sirainen <tss@iki.fi>, imapext@ietf.org
Message-ID: <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com>
In-Reply-To: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi>
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=798
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/OPHuvuW76XMvSnYD1Rl4siNMEP8
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 16:37:41 -0000

Hi Timo,

--On December 1, 2014 at 10:39:13 PM -0800 Timo Sirainen <tss@iki.fi> wrote:

> Nowadays many mail clients want to show about 100 chars of the beginning
> of mail, so there should be a nice and efficient way for clients to
> request this. I'm now wondering what would be a nice IMAP way of
> implementing this. Does anyone have some suggestions? There's what I've
> come up with so far:

Efficient as in eliminating the current extra round trip of doing a FETCH 
BODY.PEEK[<section>]<<partial>>? If so, then I think "SNIPPET" should be an 
alias for BODY.PEEK[the first significant text section]<<partial>>. i.e., 
the server does not do anything more than determine the "the first 
significant text section". The client still gets to use <<partial>> as it 
could today.

-- 
Cyrus Daboo


From nobody Tue Dec  2 08:58:27 2014
Return-Path: <alexey.melnikov@isode.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 B86A21A3BA2 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 08:58:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 ohSvS2z15LHz for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 08:58:24 -0800 (PST)
Received: from statler.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 249C11A2119 for <imapext@ietf.org>; Tue,  2 Dec 2014 08:58:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1417539503; d=isode.com; s=selector; i=@isode.com; bh=yQlGXfA5t3ojfOODcDsC78pdj05tQ6gXRyZ7CGGu9kA=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=cD6i0/y+mc97Og/qjhoC4Zt/75a8VPRZ8j7ut1AUXtxC8Z+yAMfI+exq5r3hCgmdMN1KIA pOHnAoBN+LtaZe1aZhHla160QjuFROuoYpohs8WxHxIcwPbRQv9OrvlQ/Ppu2wUUg3kgkJ E9qm9/WY0//VlF2U9hYXlNQ4a7MetAo=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <VH3vrABaEA8L@statler.isode.com>; Tue, 2 Dec 2014 16:58:23 +0000
Message-ID: <547DEF1A.6070603@isode.com>
Date: Tue, 02 Dec 2014 16:55:54 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: Cyrus Daboo <cyrus@daboo.name>, Timo Sirainen <tss@iki.fi>, imapext@ietf.org
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com>
In-Reply-To: <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/JUMY1e7_cNb5ZhKMzQ3LqNTHbfc
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 16:58:26 -0000

Hi Cyrus,

On 02/12/2014 16:37, Cyrus Daboo wrote:
> Hi Timo,
>
> --On December 1, 2014 at 10:39:13 PM -0800 Timo Sirainen <tss@iki.fi> 
> wrote:
>> Nowadays many mail clients want to show about 100 chars of the beginning
>> of mail, so there should be a nice and efficient way for clients to
>> request this. I'm now wondering what would be a nice IMAP way of
>> implementing this. Does anyone have some suggestions? There's what I've
>> come up with so far:
>
> Efficient as in eliminating the current extra round trip of doing a 
> FETCH BODY.PEEK[<section>]<<partial>>? If so, then I think "SNIPPET" 
> should be an alias for BODY.PEEK[the first significant text 
> section]<<partial>>. i.e., the server does not do anything more than 
> determine the "the first significant text section". The client still 
> gets to use <<partial>> as it could today.
I thought so too. That is why I've asked the question what exactly is 
"snippet". Unless "snippet" needs to convert from text/html to 
text/plain (or vice versa), etc.



From nobody Tue Dec  2 09:05:53 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 BC5811A3B9E for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 09:05:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 GqaLjtLmyiCv for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 09:05:49 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26C581A6EED for <imapext@ietf.org>; Tue,  2 Dec 2014 09:04:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 402A44FA248; Tue,  2 Dec 2014 12:04:42 -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 FgOoOg4-W7qJ; Tue,  2 Dec 2014 12:04:42 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 0E5F34FA23B; Tue,  2 Dec 2014 12:04:40 -0500 (EST)
Date: Tue, 02 Dec 2014 12:04:37 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Timo Sirainen <tss@iki.fi>, imapext@ietf.org
Message-ID: <F55A640012F58A950BE4E6B5@caldav.corp.apple.com>
In-Reply-To: <547DEF1A.6070603@isode.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi>            <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <547DEF1A.6070603@isode.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=1134
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/hMaW3dSba2aJ_9-b8WCKlJNnQi4
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 17:05:51 -0000

Hi Alexey,

--On December 2, 2014 at 4:55:54 PM +0000 Alexey Melnikov 
<alexey.melnikov@isode.com> wrote:

>> Efficient as in eliminating the current extra round trip of doing a
>> FETCH BODY.PEEK[<section>]<<partial>>? If so, then I think "SNIPPET"
>> should be an alias for BODY.PEEK[the first significant text
>> section]<<partial>>. i.e., the server does not do anything more than
>> determine the "the first significant text section". The client still
>> gets to use <<partial>> as it could today.
> I thought so too. That is why I've asked the question what exactly is
> "snippet". Unless "snippet" needs to convert from text/html to text/plain
> (or vice versa), etc.

Of course there is a lot that a client might do itself to "extract" the 
snippet: convert HTML to plain text (i.e., get rid of all the <..> tags, 
scripts etc, add suitable line breaks for <h> tags), strip quoted text from 
a reply or "quote headers" from a forward.

The thing is each client probably has its own heuristics as to how to 
"extract" a snippet and I am not sure we could agree on a single 
server-side approach that would do.

-- 
Cyrus Daboo


From nobody Tue Dec  2 09:06:53 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 D0AEF1A3B9E for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 09:06:46 -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 AQcr37BAkohb for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 09:06:44 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5AE61A3BA2 for <imapext@ietf.org>; Tue,  2 Dec 2014 09:06:23 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 54D37FA001D; Tue,  2 Dec 2014 17:06:22 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1417539981-22718-22717/12/8; Tue, 2 Dec 2014 17:06:21 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Tue, 2 Dec 2014 18:06:20 +0100
User-Agent: Trojita/v0.4.1-243-g4a74770; Qt/4.8.6; X11; Linux; Ubuntu 14.04.1 LTS
Mime-Version: 1.0
Message-Id: <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no>
In-Reply-To: <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/cXKt2utqm-BoZcKfCKDNHwUOid4
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 17:06:47 -0000

On Tuesday, December 2, 2014 5:37:31 PM CEST, Cyrus Daboo wrote:
> Efficient as in eliminating the current extra round trip of 
> doing a FETCH BODY.PEEK[<section>]<<partial>>? If so, then I 
> think "SNIPPET" should be an alias for BODY.PEEK[the first 
> significant text section]<<partial>>. i.e., the server does not 
> do anything more than determine the "the first significant text 
> section". The client still gets to use <<partial>> as it could 
> today.

This I like. Simple for the server, simple for the client, a clear win for 
the client. The only disadvantage is that the client still has to do the 
heavy text extraction. But it needs that code anyway if it is to work with 
unextended servers.

Arnt


From nobody Tue Dec  2 09:08:41 2014
Return-Path: <dave@cridland.net>
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 C48121A212A for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 09:08:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 PqlatP4TYrfc for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 09:08:30 -0800 (PST)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AE321A1EFE for <imapext@ietf.org>; Tue,  2 Dec 2014 09:08:30 -0800 (PST)
Received: by mail-ob0-f179.google.com with SMTP id va2so10099981obc.10 for <imapext@ietf.org>; Tue, 02 Dec 2014 09:08:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zcvFHrK7u78ZexZKE3DtLa336Jcx4HCpLfNhxfH/LSw=; b=aXEF8grGEb/bMmj0dDJID4RfqDguAxEXFmSP5toapVqWAj0VLbkWI/p3PC7Wulpvy2 0WbYudQNnG9VbIotA4xPsLf1wZmiJUoxe+NKUzMgwqzffsQHdMmKkhJIbuxim7yKvNuR eR855mXi2qEmT71U+uYSbhnaQtzD84XCQ5jBg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=zcvFHrK7u78ZexZKE3DtLa336Jcx4HCpLfNhxfH/LSw=; b=mnwfw66/4ZAiEh+zHaNXuIxrg5zDX19qxSayvw/wy5/w26X7m6FDgnB1+7CmucVCWz CQf+ohgHUHTrJs1nZpoVb8O84YvToxqggNiT8sED8KvbGMyRZNXc/h2JI/DWJ9ziD1dx 1yBXyXXyJ4u9vCP+/VpzBnrg9tK6M1v77RASe65Lcm1lawf5rqNYTZc74TogXYjyQzyu 2fhpgI4Cjpxufb6TkFsjRAItSyE4DMLwud9FCv8dKBQoWoNE7rQKIDdE+ndgKP0hAxf6 G/RxmbMqLVreYvkb7hF6G8ao0taIODVb4F0VtqD4KHEkiJeaGw2tylqOQhghwiUFr1H8 rYVw==
X-Gm-Message-State: ALoCoQlj2d7TYBElUAOEQ5jvD/eDwjI4IRU7x2roANP2+5T0gqvGtEKWjAPQWIf4tCmvF6ovW6A+
MIME-Version: 1.0
X-Received: by 10.202.220.87 with SMTP id t84mr207571oig.86.1417540109255; Tue, 02 Dec 2014 09:08:29 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Tue, 2 Dec 2014 09:08:29 -0800 (PST)
In-Reply-To: <F55A640012F58A950BE4E6B5@caldav.corp.apple.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <547DEF1A.6070603@isode.com> <F55A640012F58A950BE4E6B5@caldav.corp.apple.com>
Date: Tue, 2 Dec 2014 17:08:29 +0000
Message-ID: <CAKHUCzxqs4J1N+XV3MSUSiroMi7vY68Gk1UBJs+8g0_mGyX2-g@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: multipart/alternative; boundary=001a113d30b2aada8805093ec629
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/6GW3jLOkJ4Je4PT-ymnQ3Cq2Ihc
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Timo Sirainen <tss@iki.fi>, "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 17:08:32 -0000

--001a113d30b2aada8805093ec629
Content-Type: text/plain; charset=UTF-8

On 2 December 2014 at 17:04, Cyrus Daboo <cyrus@daboo.name> wrote:

> Hi Alexey,
>
> --On December 2, 2014 at 4:55:54 PM +0000 Alexey Melnikov <
> alexey.melnikov@isode.com> wrote:
>
>  Efficient as in eliminating the current extra round trip of doing a
>>> FETCH BODY.PEEK[<section>]<<partial>>? If so, then I think "SNIPPET"
>>> should be an alias for BODY.PEEK[the first significant text
>>> section]<<partial>>. i.e., the server does not do anything more than
>>> determine the "the first significant text section". The client still
>>> gets to use <<partial>> as it could today.
>>>
>> I thought so too. That is why I've asked the question what exactly is
>> "snippet". Unless "snippet" needs to convert from text/html to text/plain
>> (or vice versa), etc.
>>
>
> Of course there is a lot that a client might do itself to "extract" the
> snippet: convert HTML to plain text (i.e., get rid of all the <..> tags,
> scripts etc, add suitable line breaks for <h> tags), strip quoted text from
> a reply or "quote headers" from a forward.
>
> The thing is each client probably has its own heuristics as to how to
> "extract" a snippet and I am not sure we could agree on a single
> server-side approach that would do.


Yes, I entirely agree. Which is why I suspect that  trying to define a
"single server-side approach" isn't what would add the most value - you
want to define a simple protocol that returns some magic text that acts as
a snippet or preview.

Dave.

--001a113d30b2aada8805093ec629
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 2=
 December 2014 at 17:04, Cyrus Daboo <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:cyrus@daboo.name" target=3D"_blank">cyrus@daboo.name</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">Hi Alexey,<span class=3D""><br>
<br>
--On December 2, 2014 at 4:55:54 PM +0000 Alexey Melnikov &lt;<a href=3D"ma=
ilto:alexey.melnikov@isode.com" target=3D"_blank">alexey.melnikov@isode.com=
</a>&gt; wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Efficient as in eliminating the current extra round trip of doing a<br>
FETCH BODY.PEEK[&lt;section&gt;]&lt;&lt;partial&gt;<u></u>&gt;? If so, then=
 I think &quot;SNIPPET&quot;<br>
should be an alias for BODY.PEEK[the first significant text<br>
section]&lt;&lt;partial&gt;&gt;. i.e., the server does not do anything more=
 than<br>
determine the &quot;the first significant text section&quot;. The client st=
ill<br>
gets to use &lt;&lt;partial&gt;&gt; as it could today.<br>
</blockquote>
I thought so too. That is why I&#39;ve asked the question what exactly is<b=
r>
&quot;snippet&quot;. Unless &quot;snippet&quot; needs to convert from text/=
html to text/plain<br>
(or vice versa), etc.<br>
</blockquote>
<br></span>
Of course there is a lot that a client might do itself to &quot;extract&quo=
t; the snippet: convert HTML to plain text (i.e., get rid of all the &lt;..=
&gt; tags, scripts etc, add suitable line breaks for &lt;h&gt; tags), strip=
 quoted text from a reply or &quot;quote headers&quot; from a forward.<br>
<br>
The thing is each client probably has its own heuristics as to how to &quot=
;extract&quot; a snippet and I am not sure we could agree on a single serve=
r-side approach that would do.</blockquote><div><br></div><div>Yes, I entir=
ely agree. Which is why I suspect that =C2=A0trying to define a &quot;singl=
e server-side approach&quot; isn&#39;t what would add the most value - you =
want to define a simple protocol that returns some magic text that acts as =
a snippet or preview.</div><div><br></div><div>Dave.</div></div></div></div=
>

--001a113d30b2aada8805093ec629--


From nobody Tue Dec  2 09:27: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 E2F611A1AA7 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 09:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 sZhGpHOXcH0x for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 09:27:31 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46D0D1A1AD8 for <imapext@ietf.org>; Tue,  2 Dec 2014 09:27:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 6A05F4FA995; Tue,  2 Dec 2014 12:27:28 -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 DsdachGButUS; Tue,  2 Dec 2014 12:27:25 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 55D844FA986; Tue,  2 Dec 2014 12:27:25 -0500 (EST)
Date: Tue, 02 Dec 2014 12:27:21 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, imapext@ietf.org
Message-ID: <CE219298B9139C8F3B005BD7@caldav.corp.apple.com>
In-Reply-To: <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no>
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=1655
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/1k5qJLsBI0L0JuNSLYnwbHSVE10
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 17:27:33 -0000

Hi Arnt,

--On December 2, 2014 at 6:06:20 PM +0100 Arnt Gulbrandsen 
<arnt@gulbrandsen.priv.no> wrote:

>> Efficient as in eliminating the current extra round trip of
>> doing a FETCH BODY.PEEK[<section>]<<partial>>? If so, then I
>> think "SNIPPET" should be an alias for BODY.PEEK[the first
>> significant text section]<<partial>>. i.e., the server does not
>> do anything more than determine the "the first significant text
>> section". The client still gets to use <<partial>> as it could
>> today.
>
> This I like. Simple for the server, simple for the client, a clear win
> for the client. The only disadvantage is that the client still has to do
> the heavy text extraction. But it needs that code anyway if it is to work
> with unextended servers.

The problem is I am not sure how well this works with HTML where there may 
be a lot of markup prior to any real text being present. That will force 
clients to request a larger enough number of octets in <<partial>> so that 
they have a reasonable chance of extracting "real" text. But then the size 
of the response gets a lot larger and thus it becomes less efficient 
overall - defeating the whole purpose of doing that.

Do we have a summary of client behaviors that shows the set of FETCH 
requests clients currently do to populate their message lists? I think it 
would be useful to see exactly what all the clients do - in particular for 
cases where there are a large number of new messages (e.g., loading a 
mailbox for the first time) vs just a few new messages (sync'ing new mail). 
Perhaps seeing that will clarify exactly what is inefficient and could be 
improved.

-- 
Cyrus Daboo


From nobody Tue Dec  2 09:49:19 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 DF2D31A6FB7 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 09:49:16 -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 yCU8Bj2Y2oXO for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 09:49:15 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B8231A6F3C for <imapext@ietf.org>; Tue,  2 Dec 2014 09:49:15 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 4F382FA001D; Tue,  2 Dec 2014 17:49:13 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1417542551-22718-22717/11/2; Tue, 2 Dec 2014 17:49:11 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Tue, 2 Dec 2014 18:49:11 +0100
User-Agent: Trojita/v0.4.1-243-g4a74770; Qt/4.8.6; X11; Linux; Ubuntu 14.04.1 LTS
Mime-Version: 1.0
Message-Id: <96577a94-dc15-4f46-8aad-dc8767b671ee@gulbrandsen.priv.no>
In-Reply-To: <CE219298B9139C8F3B005BD7@caldav.corp.apple.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no> <CE219298B9139C8F3B005BD7@caldav.corp.apple.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/chuniYHkUd5V6K5l2ArjtCGionw
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 17:49:17 -0000

Does it matter?

As I see it, your proposal aims to solve the download problem. (Which is a 
prioblem. If it takes several roundtrips from when a mobile client has put 
up a notification until it's ready to ship a snippet, that's often >1s, 
painfully long on a mobile.) You don't solve the problem of extracting the 
right text, but rather presume that the client has logic to solve that.

Instead of a dubious solution to two problems, you supply a good solution 
to one problem. Good, say I.

Arnt


From nobody Tue Dec  2 10:09:19 2014
Return-Path: <jkt@flaska.net>
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 706A01A0392 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 10:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.209
X-Spam-Level: 
X-Spam-Status: No, score=-2.209 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, GB_I_INVITATION=-2, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 N4e2WUT43MEB for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 10:09:07 -0800 (PST)
Received: from latimerie.flaska.net (latimerie.flaska.net [IPv6:2a02:2b88:2:1::4a7:333]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB8EC1A1C06 for <imapext@ietf.org>; Tue,  2 Dec 2014 10:08:56 -0800 (PST)
Received: by latimerie.flaska.net (Postfix, from userid 1000) id BAAB3613B5; Tue,  2 Dec 2014 19:08:53 +0100 (CET)
From: =?iso-8859-1?Q?Jan_Kundr=E1t?= <jkt@flaska.net>
To: <imapext@ietf.org>
Date: Tue, 02 Dec 2014 19:08:49 +0100
User-Agent: Trojita/v0.4.1-408-g93d28e6; Qt/4.8.5; X11; Linux; 
MIME-Version: 1.0
Message-ID: <330724e6-c365-4eec-844a-57d16f174432@flaska.net>
In-Reply-To: <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/W8H1HHT267nZqrsw6U319F1t-0w
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 18:09:11 -0000

On Tuesday, 2 December 2014 17:37:31 CEST, Cyrus Daboo wrote:
> Efficient as in eliminating the current extra round trip of=20
> doing a FETCH BODY.PEEK[<section>]<<partial>>?

I don't think a roundtrip would be neccessary.

Sure, the client doesn't know whether it's a single-part text/plain, or if=20=

it's a multipart/mixed with plaintext and HTML, or whether it's something=20
yet different. However, there's principally no problem in issuing a blind=20
BODY.PEEK[1] which will "get the right thing" most of the time. One can=20
play it extra-safe and ask for a BODY.PEEK[1.1] as well, these are also=20
pretty popular and the worst case is wasting a tiny amount of bandwidth.=20
It's OK to request a non-existing part in FETCH anyway.

> If so, then I think "SNIPPET" should be an alias for BODY.PEEK[the first=20=

> significant text section]<<partial>>. i.e., the server does not=20
> do anything more than determine the "the first significant text=20
> section". The client still gets to use <<partial>> as it could=20
> today.

So that proposal would be just about finding a "first text part", and maybe=20=

returning a small, impementation-defined subset of that. As a client=20
author, I don't think that such an extension would provide much added value=20=

to my users. I can already get "99%" of this with no extensions today.

What I would like much more is something "smarter", even if with an=20
implementation-defined exact behavior. Finding a textual part is not=20
particularly compelling. It should strip away quotations (and do it=20
smartly, ignoring the leading "Hi John," or "On ABC, XYZ wrote" prefixes),=20=

kill the signature, notice that it's a meeting invitation from Exchange and=20=

display the subject/note along with time and location, etc.

Of course this cannot possibly be specified by an RFC. What I'm arguing=20
against is specifying this extension to only extract a chunk of bytes from=20=

a first textual part.

An extension which I would like to use would use loose wording such as=20
"return a textual preview of the e-mail, using implementation defined=20
heuristics for determining the content of the response". The RFC can then=20
go ahead and suggest what the typical steps to be performed are.

It would be nice to also have a command which returns back the supported=20
features of this convertor/extractor. One could go as far as to maintain a=20=

IANA list of the capabilities, but that is probably an overkill :). I can=20
certainly see a couple of use cases for that, though.

With kind regards,
Jan

--=20
Trojit=C3=A1, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/


From nobody Tue Dec  2 13:09:18 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 2A0B31A8789 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 13:09:15 -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_40=-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 rWcwuhlAxv0C for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 13:09:10 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCCCD1A8709 for <imapext@ietf.org>; Tue,  2 Dec 2014 13:07:53 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B6EBB20AA4 for <imapext@ietf.org>; Tue,  2 Dec 2014 16:07:52 -0500 (EST)
Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Tue, 02 Dec 2014 16:07:52 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:x-sasl-enc:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=mesmtp; bh=C3ZerQ5PA5Uu+D7RLVb14aLYgkQ=; b=oREJrG lS4dnnTpK0RWbTdpThgjSXcqH6AJrJz/uSfbVUHgPy/3FwGkf31xFodyKLvmHQPt W3Fvj4tZ1rStOCgW/sGwTkwZyJxLs5Fi8gLjphc2UD7NXqaxLfeEHf0tRVnPXbzM Zi21SvQYaEiaLJ8HGenSiu0tiiPy9Xb3krtKs=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:subject :date:in-reply-to:references; s=smtpout; bh=C3ZerQ5PA5Uu+D7RLVb1 4aLYgkQ=; b=TqXWnj5vakl2ShnR+CwtQVrBaJtHyYexr8l2JCDpEJ+IeLFiVaNS PBjibgT4UpmBH9iGXie1k4icuCVwH0Hw1haTpkmkBqEHhQg8PZVobRTWctihUjnM cmCKH1enntzed8XDq2/S6WqSPQ87Im8N4eRL+luATQRySrSFXQKRre4=
Received: by web3.nyi.internal (Postfix, from userid 99) id 8BAB911E776; Tue,  2 Dec 2014 16:07:52 -0500 (EST)
Message-Id: <1417554472.2253074.197997697.17E6A5B4@webmail.messagingengine.com>
X-Sasl-Enc: op5jv53hGGW/59FrXZ+uaZtQlI2GMB+ZVfobIQ15uw0Y 1417554472
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-53201334
Date: Wed, 03 Dec 2014 08:07:52 +1100
In-Reply-To: <96577a94-dc15-4f46-8aad-dc8767b671ee@gulbrandsen.priv.no>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no> <CE219298B9139C8F3B005BD7@caldav.corp.apple.com> <96577a94-dc15-4f46-8aad-dc8767b671ee@gulbrandsen.priv.no>
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/QEc0FOhdJ9IvLyeBVdE6hWNBK-4
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 21:09:15 -0000

On Wed, Dec 3, 2014, at 04:49 AM, Arnt Gulbrandsen wrote:
> Does it matter?
>
> As I see it, your proposal aims to solve the download problem. (Which
> is a prioblem. If it takes several roundtrips from when a mobile
> client has put up a notification until it's ready to ship a snippet,
> that's often >1s, painfully long on a mobile.) You don't solve the
> problem of extracting the right text, but rather presume that the
> client has logic to solve that.
>
> Instead of a dubious solution to two problems, you supply a good
> solution to one problem. Good, say I.

As someone who's done both ends of this - your solution isn't enough.
We now calculate an ANNOTATION on the server precisely because it's a
pain to fetch over IMAP.  I'm going to paste our "find the body part to
get preview from" code, so you can see how much complexity went into the
client to get efficient previews from the IMAP server.  And note, you
have to repeat this every time you lose your local cache.

There's plenty around this, but here's the preview and "has attachments"
finding bit.  Notice how it has to batch fetches by which bodystructure part
it wants to fetch the preview from:

    # Get bodystructure for messages we need bodystructure for {{{

    if (my @NeedBSUids = grep { $NeedMoreUids{$_}->{NeedBS} } keys %NeedMoreUids) {
      @NeedBSUids = sort { $a <=> $b } @NeedBSUids;

      # Hold UIDs that need each appropriate flag stored back
      my (@StoreHasAttUids, @StoreHasNoAttUids);

      my $IMAPBS = $Mailbox->fetch(\@NeedBSUids, "(bodystructure)")
        || die "IMAP fetch failed - $@";

      foreach my $Uid (@NeedBSUids) {

        # Get local references to data
        my $Row = $Uid2RowMap{$Uid};
        my $BS = ($IMAPBS->{$Uid} && $IMAPBS->{$Uid}->{bodystructure}) || next;

        # Store back 'hasatt' or 'hasnoatt' flag
        if ($NeedMoreUids{$Uid}->{NeedAttStore}) {

          # Quick heuristic to work out if has attachment
          my $HasAtt = $Self->_HasAttachment($BS);

          # Add id to appropriate list
          if ($HasAtt) {
            push @StoreHasAttUids, $Uid;
          } else {
            push @StoreHasNoAttUids, $Uid;
          }

          # Save new information back into row data
          $Row->{HasAtt} = $HasAtt;
        }

        # Fix 8-bit headers
        if ($NeedMoreUids{$Uid}->{NeedCharset}) {
          my $CharSet = lc($BS->{'Content-Type'}->{charset});

          # If no charset, or we're told it's us-ascii, (but we got here because there
          #  was 8-bit data in the header!), then assume users default charset
          $CharSet = $Self->{FallbackCharset} || 'iso-8859-1'
            if !$CharSet || $CharSet eq 'ascii' || $CharSet eq 'us-ascii';

          # For each 8-bit header, decode it with the charset we now think it's in
          my $Row = $Uid2RowMap{$Uid};
          for (grep { defined($_) && !is_utf8($_) && /[^\x20-\x7f]/ } @$Row{qw(To From Subject)}) {
            eval { $_ = decode($CharSet, $_); };
            # We decoded to utf-8, but there's still control chars? Strip them.
            s/[\x00-\x1f]//g if is_utf8($_) && /[\x00-\x1f]/;
          }
        }

        # Save copy of BS for body part below
        $Uid2BSMap{$Uid} = $BS;
      }

      # Save hasatt/hasnoatt flags back
      $Mailbox->store(\@StoreHasAttUids, '+flags.silent', "(hasatt)")
        if @StoreHasAttUids;
      $Mailbox->store(\@StoreHasNoAttUids, '+flags.silent', "(hasnoatt)")
        if @StoreHasNoAttUids;
    }

    # }}}

    # Get preview text for messages we need preview text for {{{

    if (my @NeedBodyUids = grep { $NeedMoreUids{$_}->{NeedPeek} } keys %NeedMoreUids) {
      @NeedBodyUids = sort { $a <=> $b } @NeedBodyUids;

      # Need to fetch by partnum. To fetch multiple at once, map partnum -> uids
      my (%PartNumToUidMap, %UidToPartInfoMap);
      foreach my $Uid (@NeedBodyUids) {

        # Use find_message to find the body part for this message
        #  (we stored the actual bodystructure for the mesage into
        #  %NeedBSUids above)
        my $Parts = find_message($Uid2BSMap{$Uid});
        my ($Part, $Type) = ($Parts->{text}, 'text');

        # If no text part, but an HTML part, use that
        if (!$Part && exists $Parts->{html}) {
          ($Part, $Type) = ($Parts->{html}, 'html');
        } elsif ($Part) {
          $Type = 'rtf' if lc $Part->{'MIME-Type'} eq 'text/enriched';
        }

        my $Partnum = $Part->{'IMAP-Partnum'} || '';

        push @{$PartNumToUidMap{$Partnum}}, $Uid;
        $UidToPartInfoMap{$Uid} = [ $Part, $Type ];
      }

      # Now iterate by partnums
      foreach my $Partnum (keys %PartNumToUidMap) {
        my @Uids = @{$PartNumToUidMap{$Partnum}};

        # Now get the data for all uids with body in this partnum
        my $BodyTexts = $Mailbox->fetch(\@Uids, "binary.peek[$Partnum]<0.2000>");

        # Bad transfer encodings cause error return, but there might be partial data
        if (!$BodyTexts || !ref($BodyTexts)) {
          $BodyTexts = delete $Mailbox->{PartialResp};
        }

        if (!$BodyTexts || !ref($BodyTexts)) {
          warn "fetch binary for part=$Partnum for uids=@Uids for $Self->{UserId} in $FolderDet->{FolderName} failed: $@";
        }

        # And process each of them
        foreach my $Uid (@Uids) {
          my ($Part, $Type) = @{$UidToPartInfoMap{$Uid}};
          my $BodyText = $BodyTexts->{$Uid} && $BodyTexts->{$Uid}->{binary};
          $BodyText = 'Content unavailable for preview. Probably invalid encoding'
            if !defined $BodyText;

          # Check if we need to decode
          # If any non-ascii chars, we have to decode in some way...
          if ($BodyText =~ /[^\x20-\x7f\r\n]/) {

            # Get and normalise charset
            my $Charset = lc($Part->{'Content-Type'}->{charset});
            $Charset = $Self->{FallbackCharset} || 'iso-8859-1'
              if !$Charset || $Charset eq 'ascii' || $Charset eq 'us-ascii';
            $Charset =~ s/^(iso)[\-_]?(\d+)[\-_](\d+)[\-_]?\w*/$1-$2-$3/i;

            eval { $BodyText = decode($Charset, $BodyText); };
          }

          my @Lines = CleanBodyText($BodyText, $Type);

          # Show the first 3 lines or so
          if ($PeekOutput == 1) {

            $BodyText = substr(join("\n", @Lines[0 .. (@Lines < 3 ? @Lines-1 : 2)]), 0, 1000) . "\n";

          } elsif ($PeekOutput == 2) {
            # Show only 1 line with <CR>'s replaced with \

            # Only first 8 lines and/or 200 chars
            $BodyText = substr(join($Self->{PeekSep} // " \\ ", @Lines[0 .. (@Lines < 8 ? @Lines-1 : 7)]), 0, 200) . "\n";
          } 

          # Store back into row data
          $Uid2RowMap{$Uid}->{BodyPeek} = $BodyText;
          $Uid2RowMap{$Uid}->{BodyType} = $Type;
        }
      }

    }


...

And here's the annotator that runs inside our server now, which calculates image sizes for attached images, a preview, and a bunch of things calculated from headers.

sub MakePreview {
    my ($message, $Parts) = @_;

    my ($Part, $Type) = ($Parts->{text}, 'text');

    # If no text part, but an HTML part, use that
    if (!$Part && exists $Parts->{html}) {
      ($Part, $Type) = ($Parts->{html}, 'html');
    } elsif ($Part) {
      $Type = 'rtf' if lc $Part->{'MIME-Type'} eq 'text/enriched';
    }

    my $Preview = "";
    if ($Part) {
      my $CharSet = lc($Part->{'Content-Type'}->{charset} // '');

      my $Content = $message->read_part_content($Part, MAX_CONTENT);
      $Content = MEDecodeBody($Content, $CharSet);

      my @Lines = clean_body_text($Content, $Type);

      # Want at least 3 lines or 160 characters of preview
      my ($Pos, $Length) = (0, 0);
      while ($Length < 160 && $Pos < @Lines) {
	$Length += length($Lines[$Pos++]) + 1;
      }
      $Pos = 3 if $Pos < 3;
      splice(@Lines, $Pos) if $Pos < @Lines;

      $Preview = join "\n", @Lines;
    }

    return Encode::encode_utf8($Preview);
}

And the client just does this:

    # Get previews for messages we need previews for {{{

    if (my @NeedPeekUids = grep { $NeedMoreUids{$_}->{NeedPeek} } @NeedMoreUids) {

      warn "getting preview for uids=" . join(" ", @NeedPeekUids) if DEBUG;

      my @WantItems = ("annotation", [ "/vendor/messagingengine.com/preview", "value.shared" ]);
      my $IMAPAnnot = $Mailbox->fetch(\@NeedPeekUids, \@WantItems)
        || die "IMAP fetch failed - $@ - items=" . join(" ", @WantItems) . ", uids=" . join(",", @NeedPeekUids);

      my $PeekSep = $Opts{PeekSep} // $Self->{PeekSep} // " \\ ";

      # Now extra data we need
      foreach my $Uid (@NeedPeekUids) {

        my $Row = $Uid2RowMap{$Uid};
	$Row->{BodyPeek} = '';

        # Message can always disappear, handle sanely
        my $MsgAnnot = $IMAPAnnot->{$Uid} // next;
	$MsgAnnot = $MsgAnnot->{annotation} // next;
	$MsgAnnot = $MsgAnnot->{"/vendor/messagingengine.com/preview"}->{"value.shared"} // next;

        # Data is utf-8 octets, \n separated lines
	my @Lines = split /\n/, decode_utf8($MsgAnnot);

        my $BodyText = '';

	# 3 lines
	if ($PeekOutput == 1) {

          splice(@Lines, 3) if @Lines > 3;
	  $BodyText = substr(join("\n", @Lines), 0, 1000) . "\n";

	# 1 line with <CR>'s replaced with \
	} elsif ($PeekOutput == 2) {

	  # Only first 8 lines and/or 130 chars
	  splice(@Lines, 8) if @Lines > 8;
	  $BodyText = substr(join($PeekSep, @Lines), 0, 130);
	}

	# Store back into row data
	$Row->{BodyPeek} = $BodyText;
      }
    }


Significantly simpler to implement on the client, and fewer round trips as well.  Best of all, you calculate it ONCE and store it on the server, rather than having to either cache every single one you ever see, or potentially have to re-calculate it every time you go back to a mailbox you haven't seen for a while.

Bron.

-- 
  Bron Gondwana
  brong@fastmail.fm


From nobody Tue Dec  2 13:57:00 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 B97731A6F2E for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 13:56:59 -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 05N9KmYOmrKd for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 13:56:54 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E29E41A7022 for <imapext@ietf.org>; Tue,  2 Dec 2014 13:56:51 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 1311FFA001D; Tue,  2 Dec 2014 21:56:50 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1417557409-22718-22717/11/4; Tue, 2 Dec 2014 21:56:49 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Tue, 2 Dec 2014 22:56:49 +0100
User-Agent: Trojita/v0.4.1-243-g4a74770; Qt/4.8.6; X11; Linux; Ubuntu 14.04.1 LTS
Mime-Version: 1.0
Message-Id: <94c50f02-edea-457f-8541-5e3d00a5fad1@gulbrandsen.priv.no>
In-Reply-To: <1417554472.2253074.197997697.17E6A5B4@webmail.messagingengine.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no> <CE219298B9139C8F3B005BD7@caldav.corp.apple.com> <96577a94-dc15-4f46-8aad-dc8767b671ee@gulbrandsen.priv.no> <1417554472.2253074.197997697.17E6A5B4@webmail.messagingengine.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/VdMc4aMPQEO7N7Pf5sRuc5jmdoM
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 21:57:00 -0000

That's a really good solution. Very much better than e.g. unextended IMAP, 
and even better than base IMAP + Cyrus' proposal, except for one thing: It 
seems to me to have a baseline-like character rather than an extension-like 
character. I don't see that sensible clients would support stock IMAP and 
use your (otherwise fine) extension if present.

If the goal is to produce something that mobile clients can require and 
use, while dropping support for unextended IMAP, then I'm all for your 
proposal.

Arnt


From nobody Tue Dec  2 15:35:48 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 C82541A6EE0 for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 15:35:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.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, GB_I_INVITATION=-2, 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 E_rIVzPppDBR for <imapext@ietfa.amsl.com>; Tue,  2 Dec 2014 15:35:43 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 685471A1BD2 for <imapext@ietf.org>; Tue,  2 Dec 2014 15:35:43 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D8997208FF for <imapext@ietf.org>; Tue,  2 Dec 2014 18:35:42 -0500 (EST)
Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Tue, 02 Dec 2014 18:35:42 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:x-sasl-enc:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=mesmtp; bh=c01VWkwnMKxgn+rpan/hn6xgjyI=; b=LeK/ tz7hf8SS01fa53K/fqmgO+NUvXONjzw77TjpGof+b2WIIuMbgVhBYDeyVUujvO90 7/fpG5BjAI9J2hl+xdR9AXqlKdXj/xuQRDPUYLgbb23869IZ87T43eYFiQyzL01t imKVAsbGLJNXNPW0JuSyNtDL8W24hb4bPhlnphc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=c01VWkwnMKxgn+rpan/hn6xg jyI=; b=oPkpoMfhU4xPQY/Di3anH/9dfi6ma99c44FCVMaLjhyIq2g9Bfmae4+0 34ehelQFuXvsM4UEzK+bN2vGmmU36NJEKJYjTbcIGk8lIJixTL7MQgRP19Ojg6Md rELX6pPtVGuOnvVLMJlEFxhJU6lTyZ7GGjHrdNXEJY/9Co2URyA=
Received: by web3.nyi.internal (Postfix, from userid 99) id ACDC81007E8; Tue,  2 Dec 2014 18:35:42 -0500 (EST)
Message-Id: <1417563342.2658798.198063145.6BFFCD06@webmail.messagingengine.com>
X-Sasl-Enc: mzvSa9BiLd5rwNFpnEbfOaxHnOpDLMbwSOGquyp+WUZR 1417563342
From: Bron Gondwana <brong@fastmail.fm>
To: imapext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-53201334
In-Reply-To: <330724e6-c365-4eec-844a-57d16f174432@flaska.net>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net>
Date: Wed, 03 Dec 2014 10:35:42 +1100
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/ALPYFvbyVbI6yWnHnHquIFnFB3U
Subject: Re: [imapext] Fetching short text snippet for mails
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, 02 Dec 2014 23:35:46 -0000

On Wed, Dec 3, 2014, at 05:08 AM, Jan Kundr=E1t wrote:
> What I would like much more is something "smarter", even if with an
> implementation-defined exact behavior. Finding a textual part is not
> particularly compelling. It should strip away quotations (and do it
> smartly, ignoring the leading "Hi John," or "On ABC, XYZ wrote"
> prefixes), kill the signature, notice that it's a meeting invitation
> from Exchange and display the subject/note along with time and
> location, etc.
>
> Of course this cannot possibly be specified by an RFC. What I'm
> arguing against is specifying this extension to only extract a chunk
> of bytes from a first textual part.

It's like FUZZY search.  Rather than specifying an exact algorithm which
can be identical in every server, we're much better off saying "present
a preview that gives a brief overview of what's in the message" and let
the server calculate it as it sees fit.

> An extension which I would like to use would use loose wording such as
> "return a textual preview of the e-mail, using implementation defined
> heuristics for determining the content of the response". The RFC can
> then go ahead and suggest what the typical steps to be performed are.
>
> It would be nice to also have a command which returns back the
> supported features of this convertor/extractor. One could go as far
> as to maintain a IANA list of the capabilities, but that is
> probably an overkill :). I can certainly see a couple of use cases
> for that, though.

Yeah, definitely overkill.

The one thing that we have at FastMail above this basic preview which is
pretty nice is a search-snippet version  which takes a search phrase and
returns a couple of parts of text around the matches from that search.

http://i.imgur.com/jf2k6gI.png

This is different from the normal previews:

http://i.imgur.com/EuhmfgR.png

Bron.

--=20
  Bron Gondwana
  brong@fastmail.fm


From nobody Wed Dec  3 04:35:40 2014
Return-Path: <alexey.melnikov@isode.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 091571A1ADF for <imapext@ietfa.amsl.com>; Wed,  3 Dec 2014 04:35:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.71
X-Spam-Level: 
X-Spam-Status: No, score=-1.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 JIBB-J_61Sqv for <imapext@ietfa.amsl.com>; Wed,  3 Dec 2014 04:35:38 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD911A1A93 for <imapext@ietf.org>; Wed,  3 Dec 2014 04:35:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1417610137; d=isode.com; s=selector; i=@isode.com; bh=sBWo9B9ouu3lJ/OgimOYaOCoXWnCgFCB8fHZNBAetUg=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Fk+Khei5VOlS+4Q8bjx7e9RpNcWdYGeNnE4L4MfVIuqLfbA4sM3XpddzHfiwZyROKWoySc L8px/blV6azOk8RJTNLlBzwXVwUW4kVVABUJGIycgeFcTLCr9qfN6RsZ8kBSpFkuy1oUL9 kPQ0FZlkIhq4xTjyZwNL8Zcnh7lHIbA=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <VH8DmABH1Yxb@waldorf.isode.com>; Wed, 3 Dec 2014 12:35:37 +0000
Message-ID: <547F0303.2080702@isode.com>
Date: Wed, 03 Dec 2014 12:33:07 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: =?UTF-8?B?SmFuIEt1bmRyw6F0?= <jkt@flaska.net>, imapext@ietf.org
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <CAKHUCzz6JjQ9o7T8Nx5f6zOEExCyX-J9VNVXDAnze=2Dmoxxqg@mail.gmail.com> <88b853db-cdbd-457b-8212-096b5dd48a14@flaska.net>
In-Reply-To: <88b853db-cdbd-457b-8212-096b5dd48a14@flaska.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-transfer-encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/OavJ4iUcVMWp0WQk1ZTaoGMUda8
Subject: Re: [imapext] Fetching short text snippet for mails
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, 03 Dec 2014 12:35:39 -0000

On 02/12/2014 11:37, Jan Kundr=C3=A1t wrote:
> On Tuesday, 2 December 2014 11:37:37 CEST, Dave Cridland wrote:
>> I also wonder about making this more generic, as a THUMBNAIL
> That's exactly what CONVERT is doing.
It is. And if one doesn't implement complicated conversion parameters,=20
supported MIME type discovery, this would be an easy use case:

c001 UID CONVERT 2001 ("TEXT/PLAIN") BINARY[1]<1.100>

> There's probably a reason nobody implements CONVERT, so I suggest not=20
> to make this proposal any more generic.


From nobody Wed Dec  3 11:06:58 2014
Return-Path: <paul@pscs.co.uk>
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 01B331A1A06 for <imapext@ietfa.amsl.com>; Wed,  3 Dec 2014 02:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 a6KBB0-D5_As for <imapext@ietfa.amsl.com>; Wed,  3 Dec 2014 02:43:33 -0800 (PST)
Received: from mail.pscs.co.uk (mail.pscs.co.uk [188.65.177.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B9AB1A0461 for <imapext@ietf.org>; Wed,  3 Dec 2014 02:43:32 -0800 (PST)
Authentication-Results: mail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=paul
Received: from lmail.pscs.co.uk ([82.68.5.206]) by mail.pscs.co.uk ([188.65.177.237] running VPOP3) with ESMTP for <imapext@ietf.org>; Wed, 3 Dec 2014 10:48:03 -0000
Authentication-Results: lmail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=paul
Received: from [192.168.66.101] ([192.168.66.101]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTP for <imapext@ietf.org>; Wed, 3 Dec 2014 10:42:12 -0000
Message-ID: <547EE903.5090900@pscs.co.uk>
Date: Wed, 03 Dec 2014 10:42:11 +0000
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: imapext@ietf.org
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no>
In-Reply-To: <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V6.11 - Registered
X-Organisation: Paul Smith Computer Services
X-Authenticated-Sender: paul
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/RXEkMGFTLG_eUsnS795drQhRl3g
X-Mailman-Approved-At: Wed, 03 Dec 2014 11:06:56 -0800
Subject: Re: [imapext] Fetching short text snippet for mails
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, 03 Dec 2014 10:43:36 -0000

On 02/12/2014 17:06, Arnt Gulbrandsen wrote:
> On Tuesday, December 2, 2014 5:37:31 PM CEST, Cyrus Daboo wrote:
>> Efficient as in eliminating the current extra round trip of doing a 
>> FETCH BODY.PEEK[<section>]<<partial>>? If so, then I think "SNIPPET" 
>> should be an alias for BODY.PEEK[the first significant text 
>> section]<<partial>>. i.e., the server does not do anything more than 
>> determine the "the first significant text section". The client still 
>> gets to use <<partial>> as it could today.
>
> This I like. Simple for the server, simple for the client, a clear win 
> for the client. The only disadvantage is that the client still has to 
> do the heavy text extraction. But it needs that code anyway if it is 
> to work with unextended servers.
Agreed

You aren't going to be able to solve the problem perfectly to everyone's 
satisfaction - at least not in an extension which will ever be 
implemented widely.

So, keep it simple, and make things *better* than they are now. Servers 
implementers will include simple extensions, and the client will benefit 
somewhat. No, it may not be perfect, but it's better than now.

You could go a step further and say that SNIPPET should strip HTML 
control code out of any HTML sections (as long as the rules for doing so 
are defined in the RFC, eg tags, text between <style></style> tags, etc)



-


Paul Smith Computer Services
Tel: 01484 855800
Vat No: GB 685 6987 53

Sign up for news & updates at http://www.pscs.co.uk/go/subscribe


From nobody Thu Dec  4 06:04:38 2014
Return-Path: <dave@cridland.net>
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 CFABA1AD3AC for <imapext@ietfa.amsl.com>; Thu,  4 Dec 2014 06:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 kKjcd9Ow8XNS for <imapext@ietfa.amsl.com>; Thu,  4 Dec 2014 06:04:35 -0800 (PST)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CCF31AD392 for <imapext@ietf.org>; Thu,  4 Dec 2014 06:04:35 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id wp4so2825339obc.11 for <imapext@ietf.org>; Thu, 04 Dec 2014 06:04:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SU4gxFmOWIbuml7jkxpapD3JUMW93GnRTpOGEZwGVSE=; b=POzbvgoKm1SUu50wCc5g57xSx1ga0pYcAemKBGhvrMOyTHUwOFnCLnq1PnYNVyrdg3 om4L/ah2RInaqnRUZUjKIJRZy1aBAdImLKfrSfLW9EI5qbE9ejWv5FbNG+OgmYllUrmX PcDx492b1jUeBgLpfJUH7E7H//Jx74bDsBXFI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=SU4gxFmOWIbuml7jkxpapD3JUMW93GnRTpOGEZwGVSE=; b=JpzzqKnZYmhYC6o/LdK3C8crA9WL4z3ruEm47jJGVAmR/l3PmUwGIGyq7UxANP1MZA zjsdZ81R+vVb3sX3In9akyg3451rX1FtSXvPkgP5bzGNGqdAelwci6Xv1WT0skPjj3sc SRCKa4TbKJSam58IHVUie4Gpl2VGtwRFEUKZqW4c3O+ZVC3J5nz6sUzT0RMZrgLhdagB xUj9KtBWb88VSNYBGJxxGrIU/aCn6Ods9O52aGmPzdGE33lBjV9N0D+xHWI+gbHfbDyB vvai014expCZ5rWJKNcckm46Sh/A1MlyhaQ2jEJ/viUwNyDPU7vv6tXCeKnC/1flCZKo AIeA==
X-Gm-Message-State: ALoCoQme5urZGCkM/qMgTGtsryTNPLP7u3u1Lg90FSSgjdlPLJI0qAuOBW2xP3CFfeFeYWZ2+YzK
MIME-Version: 1.0
X-Received: by 10.182.33.232 with SMTP id u8mr6747927obi.54.1417701874564; Thu, 04 Dec 2014 06:04:34 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Thu, 4 Dec 2014 06:04:34 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Thu, 4 Dec 2014 06:04:34 -0800 (PST)
In-Reply-To: <547EE903.5090900@pscs.co.uk>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no> <547EE903.5090900@pscs.co.uk>
Date: Thu, 4 Dec 2014 14:04:34 +0000
Message-ID: <CAKHUCzy01RBUqsrds=+QBZpRLUCQBqJ5b4-J_GF2fGfpsMMCsA@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Paul Smith <paul@pscs.co.uk>
Content-Type: multipart/alternative; boundary=001a11c2d0c6a1999c050964700e
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/pzln3Bk85RiTV4Dnj7TQut51MHw
Cc: imapext@ietf.org
Subject: Re: [imapext] Fetching short text snippet for mails
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, 04 Dec 2014 14:04:37 -0000

--001a11c2d0c6a1999c050964700e
Content-Type: text/plain; charset=UTF-8

On 3 Dec 2014 19:06, "Paul Smith" <paul@pscs.co.uk> wrote:
> You could go a step further and say that SNIPPET should strip HTML
control code out of any HTML sections (as long as the rules for doing so
are defined in the RFC, eg tags, text between <style></style> tags, etc)

This is exactly what I think doesn't need specifying. It doesn't matter if
every implementation generates a slightly different snippet, it just
matters that a client can get it in the same way.

Dave.

--001a11c2d0c6a1999c050964700e
Content-Type: text/html; charset=UTF-8

<p dir="ltr"><br>
On 3 Dec 2014 19:06, &quot;Paul Smith&quot; &lt;<a href="mailto:paul@pscs.co.uk">paul@pscs.co.uk</a>&gt; wrote:<br>
&gt; You could go a step further and say that SNIPPET should strip HTML control code out of any HTML sections (as long as the rules for doing so are defined in the RFC, eg tags, text between &lt;style&gt;&lt;/style&gt; tags, etc)</p>
<p dir="ltr">This is exactly what I think doesn&#39;t need specifying. It doesn&#39;t matter if every implementation generates a slightly different snippet, it just matters that a client can get it in the same way.</p>
<p dir="ltr">Dave.<br>
</p>

--001a11c2d0c6a1999c050964700e--


From nobody Fri Dec  5 14:03:06 2014
Return-Path: <nicolson@google.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 781841A1BDA for <imapext@ietfa.amsl.com>; Fri,  5 Dec 2014 14:02:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level: 
X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 QZhUOw4kXtZg for <imapext@ietfa.amsl.com>; Fri,  5 Dec 2014 14:02:55 -0800 (PST)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE6281A1B69 for <imapext@ietf.org>; Fri,  5 Dec 2014 14:02:54 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id tr6so1591515ieb.17 for <imapext@ietf.org>; Fri, 05 Dec 2014 14:02:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=D1QfFAElg+0qaQ+WakN7GUC7op8Xc1zOKOuyLmzQKZ8=; b=lf402Shboq44UG4shAF5jVm7V2lxWSqAxV7QBW51ve2ssS1gfvZPIgo/BFCdqgVUXV 2//Swip00X3nTHW5kVfqPobEvQGskK9140UK0uHztPUkXhbhaDk7causIw29ZxjzwBFT 4RitrilWtJKNFx1pgkNBjtleZYYo+8kiOr4iEGzBAxQCd/n9IBnNPbz4xc4Ua9QsqnXI OAkP+5rJ7lftHg+rL6yk0asKjP99bQCYphIqa1OiQegb99yupHESjdgELJho6eHvuSul W97f7H8o/sJ4ndY5ZgnhJW8NiqNHB8mYhRTr0WVDGJGulvgfqGPSLnYXZoQFx8m2YBTA hHEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=D1QfFAElg+0qaQ+WakN7GUC7op8Xc1zOKOuyLmzQKZ8=; b=QjQMTBsX9RWLwjtp5C7ricYKsIdiiPJmLTfvHtlbrbuhfRx03xRQ/6/c7J/kbldvp/ eUHZvdWlzu+Hys81qO9wSr/w6f9wZcsm6JkICka0jScR5clN2VC3UbNt/os7j+FOSPP2 tjl/3XC5cl5Bd3w81t9LZOpsT/LghOfl/5LH7SaNQzZPnewt3Juoi8AOCT0iVQZY1WZr xm9Pbq9kmxJmznRcy/bGuI7sHIH38PjZKTHvwdSm1E9xvIuOgfuu2EPO4SIqjxamGNer OLj9w0rG1/LQ+XpljGBiZAhqJ4Ea6sjweL/PPFLvNq6Hvru9F/bNmp/PI05pixa6dFBi AdzA==
X-Gm-Message-State: ALoCoQnjPV/Uy2mwRVKXdMTJER/2kTjkW2Y27oHGezInvGsWCNK7TNdU4KsxNoL2Sz1c3pvN8X6f
X-Received: by 10.50.29.3 with SMTP id f3mr4654138igh.23.1417816973893; Fri, 05 Dec 2014 14:02:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.1.165 with HTTP; Fri, 5 Dec 2014 14:02:23 -0800 (PST)
From: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Date: Fri, 5 Dec 2014 14:02:23 -0800
Message-ID: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com>
To: imapext@ietf.org
Content-Type: multipart/alternative; boundary=047d7bd74b5416000605097f3d4b
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/Y0_hanRlV7ZTm4v5X4brBXbL3Ec
Subject: [imapext] client support for RFC 3516 (BINARY)?
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, 05 Dec 2014 22:03:02 -0000

--047d7bd74b5416000605097f3d4b
Content-Type: text/plain; charset=UTF-8

Anyone know of clients that support RFC 3516? It seems like it could be
particularly useful for mobile clients, to reduce both download size and
CPU usage for base64-decoding.

--047d7bd74b5416000605097f3d4b
Content-Type: text/html; charset=UTF-8

<div dir="ltr">Anyone know of clients that support RFC 3516? It seems like it could be particularly useful for mobile clients, to reduce both download size and CPU usage for base64-decoding.</div>

--047d7bd74b5416000605097f3d4b--


From nobody Fri Dec  5 14:42:52 2014
Return-Path: <dave@cridland.net>
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 2A3661A6FB0 for <imapext@ietfa.amsl.com>; Fri,  5 Dec 2014 14:42:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.078
X-Spam-Level: 
X-Spam-Status: No, score=-1.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 uzBv-3SzH0sZ for <imapext@ietfa.amsl.com>; Fri,  5 Dec 2014 14:42:41 -0800 (PST)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4A2F1A6FA3 for <imapext@ietf.org>; Fri,  5 Dec 2014 14:42:41 -0800 (PST)
Received: by mail-oi0-f41.google.com with SMTP id a3so1147165oib.28 for <imapext@ietf.org>; Fri, 05 Dec 2014 14:42:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VlwzASsmwtcqJTLilChxy+IFIJWHLkyfNoVy0MniRNM=; b=TqeAFTbY1Z8eDz8+DGOm3O7eAvp8ud7aUP1hxvousgIk/hR90YOAo6PtbNKHI984k1 RcXKUZZ3ulhXvEFdjE3xzv3N9j7560ccRfaM2rQiDG3AmSIa4/r9JxfEykr1OIQhxgXN Gq+YPObZd5PFnUjoJmRZPk5n/KBPSa59mt7wE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=VlwzASsmwtcqJTLilChxy+IFIJWHLkyfNoVy0MniRNM=; b=SOfpvIyw/EaCqOBjXDcRV/mj2/JLtSxOD2jsYzD47sPjZ6pOeEh8uhfFJu5h1TdX1Q C9cydBqqhcP4r03eXidUG+I5VjG4StXntG0f4GM8iDWClM9+56muN6gEV/GhF/czq8Dt 1SbrGYX6Eqo8B2R53fTr80hHjsx/jqH+hyB7mX+KNJ4wgRLj8jiY05CMUI/rGj4+C1gy ax9TcxE1l9X7MYFzj4wna14T3mLPzzZVrcO3hX6ISbO2vcGk1AGqvyKL4pCOa3DHt9RO izTF4rijcDT+0WTiDhDrLItfu1JyDrUTn+FOBh3vKYsJPV7dLuMCPwYyIIGabVqukj7Z Pqcw==
X-Gm-Message-State: ALoCoQni3bGm22CxSmjn37XyOZCLYUjCI8YY4d87dz9+8JqlmoBxb/QtyUFomslX1YeFvqYvqxmi
MIME-Version: 1.0
X-Received: by 10.60.123.77 with SMTP id ly13mr192128oeb.79.1417819361043; Fri, 05 Dec 2014 14:42:41 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Fri, 5 Dec 2014 14:42:40 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Fri, 5 Dec 2014 14:42:40 -0800 (PST)
In-Reply-To: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com>
Date: Fri, 5 Dec 2014 22:42:40 +0000
Message-ID: <CAKHUCzxw0H9DGHNtOGPjsEufd-z1=EHBrjF4sXm-u+SOccq+1w@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Content-Type: multipart/alternative; boundary=047d7b5d39165f06f805097fcb65
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/XGkQTrRj_0TcAw98oW8To6sm6b4
Cc: imapext@ietf.org
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 05 Dec 2014 22:42:43 -0000

--047d7b5d39165f06f805097fcb65
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 5 Dec 2014 22:03, "Jamie Nicolson (=E5=80=AA=E5=BF=97=E6=98=8E)" <nicols=
on@google.com> wrote:
>
> Anyone know of clients that support RFC 3516? It seems like it could be
particularly useful for mobile clients, to reduce both download size and
CPU usage for base64-decoding.
>

I have a vague recollection that it's in Inky, http://inky.com/ - it's
something of a no brainer to support in a client, in any case. Servers have
to handle binary append, such is somewhat harder.

Dave.

--047d7b5d39165f06f805097fcb65
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On 5 Dec 2014 22:03, &quot;Jamie Nicolson (=E5=80=AA=E5=BF=97=E6=98=8E)&quo=
t; &lt;<a href=3D"mailto:nicolson@google.com">nicolson@google.com</a>&gt; w=
rote:<br>
&gt;<br>
&gt; Anyone know of clients that support RFC 3516? It seems like it could b=
e particularly useful for mobile clients, to reduce both download size and =
CPU usage for base64-decoding.<br>
&gt;</p>
<p dir=3D"ltr">I have a vague recollection that it&#39;s in Inky, <a href=
=3D"http://inky.com/">http://inky.com/</a> - it&#39;s something of a no bra=
iner to support in a client, in any case. Servers have to handle binary app=
end, such is somewhat harder.</p>
<p dir=3D"ltr">Dave.</p>

--047d7b5d39165f06f805097fcb65--


From nobody Fri Dec  5 15:56:26 2014
Return-Path: <slusarz@horde.org>
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 BDD231A872B for <imapext@ietfa.amsl.com>; Fri,  5 Dec 2014 15:56:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 XLXxptR7HNTg for <imapext@ietfa.amsl.com>; Fri,  5 Dec 2014 15:56:23 -0800 (PST)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1907E1A6F0D for <imapext@ietf.org>; Fri,  5 Dec 2014 15:56:23 -0800 (PST)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-10v.sys.comcast.net with comcast id Pzvw1p00B2Udklx01zwNCp; Fri, 05 Dec 2014 23:56:22 +0000
Received: from bigworm.curecanti.org ([67.176.83.228]) by resomta-ch2-18v.sys.comcast.net with comcast id PzwM1p0094vagWz01zwMer; Fri, 05 Dec 2014 23:56:22 +0000
Received: from bigworm.curecanti.org (localhost.localdomain [IPv6:::1]) (Authenticated sender: slusarz) by bigworm.curecanti.org (Postfix) with ESMTPSA id B02306809B for <imapext@ietf.org>; Fri,  5 Dec 2014 16:56:20 -0700 (MST)
Received: from dangerzone.curecanti.org (dangerzone.curecanti.org [172.18.5.4]) by bigworm.curecanti.org (Horde Framework) with HTTP; Fri, 05 Dec 2014 16:56:20 -0700
Date: Fri, 05 Dec 2014 16:56:20 -0700
Message-ID: <20141205165620.Horde.-sbLV87XYRYWrxO72a0ZAQ6@bigworm.curecanti.org>
From: Michael M Slusarz <slusarz@horde.org>
To: imapext@ietf.org
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CAKHUCzxw0H9DGHNtOGPjsEufd-z1=EHBrjF4sXm-u+SOccq+1w@mail.gmail.com>
In-Reply-To: <CAKHUCzxw0H9DGHNtOGPjsEufd-z1=EHBrjF4sXm-u+SOccq+1w@mail.gmail.com>
User-Agent: Horde Application Framework 5
Accept-Language: en
X-Originating-IP: 172.18.5.4
X-Remote-Browser: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417823782; bh=7riQL2N0Ch2YxP3DZltCda1rJf8cXtZDc4zqhxGe/QA=; h=Received:Received:Received:Received:Date:Message-ID:From:To: Subject:Content-Type:MIME-Version; b=ERCrew+6Vh62PF94tOSLU3jL8F0aRMmF9NQPwhJgGq5rP19MRnai+tthPoS6Ao9m4 cccRAaLzvHkLfpXt9iGlu8H1MNGmGvabQXkNOtMvo4RBgjFOVeA/ESJ/z6HEFRjJ6/ PjX2jE0dU6viRc5DHDP3IAr3SvGSGjRHNyPDNiacRW4c1VhaDMwWWxk7tc6sfcqSqa lHcsrDokzhHoFYMIU27i5ESA6tHliBnTm3xhOViq0pS/yF1UpXMnVBvxEA4h+n5fRW 9Fh6SlbiDG0wOcABOHbVFCgBPIh0juAoyzwc5D2TdsrpdlgoowXR/CPgwER18gB+FI CcYtv31RYTc5A==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/G3W8IstRbuyGBNZ9ff6cMwYJPgQ
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 05 Dec 2014 23:56:25 -0000

Quoting Dave Cridland <dave@cridland.net>:

> On 5 Dec 2014 22:03, "Jamie Nicolson (å€ªå¿—æ˜Ž)" <nicolson@google.com> wrote:
>>
>> Anyone know of clients that support RFC 3516? It seems like it could be
> particularly useful for mobile clients, to reduce both download size and
> CPU usage for base64-decoding.
>>
>
> I have a vague recollection that it's in Inky, http://inky.com/ - it's
> something of a no brainer to support in a client, in any case. Servers have
> to handle binary append, such is somewhat harder.

Horde/IMP uses binary, if available, to FETCH binary data.  As Dave  
mentions, this is trivial to do in a client (if BINARY FETCH data is  
available, you just skip all the code client-side that does the  
transfer-decoding).

Might as well add some additional notes here, as they may possible be  
of interest to future implementers...

Current (or at least recent-ish versions) servers do several different  
things when they encounter bad encoded data.  See, e.g.:

http://markmail.org/message/anldcux5fhqz6m65

Dovecot used to issue NIL ... newer versions still issue NIL but with  
a UNKNOWN-CTE response.  Cyrus does the best it can to decode and  
returns that data.

This can be seen as a limitation of the current BINARY spec, since it  
isn't obvious which (if any) of these responses are correct.  Speaking  
as a client author, I just care about the UNKNOWN-CTE response though  
since that leaves open the possibility of fetching the unencoded part  
and dealing with broken transfer-encoding the way that I want to.

BINARY APPENDs are a different story though.  It is broken on multiple  
servers, and in several different ways.  At a minimum, versions of  
UW-IMAP, Cyrus, and Sun Java System Messaging have problems.  IIRC,  
one of the issues is that these servers have issues with the literal8  
format.  It's so widespread that we've disabled LITERAL+ entirely when  
appending BINARY data in order to prevent unneeded traffic.  (We  
normally use LITERAL+ for small APPENDs as a compromise between the  
need to catch errors before sending the data - RFC 4549 - and the  
benefits of pipelining).

My thought originally was, if BINARY was available, then always APPEND  
using that because it prevents us from having to scan the output data  
on the client side to determine whether the data really was binary  
(null, long-lines) or not.  But the above described server issues  
encountered ended that experiment fairly quickly.

michael

___________________________________
Michael Slusarz [slusarz@horde.org]


From nobody Fri Dec  5 16:25:44 2014
Return-Path: <slusarz@horde.org>
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 787021A86EE for <imapext@ietfa.amsl.com>; Fri,  5 Dec 2014 16:25:42 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 AP8nJOzPARmH for <imapext@ietfa.amsl.com>; Fri,  5 Dec 2014 16:25:40 -0800 (PST)
Received: from resqmta-po-09v.sys.comcast.net (resqmta-po-09v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:168]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B729B1A8549 for <imapext@ietf.org>; Fri,  5 Dec 2014 16:25:40 -0800 (PST)
Received: from resomta-po-01v.sys.comcast.net ([96.114.154.225]) by resqmta-po-09v.sys.comcast.net with comcast id Q0Qg1p0024s37d4010RgUM; Sat, 06 Dec 2014 00:25:40 +0000
Received: from bigworm.curecanti.org ([IPv6:2002:43b0:53e4:0:21e:68ff:fe1e:2860]) by resomta-po-01v.sys.comcast.net with comcast id Q0Rf1p00Q3cyTSr010RgqL; Sat, 06 Dec 2014 00:25:40 +0000
Received: from bigworm.curecanti.org (localhost.localdomain [IPv6:::1]) (Authenticated sender: slusarz) by bigworm.curecanti.org (Postfix) with ESMTPSA id E146F6809B for <imapext@ietf.org>; Fri,  5 Dec 2014 17:25:38 -0700 (MST)
Received: from dangerzone.curecanti.org (dangerzone.curecanti.org [172.18.5.4]) by bigworm.curecanti.org (Horde Framework) with HTTP; Fri, 05 Dec 2014 17:25:38 -0700
Date: Fri, 05 Dec 2014 17:25:38 -0700
Message-ID: <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org>
From: Michael M Slusarz <slusarz@horde.org>
To: imapext@ietf.org
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net>
In-Reply-To: <330724e6-c365-4eec-844a-57d16f174432@flaska.net>
User-Agent: Horde Application Framework 5
Accept-Language: en
X-Originating-IP: 172.18.5.4
X-Remote-Browser: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417825540; bh=VzzvserZZ9nepo5qPRlnSaWDM/OtG082SAEkMRN/zgM=; h=Received:Received:Received:Received:Date:Message-ID:From:To: Subject:Content-Type:MIME-Version; b=i5sNj0YH5i1N55/t9bR4A466fy1ilas20gN8Y8Xsw2dhQ7n1YnUAlWAnvB+uZo65X o5j3tCYkicazAIthlg67P5+eDe8Sq5DW88g7q6ikJUi6Z6QWZuO3hBzsIrO5RAznpo UgI2U7rjLKxWEqzZnZhvLITqTTwDVVY62cEms7E1PqlEX3SBfr/4bCS8qpAFO8GoRP 8npG1KWQM7JSBxlem+FHaHcLAHEgzIr7NumfjPrONabAe1lDwVuu/MT83FRzuWzQtc RCecDncxWTUiooj1EK91Plaw7S0DYdb+AQfLmXrJi7a1Qcd2Z1E6rXIANrPzgb05H5 OHYd77M6+mo0A==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/eUEssS2CZsrrVQ6la16bMOc-Wwg
Subject: Re: [imapext] Fetching short text snippet for mails
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, 06 Dec 2014 00:25:42 -0000

Quoting Jan KundrÃ¡t <jkt@flaska.net>:

> On Tuesday, 2 December 2014 17:37:31 CEST, Cyrus Daboo wrote:
>> Efficient as in eliminating the current extra round trip of doing a  
>> FETCH BODY.PEEK[<section>]<<partial>>?
>
> I don't think a roundtrip would be neccessary.
>
> Sure, the client doesn't know whether it's a single-part text/plain,  
> or if it's a multipart/mixed with plaintext and HTML, or whether  
> it's something yet different. However, there's principally no  
> problem in issuing a blind BODY.PEEK[1] which will "get the right  
> thing" most of the time. One can play it extra-safe and ask for a  
> BODY.PEEK[1.1] as well, these are also pretty popular and the worst  
> case is wasting a tiny amount of bandwidth. It's OK to request a  
> non-existing part in FETCH anyway.

We've found this kind of blind-fetching technique isn't very useful,  
at least coming from the perspective of a client that has to handle  
1000's of concurrent users.

If building a mailbox listing, there's a good chance that  
envelop(-ish) data is cached on the server.  Once you start adding  
body fetches to this mailbox listing it becomes more expensive I/O  
wise to generate these responses.

And this doesn't work very well for multipart/alternative e-mails,  
especially since more and more of those messages have a [1] text/plain  
content of either "Go to URL http://example.com/ to view the contents  
of this message" or an automated down-converted representation of the  
HTML part that is difficult to read.

For a 50,000 foot preview of the message content, I have no issue  
relying on a server to figure out how to parse the  
multipart/alternative message and strip out the HTML tags in order to  
provide something useful.

michael

___________________________________
Michael Slusarz [slusarz@horde.org]


From nobody Fri Dec  5 17:49:09 2014
Return-Path: <nicolson@google.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 AC1371A87D5 for <imapext@ietfa.amsl.com>; Fri,  5 Dec 2014 17:49:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level: 
X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 5uPkFZPe4an0 for <imapext@ietfa.amsl.com>; Fri,  5 Dec 2014 17:49:01 -0800 (PST)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 086381A87C3 for <imapext@ietf.org>; Fri,  5 Dec 2014 17:49:01 -0800 (PST)
Received: by mail-ie0-f170.google.com with SMTP id rd18so1846626iec.1 for <imapext@ietf.org>; Fri, 05 Dec 2014 17:49:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=kS5YX9FheWIV8d5PB5IdZ/9BtQCpDkbV6d44EoKO/VU=; b=VaX54v/b9lpnWKbw4KKmFP/n+QLCi+95m5etOXmUAK1iz8Y+mjp+tjKybaEgrPhZNJ BzpggcGu+nzwZ26bRUTg3Ys9JHnXYMZzfAk+/S9ZQyUuAfG0M+m+ATIExm48yb8Yr8fW 2Fj/Z00TdCMnKPzLV6ssyURetnABsbN6W35H3m15TJNELjBwwOmPGUjq2iB+041YKC/g +rn2uOGRIctB4fNw8p4nFU/b1gRgf5dT1q8gypkK+JDWXV/Ea8KM8cIJX1JsCsfQLV0U 0S2Q9zasvcSu+y/++mvhf2FJkZg84PCxJDSka7gofI63PPH06Zi1WW6+DlKwvwMZYHud dUDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=kS5YX9FheWIV8d5PB5IdZ/9BtQCpDkbV6d44EoKO/VU=; b=kD6/pvrg3xfgtBUg1wcV0H7PFDfuevyR36DY5aCjzVR4r/eoZqJhqY6ONSgAidz4nB cwi2QXJd+2nr8gVGHL50be5jWxk3yRMXi2AfM5VyaaKjxX6qcnecXXh9vYL1O5asjAkR TQxkzLhmEFh22gvUW6C+AXbeewRDA5hJW0qCA5yAlaB4rpfftl7wPrRD8UNx6j18eA5E L8zXnBp7JfOROjiAuzhlKrraMqQLaohPevHJWuUPnnzKLPWr7TDWNbRLeE3VOBt/+zPt nnEkiNAeGINLZSk9uLg8ua36uV8d1wqsPYpmv2Px4fxLVWMXaFFH4W2goegwv1FainUz hiLw==
X-Gm-Message-State: ALoCoQkXeDgrerAo2V1Ln4mFGPxwZj9Mdjp/nf189OJWDEav0Yxnpu+h67ukxwD4wwUBkglIiTQR
X-Received: by 10.50.142.33 with SMTP id rt1mr5376270igb.12.1417830540090; Fri, 05 Dec 2014 17:49:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.1.165 with HTTP; Fri, 5 Dec 2014 17:48:29 -0800 (PST)
In-Reply-To: <CAKHUCzxw0H9DGHNtOGPjsEufd-z1=EHBrjF4sXm-u+SOccq+1w@mail.gmail.com>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CAKHUCzxw0H9DGHNtOGPjsEufd-z1=EHBrjF4sXm-u+SOccq+1w@mail.gmail.com>
From: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Date: Fri, 5 Dec 2014 17:48:29 -0800
Message-ID: <CACU8CfRJ6kTP9Of+DTng-8titS3dTbJveZqhTMZqbP7ee+1-cw@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=001a1130d17ab1c7160509826521
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/lNlduy_YsbyYcqkrXPLH6ZNKU7s
Cc: imapext@ietf.org
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 06 Dec 2014 01:49:03 -0000

--001a1130d17ab1c7160509826521
Content-Type: text/plain; charset=UTF-8

On Fri, Dec 5, 2014 at 2:42 PM, Dave Cridland <dave@cridland.net> wrote:
>
> I have a vague recollection that it's in Inky, http://inky.com/ - it's
> something of a no brainer to support in a client, in any case. Servers have
> to handle binary append, such is somewhat harder.
>

My reading of binary append is just that the server needs to accept the
<literal8> syntax and accept data that contains NULs. The spec allows for
modifying the CTE at append time, but discourages it in section 6 ("this
should only be done when it is absolutely necessary"). So it seems like
supporting binary append should be fairly straightforward.

Are you perhaps referring to the re-encoding of binary data with a
conforming CTE when it is FETCHed with a (non-binary) BODY or
BODYSTRUCTURE? This requirement puzzles me because it seems to be
retroactive, and independent of whether BINARY append is supported. We
already have binary data in our system, and we make no attempt to re-encode
it for IMAP download now, even without implementing BINARY. Is the spec
assuming that, prior to implementing BINARY, there was no way for binary
data to get into the system, and so only a server that supports BINARY
append needs to worry about re-encoding it for download?

--001a1130d17ab1c7160509826521
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Dec 5, 2014 at 2:42 PM, Dave Cridland <span dir=3D"ltr">&lt;<a href=3D"=
mailto:dave@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt;</span=
> wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style=
:solid;padding-left:1ex"><p dir=3D"ltr">I have a vague recollection that it=
&#39;s in Inky, <a href=3D"http://inky.com/" target=3D"_blank">http://inky.=
com/</a> - it&#39;s something of a no brainer to support in a client, in an=
y case. Servers have to handle binary append, such is somewhat harder.</p><=
/blockquote><div><br></div><div style=3D"font-size:12.8000001907349px">My r=
eading of binary append is just that the server needs to accept the &lt;lit=
eral8&gt; syntax and accept data that contains NULs. The spec allows for mo=
difying the CTE at append time, but discourages it in section 6 (&quot;this=
 should only be done when it is absolutely necessary&quot;). So it seems li=
ke supporting binary append should be fairly straightforward.</div><div sty=
le=3D"font-size:12.8000001907349px"><br></div><div><span style=3D"font-size=
:12.8000001907349px">Are you perhaps referring to the re-encoding of binary=
 data with a conforming CTE when it is FETCHed with a (non-binary) BODY or =
BODYSTRUCTURE? This requirement puzzles me because it seems to be retroacti=
ve, and independent of whether BINARY append is supported. We already have =
binary data in our system, and we make no attempt to re-encode it for IMAP =
download now, even without implementing BINARY. Is the spec assuming that, =
prior to implementing BINARY, there was no way for binary data to get into =
the system, and so only a server that supports BINARY append needs to worry=
 about re-encoding it for download?</span>=C2=A0</div></div></div></div>

--001a1130d17ab1c7160509826521--


From nobody Sat Dec  6 01:40:17 2014
Return-Path: <dave@cridland.net>
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 4E02A1A8FD2 for <imapext@ietfa.amsl.com>; Sat,  6 Dec 2014 01:40:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.078
X-Spam-Level: 
X-Spam-Status: No, score=-1.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 PSGy5fAz4WUY for <imapext@ietfa.amsl.com>; Sat,  6 Dec 2014 01:40:14 -0800 (PST)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C75AA1A895E for <imapext@ietf.org>; Sat,  6 Dec 2014 01:40:13 -0800 (PST)
Received: by mail-oi0-f46.google.com with SMTP id h136so1519951oig.33 for <imapext@ietf.org>; Sat, 06 Dec 2014 01:40:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nRkE3eJHoHp911J5h/EZFpfeQQVa2eJ7GZYUKy03RS8=; b=Z8gmxvjA6muvQmM7Hm+eNhxQmAgsatdg4jBZDHhdHpUvWOx39bJ76vA6S6t/jBea3I dU1oCCJ0xyGCFdJIa+RdJka+F//HvQLD3xnpYV01W+gtfx/QYN0+I3iIDxxtfY4kk/4C qo+VqLLlho05fPy+z9unPTNfl0sSJYZGACnIQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=nRkE3eJHoHp911J5h/EZFpfeQQVa2eJ7GZYUKy03RS8=; b=Gkqh+T6imCBrM5e0JaQuW/Yenq2D8Gy8p233dZfkWwsA7VOIW2ShumW5eWsKWbVipq TpyVWcMQukmfw6M1gvcRZ9QgtjCmkn4GXOL6bqaBejfqLRVBUTQEaW/DK+LTwb5PPCMa V8rgK1rxJQGlDpUG+B2+rVmmn8UeH8MffNj7STgmeUiWzCaIFdhLa/ioIkaSpz+psPZ0 jmtqxUkYKPOiLZhy8ZwdZDkc+EX7bjeRFNjfTE5ieamB2lzz4b6zlZvWlqMj18VcPTs2 qNrsslfJTuNwFpopweAJ64533T27e66JVJE0yckVmataewKOJRHiHkvX/bicaAZqqkab zigg==
X-Gm-Message-State: ALoCoQnQBlCj0yZ2p9y2q49ogSfWLnk6xI1iQ8mvWmVz1KOD6uhHqnrlHYRwhNUX1v+hzT2frraL
MIME-Version: 1.0
X-Received: by 10.182.245.231 with SMTP id xr7mr13485895obc.78.1417858813023;  Sat, 06 Dec 2014 01:40:13 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Sat, 6 Dec 2014 01:40:12 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Sat, 6 Dec 2014 01:40:12 -0800 (PST)
In-Reply-To: <CACU8CfRJ6kTP9Of+DTng-8titS3dTbJveZqhTMZqbP7ee+1-cw@mail.gmail.com>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CAKHUCzxw0H9DGHNtOGPjsEufd-z1=EHBrjF4sXm-u+SOccq+1w@mail.gmail.com> <CACU8CfRJ6kTP9Of+DTng-8titS3dTbJveZqhTMZqbP7ee+1-cw@mail.gmail.com>
Date: Sat, 6 Dec 2014 09:40:12 +0000
Message-ID: <CAKHUCzzsAEKLFx2nq7ySaP1zvYrY0mufk9g+7E8QQg=vWpjegA@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Content-Type: multipart/alternative; boundary=001a11c2afd2e47540050988fa45
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/TtYmDqpR5PNEfr5GKQ-8jUARKOo
Cc: imapext@ietf.org
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 06 Dec 2014 09:40:15 -0000

--001a11c2afd2e47540050988fa45
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 6 Dec 2014 01:49, "Jamie Nicolson (=E5=80=AA=E5=BF=97=E6=98=8E)" <nicols=
on@google.com> wrote:
>
> On Fri, Dec 5, 2014 at 2:42 PM, Dave Cridland <dave@cridland.net> wrote:
>>
>> I have a vague recollection that it's in Inky, http://inky.com/ - it's
something of a no brainer to support in a client, in any case. Servers have
to handle binary append, such is somewhat harder.
>
>
> My reading of binary append is just that the server needs to accept the
<literal8> syntax and accept data that contains NULs. The spec allows for
modifying the CTE at append time, but discourages it in section 6 ("this
should only be done when it is absolutely necessary"). So it seems like
supporting binary append should be fairly straightforward.
>
> Are you perhaps referring to the re-encoding of binary data with a
conforming CTE when it is FETCHed with a (non-binary) BODY or
BODYSTRUCTURE? This requirement puzzles me because it seems to be
retroactive, and independent of whether BINARY append is supported. We
already have binary data in our system, and we make no attempt to re-encode
it for IMAP download now, even without implementing BINARY. Is the spec
assuming that, prior to implementing BINARY, there was no way for binary
data to get into the system, and so only a server that supports BINARY
append needs to worry about re-encoding it for download?

I think every implementation I knew of recodes binary mime to 8bit on
append. But yeah, I recall that Google lets you slip binary past it
sometimes, and it gives that back to clients. I don't think that's uncommon=
.

Dave.

--001a11c2afd2e47540050988fa45
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On 6 Dec 2014 01:49, &quot;Jamie Nicolson (=E5=80=AA=E5=BF=97=E6=98=8E)&quo=
t; &lt;<a href=3D"mailto:nicolson@google.com">nicolson@google.com</a>&gt; w=
rote:<br>
&gt;<br>
&gt; On Fri, Dec 5, 2014 at 2:42 PM, Dave Cridland &lt;<a href=3D"mailto:da=
ve@cridland.net">dave@cridland.net</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; I have a vague recollection that it&#39;s in Inky, <a href=3D"http=
://inky.com/">http://inky.com/</a> - it&#39;s something of a no brainer to =
support in a client, in any case. Servers have to handle binary append, suc=
h is somewhat harder.<br>
&gt;<br>
&gt;<br>
&gt; My reading of binary append is just that the server needs to accept th=
e &lt;literal8&gt; syntax and accept data that contains NULs. The spec allo=
ws for modifying the CTE at append time, but discourages it in section 6 (&=
quot;this should only be done when it is absolutely necessary&quot;). So it=
 seems like supporting binary append should be fairly straightforward.<br>
&gt;<br>
&gt; Are you perhaps referring to the re-encoding of binary data with a con=
forming CTE when it is FETCHed with a (non-binary) BODY or BODYSTRUCTURE? T=
his requirement puzzles me because it seems to be retroactive, and independ=
ent of whether BINARY append is supported. We already have binary data in o=
ur system, and we make no attempt to re-encode it for IMAP download now, ev=
en without implementing BINARY. Is the spec assuming that, prior to impleme=
nting BINARY, there was no way for binary data to get into the system, and =
so only a server that supports BINARY append needs to worry about re-encodi=
ng it for download?=C2=A0</p>
<p dir=3D"ltr">I think every implementation I knew of recodes binary mime t=
o 8bit on append. But yeah, I recall that Google lets you slip binary past =
it sometimes, and it gives that back to clients. I don&#39;t think that&#39=
;s uncommon.</p>
<p dir=3D"ltr">Dave.</p>

--001a11c2afd2e47540050988fa45--


From nobody Sat Dec  6 01:51:02 2014
Return-Path: <dave@cridland.net>
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 BD5401A9006 for <imapext@ietfa.amsl.com>; Sat,  6 Dec 2014 01:51:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 Lu6fs8gTllEL for <imapext@ietfa.amsl.com>; Sat,  6 Dec 2014 01:50:59 -0800 (PST)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FEA11A9004 for <imapext@ietf.org>; Sat,  6 Dec 2014 01:50:59 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id vb8so1698096obc.28 for <imapext@ietf.org>; Sat, 06 Dec 2014 01:50:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7Hv5NZ+/IbY7rIkd40lVXNhl+AQaDvnpOnALJsjCIJ4=; b=KS9KTNUnzEavQZ5rqdxqL8N4Ppi+uAJk67IiEvkR+V41GJJ3SD1Dt1ClFSUQAFv/kH rq1L5VXg3B7NG+JJZff+D8atksmKHxZFDlnfcvZXsLjtOcYIHolBVYcFf6jN1m4KTmtH VrbcwVUblKh1+uxmoNLMOJxd3pX492hINmSCU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7Hv5NZ+/IbY7rIkd40lVXNhl+AQaDvnpOnALJsjCIJ4=; b=FmlrxdfZhLdhbs3BD8Z6iBzUvab7Q22aoed2kXTrtnuAF5CM1maMdxIcQI/xqabMKw tmz8nVVjEK4lTrgVfMfDY4NUrAWwPfpqg9acpRyh9aGR/HFwtqZLJONcoFaYE4gMg8ch cr4q1dNai3Y2I6SRkujoDBPWFevuFUszWymxf3U7uemLrW1O7yOu51aLx9niWOLYZ56U hk+hYLh7cDHD5Ze6O/JaxMY1w9qGlppdCVaIy6tpdy+gCt31n0sr/pGOEvIcb3k5kNoa ASq0dmiDXblqxz/kYvTbpVecriQCPtJjjW47WSqPYSVOnWpXInnz6syMMwQbXNoQN4UR b0og==
X-Gm-Message-State: ALoCoQkAHazk/ryN3u85axr8nx4Y+TN97BB6gVcN6Q3kmXLvowjaGFyEusPY+eva4cLm/QHCbi0/
MIME-Version: 1.0
X-Received: by 10.182.130.162 with SMTP id of2mr13468495obb.52.1417859458573;  Sat, 06 Dec 2014 01:50:58 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Sat, 6 Dec 2014 01:50:58 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Sat, 6 Dec 2014 01:50:58 -0800 (PST)
In-Reply-To: <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org>
Date: Sat, 6 Dec 2014 09:50:58 +0000
Message-ID: <CAKHUCzzHxVfDvaySFupBtoS5wGasWQ9B5KUiFnqtyvnjTX+EVg@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Michael M Slusarz <slusarz@horde.org>
Content-Type: multipart/alternative; boundary=089e013cbb2c5ebdf10509892173
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/EskbzDunWTq5XbKSmusfTnje7hY
Cc: imapext@ietf.org
Subject: Re: [imapext] Fetching short text snippet for mails
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, 06 Dec 2014 09:51:01 -0000

--089e013cbb2c5ebdf10509892173
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 6 Dec 2014 00:25, "Michael M Slusarz" <slusarz@horde.org> wrote:
>
> Quoting Jan Kundr=C3=A1t <jkt@flaska.net>:
>
>> On Tuesday, 2 December 2014 17:37:31 CEST, Cyrus Daboo wrote:
>>>
>>> Efficient as in eliminating the current extra round trip of doing a
FETCH BODY.PEEK[<section>]<<partial>>?
>>
>>
>> I don't think a roundtrip would be neccessary.
>>
>> Sure, the client doesn't know whether it's a single-part text/plain, or
if it's a multipart/mixed with plaintext and HTML, or whether it's
something yet different. However, there's principally no problem in issuing
a blind BODY.PEEK[1] which will "get the right thing" most of the time. One
can play it extra-safe and ask for a BODY.PEEK[1.1] as well, these are also
pretty popular and the worst case is wasting a tiny amount of bandwidth.
It's OK to request a non-existing part in FETCH anyway.
>
>
> We've found this kind of blind-fetching technique isn't very useful, at
least coming from the perspective of a client that has to handle 1000's of
concurrent users.
>
> If building a mailbox listing, there's a good chance that envelop(-ish)
data is cached on the server.  Once you start adding body fetches to this
mailbox listing it becomes more expensive I/O wise to generate these
responses.
>
> And this doesn't work very well for multipart/alternative e-mails,
especially since more and more of those messages have a [1] text/plain
content of either "Go to URL http://example.com/ to view the contents of
this message" or an automated down-converted representation of the HTML
part that is difficult to read.
>
> For a 50,000 foot preview of the message content, I have no issue relying
on a server to figure out how to parse the multipart/alternative message
and strip out the HTML tags in order to provide something useful.
>

+1 - Also I really don't think every octet of the preview needs specifying
rigidly.

> michael
>
> ___________________________________
> Michael Slusarz [slusarz@horde.org]
>
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext

--089e013cbb2c5ebdf10509892173
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On 6 Dec 2014 00:25, &quot;Michael M Slusarz&quot; &lt;<a href=3D"mailto:sl=
usarz@horde.org">slusarz@horde.org</a>&gt; wrote:<br>
&gt;<br>
&gt; Quoting Jan Kundr=C3=A1t &lt;<a href=3D"mailto:jkt@flaska.net">jkt@fla=
ska.net</a>&gt;:<br>
&gt;<br>
&gt;&gt; On Tuesday, 2 December 2014 17:37:31 CEST, Cyrus Daboo wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Efficient as in eliminating the current extra round trip of do=
ing a FETCH BODY.PEEK[&lt;section&gt;]&lt;&lt;partial&gt;&gt;?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; I don&#39;t think a roundtrip would be neccessary.<br>
&gt;&gt;<br>
&gt;&gt; Sure, the client doesn&#39;t know whether it&#39;s a single-part t=
ext/plain, or if it&#39;s a multipart/mixed with plaintext and HTML, or whe=
ther it&#39;s something yet different. However, there&#39;s principally no =
problem in issuing a blind BODY.PEEK[1] which will &quot;get the right thin=
g&quot; most of the time. One can play it extra-safe and ask for a BODY.PEE=
K[1.1] as well, these are also pretty popular and the worst case is wasting=
 a tiny amount of bandwidth. It&#39;s OK to request a non-existing part in =
FETCH anyway.<br>
&gt;<br>
&gt;<br>
&gt; We&#39;ve found this kind of blind-fetching technique isn&#39;t very u=
seful, at least coming from the perspective of a client that has to handle =
1000&#39;s of concurrent users.<br>
&gt;<br>
&gt; If building a mailbox listing, there&#39;s a good chance that envelop(=
-ish) data is cached on the server.=C2=A0 Once you start adding body fetche=
s to this mailbox listing it becomes more expensive I/O wise to generate th=
ese responses.<br>
&gt;<br>
&gt; And this doesn&#39;t work very well for multipart/alternative e-mails,=
 especially since more and more of those messages have a [1] text/plain con=
tent of either &quot;Go to URL <a href=3D"http://example.com/">http://examp=
le.com/</a> to view the contents of this message&quot; or an automated down=
-converted representation of the HTML part that is difficult to read.<br>
&gt;<br>
&gt; For a 50,000 foot preview of the message content, I have no issue rely=
ing on a server to figure out how to parse the multipart/alternative messag=
e and strip out the HTML tags in order to provide something useful.<br>
&gt;</p>
<p dir=3D"ltr">+1 - Also I really don&#39;t think every octet of the previe=
w needs specifying rigidly.<br></p>
<p dir=3D"ltr">&gt; michael<br>
&gt;<br>
&gt; ___________________________________<br>
&gt; Michael Slusarz [<a href=3D"mailto:slusarz@horde.org">slusarz@horde.or=
g</a>]<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; imapext mailing list<br>
&gt; <a href=3D"mailto:imapext@ietf.org">imapext@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/imapext">https://www.=
ietf.org/mailman/listinfo/imapext</a><br>
</p>

--089e013cbb2c5ebdf10509892173--


From nobody Sat Dec  6 02:38:46 2014
Return-Path: <jkt@flaska.net>
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 EFFC21A902A for <imapext@ietfa.amsl.com>; Sat,  6 Dec 2014 02:38:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.609
X-Spam-Level: 
X-Spam-Status: No, score=-1.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 LXarYa9DNWLV for <imapext@ietfa.amsl.com>; Sat,  6 Dec 2014 02:38:42 -0800 (PST)
Received: from latimerie.flaska.net (latimerie.flaska.net [IPv6:2a02:2b88:2:1::4a7:333]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EA541A9004 for <imapext@ietf.org>; Sat,  6 Dec 2014 02:38:41 -0800 (PST)
Received: by latimerie.flaska.net (Postfix, from userid 1000) id A6211613B5; Sat,  6 Dec 2014 11:38:36 +0100 (CET)
From: =?iso-8859-1?Q?Jan_Kundr=E1t?= <jkt@flaska.net>
To: <imapext@ietf.org>
Date: Sat, 06 Dec 2014 11:38:35 +0100
User-Agent: Trojita/v0.4.1-408-g93d28e6; Qt/4.8.5; X11; Linux; 
MIME-Version: 1.0
Message-ID: <0ea3bdd5-2fc3-43b2-8f7a-b3560ce2929c@flaska.net>
In-Reply-To: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/8htaTdiXay881P5lBsLLsy5wlVI
Subject: Re: [imapext] =?iso-8859-1?q?client_support_for_RFC_3516_=28BINARY=29?= =?iso-8859-1?q?=3F?=
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, 06 Dec 2014 10:38:45 -0000

On Friday, 5 December 2014 23:02:23 CEST, Jamie Nicolson (=E5=80=AA=E5=BF=97=E6=
=98=8E) wrote:
> Anyone know of clients that support RFC 3516?

Trojit=C3=A1 will happily use BINARY whenever it's available for all of its=20=

fetching operations where it's legal, and unless the client needs the raw,=20=

encoded data e.g. for signature validation.

Because the composer always produces 7bit messages, BINARY is not used for=20=

APPENDs.

With kind regards,
Jan

--=20
Trojit=C3=A1, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/


From nobody Sat Dec  6 02:42:21 2014
Return-Path: <jkt@flaska.net>
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 68B421A902C for <imapext@ietfa.amsl.com>; Sat,  6 Dec 2014 02:42:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 RyE_S42pkig4 for <imapext@ietfa.amsl.com>; Sat,  6 Dec 2014 02:42:18 -0800 (PST)
Received: from latimerie.flaska.net (latimerie.flaska.net [IPv6:2a02:2b88:2:1::4a7:333]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61AF91A902A for <imapext@ietf.org>; Sat,  6 Dec 2014 02:42:18 -0800 (PST)
Received: by latimerie.flaska.net (Postfix, from userid 1000) id 86010613B5; Sat,  6 Dec 2014 11:42:15 +0100 (CET)
From: =?iso-8859-1?Q?Jan_Kundr=E1t?= <jkt@flaska.net>
To: <imapext@ietf.org>
Date: Sat, 06 Dec 2014 11:42:15 +0100
User-Agent: Trojita/v0.4.1-408-g93d28e6; Qt/4.8.5; X11; Linux; 
MIME-Version: 1.0
Message-ID: <e602d161-aeef-46ec-beab-7f671020f9c1@flaska.net>
In-Reply-To: <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/gOqAKFVowXobB7nFtnyUFnK9QtU
Subject: Re: [imapext] Fetching short text snippet for mails
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, 06 Dec 2014 10:42:19 -0000

On Saturday, 6 December 2014 01:25:38 CEST, Michael M Slusarz wrote:
> If building a mailbox listing, there's a good chance that=20
> envelop(-ish) data is cached on the server.  Once you start=20
> adding body fetches to this mailbox listing it becomes more=20
> expensive I/O wise to generate these responses.

If I'm reading this correctly, this means that you won't use this preview=20
thing either because it fetches actual body part data. Fair enough, that's=20=

probably a good optimization, but I do not see how is that relevant to the=20=

proposed extension which would have a very similar cost. Unless you assume=20=

servers will add adaptive caching, which they can already do now.

With kind regards,
Jan

--=20
Trojit=C3=A1, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/


From nobody Sat Dec  6 03:25:18 2014
Return-Path: <dave@cridland.net>
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 27B901A9031 for <imapext@ietfa.amsl.com>; Sat,  6 Dec 2014 03:25:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.078
X-Spam-Level: 
X-Spam-Status: No, score=-1.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 pgDMwbvoQpFS for <imapext@ietfa.amsl.com>; Sat,  6 Dec 2014 03:25:15 -0800 (PST)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A6DA1A9029 for <imapext@ietf.org>; Sat,  6 Dec 2014 03:25:15 -0800 (PST)
Received: by mail-oi0-f52.google.com with SMTP id h136so1554414oig.25 for <imapext@ietf.org>; Sat, 06 Dec 2014 03:25:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=T8bXU0Hiry1/OZFgE87dtypiAbrXa1cLCMDxMPzpJi4=; b=OW0hSv8E3E/jE6EPH+W1aw2StSbmnTdq8HTUBWb5qEZVWEvAMK+dicB94Y+SGpniFE L4NbDAAU2SCBT7ovWigcr3rJb9xMoCspAqhxh5d+16LCQBj2Db6j9/HMP7Omqbscbg0S v66JtqiEeh5v+2QWAa/nnhDAvWYLrUc1GaaVI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=T8bXU0Hiry1/OZFgE87dtypiAbrXa1cLCMDxMPzpJi4=; b=Hk/8rChb3gboYqWzRWNWMnim8ljpIfbtrZcBqwvZ/L9gRyVc8NB8T9rBoL2/2e5Rmi 5hSBfymCL8c3k1OKDJu7RWrnV/RINpZbvj9zHpsVpk1zteA5N1qrpnl2m36rXHfZ1y56 ee05G5TBDEBPqqeMMCB6QASI1aki4KqLnNGZSbid6nbJoJp44YfNwPXW4o29ygSAAfRH y+0RP/aCHSSzmxMnHixFMLoamXMYMGR1i2OW/4PiPzkVnv3VSXrvYwmdHRFrDAjcWL9Y kE2WeeU/49xzJi0JunmlmY4WQO07b76Xgaofz2oPadqyBNYm0og5ZyKVm/cyYPgOgJmu wbEA==
X-Gm-Message-State: ALoCoQkTvuk4ZrOtEEIfQG6DMai0/36qhOQpKYjkuC2mGcZiVgYIA13CM+f/g07Bww6eXEEEeTVa
MIME-Version: 1.0
X-Received: by 10.60.68.108 with SMTP id v12mr1632363oet.69.1417865114626; Sat, 06 Dec 2014 03:25:14 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Sat, 6 Dec 2014 03:25:14 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Sat, 6 Dec 2014 03:25:14 -0800 (PST)
In-Reply-To: <e602d161-aeef-46ec-beab-7f671020f9c1@flaska.net>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org> <e602d161-aeef-46ec-beab-7f671020f9c1@flaska.net>
Date: Sat, 6 Dec 2014 11:25:14 +0000
Message-ID: <CAKHUCzwPJb0KB1fsOwh4fiuwQC62EpS=Qr3OKNP=H5M25LXmcQ@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: =?UTF-8?B?SmFuIEt1bmRyw6F0?= <jkt@flaska.net>
Content-Type: multipart/alternative; boundary=001a11330d5e7f451005098a72ca
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/jJpUofjRrqIk2dGXxwtaZw-bImE
Cc: imapext@ietf.org
Subject: Re: [imapext] Fetching short text snippet for mails
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, 06 Dec 2014 11:25:17 -0000

--001a11330d5e7f451005098a72ca
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 6 Dec 2014 10:42, "Jan Kundr=C3=A1t" <jkt@flaska.net> wrote:
>
> On Saturday, 6 December 2014 01:25:38 CEST, Michael M Slusarz wrote:
>>
>> If building a mailbox listing, there's a good chance that envelop(-ish)
data is cached on the server.  Once you start adding body fetches to this
mailbox listing it becomes more expensive I/O wise to generate these
responses.
>
>
> If I'm reading this correctly, this means that you won't use this preview
thing either because it fetches actual body part data. Fair enough, that's
probably a good optimization, but I do not see how is that relevant to the
proposed extension which would have a very similar cost. Unless you assume
servers will add adaptive caching, which they can already do now.

Except caching based on an arbitrary prefix is harder than caching based on
a known semantic preview. Caching and other optimizations are generally
easier when semantics are well defined.

--001a11330d5e7f451005098a72ca
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On 6 Dec 2014 10:42, &quot;Jan Kundr=C3=A1t&quot; &lt;<a href=3D"mailto:jkt=
@flaska.net">jkt@flaska.net</a>&gt; wrote:<br>
&gt;<br>
&gt; On Saturday, 6 December 2014 01:25:38 CEST, Michael M Slusarz wrote:<b=
r>
&gt;&gt;<br>
&gt;&gt; If building a mailbox listing, there&#39;s a good chance that enve=
lop(-ish) data is cached on the server.=C2=A0 Once you start adding body fe=
tches to this mailbox listing it becomes more expensive I/O wise to generat=
e these responses.<br>
&gt;<br>
&gt;<br>
&gt; If I&#39;m reading this correctly, this means that you won&#39;t use t=
his preview thing either because it fetches actual body part data. Fair eno=
ugh, that&#39;s probably a good optimization, but I do not see how is that =
relevant to the proposed extension which would have a very similar cost. Un=
less you assume servers will add adaptive caching, which they can already d=
o now.</p>
<p dir=3D"ltr">Except caching based on an arbitrary prefix is harder than c=
aching based on a known semantic preview. Caching and other optimizations a=
re generally easier when semantics are well defined.</p>

--001a11330d5e7f451005098a72ca--


From nobody Mon Dec  8 17:15:58 2014
Return-Path: <nicolson@google.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 C787A1A1AFA for <imapext@ietfa.amsl.com>; Mon,  8 Dec 2014 17:15:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level: 
X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 HcXRhkcGShwV for <imapext@ietfa.amsl.com>; Mon,  8 Dec 2014 17:15:56 -0800 (PST)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AB241A1AE2 for <imapext@ietf.org>; Mon,  8 Dec 2014 17:15:56 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id y20so5627831ier.4 for <imapext@ietf.org>; Mon, 08 Dec 2014 17:15:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=a4GjQYBhtvhAwarMi7ZT2HznWk2Jdq7YBDSpVCkeJr0=; b=cEIiA0jEfirpSQ3ILuJ7JOg7f0QYUSb1pLL8gj82mbLJvJFlv7NDM/46UEvqLubIBh 2aalWCSQhTeQ2dQdESl+Q1bvNBLEL04UdOkkXYePKYw8qJElviaNwb1hat5aMeiYHRo5 DJRA3MgLVNNTviYI7NjReIJfgFtjUnEfWY7K+lw7ObfQdwUDFxoJJMQPPKEgKwLxVRPA vAWyTrClg4rwqyPCwOr3NZH2VKcHqaKYBPX1ST+C1dPKsYIsKd4QNPx1bEmIfyOFrZsv O+T2nHsfDz2JP4ZKO4ZxrzPNbvUCMud/QPMNJmCt0YL5ZWjYox6qi8JaTQBp75ACM3Oc xtgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=a4GjQYBhtvhAwarMi7ZT2HznWk2Jdq7YBDSpVCkeJr0=; b=gLSQ4BowgvfW7BMBLS9DdAyGd4zC/BWQOiswgEMrNpFdV1/B/rLyd8aS5TW+Vm9eB2 fwgxhFHVHbsszTyl2h+EWRJsX7mDOi20y+NoHSXfLqHMQMYXQuoAhA1ykMEJ77d082pj Rg9BtBmO7eBBCGFNzAuvBJOEmwI687zsB2pTCRB7bgpqv6tsx9BiKECKOc18ggHBEnGE jaRN6FsSy6RK2/ytuU5AxVMOwjOaWBhKaE+Y/w8ZLOGqr35BMRim2pSgwm9vhf3C0bkx 3PqMHbZLWQ6PGlpYmJXJJSmEmwAo+fsSG/6t66XqmzJ9pf09vK/5RfTBiIIkVdDlMBoT VBjw==
X-Gm-Message-State: ALoCoQmgUCrU73G5Vmck/BQa5Jz7Jt5md/W1VfG6NrLp6uS1nRgpSmMtqr8qEAR7zFnGN/uvRgvc
X-Received: by 10.42.255.72 with SMTP id nh8mr24608icb.1.1418087755184; Mon, 08 Dec 2014 17:15:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.1.165 with HTTP; Mon, 8 Dec 2014 17:15:24 -0800 (PST)
In-Reply-To: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com>
From: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Date: Mon, 8 Dec 2014 17:15:24 -0800
Message-ID: <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com>
To: imapext@ietf.org
Content-Type: multipart/alternative; boundary=bcaec511e5fae89e780509be48b5
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/C1hSD65K0mbm5KDkG9zVhENLSB4
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 09 Dec 2014 01:15:58 -0000

--bcaec511e5fae89e780509be48b5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks for the responses. A couple of follow-up questions:

1. This thread (
http://mailman13.u.washington.edu/pipermail/imap-protocol/2012-August/00180=
3.html)
implies that fetching non-terminal MIME parts, while allowed by the spec,
is strongly discouraged because it may require rewriting CTE headers and
other on-the-fly modifications. Are people typically restricting the use of
BINARY to terminal parts, or are they issuing things like FETCH BINARY[] ?

2. Some folks indicated they use BINARY append. Does mean you're also using
a binary CTE in your messages, or that you're just using literal8 syntax to
upload messages that are 7bit or 8bit?

On Fri, Dec 5, 2014 at 2:02 PM, Jamie Nicolson (=E5=80=AA=E5=BF=97=E6=98=8E=
) <nicolson@google.com>
wrote:

> Anyone know of clients that support RFC 3516? It seems like it could be
> particularly useful for mobile clients, to reduce both download size and
> CPU usage for base64-decoding.
>

--bcaec511e5fae89e780509be48b5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks for the responses. A couple of follow-up questions:=
<div><br></div><div>1. This thread (<a href=3D"http://mailman13.u.washingto=
n.edu/pipermail/imap-protocol/2012-August/001803.html">http://mailman13.u.w=
ashington.edu/pipermail/imap-protocol/2012-August/001803.html</a>) implies =
that fetching non-terminal MIME parts, while allowed by the spec, is strong=
ly discouraged because it may require rewriting CTE headers and other on-th=
e-fly modifications. Are people typically restricting the use of BINARY to =
terminal parts, or are they issuing things like FETCH BINARY[] ?</div><div>=
<br></div><div>2. Some folks indicated they use BINARY append. Does mean yo=
u&#39;re also using a binary CTE in your messages, or that you&#39;re just =
using literal8 syntax to upload messages that are 7bit or 8bit?</div></div>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Dec 5, 20=
14 at 2:02 PM, Jamie Nicolson (=E5=80=AA=E5=BF=97=E6=98=8E) <span dir=3D"lt=
r">&lt;<a href=3D"mailto:nicolson@google.com" target=3D"_blank">nicolson@go=
ogle.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr">Anyone know of clients that support RFC 3516? It seems like it cou=
ld be particularly useful for mobile clients, to reduce both download size =
and CPU usage for base64-decoding.</div>
</blockquote></div><br></div>

--bcaec511e5fae89e780509be48b5--


From nobody Tue Dec  9 05:44:14 2014
Return-Path: <jkt@flaska.net>
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 E19AC1A1B2D for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 05:44:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.289
X-Spam-Level: 
X-Spam-Status: No, score=0.289 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 g-68KeBCsnzv for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 05:44:12 -0800 (PST)
Received: from latimerie.flaska.net (latimerie.flaska.net [IPv6:2a02:2b88:2:1::4a7:333]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA8131A1B21 for <imapext@ietf.org>; Tue,  9 Dec 2014 05:44:11 -0800 (PST)
Received: by latimerie.flaska.net (Postfix, from userid 1000) id 5084960A61; Tue,  9 Dec 2014 14:44:08 +0100 (CET)
From: =?iso-8859-1?Q?Jan_Kundr=E1t?= <jkt@flaska.net>
To: <imapext@ietf.org>
Date: Tue, 09 Dec 2014 14:44:07 +0100
User-Agent: Trojita/v0.4.1-408-g93d28e6; Qt/4.8.5; X11; Linux; 
MIME-Version: 1.0
Message-ID: <3b213806-8498-40d5-90fa-bb5483a96879@flaska.net>
In-Reply-To: <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/lIIA7WWKU8dmBUlMW1ulBuQhH2k
Subject: Re: [imapext] =?iso-8859-1?q?client_support_for_RFC_3516_=28BINARY=29?= =?iso-8859-1?q?=3F?=
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, 09 Dec 2014 13:44:14 -0000

On Tuesday, 9 December 2014 02:15:24 CEST, Jamie Nicolson (=E5=80=AA=E5=BF=97=
=E6=98=8E) wrote:
> Are people typically restricting the use of
> BINARY to terminal parts, or are they issuing things like FETCH BINARY[] ?

In case of Trojita, we don't request a BINARY on a non-leaf part because I=20=

don't think doing that should be "legal". As I originally said in that=20
e-mail thread, this is probably worth an errata update to the RFC, IMHO.

With kind regards,
Jan

--=20
Trojit=C3=A1, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/


From nobody Tue Dec  9 06:01:46 2014
Return-Path: <murch@andrew.cmu.edu>
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 2C93A1A1B3A for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 06:01:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level: 
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 zGkCe8CsjaPE for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 06:01:43 -0800 (PST)
Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.105.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 150991A1B9B for <imapext@ietf.org>; Tue,  9 Dec 2014 06:01:38 -0800 (PST)
Received: from localhost.localdomain (cpe-76-180-151-43.buffalo.res.rr.com [76.180.151.43]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.14.8/8.14.8) with ESMTP id sB9E1U9e010776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Dec 2014 09:01:30 -0500
Message-ID: <548700B9.3050406@andrew.cmu.edu>
Date: Tue, 09 Dec 2014 09:01:29 -0500
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Michael M Slusarz <slusarz@horde.org>, imapext@ietf.org
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CAKHUCzxw0H9DGHNtOGPjsEufd-z1=EHBrjF4sXm-u+SOccq+1w@mail.gmail.com> <20141205165620.Horde.-sbLV87XYRYWrxO72a0ZAQ6@bigworm.curecanti.org>
In-Reply-To: <20141205165620.Horde.-sbLV87XYRYWrxO72a0ZAQ6@bigworm.curecanti.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.11.6.144520
X-SMTP-Spam-Clean: 28% ( SXL_IP_DYNAMIC 3, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_400_499 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, NO_URI_FOUND 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_RESIDENTIAL 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, REFERENCES 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __MOZILLA_USER_AGENT 0, __PHISH_SPEAR_STRUCTURE_1 0, __RDNS_POOLED_1 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __USER_AGENT 0)
X-SMTP-Spam-Score: 28%
X-Scanned-By: MIMEDefang 2.74 on 128.2.105.204
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/Ba24bGooWb5DotpoiqCLOWZ95j0
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 09 Dec 2014 14:01:45 -0000

Hi Michael,


On 12/05/2014 06:56 PM, Michael M Slusarz wrote:
>
> BINARY APPENDs are a different story though.  It is broken on multiple 
> servers, and in several different ways.  At a minimum, versions of 
> UW-IMAP, Cyrus, and Sun Java System Messaging have problems.

I'm unaware of any issues with BINARY APPEND in Cyrus.  Have you opened 
a bug for this?

-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University


From nobody Tue Dec  9 09:12:22 2014
Return-Path: <slusarz@horde.org>
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 8CCCC1A1A83 for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 09:12:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 V2VLOyg6MxrP for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 09:12:19 -0800 (PST)
Received: from resqmta-po-03v.sys.comcast.net (resqmta-po-03v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:162]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54A5A1A1A0B for <imapext@ietf.org>; Tue,  9 Dec 2014 09:12:19 -0800 (PST)
Received: from resomta-po-01v.sys.comcast.net ([96.114.154.225]) by resqmta-po-03v.sys.comcast.net with comcast id RVAi1p0074s37d401VCJAj; Tue, 09 Dec 2014 17:12:18 +0000
Received: from bigworm.curecanti.org ([67.176.83.228]) by resomta-po-01v.sys.comcast.net with comcast id RVCH1p00b4vagWz01VCHzH; Tue, 09 Dec 2014 17:12:18 +0000
Received: from bigworm.curecanti.org (localhost.localdomain [IPv6:::1]) (Authenticated sender: slusarz) by bigworm.curecanti.org (Postfix) with ESMTPSA id 41D926809B; Tue,  9 Dec 2014 10:12:17 -0700 (MST)
Received: from dangerzone.curecanti.org (dangerzone.curecanti.org [172.18.5.4]) by bigworm.curecanti.org (Horde Framework) with HTTP; Tue, 09 Dec 2014 10:12:17 -0700
Date: Tue, 09 Dec 2014 10:12:17 -0700
Message-ID: <20141209101217.Horde.K7YYd3JfY3d5gm3pxjVRHA1@bigworm.curecanti.org>
From: Michael M Slusarz <slusarz@horde.org>
To: Ken Murchison <murch@andrew.cmu.edu>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CAKHUCzxw0H9DGHNtOGPjsEufd-z1=EHBrjF4sXm-u+SOccq+1w@mail.gmail.com> <20141205165620.Horde.-sbLV87XYRYWrxO72a0ZAQ6@bigworm.curecanti.org> <548700B9.3050406@andrew.cmu.edu>
In-Reply-To: <548700B9.3050406@andrew.cmu.edu>
User-Agent: Horde Application Framework 5
Accept-Language: en
X-Originating-IP: 172.18.5.4
X-Remote-Browser: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418145138; bh=83jnfTNUjruS+a6n3/WwXZZ3+WPV8uaqRc/txa9T0RU=; h=Received:Received:Received:Received:Date:Message-ID:From:To: Subject:Content-Type:MIME-Version; b=H9fpS30nxChRsviTwJG9aFK20LWXsfn0wb/rnuWpGZsF+U4l/mS+qwtABZJYyUUF3 F0S4jAKXZnYdmZpmIamCuHCQaTdgsw76szViB3pt082UNx7AXbcdg1JFuqLieT1ORs AgEKFLSPtPVcdBD83ubulfa9D5FN/DRM8GGu8TFgsbqW42vHolEmCIypBmq7+zh3yk sibHDJNT8si+2/7ZgObz/8cX5GctYvKmu1kcUrV38eCV/LCswULDKAvjmkcUDYyDS3 Oy4ZcXg76b+Pbp8lQ9Q3gC5uiy6EKiTkzLJAHoCQYlRVHZIV424slS8dW7Y/L6L9sU yIYHgBV5UAG5Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/VyLPiCZBd_TWSXrQxZrDn7OQW6Q
Cc: imapext@ietf.org
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 09 Dec 2014 17:12:21 -0000

Quoting Ken Murchison <murch@andrew.cmu.edu>:

> Hi Michael,
>
>
> On 12/05/2014 06:56 PM, Michael M Slusarz wrote:
>>
>> BINARY APPENDs are a different story though.  It is broken on  
>> multiple servers, and in several different ways.  At a minimum,  
>> versions of UW-IMAP, Cyrus, and Sun Java System Messaging have  
>> problems.
>
> I'm unaware of any issues with BINARY APPEND in Cyrus.  Have you  
> opened a bug for this?

Hi Ken,

I can't reproduce BINARY APPEND issues in current Cyrus code, at least  
with the current Debian 7 version (v2.4.16-Debian-2.4.16-4+deb7u2).  I  
believe that's why I never filed a bug since the issue now appears  
fixed.

But I can confirm that old 2.2 versions of Cyrus have this issue.   
E.g., the current Debian 6 version shows this behavior:

* OK bernard Cyrus IMAP4 v2.2.13-Debian-2.2.13-19+squeeze3 server ready
[...]
B APPEND "INBOX" (\seen) ~{200+}
B NO [UNKNOWN-CTE] Can not process the binary data

My notes additionally indicate that certain versions of Cyrus, instead  
of responding with a NO + UNKNOWN-CTE, will simply issue a BYE and  
disconnect instead.

michael


___________________________________
Michael Slusarz [slusarz@horde.org]


From nobody Tue Dec  9 14:17:06 2014
Return-Path: <prvs=24206e0fef=j.sb@sta.samsung.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 BFDB11A1A27 for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 14:17:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.896
X-Spam-Level: 
X-Spam-Status: No, score=0.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, 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 jIK5JmA4sj3P for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 14:16:54 -0800 (PST)
Received: from smg1.telecom.sna.samsung.com (unknown [63.166.115.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AB551A00F1 for <imapext@ietf.org>; Tue,  9 Dec 2014 14:16:53 -0800 (PST)
X-AuditID: 41a9fa1f-f79fd6d00000102f-cd-548774c74762
Received: from exHub2.telecom.sna.samsung.com (Unknown_Domain [105.52.12.243]) by smg1.telecom.sna.samsung.com (SMGOUT STA) with SMTP id 13.A4.04143.7C477845; Tue,  9 Dec 2014 16:16:39 -0600 (CST)
Received: from EXMB5.telecom.sna.samsung.com ([fe80::e195:28bd:121f:99dd]) by exHub2.telecom.sna.samsung.com ([fe80::348a:877:72e7:524b%22]) with mapi id 14.03.0146.000; Tue, 9 Dec 2014 16:16:55 -0600
From: Jayantheesh S B <j.sb@sta.samsung.com>
To: 'Alexey Melnikov' <alexey.melnikov@isode.com>, 'Stuart Brandt' <stujenerin@aol.com>
Thread-Topic: [imapext] [IMAP] APPEND Command Usage
Thread-Index: Ac/zikIaeRUU045cSKC+QFTd6ghr0ZyH6BxA
Date: Tue, 9 Dec 2014 22:16:55 +0000
Message-ID: <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <951F3F0E-25E5-42AC-9B61-BA669FD9E1F4@isode.com> <02454F842DD7B449B96715A2AD90C0361A257739@exMB5.telecom.sna.samsung.com> <25c4d3b3-a86c-4a3b-ae8e-5ec8a058cad6@flaska.net> <1414826667.1966384.185790009.6548B0D1@webmail.messagingengine.com> <9EB51A28-A50B-4494-A895-BF2E2C71C46B@isode.com> <20141102184949.Horde.qakr4M6-mMtk2LS-NnDAmw2@bigworm.curecanti.org> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com>
In-Reply-To: <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [105.52.12.197]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsWSacLzWfd4SXuIwYXtShYzVhdZPJ7FZdH1 MtyB2eP+7pXsHkuW/GTyONVsGMAcxW2TlFhSFpyZnqdvl8Cd0T15I1PBFoGKRxNesTcwruHt YuTkkBAwkehceYIZwhaTuHBvPVsXIxeHkMAxRom/jdtZIJwzjBKTP+xi72Jk52AT0JF4EgxS LyIQKbHlw0dWEJtZQFti1ef1jCC2sICRxObne4BmcgDVGEv8P2MJUW4k8avnKhuIzSKgItEy 8RUrSAmvQIjExhUmEIt2ckjMv7cAbAyngK3EwQ6Iekag076fWsMEsUpc4taT+UwQJwtILNlz Hup8UYmXj/+xQtiKEnN/3WSGqNeRWLD7ExvMmcsWvgaL8woISpyc+YRlAqPYLCRjZyFpmYWk ZRaSlgWMLKsYZYpz0w31SlJzUpPzc/WK8xL1ihNzi0vz0vWA/E2MwLhyXPlLfgfjuu32hxiZ ODgPMUpwcEmJFKfmpaQWJZaWZMSDYie+GBg9Ug2M7A93tot+5HkgVnwr5v0lpv8q0penyInp TF2g3JnsaKs3Kf7E3cjXb3ew35srFZr1McvENKR3T0DaoVW2F7tf1S970Tzr0i7ZPQHVpx59 nCoyM+PRMz7BJ1l/J3RIfV2oHtG1/EA2N6OU6+xMu4PFqae27IsSa7ppJfLoqnvuYz6vEtVp DXKySizFGYmGWsxFxYkATFwJP3YCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/0a6JHZZHYHy3zi1Ezd7loy6CSyQ
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 09 Dec 2014 22:17:05 -0000

Hi All,

Thanks for your response.=20

New response code APPENDLIMIT will be returned as part of SELECT response t=
o convey per mailbox limit=20
 and APPEND command response, if the APPENTLIMIT size is exceeded.

C: t2 SELECT INBOX
S: * 172 EXISTS
S: * OK [APPENDLIMIT 257890] Maximum upload limit
S: [...]
S: t2 OK [READ-WRITE] SELECT completed

C: t1 APPEND "Draft" (\SEEN \DRAFT) {98994952}
S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size

Whereas TOOBIG response, does not covey the size restriction applied by the=
 server.=20

 resp-text-code =3D/ toobig-response-code / badurl-response-code
 toobig-response-code =3D "TOOBIG"

We feel APPENDLIMIT response can convey per mailbox size restriction and it=
 can overcome the limitation of TOOBIG response.=20

Please share your thoughts.=20

Regards,
Jay

-----Original Message-----
From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]=20
Sent: Sunday, November 23, 2014 11:32 PM
To: Stuart Brandt
Cc: imapext@ietf.org
Subject: Re: [imapext] [IMAP] APPEND Command Usage

Hi Stuart,

> On 21 Nov 2014, at 03:04, Stuart Brandt <stujenerin@aol.com> wrote:
>=20
> Is it appropriate to cover interaction with the CATENATE extension (rfc44=
69) in the draft? That RFC already suggests that the server return TOOBIG i=
f construction of the server-side message exceeds a server-specific limit, =
but I'd imagine APPENDLIMIT=3D<n> would be a more useful response for those=
 servers/clients that support APPENDLIMIT.

You have a very good point!
And yes, we should reuse the TOOBIG response code, if it can convey the per=
-mailbox limit.
>=20
> - Stuart
>=20
>=20
>> On 11/17/14 12:16 PM, Jayantheesh S B wrote:
>> Hi All,
>>=20
>> I have incorporated all the review comments and updated the next=20
>> version of the draft.
>>=20
>> Kindly review and share your valuable comments.
>>=20
>> Regards,
>>=20
>> Jay
>=20
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext



From nobody Tue Dec  9 15:54:36 2014
Return-Path: <lyndon@orthanc.ca>
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 035A61A6ED9 for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 15:54:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.612
X-Spam-Level: 
X-Spam-Status: No, score=-1.612 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 swOFGg8hcGMx for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 15:54:33 -0800 (PST)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E963B1A01C6 for <imapext@ietf.org>; Tue,  9 Dec 2014 15:54:32 -0800 (PST)
Received: from [192.168.42.6] (d66-183-211-183.bchsia.telus.net [66.183.211.183]) (authenticated bits=0) by orthanc.ca (8.14.7/8.14.7) with ESMTP id sB9NsOVh074130 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 9 Dec 2014 15:54:26 -0800 (PST) (envelope-from lyndon@orthanc.ca)
Content-Type: multipart/signed; boundary="Apple-Mail=_8C3AF3E6-8D03-4C47-9728-D43F5694D22F"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Lyndon Nerenberg <lyndon@orthanc.ca>
In-Reply-To: <3b213806-8498-40d5-90fa-bb5483a96879@flaska.net>
Date: Tue, 9 Dec 2014 15:54:24 -0800
Message-Id: <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com> <3b213806-8498-40d5-90fa-bb5483a96879@flaska.net>
To: =?iso-8859-1?Q?Jan_Kundr=E1t?= <jkt@flaska.net>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/5aK8kK73BEmrN5-g7uvBEr70feU
Cc: imapext@ietf.org
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 09 Dec 2014 23:54:34 -0000

--Apple-Mail=_8C3AF3E6-8D03-4C47-9728-D43F5694D22F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Dec 9, 2014, at 5:44 AM, Jan Kundr=E1t <jkt@flaska.net> wrote:

> In case of Trojita, we don't request a BINARY on a non-leaf part =
because I don't think doing that should be "legal". As I originally said =
in that e-mail thread, this is probably worth an errata update to the =
RFC, IMHO.

Yes, 3516 was supposed to restrict binary fetches to terminal MIME =
parts.  I was sure the final version of the draft had that text, and it =
still baffles me how it got through last call without me noticing, but =
there you go.

I think the changes to add that restriction might be a bit too =
substantive for an errata.  (Barry, are you lurking  out there?)  Also, =
others have complained about parts of the document that are ambiguous or =
just not clear, so maybe it's time for an update. =20

--lyndon


--Apple-Mail=_8C3AF3E6-8D03-4C47-9728-D43F5694D22F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQIcBAEBAgAGBQJUh4uwAAoJEG8PnXiV/JnU/VAP/0RBZ1AWapYrSRru2NrpcqmC
ho+wOVu7bVVfUmErpCgaf/xnCZ+u2eX4reO1BQfe6eL1fhCf2lqXNKYOa6Ei4KqI
DQMnR2wVSoseS/1yBTE1AiU4cmkvYT+6JR2dfdvWXUbheYG2ZrHgnBpyIl+gCNvm
dMKdRXaiwdN+pphcRbtDrKG3O4l2edPJqd5iprigKh0K3Yl9VSb/tceB/3QbYo2/
CaEgr7q9ALlDu7m6fCIidH2U0od2UMAcgULtDUfgQOOxq7z4KTtFIMvpt/R8SFjC
yEDDfBGjhVD2CakFbsOZprvNMHYFinMqCFhHAS5EdHiM23BVyTWcX8UTBKl8mrEO
OIQz+TU+GO6e1RbPSTeVvaGQJV3s+cxTyryg+JdGMGlX0gp0cig6n8Hp4677xY2O
WqA3zdJjQ2GY6dCgG5Npp1fj5TqrMblHYcSfb1TFsxge2DZN+7yh9FiAtv7LuAYa
gUsiTJJyQNrKJUZUzPB7mJnPQzNFYyR/HYkQAbxfpM3Yp6RLiS/0eirZfEhlM6VV
7CyAJSsaBF1xuUOSLK8WBlV9AeoJG/1p0kBufb9fpCAQVWDvR8k2PpclSfok378M
MJaNr5mWbVev0XWv7mtP5tyayzSR9L0U9dxry8Ts6WIKI2eOddjrnOnb/vSTEaSA
xHnohWqW0Vfpgx15247t
=mmIj
-----END PGP SIGNATURE-----

--Apple-Mail=_8C3AF3E6-8D03-4C47-9728-D43F5694D22F--


From nobody Tue Dec  9 17:25:24 2014
Return-Path: <stujenerin@aol.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 5F6C31A1B3E for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 17:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level: 
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 UrmG_hy28one for <imapext@ietfa.amsl.com>; Tue,  9 Dec 2014 17:25:10 -0800 (PST)
Received: from omr-m10.mx.aol.com (omr-m10.mx.aol.com [64.12.143.86]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F5131A038F for <imapext@ietf.org>; Tue,  9 Dec 2014 17:25:10 -0800 (PST)
Received: from mtaout-aai02.mx.aol.com (mtaout-aai02.mx.aol.com [172.27.2.98]) by omr-m10.mx.aol.com (Outbound Mail Relay) with ESMTP id 8A61A70472075; Tue,  9 Dec 2014 20:25:09 -0500 (EST)
Received: from [10.172.1.2] (unknown [10.172.1.2]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-aai02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id D5C6638000084; Tue,  9 Dec 2014 20:25:08 -0500 (EST)
Message-ID: <5487A0EC.4070603@aol.com>
Date: Tue, 09 Dec 2014 20:25:00 -0500
From: Stuart Brandt <stujenerin@aol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Jayantheesh S B <j.sb@sta.samsung.com>,  'Alexey Melnikov' <alexey.melnikov@isode.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <1414826667.1966384.185790009.6548B0D1@webmail.messagingengine.com> <9EB51A28-A50B-4494-A895-BF2E2C71C46B@isode.com> <20141102184949.Horde.qakr4M6-mMtk2LS-NnDAmw2@bigworm.curecanti.org> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com>
In-Reply-To: <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1418174709; bh=tffykhWIsynv825Nrq35CDJunje/GIjORfuNM37j4v0=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=zNt1mcMd1dSeKsESldm4RTB+QcAf0Fp/Z8cGoro8plJ4jof+ba7im3bxnG8l4zXYX 0zLPyvu1YDqcYzpy6+Hb+l/qaviAQ58MHu0SCc7wFdZIX3gjUQ6oETJKxUxNgot0Ol XwO+bAamBw6cHCnYTvL89Fn0hxVcXih4AVdd7LtY=
x-aol-sid: 3039ac1b02625487a0f439b4
X-AOL-IP: 10.172.1.2
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/RSv1uFdBQn_Xv3Nxt4sA6oG2bT0
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 10 Dec 2014 01:25:15 -0000

If I'm understanding the proposal correctly, a server that has already 
implemented CATENATE and now implements APPENDLIMIT is left in an 
ambiguous state whenever the limit is exceeded. If it returns [TOOBIG], 
then it's not compliant with the APPENDLIMIT recommendation. If it 
returns [APPENDLIMIT x] then it's returning an unexpected response to 
clients that have yet to implement APPENDLIMIT, thereby "breaking" 
existing functionality.


On 12/9/14 5:16 PM, Jayantheesh S B wrote:
> Hi All,
>
> Thanks for your response.
>
> New response code APPENDLIMIT will be returned as part of SELECT response to convey per mailbox limit
>   and APPEND command response, if the APPENTLIMIT size is exceeded.
>
> C: t2 SELECT INBOX
> S: * 172 EXISTS
> S: * OK [APPENDLIMIT 257890] Maximum upload limit
> S: [...]
> S: t2 OK [READ-WRITE] SELECT completed
>
> C: t1 APPEND "Draft" (\SEEN \DRAFT) {98994952}
> S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size
>
> Whereas TOOBIG response, does not covey the size restriction applied by the server.
>
>   resp-text-code =/ toobig-response-code / badurl-response-code
>   toobig-response-code = "TOOBIG"
>
> We feel APPENDLIMIT response can convey per mailbox size restriction and it can overcome the limitation of TOOBIG response.
>
> Please share your thoughts.
>
> Regards,
> Jay


From nobody Wed Dec 10 00:54:09 2014
Return-Path: <dave@cridland.net>
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 D970D1A01A5 for <imapext@ietfa.amsl.com>; Wed, 10 Dec 2014 00:54:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 4FXrf4RYYN_Z for <imapext@ietfa.amsl.com>; Wed, 10 Dec 2014 00:54:06 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B30D41A014C for <imapext@ietf.org>; Wed, 10 Dec 2014 00:54:06 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id va8so1900799obc.31 for <imapext@ietf.org>; Wed, 10 Dec 2014 00:54:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yts2A+11AmDteDyfJuXXezTGlIdz6O4rGsNGkw0WN/E=; b=hXD4MoN9pRyVpbc2MFHZSu5F1qzngpiR+JKi9J5BxJeURzwly9DslUnZ0JeqaeYP8U hNdGE8B2hc4ca/8oAQ8BMqkei2KleyZwix8gcQFt1RWYC8xFA0YH17C1D4XBlHoAk8Av wCTAdiRftSpfug3aD2vidAWMqVDO0+HwMyKto=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=yts2A+11AmDteDyfJuXXezTGlIdz6O4rGsNGkw0WN/E=; b=IX51xLY5CrpWK8MnRDLyeuWzWCwImDysbvpSdH991VM1wHMF1m6Tjkr8UmAyKga9nd h7coL+MoW9KNnw0zKuWhmfNrbcV7FKKTm9Vbnl32/4RiBsVstrUSTjyK7jZBY4wZzO82 znewXPWIuNjvRJgYpnmCEBpEY0oY51AH2CH+HL006pu/HmLzBLwexJW7BrvYCB+Y95fh q2DifZd8Xxkw/H3wZjBhswfBmyl7TqZn8cNWsN0sme+K0UGgytq4qRt6oqN6tuW6uJTo mIhrbmEnf1WARYaL2LyZzwOVzxR+Z9tBH67uuj9arj8GgweqCNncKIuI1yytY4lezggr ic+g==
X-Gm-Message-State: ALoCoQn9GaThO9XAW5TxpbkK6QJDZ1bugmnA4bmfKPX8dIX+RKXBLimEafrFHMrAO5oJZ+ee0/EG
MIME-Version: 1.0
X-Received: by 10.202.54.86 with SMTP id d83mr1665803oia.55.1418201646012; Wed, 10 Dec 2014 00:54:06 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Wed, 10 Dec 2014 00:54:05 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Wed, 10 Dec 2014 00:54:05 -0800 (PST)
In-Reply-To: <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com> <3b213806-8498-40d5-90fa-bb5483a96879@flaska.net> <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca>
Date: Wed, 10 Dec 2014 08:54:05 +0000
Message-ID: <CAKHUCzyM00ZVUA1SkZFsSU5FWYdm1NSRokVad--jiKDcm4b7Ng@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Lyndon Nerenberg <lyndon@orthanc.ca>
Content-Type: multipart/alternative; boundary=001a113ce1b054b11d0509d8cd12
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/2iwL3tPNVATrTsveK3MqNETnlxw
Cc: =?UTF-8?B?SmFuIEt1bmRyw6F0?= <jkt@flaska.net>, imapext@ietf.org
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 10 Dec 2014 08:54:08 -0000

--001a113ce1b054b11d0509d8cd12
Content-Type: text/plain; charset=UTF-8

On 9 Dec 2014 23:54, "Lyndon Nerenberg" <lyndon@orthanc.ca> wrote:
> Yes, 3516 was supposed to restrict binary fetches to terminal MIME
parts.  I was sure the final version of the draft had that text, and it
still baffles me how it got through last call without me noticing, but
there you go.

The RFC does seem to be written entirely with leaf nodes in mind, though it
never actually makes the restriction. On the basis that all implementations
reject noon leaf sections anyway, making it an errata seems the most
pragmatic solution, whatever the process says.

Dave.

--001a113ce1b054b11d0509d8cd12
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On 9 Dec 2014 23:54, &quot;Lyndon Nerenberg&quot; &lt;<a href=3D"mailto:lyn=
don@orthanc.ca">lyndon@orthanc.ca</a>&gt; wrote:<br>
&gt; Yes, 3516 was supposed to restrict binary fetches to terminal MIME par=
ts.=C2=A0 I was sure the final version of the draft had that text, and it s=
till baffles me how it got through last call without me noticing, but there=
 you go.</p>
<p dir=3D"ltr">The RFC does seem to be written entirely with leaf nodes in =
mind, though it never actually makes the restriction. On the basis that all=
 implementations reject noon leaf sections anyway, making it an errata seem=
s the most pragmatic solution, whatever the process says.</p>
<p dir=3D"ltr">Dave.</p>

--001a113ce1b054b11d0509d8cd12--


From nobody Wed Dec 10 08:20:38 2014
Return-Path: <prvs=1421572e6b=j.sb@sta.samsung.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 536091A86F7 for <imapext@ietfa.amsl.com>; Wed, 10 Dec 2014 08:20:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.896
X-Spam-Level: 
X-Spam-Status: No, score=0.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, 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 3BJzygYgpdI0 for <imapext@ietfa.amsl.com>; Wed, 10 Dec 2014 08:20:27 -0800 (PST)
Received: from smg1.telecom.sna.samsung.com (unknown [63.166.115.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 879D81A86F4 for <imapext@ietf.org>; Wed, 10 Dec 2014 08:20:27 -0800 (PST)
X-AuditID: 41a9fa1f-f79fd6d00000102f-99-548872c1c7b3
Received: from exHub2.telecom.sna.samsung.com (Unknown_Domain [105.52.12.243]) by smg1.telecom.sna.samsung.com (SMGOUT STA) with SMTP id 74.1D.04143.1C278845; Wed, 10 Dec 2014 10:20:17 -0600 (CST)
Received: from EXMB5.telecom.sna.samsung.com ([fe80::e195:28bd:121f:99dd]) by exHub2.telecom.sna.samsung.com ([fe80::348a:877:72e7:524b%22]) with mapi id 14.03.0146.000; Wed, 10 Dec 2014 10:20:30 -0600
From: Jayantheesh S B <j.sb@sta.samsung.com>
To: 'Stuart Brandt' <stujenerin@aol.com>, 'Alexey Melnikov' <alexey.melnikov@isode.com>
Thread-Topic: [imapext] [IMAP] APPEND Command Usage
Thread-Index: Ac/zikIaeRUU045cSKC+QFTd6ghr0ZxK6Vlg48oYyFOAAJQ50oAAgMAAgAB8E7CAKoibP///DhnA
Date: Wed, 10 Dec 2014 16:20:29 +0000
Message-ID: <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <1414826667.1966384.185790009.6548B0D1@webmail.messagingengine.com> <9EB51A28-A50B-4494-A895-BF2E2C71C46B@isode.com> <20141102184949.Horde.qakr4M6-mMtk2LS-NnDAmw2@bigworm.curecanti.org> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com>
In-Reply-To: <5487A0EC.4070603@aol.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [105.52.12.197]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsWSacLzWfdgUUeIwYEjkhYzVhdZPJ7FZdH1 MtyB2eP+7pXsHkuW/GTyONVsGMAcxW2TlFhSFpyZnqdvl8CdMe3sScaCTwIVe9YdYm1gvM3b xcjJISFgInH22BwmCFtM4sK99WxdjFwcQgLHGCUmHDgP5ZxllHi2fhprFyM7B5uAjsSTYJB6 EYFIiQl/Z7GB2MwC2hKrPq9nBLGFBYwkNj/fw9zFyAFUYyzx/4wlRHmUxNSzq1lBbBYBVYkr a58yg9i8AiESNzoXskBses8usevhe7A5nALqEie3XQG7jRHotu+n1jBB7BKXuPVkPtTNAhJL 9pxnhrBFJV4+/scKYStKzP11kxmiXkdiwe5PcHcuW/gaarGgxMmZT1gmMIrNQjJ2FpKWWUha ZiFpWcDIsopRpjg33VCvJDUnNTk/V684L1GvODG3uDQvXQ/I38QIjCzHlb/kdzCu225/iJGJ g/MQowQHl5RIcWpeSmpRYmlJRjwoeuKLgfEj1cBYY+C/4cwZQ4vfOpFvjM6Fvii2N6jQTVjq WHXsrsHZiwc/T/c8/s1kU2vaHym5ukyty3O7LhsEy28RTF6RcutL6L4jLq7nDTXk35/Ijzrt kMVbnKzSsaZbpKGtMWr6QuOM1U9Cfug7X91S++X8PcdLx+TKRNzTF/iwTtzx9sqHN5pta1eE p+9QYinOSDTUYi4qTgQAdYoVF3cCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/VaDoT2tz8QAOGM30PCjridIkMSs
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 10 Dec 2014 16:20:29 -0000

Yes, I agree with your comments. Existing functionality should be broken wi=
th this new proposal.=20

But the TOOBIG response syntax does not convey the size supported by the se=
rver=20

resp-text-code =3D/ toobig-response-code / badurl-response-code
toobig-response-code =3D "TOOBIG"

Reusing the TOOBIG response code with updated syntax like below solves the =
issue

toobig-response-code =3D " TOOBIG " [SP nz-number]
resp-text-code /=3D  toobig-response-code

Please share your comments.

Regards,
Jay

-----Original Message-----
From: Stuart Brandt [mailto:stujenerin@aol.com]=20
Sent: Tuesday, December 09, 2014 8:25 PM
To: Jayantheesh S B; 'Alexey Melnikov'
Cc: 'imapext@ietf.org'
Subject: Re: [imapext] [IMAP] APPEND Command Usage

If I'm understanding the proposal correctly, a server that has already impl=
emented CATENATE and now implements APPENDLIMIT is left in an ambiguous sta=
te whenever the limit is exceeded. If it returns [TOOBIG], then it's not co=
mpliant with the APPENDLIMIT recommendation. If it returns [APPENDLIMIT x] =
then it's returning an unexpected response to clients that have yet to impl=
ement APPENDLIMIT, thereby "breaking"=20
existing functionality.


On 12/9/14 5:16 PM, Jayantheesh S B wrote:
> Hi All,
>
> Thanks for your response.
>
> New response code APPENDLIMIT will be returned as part of SELECT response=
 to convey per mailbox limit
>   and APPEND command response, if the APPENTLIMIT size is exceeded.
>
> C: t2 SELECT INBOX
> S: * 172 EXISTS
> S: * OK [APPENDLIMIT 257890] Maximum upload limit
> S: [...]
> S: t2 OK [READ-WRITE] SELECT completed
>
> C: t1 APPEND "Draft" (\SEEN \DRAFT) {98994952}
> S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size
>
> Whereas TOOBIG response, does not covey the size restriction applied by t=
he server.
>
>   resp-text-code =3D/ toobig-response-code / badurl-response-code
>   toobig-response-code =3D "TOOBIG"
>
> We feel APPENDLIMIT response can convey per mailbox size restriction and =
it can overcome the limitation of TOOBIG response.
>
> Please share your thoughts.
>
> Regards,
> Jay


From nobody Wed Dec 10 09:46:00 2014
Return-Path: <alexey.melnikov@isode.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 48E2C1A1A64 for <imapext@ietfa.amsl.com>; Wed, 10 Dec 2014 09:45:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 oWDM3vRC9QJC for <imapext@ietfa.amsl.com>; Wed, 10 Dec 2014 09:45:46 -0800 (PST)
Received: from statler.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 8EE261A6FD4 for <imapext@ietf.org>; Wed, 10 Dec 2014 09:45:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418233521; d=isode.com; s=selector; i=@isode.com; bh=sps2jpf64gz10skcmYWaovhgvqSM9ofAJcEBvMlcrBA=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Jr6o6KE1w9hcAyMgDfTGc5/YGGiUGrMsXOMsAtLr4fSnCYGlJMNyaOQSGxbNP9SRRfvFKt 0rT8RjjyFa4D+BWGDDZy8b3wnof3OojoGDyEAykg7ozaLJBYo0ViMCUJPRhMpzV1MCWAxk 6ixyG9oo8Rr5LHPc8gKz392zUPiZzOE=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <VIiGWwB3u3LJ@statler.isode.com>; Wed, 10 Dec 2014 17:45:16 +0000
Message-ID: <54888653.5030108@isode.com>
Date: Wed, 10 Dec 2014 17:43:47 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: Jayantheesh S B <j.sb@sta.samsung.com>, 'Stuart Brandt' <stujenerin@aol.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <9EB51A28-A50B-4494-A895-BF2E2C71C46B@isode.com> <20141102184949.Horde.qakr4M6-mMtk2LS-NnDAmw2@bigworm.curecanti.org> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com>
In-Reply-To: <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/EWShSXH5hpQrzI0AZi2thXN1Cv8
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 10 Dec 2014 17:45:51 -0000

Hi,

On 10/12/2014 16:20, Jayantheesh S B wrote:
> Yes, I agree with your comments. Existing functionality should be broken with this new proposal.
>
> But the TOOBIG response syntax does not convey the size supported by the server
>
> resp-text-code =/ toobig-response-code / badurl-response-code
> toobig-response-code = "TOOBIG"
>
> Reusing the TOOBIG response code with updated syntax like below solves the issue
>
> toobig-response-code = " TOOBIG " [SP nz-number]
> resp-text-code /=  toobig-response-code
>
> Please share your comments.
Other people should weight in, but I am a bit unsure how safe is 
extending already registered response codes. I can be convinced that 
this is a non issue though.
> Regards,
> Jay
>
> -----Original Message-----
> From: Stuart Brandt [mailto:stujenerin@aol.com]
> Sent: Tuesday, December 09, 2014 8:25 PM
> To: Jayantheesh S B; 'Alexey Melnikov'
> Cc: 'imapext@ietf.org'
> Subject: Re: [imapext] [IMAP] APPEND Command Usage
>
> If I'm understanding the proposal correctly, a server that has already implemented CATENATE and now implements APPENDLIMIT is left in an ambiguous state whenever the limit is exceeded. If it returns [TOOBIG], then it's not compliant with the APPENDLIMIT recommendation. If it returns [APPENDLIMIT x] then it's returning an unexpected response to clients that have yet to implement APPENDLIMIT, thereby "breaking"
> existing functionality.
>
>
> On 12/9/14 5:16 PM, Jayantheesh S B wrote:
>> Hi All,
>>
>> Thanks for your response.
>>
>> New response code APPENDLIMIT will be returned as part of SELECT response to convey per mailbox limit
>>    and APPEND command response, if the APPENTLIMIT size is exceeded.
>>
>> C: t2 SELECT INBOX
>> S: * 172 EXISTS
>> S: * OK [APPENDLIMIT 257890] Maximum upload limit
>> S: [...]
>> S: t2 OK [READ-WRITE] SELECT completed
>>
>> C: t1 APPEND "Draft" (\SEEN \DRAFT) {98994952}
>> S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size
>>
>> Whereas TOOBIG response, does not covey the size restriction applied by the server.
>>
>>    resp-text-code =/ toobig-response-code / badurl-response-code
>>    toobig-response-code = "TOOBIG"
>>
>> We feel APPENDLIMIT response can convey per mailbox size restriction and it can overcome the limitation of TOOBIG response.
>>
>> Please share your thoughts.
>>
>> Regards,
>> Jay
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext


From nobody Wed Dec 10 11:31:59 2014
Return-Path: <dave@cridland.net>
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 68CFE1A90D3 for <imapext@ietfa.amsl.com>; Wed, 10 Dec 2014 11:31:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 1O5mHW10PChp for <imapext@ietfa.amsl.com>; Wed, 10 Dec 2014 11:31:56 -0800 (PST)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F8E11A90E0 for <imapext@ietf.org>; Wed, 10 Dec 2014 11:31:54 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id gq1so2756587obb.37 for <imapext@ietf.org>; Wed, 10 Dec 2014 11:31:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H5FpT+OuMLehHjc6ErUiaioZ/sVolOJssv0d67khRfU=; b=NqiopCYDOCya5aVxbvyw+POmRJ8tUj96NejY/fdrCqu44wvLOSTHrqirb6dHI+A1BD wpQ7nMfUNJ3kTNBCidAG5sIcT+B+Ceyz3+vvMHh4HJnSM9x2OsMd3xQHliNc0JmjoCLY HRQSib8txCLPHLw/BgjC5hR8BUSwAQWCYf3iA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=H5FpT+OuMLehHjc6ErUiaioZ/sVolOJssv0d67khRfU=; b=S2N8FuUxAfVsyzCjMf1NUO3Lzi76Q8rsELzkm9Na0ef+D7YwhSHlwHGCwtNhpyUkPj 4LAIRuMllMJIluyF8ajFLmMSK9pOouOhVePYmSe7CD9zU6jM7mv+lTi07w64FoELmMIL m29ujt2Z1nRcCE9KUaWY+r6Q28W0RzWlImkCd6ku7NXYNL6q4oMXZU4Dk/2pMTRTRB4U C013qbdOLasWLJMU6WcYCtd4h4k49J3lohf+xmoshHFcPLCnavtDW8pUWNuRK/9oOTAn 8Yr3uCXnSBsqIx4I4brEyq7EMcZUbZ+yVBg+gEDGIh99gefndtxgZA22v7fwHihsGaxQ vMkQ==
X-Gm-Message-State: ALoCoQl2aivHbKsqZIZ9RhLhbSZeuql7RVzZO+0guLHzAe9ziJ07yQMMSvP+EVwZcHhdwkWyZPKu
MIME-Version: 1.0
X-Received: by 10.202.63.139 with SMTP id m133mr3456610oia.117.1418239913724;  Wed, 10 Dec 2014 11:31:53 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Wed, 10 Dec 2014 11:31:53 -0800 (PST)
Received: by 10.60.227.199 with HTTP; Wed, 10 Dec 2014 11:31:53 -0800 (PST)
In-Reply-To: <54888653.5030108@isode.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <9EB51A28-A50B-4494-A895-BF2E2C71C46B@isode.com> <20141102184949.Horde.qakr4M6-mMtk2LS-NnDAmw2@bigworm.curecanti.org> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <54888653.5030108@isode.com>
Date: Wed, 10 Dec 2014 19:31:53 +0000
Message-ID: <CAKHUCzysV-5d3D5zohSzS_SNiX0uVDCZi6+YR21y2dhhWMSUqA@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: multipart/alternative; boundary=001a113dcf0a43abb10509e1b631
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/VQq1uRM267ludqYjRiPzdo5CzVg
Cc: Jayantheesh S B <j.sb@sta.samsung.com>, Stuart Brandt <stujenerin@aol.com>, imapext@ietf.org
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 10 Dec 2014 19:31:58 -0000

--001a113dcf0a43abb10509e1b631
Content-Type: text/plain; charset=UTF-8

On 10 Dec 2014 17:46, "Alexey Melnikov" <alexey.melnikov@isode.com> wrote:
>
> Hi,
>
>
> On 10/12/2014 16:20, Jayantheesh S B wrote:
>>
>> Yes, I agree with your comments. Existing functionality should be broken
with this new proposal.
>>
>> But the TOOBIG response syntax does not convey the size supported by the
server
>>
>> resp-text-code =/ toobig-response-code / badurl-response-code
>> toobig-response-code = "TOOBIG"
>>
>> Reusing the TOOBIG response code with updated syntax like below solves
the issue
>>
>> toobig-response-code = " TOOBIG " [SP nz-number]
>> resp-text-code /=  toobig-response-code
>>
>> Please share your comments.
>
> Other people should weight in, but I am a bit unsure how safe is
extending already registered response codes. I can be convinced that this
is a non issue though.
>

Seems fraught with danger to me. We could always use enable and since the
problem by negotiation.

>> Regards,
>> Jay
>>
>> -----Original Message-----
>> From: Stuart Brandt [mailto:stujenerin@aol.com]
>> Sent: Tuesday, December 09, 2014 8:25 PM
>> To: Jayantheesh S B; 'Alexey Melnikov'
>> Cc: 'imapext@ietf.org'
>> Subject: Re: [imapext] [IMAP] APPEND Command Usage
>>
>> If I'm understanding the proposal correctly, a server that has already
implemented CATENATE and now implements APPENDLIMIT is left in an ambiguous
state whenever the limit is exceeded. If it returns [TOOBIG], then it's not
compliant with the APPENDLIMIT recommendation. If it returns [APPENDLIMIT
x] then it's returning an unexpected response to clients that have yet to
implement APPENDLIMIT, thereby "breaking"
>> existing functionality.
>>
>>
>> On 12/9/14 5:16 PM, Jayantheesh S B wrote:
>>>
>>> Hi All,
>>>
>>> Thanks for your response.
>>>
>>> New response code APPENDLIMIT will be returned as part of SELECT
response to convey per mailbox limit
>>>    and APPEND command response, if the APPENTLIMIT size is exceeded.
>>>
>>> C: t2 SELECT INBOX
>>> S: * 172 EXISTS
>>> S: * OK [APPENDLIMIT 257890] Maximum upload limit
>>> S: [...]
>>> S: t2 OK [READ-WRITE] SELECT completed
>>>
>>> C: t1 APPEND "Draft" (\SEEN \DRAFT) {98994952}
>>> S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size
>>>
>>> Whereas TOOBIG response, does not covey the size restriction applied by
the server.
>>>
>>>    resp-text-code =/ toobig-response-code / badurl-response-code
>>>    toobig-response-code = "TOOBIG"
>>>
>>> We feel APPENDLIMIT response can convey per mailbox size restriction
and it can overcome the limitation of TOOBIG response.
>>>
>>> Please share your thoughts.
>>>
>>> Regards,
>>> Jay
>>
>> _______________________________________________
>> imapext mailing list
>> imapext@ietf.org
>> https://www.ietf.org/mailman/listinfo/imapext
>
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext

--001a113dcf0a43abb10509e1b631
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On 10 Dec 2014 17:46, &quot;Alexey Melnikov&quot; &lt;<a href=3D"mailto:ale=
xey.melnikov@isode.com">alexey.melnikov@isode.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi,<br>
&gt;<br>
&gt;<br>
&gt; On 10/12/2014 16:20, Jayantheesh S B wrote:<br>
&gt;&gt;<br>
&gt;&gt; Yes, I agree with your comments. Existing functionality should be =
broken with this new proposal.<br>
&gt;&gt;<br>
&gt;&gt; But the TOOBIG response syntax does not convey the size supported =
by the server<br>
&gt;&gt;<br>
&gt;&gt; resp-text-code =3D/ toobig-response-code / badurl-response-code<br=
>
&gt;&gt; toobig-response-code =3D &quot;TOOBIG&quot;<br>
&gt;&gt;<br>
&gt;&gt; Reusing the TOOBIG response code with updated syntax like below so=
lves the issue<br>
&gt;&gt;<br>
&gt;&gt; toobig-response-code =3D &quot; TOOBIG &quot; [SP nz-number]<br>
&gt;&gt; resp-text-code /=3D=C2=A0 toobig-response-code<br>
&gt;&gt;<br>
&gt;&gt; Please share your comments.<br>
&gt;<br>
&gt; Other people should weight in, but I am a bit unsure how safe is exten=
ding already registered response codes. I can be convinced that this is a n=
on issue though.<br>
&gt;</p>
<p dir=3D"ltr">Seems fraught with danger to me. We could always use enable =
and since the problem by negotiation.</p>
<p dir=3D"ltr">&gt;&gt; Regards,<br>
&gt;&gt; Jay<br>
&gt;&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: Stuart Brandt [mailto:<a href=3D"mailto:stujenerin@aol.com">=
stujenerin@aol.com</a>]<br>
&gt;&gt; Sent: Tuesday, December 09, 2014 8:25 PM<br>
&gt;&gt; To: Jayantheesh S B; &#39;Alexey Melnikov&#39;<br>
&gt;&gt; Cc: &#39;<a href=3D"mailto:imapext@ietf.org">imapext@ietf.org</a>&=
#39;<br>
&gt;&gt; Subject: Re: [imapext] [IMAP] APPEND Command Usage<br>
&gt;&gt;<br>
&gt;&gt; If I&#39;m understanding the proposal correctly, a server that has=
 already implemented CATENATE and now implements APPENDLIMIT is left in an =
ambiguous state whenever the limit is exceeded. If it returns [TOOBIG], the=
n it&#39;s not compliant with the APPENDLIMIT recommendation. If it returns=
 [APPENDLIMIT x] then it&#39;s returning an unexpected response to clients =
that have yet to implement APPENDLIMIT, thereby &quot;breaking&quot;<br>
&gt;&gt; existing functionality.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On 12/9/14 5:16 PM, Jayantheesh S B wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Hi All,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Thanks for your response.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; New response code APPENDLIMIT will be returned as part of SELE=
CT response to convey per mailbox limit<br>
&gt;&gt;&gt; =C2=A0 =C2=A0and APPEND command response, if the APPENTLIMIT s=
ize is exceeded.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; C: t2 SELECT INBOX<br>
&gt;&gt;&gt; S: * 172 EXISTS<br>
&gt;&gt;&gt; S: * OK [APPENDLIMIT 257890] Maximum upload limit<br>
&gt;&gt;&gt; S: [...]<br>
&gt;&gt;&gt; S: t2 OK [READ-WRITE] SELECT completed<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; C: t1 APPEND &quot;Draft&quot; (\SEEN \DRAFT) {98994952}<br>
&gt;&gt;&gt; S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size=
<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Whereas TOOBIG response, does not covey the size restriction a=
pplied by the server.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; =C2=A0 =C2=A0resp-text-code =3D/ toobig-response-code / badurl=
-response-code<br>
&gt;&gt;&gt; =C2=A0 =C2=A0toobig-response-code =3D &quot;TOOBIG&quot;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; We feel APPENDLIMIT response can convey per mailbox size restr=
iction and it can overcome the limitation of TOOBIG response.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Please share your thoughts.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Regards,<br>
&gt;&gt;&gt; Jay<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; imapext mailing list<br>
&gt;&gt; <a href=3D"mailto:imapext@ietf.org">imapext@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/imapext">https://=
www.ietf.org/mailman/listinfo/imapext</a><br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; imapext mailing list<br>
&gt; <a href=3D"mailto:imapext@ietf.org">imapext@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/imapext">https://www.=
ietf.org/mailman/listinfo/imapext</a><br>
</p>

--001a113dcf0a43abb10509e1b631--


From nobody Wed Dec 10 11:58:07 2014
Return-Path: <stujenerin@aol.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 5B5801A8B84 for <imapext@ietfa.amsl.com>; Wed, 10 Dec 2014 11:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 vN-gMROi5cjS for <imapext@ietfa.amsl.com>; Wed, 10 Dec 2014 11:58:03 -0800 (PST)
Received: from omr-m2.mx.aol.com (omr-m2.mx.aol.com [64.12.133.13]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 857D41A8AF9 for <imapext@ietf.org>; Wed, 10 Dec 2014 11:58:03 -0800 (PST)
Received: from mtaout-aaj02.mx.aol.com (mtaout-aaj02.mx.aol.com [172.27.3.206]) by omr-m2.mx.aol.com (Outbound Mail Relay) with ESMTP id 97C5E3800011D; Wed, 10 Dec 2014 14:58:02 -0500 (EST)
Received: from [10.172.1.2] (unknown [10.172.1.2]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-aaj02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 652F33800008B; Wed, 10 Dec 2014 14:58:01 -0500 (EST)
Message-ID: <5488A5C9.9050904@aol.com>
Date: Wed, 10 Dec 2014 14:58:01 -0500
From: Stuart Brandt <stujenerin@aol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Jayantheesh S B <j.sb@sta.samsung.com>,  'Alexey Melnikov' <alexey.melnikov@isode.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <9EB51A28-A50B-4494-A895-BF2E2C71C46B@isode.com> <20141102184949.Horde.qakr4M6-mMtk2LS-NnDAmw2@bigworm.curecanti.org> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com>
In-Reply-To: <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1418241482; bh=6yZ5SWS4SBTZ/CUx2QcwpHhSyque2b0O4oc0ubh6qGU=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=Fp0UM3Y/cyZIQgnc7oVmOMnMUypmi1iHF1dEwPEQu8WJeeuMZOzpERt40IU+fPEmw 55YCTULE98c5Yj/Oagibigf53E/J4OukhRTbIOZZEw0pE6hzXdHmxM/obXjzmLbiWt jbqv1HlrQq5RXpFU57dKGwgXRXz9OEK0C8/KIAGM=
x-aol-sid: 3039ac1b03ce5488a5c9374b
X-AOL-IP: 10.172.1.2
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/nRsH6EPETtcbnHtxoUm9knjRPdw
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 10 Dec 2014 19:58:05 -0000

 From a server perspective, the proposal solves my concern. From a 
client perspective, I'm not sure whether the addition of [SP nz-number] 
to the TOOBIG response would present problems for clients that only 
implement CATENATE and not APPENDLIMIT. I too would like to see others 
chime in on that part.

 From what I see, most IMAP sessions either precede an APPEND with a 
SELECT/EXAMINE or LIST...likely to confirm the existence of the target 
mailbox into which they're going to append.  The proposal already covers 
SELECT/EXAMINE, so would it be reasonable to add the APPENDLIMIT=x as an 
attribute to the LIST response data in order to reflect any per-mailbox 
limit and avoid trying to convey the limit as part of the TOOBIG 
response code to APPEND? Something along the line of:

C: t1 LIST "" "%"
S: * LIST (\Marked \HasNoChildren) "/" Inbox
S: * LIST (\HasNoChildren) "/" ToDo
S: * LIST (\HasChildren) "/" Projects
S: * LIST (\Sent \HasNoChildren) "/" SentMail
S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=257890) "/" MyDrafts
S: * LIST (\Trash \HasNoChildren) "/" Trash
S: t1 OK done

Comments?

- Stuart

On 12/10/14 11:20 AM, Jayantheesh S B wrote:
> Yes, I agree with your comments. Existing functionality should be broken with this new proposal.
>
> But the TOOBIG response syntax does not convey the size supported by the server
>
> resp-text-code =/ toobig-response-code / badurl-response-code
> toobig-response-code = "TOOBIG"
>
> Reusing the TOOBIG response code with updated syntax like below solves the issue
>
> toobig-response-code = " TOOBIG " [SP nz-number]
> resp-text-code /=  toobig-response-code
>
> Please share your comments.
>
> Regards,
> Jay
>
> -----Original Message-----
> From: Stuart Brandt [mailto:stujenerin@aol.com]
> Sent: Tuesday, December 09, 2014 8:25 PM
> To: Jayantheesh S B; 'Alexey Melnikov'
> Cc: 'imapext@ietf.org'
> Subject: Re: [imapext] [IMAP] APPEND Command Usage
>
> If I'm understanding the proposal correctly, a server that has already implemented CATENATE and now implements APPENDLIMIT is left in an ambiguous state whenever the limit is exceeded. If it returns [TOOBIG], then it's not compliant with the APPENDLIMIT recommendation. If it returns [APPENDLIMIT x] then it's returning an unexpected response to clients that have yet to implement APPENDLIMIT, thereby "breaking"
> existing functionality.
>
>
> On 12/9/14 5:16 PM, Jayantheesh S B wrote:
>> Hi All,
>>
>> Thanks for your response.
>>
>> New response code APPENDLIMIT will be returned as part of SELECT response to convey per mailbox limit
>>    and APPEND command response, if the APPENTLIMIT size is exceeded.
>>
>> C: t2 SELECT INBOX
>> S: * 172 EXISTS
>> S: * OK [APPENDLIMIT 257890] Maximum upload limit
>> S: [...]
>> S: t2 OK [READ-WRITE] SELECT completed
>>
>> C: t1 APPEND "Draft" (\SEEN \DRAFT) {98994952}
>> S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size
>>
>> Whereas TOOBIG response, does not covey the size restriction applied by the server.
>>
>>    resp-text-code =/ toobig-response-code / badurl-response-code
>>    toobig-response-code = "TOOBIG"
>>
>> We feel APPENDLIMIT response can convey per mailbox size restriction and it can overcome the limitation of TOOBIG response.
>>
>> Please share your thoughts.
>>
>> Regards,
>> Jay


From nobody Thu Dec 11 03:14:42 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 5BA2E1A8785 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 03:14:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2
X-Spam-Level: **
X-Spam-Status: No, score=2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_26=0.6, J_CHICKENPOX_66=0.6] 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 f1NCjNWSQd1W for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 03:14:39 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 288C41A6F97 for <imapext@ietf.org>; Thu, 11 Dec 2014 03:14:38 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 40872FA00A9; Thu, 11 Dec 2014 11:14:36 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1418296475-22718-22717/12/51; Thu, 11 Dec 2014 11:14:35 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Thu, 11 Dec 2014 12:14:34 +0100
User-Agent: Trojita/v0.4.1-243-g4a74770; Qt/4.8.6; X11; Linux; Ubuntu 14.04.1 LTS
Mime-Version: 1.0
Message-Id: <bc93fedb-a254-44b8-a54d-4cdafb166780@gulbrandsen.priv.no>
In-Reply-To: <1417563342.2658798.198063145.6BFFCD06@webmail.messagingengine.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <1417563342.2658798.198063145.6BFFCD06@webmail.messagingengine.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/FIp4GTMmYYX6nCEQNL-9aRgw68E
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 11:14:40 -0000

On Wednesday, December 3, 2014 12:35:42 AM CEST, Bron Gondwana wrote:
> It's like FUZZY search.  Rather than specifying an exact algorithm which
> can be identical in every server, we're much better off saying "present
> a preview that gives a brief overview of what's in the message" and let
> the server calculate it as it sees fit.

Fuzzy is roughly like this:

   if(server supports fuzzy)
      send "fuzzy + " foo
   else
      send "(or subject " + foo + " body " + foo + ")"

Your client uses your snippet extension more like this:

   assert(server supports snippet)
   send "uid fetch snippet"

Quite similar in that it's simple for the client and good for the user, but 
there is a difference between if and assert ;)

Arnt


From nobody Thu Dec 11 03:20:15 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 395B51A8788 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 03:20:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.2
X-Spam-Level: *
X-Spam-Status: No, score=1.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_26=0.6, J_CHICKENPOX_66=0.6, RCVD_IN_DNSWL_LOW=-0.7, 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 XEKii_0zWTU4 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 03:20:12 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E8291A065C for <imapext@ietf.org>; Thu, 11 Dec 2014 03:20:12 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B800620765 for <imapext@ietf.org>; Thu, 11 Dec 2014 06:20:10 -0500 (EST)
Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Thu, 11 Dec 2014 06:20:10 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:x-sasl-enc:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=mesmtp; bh=nwkoEXGiL+1MJ/5HSKN9wvX+ybo=; b=BU9F FusBF+0MY9AqFm9IG8V6dQQKNsN4p/yGQpEE9JJ2hxL0wvnsR4fEyXKxqKROfqoV fN+gAXPg1CzB2Vq4x4SNfDUn/ukpDjIjHOTHa0r59wTerj9ebOjWO8TII30NqxmQ RRFOyW9QrDY4qYW/CLKvBndYZbzO+5DxVxAvFT0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=nwkoEXGiL+1MJ/5HSKN9wvX+ ybo=; b=rspUxrhodwp8Mt8i+KLMeqRP/W5QJbs85uRd7dLUpwWqCfF9YtyeUsQ7 qOgsP9ix96R6LZwolH5NheGwta3hWZOLk1L1CIeuwb4W/w2tlGn3U7m90uwZnGsa nl2NGSPdoXyPYtfP2dyu973kd90RTskcXMIOEkHxjAgq6v8LskA=
Received: by web3.nyi.internal (Postfix, from userid 99) id 8C934119B09; Thu, 11 Dec 2014 06:20:10 -0500 (EST)
Message-Id: <1418296810.2263306.201612225.3920308B@webmail.messagingengine.com>
X-Sasl-Enc: t/rImJKWOSPMv5TV9Ak/kDmDP2GS4f3vws89HBDal2yr 1418296810
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-c5cca857
In-Reply-To: <bc93fedb-a254-44b8-a54d-4cdafb166780@gulbrandsen.priv.no>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <1417563342.2658798.198063145.6BFFCD06@webmail.messagingengine.com> <bc93fedb-a254-44b8-a54d-4cdafb166780@gulbrandsen.priv.no>
Date: Thu, 11 Dec 2014 22:20:10 +1100
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/tmVmG79p47TMnuGdei5L9UfPC0o
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 11:20:14 -0000

On Thu, Dec 11, 2014, at 10:14 PM, Arnt Gulbrandsen wrote:
> On Wednesday, December 3, 2014 12:35:42 AM CEST, Bron Gondwana wrote:
> > It's like FUZZY search.  Rather than specifying an exact algorithm which
> > can be identical in every server, we're much better off saying "present
> > a preview that gives a brief overview of what's in the message" and let
> > the server calculate it as it sees fit.
> 
> Fuzzy is roughly like this:
> 
>    if(server supports fuzzy)
>       send "fuzzy + " foo
>    else
>       send "(or subject " + foo + " body " + foo + ")"
> 
> Your client uses your snippet extension more like this:
> 
>    assert(server supports snippet)
>    send "uid fetch snippet"
> 
> Quite similar in that it's simple for the client and good for the user, but 
> there is a difference between if and assert ;)

if (server support snippet)
  send "uid fetch snippet"
else if (use dumb snippets anyway)
  send "uid fetch BODY<0.140>"
else
  don't display snippet field

It's not rocket surgery.

(there's a complex else case too, I pasted it earlier, but the easy is to just not display it, or display the first 140 bytes of the body)

-- 
  Bron Gondwana
  brong@fastmail.fm


From nobody Thu Dec 11 05:41:55 2014
Return-Path: <stujenerin@aol.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 AF4171A1B2B for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 05:41:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level: 
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 hv46rQRuw2m9 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 05:41:52 -0800 (PST)
Received: from omr-m09.mx.aol.com (omr-m09.mx.aol.com [64.12.143.82]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 068341A0004 for <imapext@ietf.org>; Thu, 11 Dec 2014 05:41:52 -0800 (PST)
Received: from mtaout-aag01.mx.aol.com (mtaout-aag01.mx.aol.com [172.26.126.77]) by omr-m09.mx.aol.com (Outbound Mail Relay) with ESMTP id 3A7FF700000A2 for <imapext@ietf.org>; Thu, 11 Dec 2014 08:41:51 -0500 (EST)
Received: from [10.172.0.204] (unknown [10.172.0.204]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-aag01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 51DFB38000089 for <imapext@ietf.org>; Thu, 11 Dec 2014 08:41:50 -0500 (EST)
Message-ID: <54899F1E.9030801@aol.com>
Date: Thu, 11 Dec 2014 08:41:50 -0500
From: Stuart Brandt <stujenerin@aol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: imapext@ietf.org
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org>
In-Reply-To: <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1418305311; bh=0RKXGIe+8w6eS4inOyzVetd7mD9Jpic5yMGbOBDrjoM=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=ii7FNLuLEoUW7u8t53v8kcJ8NT2FXOBXaM5WHF24MuN1+sqE0M4Xo4GdnuwBYtMdH VUoYzLHsI584WT95ab3aPT0YLjzMzjZyN4SqL8u/YH4ZNakmiBDBHIifCtHlFsFffj PKO5Rd9blSN7yUTvFT5Sdurl0pg+2+43HVeDGzjg=
x-aol-sid: 3039ac1a7e4d54899f1e2012
X-AOL-IP: 10.172.0.204
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/nLO4TaX5JnsXeYcAhHJz7D_g6v4
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 13:41:53 -0000

Is snippet intended to be immutable? A server figuring out how to best 
parse an HTML body part and offer up of the most meaningful snippet for 
a user almost assuredly will result in versioning of the extraction 
algorithm, thereby leading to the potential for a mutable snippet element.

Additionally, a fixed sized snippet seems limiting given the trend of 
using the 'stretch' gesture on mobile devices to expose an increasing 
amount of snippet/message while viewing a message listing.

- Stuart

On 12/5/14 7:25 PM, Michael M Slusarz wrote:
> For a 50,000 foot preview of the message content, I have no issue
> relying on a server to figure out how to parse the multipart/alternative
> message and strip out the HTML tags in order to provide something useful.


From nobody Thu Dec 11 05:49:12 2014
Return-Path: <paul@pscs.co.uk>
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 599B51ACE67 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 05:49:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.089
X-Spam-Level: 
X-Spam-Status: No, score=0.089 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 cmGh1EODKFd4 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 05:49:07 -0800 (PST)
Received: from mail.pscs.co.uk (mail.pscs.co.uk [188.65.177.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4548B1A1B65 for <imapext@ietf.org>; Thu, 11 Dec 2014 05:49:07 -0800 (PST)
Authentication-Results: mail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=paul
Received: from lmail.pscs.co.uk ([82.68.5.206]) by mail.pscs.co.uk ([188.65.177.237] running VPOP3) with ESMTP for <imapext@ietf.org>; Thu, 11 Dec 2014 13:53:58 -0000
Authentication-Results: lmail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=paul
Received: from [192.168.66.101] ([192.168.66.101]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTP for <imapext@ietf.org>; Thu, 11 Dec 2014 13:48:54 -0000
Message-ID: <5489A0C6.4070807@pscs.co.uk>
Date: Thu, 11 Dec 2014 13:48:54 +0000
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: imapext@ietf.org
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org> <54899F1E.9030801@aol.com>
In-Reply-To: <54899F1E.9030801@aol.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V6.11 - Registered
X-Organisation: Paul Smith Computer Services
X-Authenticated-Sender: paul
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/VKxBx_SWoxGpkn3arsZ4mY4Bgi0
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 13:49:10 -0000

On 11/12/2014 13:41, Stuart Brandt wrote:
> Is snippet intended to be immutable? A server figuring out how to best 
> parse an HTML body part and offer up of the most meaningful snippet 
> for a user almost assuredly will result in versioning of the 
> extraction algorithm, thereby leading to the potential for a mutable 
> snippet element.

Does it matter?

> Additionally, a fixed sized snippet seems limiting given the trend of 
> using the 'stretch' gesture on mobile devices to expose an increasing 
> amount of snippet/message while viewing a message listing.

Surely the point of 'snippet' is to allow the client to get 100+ 
snippets in one FETCH command (like they can get subject, sender, date). 
That has to be quick. If it takes 0.1 seconds per message to 
generate/retrieve the snippet, that's too slow in this situation. Having 
a fixed size snippet will mean that the server can cache/precalculate 
it, making the responses potentially really quick.

Once the user starts interacting with a particular email, then the 
client will probably want to fetch the whole body content, as the user 
is interested in the message. If it takes 0.1 seconds here, it doesn't 
matter.



-


Paul Smith Computer Services
Tel: 01484 855800
Vat No: GB 685 6987 53

Sign up for news & updates at http://www.pscs.co.uk/go/subscribe


From nobody Thu Dec 11 06:15:26 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 90EB41A6F90 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 06:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-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 smfvaKU5ZiGl for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 06:15:21 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC9771A03A9 for <imapext@ietf.org>; Thu, 11 Dec 2014 06:15:20 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 45BF7FA00A9; Thu, 11 Dec 2014 14:15:19 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1418307318-22718-22717/11/21; Thu, 11 Dec 2014 14:15:18 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Thu, 11 Dec 2014 15:15:17 +0100
User-Agent: Trojita/v0.4.1-243-g4a74770; Qt/4.8.6; X11; Linux; Ubuntu 14.04.1 LTS
Mime-Version: 1.0
Message-Id: <d28654dd-954a-4717-8476-7b071dc7a2af@gulbrandsen.priv.no>
In-Reply-To: <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com> <3b213806-8498-40d5-90fa-bb5483a96879@flaska.net> <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/KqqkKNNkmM4b-0g5KPXi26p9irg
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 11 Dec 2014 14:15:24 -0000

On Wednesday, December 10, 2014 12:54:24 AM CEST, Lyndon Nerenberg wrote:
> Yes, 3516 was supposed to restrict binary fetches to terminal 
> MIME parts.  I was sure the final version of the draft had that 
> text, and it still baffles me how it got through last call 
> without me noticing, but there you go.

Yes, I was the guilty reviewer. You told me you would or wanted to add a 
leaf-only rule and I then wrote unit tests only for leaf parts. I should 
have checked the wording again later but didn't, lazy slob that I am.

Things fall through cracks.

I don't think it really matters. We've survived eleven point something 
years without noticeable interop problems.

Arnt


From nobody Thu Dec 11 06:18:30 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 89EC31A1A77 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 06:18:29 -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, RCVD_IN_DNSWL_NONE=-0.0001] 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 78FSxYBTyDm4 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 06:18:28 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89AD71A6FC3 for <imapext@ietf.org>; Thu, 11 Dec 2014 06:17:30 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 548FCFA00A9; Thu, 11 Dec 2014 14:17:28 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1418307447-22718-22717/11/22; Thu, 11 Dec 2014 14:17:27 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Thu, 11 Dec 2014 15:17:26 +0100
User-Agent: Trojita/v0.4.1-243-g4a74770; Qt/4.8.6; X11; Linux; Ubuntu 14.04.1 LTS
Mime-Version: 1.0
Message-Id: <4a62a767-ca9d-4d6d-959a-1ce2da0c574b@gulbrandsen.priv.no>
In-Reply-To: <CAKHUCzy01RBUqsrds=+QBZpRLUCQBqJ5b4-J_GF2fGfpsMMCsA@mail.gmail.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no> <547EE903.5090900@pscs.co.uk> <CAKHUCzy01RBUqsrds=+QBZpRLUCQBqJ5b4-J_GF2fGfpsMMCsA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/tfDZqrQJ9_Ws5zBXzYtUQGy76AE
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 14:18:29 -0000

On Thursday, December 4, 2014 3:04:34 PM CEST, Dave Cridland wrote:
> This is exactly what I think doesn't need specifying. It 
> doesn't matter if every implementation generates a slightly 
> different snippet, it just matters that a client can get it in 
> the same way.

Right. But OTOH the snippet has to be as least as good as the client's 
stock-IMAP fallback. I looked at two now, and both go to some length to 
snip away quoted matter etc (the first 270-odd characters of this messsage) 
and parse HTMML.

Arnt


From nobody Thu Dec 11 07:30:05 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 1DAD51A1B1D for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 07:30:01 -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 h6glI1mDys-E for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 07:29:59 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F1EF1A1AD3 for <imapext@ietf.org>; Thu, 11 Dec 2014 07:29:58 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 5C8B5FA00A9; Thu, 11 Dec 2014 15:29:57 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1418311796-22718-22717/12/52; Thu, 11 Dec 2014 15:29:56 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Message-Id: <4a0d71ef668ef7464f3235fc2611d975106d9ab30bbff241e90f0c70033b7169.sha-256@android.antelope.email>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <3b4aed10-5422-408e-9ad9-123ff2778329@gulbrandsen.priv.no> <547EE903.5090900@pscs.co.uk> <CAKHUCzy01RBUqsrds=+QBZpRLUCQBqJ5b4-J_GF2fGfpsMMCsA@mail.gmail.com> <4a62a767-ca9d-4d6d-959a-1ce2da0c574b@gulbrandsen.priv.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Date: Thu, 11 Dec 2014 15:29:56 +0000
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/VTsnImOpUQTTkrmzV-6Oht_F4ho
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 15:30:01 -0000

Now I worry that I may have tested one twice. Oh well.

Arnt


From nobody Thu Dec 11 07:47:45 2014
Return-Path: <stujenerin@aol.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 1B5A91ACE97 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 07:47:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 CUgIkJSbICPr for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 07:47:35 -0800 (PST)
Received: from omr-m3.mx.aol.com (omr-m3.mx.aol.com [64.12.233.221]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE1A71A9028 for <imapext@ietf.org>; Thu, 11 Dec 2014 07:47:35 -0800 (PST)
Received: from mtaout-aag01.mx.aol.com (mtaout-aag01.mx.aol.com [172.26.126.77]) by omr-m3.mx.aol.com (Outbound Mail Relay) with ESMTP id 198DB38000083 for <imapext@ietf.org>; Thu, 11 Dec 2014 10:47:35 -0500 (EST)
Received: from [10.172.0.204] (unknown [10.172.0.204]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-aag01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id A503238000088 for <imapext@ietf.org>; Thu, 11 Dec 2014 10:47:34 -0500 (EST)
Message-ID: <5489BC96.2050104@aol.com>
Date: Thu, 11 Dec 2014 10:47:34 -0500
From: Stuart Brandt <stujenerin@aol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: imapext@ietf.org
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org> <54899F1E.9030801@aol.com> <5489A0C6.4070807@pscs.co.uk>
In-Reply-To: <5489A0C6.4070807@pscs.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1418312855; bh=uzVFAkxxE5bX6YGbS+0lTJt2R2c2A63+LhUHE0wUr5A=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=kHY9guYA3SGxvUg0BwbfFvWpO3QjwnIyHaCjkypw2C8ej1LfDmV7p02lOmvHuZsxL ovfvussYW8j5+YrGcQlaMY2z01S5nQkt6u+MBH5MHfDJh6GIzltHI0O0iuxZXgWZ+w hV2hE6oE81xhAd+kY6rtnnse+ZykXysGPuzwpgDk=
x-aol-sid: 3039ac1a7e4d5489bc96000d
X-AOL-IP: 10.172.0.204
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/QRIy9gPOmkbKIzrQpKgTbsrP5Pc
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 15:47:41 -0000

Hi Paul -

My responses are inline

On 12/11/14 8:48 AM, Paul Smith wrote:
>
> On 11/12/2014 13:41, Stuart Brandt wrote:
>> Is snippet intended to be immutable? A server figuring out how to best
>> parse an HTML body part and offer up of the most meaningful snippet
>> for a user almost assuredly will result in versioning of the
>> extraction algorithm, thereby leading to the potential for a mutable
>> snippet element.
>
> Does it matter?

Yes. Mutable implies the need for synchronizing snippet changes between 
client and server, which in turn might have implications for 
QRESYNC/CONDSTORE or other synchronization approaches.

>
>> Additionally, a fixed sized snippet seems limiting given the trend of
>> using the 'stretch' gesture on mobile devices to expose an increasing
>> amount of snippet/message while viewing a message listing.
>
> Surely the point of 'snippet' is to allow the client to get 100+
> snippets in one FETCH command (like they can get subject, sender, date).
> That has to be quick. If it takes 0.1 seconds per message to
> generate/retrieve the snippet, that's too slow in this situation. Having
> a fixed size snippet will mean that the server can cache/precalculate
> it, making the responses potentially really quick.
>
> Once the user starts interacting with a particular email, then the
> client will probably want to fetch the whole body content, as the user
> is interested in the message. If it takes 0.1 seconds here, it doesn't
> matter.

I don't dispute the value of fixed sized snippet for caching. What I'm 
questioning is whether all clients and all servers should use a single 
fixed size indicated by this spec. Whether it be 'relaxed' vs. 'compact' 
list spacing in desktop Web clients, or pinch/stretch gestures performed 
on a tablet's message list, user viewable snippet sizes are something 
that's been changing over the last few years. Given these changes, 
something along the line of...
- server advertising its max snippet size
- client indicating how much of the snippet it wants
...seems to be a bit more flexible than a fixed size.

- Stuart


>
>
>
> -
>
>
> Paul Smith Computer Services
> Tel: 01484 855800
> Vat No: GB 685 6987 53
>
> Sign up for news & updates at http://www.pscs.co.uk/go/subscribe
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext


From nobody Thu Dec 11 08:54:17 2014
Return-Path: <paul@pscs.co.uk>
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 00E4A1A6F32 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 08:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ePQ9sxxsT-Ya for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 08:54:13 -0800 (PST)
Received: from mail.pscs.co.uk (mail.pscs.co.uk [188.65.177.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 077871A1F04 for <imapext@ietf.org>; Thu, 11 Dec 2014 08:54:12 -0800 (PST)
Authentication-Results: mail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=paul
Received: from lmail.pscs.co.uk ([82.68.5.206]) by mail.pscs.co.uk ([188.65.177.237] running VPOP3) with ESMTP for <imapext@ietf.org>; Thu, 11 Dec 2014 16:59:01 -0000
Authentication-Results: lmail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=paul
Received: from [192.168.66.101] ([192.168.66.101]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTP for <imapext@ietf.org>; Thu, 11 Dec 2014 16:53:59 -0000
Message-ID: <5489CC26.9010002@pscs.co.uk>
Date: Thu, 11 Dec 2014 16:53:58 +0000
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: imapext@ietf.org
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org> <54899F1E.9030801@aol.com> <5489A0C6.4070807@pscs.co.uk> <5489BC96.2050104@aol.com>
In-Reply-To: <5489BC96.2050104@aol.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V6.11 - Registered
X-Organisation: Paul Smith Computer Services
X-Authenticated-Sender: paul
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/RpzUTe0S-YprK-Mm5gM8F0Iavjc
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 16:54:16 -0000

On 11/12/2014 15:47, Stuart Brandt wrote:
> Hi Paul -
>
> My responses are inline
>
> On 12/11/14 8:48 AM, Paul Smith wrote:
>>
>> On 11/12/2014 13:41, Stuart Brandt wrote:
>>> Is snippet intended to be immutable? A server figuring out how to best
>>> parse an HTML body part and offer up of the most meaningful snippet
>>> for a user almost assuredly will result in versioning of the
>>> extraction algorithm, thereby leading to the potential for a mutable
>>> snippet element.
>>
>> Does it matter?
>
> Yes. Mutable implies the need for synchronizing snippet changes 
> between client and server, which in turn might have implications for 
> QRESYNC/CONDSTORE or other synchronization approaches.

But does it matter?

What I mean is, if one day, the SNIPPET gets returned as:

"Hi Paul - My responses are inline On 12/11/14 8:48 AM, Paul Smith wrote: "

and the next day it would have been returned as:

"Hi Paul - My responses are inline Yes. Mutable implies the need for 
synchronizing snippet changes"

does that really matter? Will it cause real problems if the client has 
cached the old snippet and doesn't refresh it?

>
> I don't dispute the value of fixed sized snippet for caching. What I'm 
> questioning is whether all clients and all servers should use a single 
> fixed size indicated by this spec. Whether it be 'relaxed' vs. 
> 'compact' list spacing in desktop Web clients, or pinch/stretch 
> gestures performed on a tablet's message list, user viewable snippet 
> sizes are something that's been changing over the last few years. 
> Given these changes, something along the line of...
> - server advertising its max snippet size
> - client indicating how much of the snippet it wants
> ...seems to be a bit more flexible than a fixed size.
OK, as long as the server can specify its maximum size, and the client 
can't expect to get more than that. In that case, the server can just 
cache the maximum size and return a subset of that if the client wants 
less. If the client can request any size snippet, then the server could 
have to work it out each time.


-


Paul Smith Computer Services
Tel: 01484 855800
Vat No: GB 685 6987 53

Sign up for news & updates at http://www.pscs.co.uk/go/subscribe


From nobody Thu Dec 11 09:28:25 2014
Return-Path: <stujenerin@aol.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 2367E1A854D for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 09:28:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 9GxIsQjPM6Nm for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 09:28:22 -0800 (PST)
Received: from omr-m10.mx.aol.com (omr-m10.mx.aol.com [64.12.143.86]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A6631A8860 for <imapext@ietf.org>; Thu, 11 Dec 2014 09:28:22 -0800 (PST)
Received: from mtaout-aae02.mx.aol.com (mtaout-aae02.mx.aol.com [172.27.1.98]) by omr-m10.mx.aol.com (Outbound Mail Relay) with ESMTP id 35B867047A4BC for <imapext@ietf.org>; Thu, 11 Dec 2014 12:28:21 -0500 (EST)
Received: from [10.172.0.204] (unknown [10.172.0.204]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-aae02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id C356338000087 for <imapext@ietf.org>; Thu, 11 Dec 2014 12:28:17 -0500 (EST)
Message-ID: <5489D431.9010705@aol.com>
Date: Thu, 11 Dec 2014 12:28:17 -0500
From: Stuart Brandt <stujenerin@aol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: imapext@ietf.org
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org> <54899F1E.9030801@aol.com> <5489A0C6.4070807@pscs.co.uk> <5489BC96.2050104@aol.com> <5489CC26.9010002@pscs.co.uk>
In-Reply-To: <5489CC26.9010002@pscs.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1418318901; bh=VU4XhBRTCxefO6Sn+incskTPCz+SOvX1yJzJViWJ+UI=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=tKT55/SGHlOGOjEEgGjB4rzT0VNnNGjlyBC/99D4YcA0foBdScGW/Up4W3AuVQ0sb 9cdrOHwaUv1u2WxSzHgHo72JsqcUwZ/fLeHSA/vQp7V17zWv3cKvj7oOjZw48KzZmJ I7sJpikcA2wSTl8sZUkh5xWgHBtUJJnLicELmUt0=
x-aol-sid: 3039ac1b01625489d4310022
X-AOL-IP: 10.172.0.204
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/auf4dbcKR6bf6DNlCXCirQUmiE0
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 17:28:24 -0000

Inline...

On 12/11/14 11:53 AM, Paul Smith wrote:
>
> On 11/12/2014 15:47, Stuart Brandt wrote:
>> Hi Paul -
>>
>> My responses are inline
>>
>> On 12/11/14 8:48 AM, Paul Smith wrote:
>>>
>>> On 11/12/2014 13:41, Stuart Brandt wrote:
>>>> Is snippet intended to be immutable? A server figuring out how to best
>>>> parse an HTML body part and offer up of the most meaningful snippet
>>>> for a user almost assuredly will result in versioning of the
>>>> extraction algorithm, thereby leading to the potential for a mutable
>>>> snippet element.
>>>
>>> Does it matter?
>>
>> Yes. Mutable implies the need for synchronizing snippet changes
>> between client and server, which in turn might have implications for
>> QRESYNC/CONDSTORE or other synchronization approaches.
>
> But does it matter?
>
> What I mean is, if one day, the SNIPPET gets returned as:
>
> "Hi Paul - My responses are inline On 12/11/14 8:48 AM, Paul Smith wrote: "
>
> and the next day it would have been returned as:
>
> "Hi Paul - My responses are inline Yes. Mutable implies the need for
> synchronizing snippet changes"
>
> does that really matter? Will it cause real problems if the client has
> cached the old snippet and doesn't refresh it?

The real problem is an impact to the user experience.

Setting text/plain aside because in multipart/alternative cases the 
text/html part is what's most useful for snippet generation...we see all 
sorts of interesting malformed HTML variants that are expected to be 
handled gracefully. Generation of snippet from such cases can yield some 
pretty useless snippets. When such a case is found and a workaround is 
released, it would be in the user's best interest if the prior ugly 
snippet were "fixed".

When this sort of issue comes up today with client-side snippet 
generation (or HTML rendering for that matter), a new app/client is 
released and in some cases it's auto-updated on the user's device. In 
the end, the user experience is made whole.


>
>>
>> I don't dispute the value of fixed sized snippet for caching. What I'm
>> questioning is whether all clients and all servers should use a single
>> fixed size indicated by this spec. Whether it be 'relaxed' vs.
>> 'compact' list spacing in desktop Web clients, or pinch/stretch
>> gestures performed on a tablet's message list, user viewable snippet
>> sizes are something that's been changing over the last few years.
>> Given these changes, something along the line of...
>> - server advertising its max snippet size
>> - client indicating how much of the snippet it wants
>> ...seems to be a bit more flexible than a fixed size.
> OK, as long as the server can specify its maximum size, and the client
> can't expect to get more than that. In that case, the server can just
> cache the maximum size and return a subset of that if the client wants
> less. If the client can request any size snippet, then the server could
> have to work it out each time.
>
>
> -
>
>
> Paul Smith Computer Services
> Tel: 01484 855800
> Vat No: GB 685 6987 53
>
> Sign up for news & updates at http://www.pscs.co.uk/go/subscribe
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext


From nobody Thu Dec 11 09:42:00 2014
Return-Path: <prvs=442288e542=j.sb@sta.samsung.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 F2DF01A904C for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 09:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.596
X-Spam-Level: ***
X-Spam-Status: No, score=3.596 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, 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 C4UF4YurdLby for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 09:41:58 -0800 (PST)
Received: from smg1.telecom.sna.samsung.com (unknown [63.166.115.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A56E1A9033 for <imapext@ietf.org>; Thu, 11 Dec 2014 09:41:58 -0800 (PST)
X-AuditID: 41a9fa1f-f79486d0000004ef-9f-5489d75b7ec0
Received: from exHub3.telecom.sna.samsung.com (Unknown_Domain [105.52.12.230]) by smg1.telecom.sna.samsung.com (SMGOUT STA) with SMTP id 0F.A5.01263.B57D9845; Thu, 11 Dec 2014 11:41:47 -0600 (CST)
Received: from EXMB5.telecom.sna.samsung.com ([fe80::5f4:56d9:ea68:f480]) by exHub3.telecom.sna.samsung.com ([fe80::c8b4:f629:c3bb:7bbc%17]) with mapi id 14.03.0146.000; Thu, 11 Dec 2014 11:42:02 -0600
From: Jayantheesh S B <j.sb@sta.samsung.com>
To: 'Stuart Brandt' <stujenerin@aol.com>, 'Alexey Melnikov' <alexey.melnikov@isode.com>
Thread-Topic: [imapext] [IMAP] APPEND Command Usage
Thread-Index: Ac/zikIaeRUU045cSKC+QFTd6ghr0ZxK6Vlg48oYyFOAAJQ50oAAgMAAgAB8E7CAKoibP4ABNvGt//6htqA=
Date: Thu, 11 Dec 2014 17:42:01 +0000
Message-ID: <02454F842DD7B449B96715A2AD90C0363E989A68@exMB5.telecom.sna.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <9EB51A28-A50B-4494-A895-BF2E2C71C46B@isode.com> <20141102184949.Horde.qakr4M6-mMtk2LS-NnDAmw2@bigworm.curecanti.org> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com>
In-Reply-To: <5488A5C9.9050904@aol.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [105.52.12.197]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsWSacLzTDf6emeIwec/ZhYzVhdZPJ7FZdH1 MtyB2eP+7pXsHkuW/GTyONVsGMAcxW2TlFhSFpyZnqdvl8CdsadpAktBn1zFzHNtzA2MmyW6 GDk5JARMJA7euc8KYYtJXLi3nq2LkYtDSOAYo8T0M7eYIJyzjBKXFx5g6WJk52AT0JF4EgxS LyIQKTHh7yw2EJtZQFti1ef1jCC2sICRxObne5i7GDmAaowl/p+xhChPkjj6og2shEVAVeLJ h33sIDavQIhE45YlUJsmckg0/drCBJLgFFCXaPh1EayBEei276fWMEHsEpe49WQ+E8TNAhJL 9pxnhrBFJV4+/gf1i6LE3F83mSHqdSQW7P4Ed+eyha+ZIRYLSpyc+YRlAqPYLCRjZyFpmYWk ZRaSlgWMLKsYZYpz0w31SlJzUpPzc/WK8xL1ihNzi0vz0vWA/E2MwMhyXPlLfgfjuu32hxiZ ODgPMUpwcEmJFKfmpaQWJZaWZMSDoie+GBg/Ug2My5Y+mPhWh/GMzJV9j6suLhZYwr6/dm16 opSsXa6qiBzjZLtJYif2qD1Krb7i8Sz2kPRi55fPf0yrs7RqYH3++9R0YRupuHY3v4+LuNU2 pxtd/7eN5aVd5bL4wsyNM6K/T/175aDs5vfNvY6H62R0w3Ttilnyf300PC38fj+r5Gmh9/MC rlqHKbEUZyQaajEXFScCAIod72J3AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/Gx6kEzic0f5qdRWcb9X7HCpCBj8
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 11 Dec 2014 17:42:00 -0000

Sounds OK. By this way, we can avoid changing the already registered respon=
se "TOOBIG" for APPEND command as part of CATENATE extension (rfc4469).=20

-----Original Message-----
From: Stuart Brandt [mailto:stujenerin@aol.com]=20
Sent: Wednesday, December 10, 2014 2:58 PM
To: Jayantheesh S B; 'Alexey Melnikov'
Cc: 'imapext@ietf.org'
Subject: Re: [imapext] [IMAP] APPEND Command Usage

 From a server perspective, the proposal solves my concern. From a client p=
erspective, I'm not sure whether the addition of [SP nz-number] to the TOOB=
IG response would present problems for clients that only implement CATENATE=
 and not APPENDLIMIT. I too would like to see others chime in on that part.

 From what I see, most IMAP sessions either precede an APPEND with a SELECT=
/EXAMINE or LIST...likely to confirm the existence of the target mailbox in=
to which they're going to append.  The proposal already covers SELECT/EXAMI=
NE, so would it be reasonable to add the APPENDLIMIT=3Dx as an attribute to=
 the LIST response data in order to reflect any per-mailbox limit and avoid=
 trying to convey the limit as part of the TOOBIG response code to APPEND? =
Something along the line of:

C: t1 LIST "" "%"
S: * LIST (\Marked \HasNoChildren) "/" Inbox
S: * LIST (\HasNoChildren) "/" ToDo
S: * LIST (\HasChildren) "/" Projects
S: * LIST (\Sent \HasNoChildren) "/" SentMail
S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=3D257890) "/" MyDraf=
ts
S: * LIST (\Trash \HasNoChildren) "/" Trash
S: t1 OK done

Comments?

- Stuart

On 12/10/14 11:20 AM, Jayantheesh S B wrote:
> Yes, I agree with your comments. Existing functionality should be broken =
with this new proposal.
>
> But the TOOBIG response syntax does not convey the size supported by=20
> the server
>
> resp-text-code =3D/ toobig-response-code / badurl-response-code=20
> toobig-response-code =3D "TOOBIG"
>
> Reusing the TOOBIG response code with updated syntax like below solves=20
> the issue
>
> toobig-response-code =3D " TOOBIG " [SP nz-number] resp-text-code /=3D =20
> toobig-response-code
>
> Please share your comments.
>
> Regards,
> Jay
>
> -----Original Message-----
> From: Stuart Brandt [mailto:stujenerin@aol.com]
> Sent: Tuesday, December 09, 2014 8:25 PM
> To: Jayantheesh S B; 'Alexey Melnikov'
> Cc: 'imapext@ietf.org'
> Subject: Re: [imapext] [IMAP] APPEND Command Usage
>
> If I'm understanding the proposal correctly, a server that has already im=
plemented CATENATE and now implements APPENDLIMIT is left in an ambiguous s=
tate whenever the limit is exceeded. If it returns [TOOBIG], then it's not =
compliant with the APPENDLIMIT recommendation. If it returns [APPENDLIMIT x=
] then it's returning an unexpected response to clients that have yet to im=
plement APPENDLIMIT, thereby "breaking"
> existing functionality.
>
>
> On 12/9/14 5:16 PM, Jayantheesh S B wrote:
>> Hi All,
>>
>> Thanks for your response.
>>
>> New response code APPENDLIMIT will be returned as part of SELECT respons=
e to convey per mailbox limit
>>    and APPEND command response, if the APPENTLIMIT size is exceeded.
>>
>> C: t2 SELECT INBOX
>> S: * 172 EXISTS
>> S: * OK [APPENDLIMIT 257890] Maximum upload limit
>> S: [...]
>> S: t2 OK [READ-WRITE] SELECT completed
>>
>> C: t1 APPEND "Draft" (\SEEN \DRAFT) {98994952}
>> S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size
>>
>> Whereas TOOBIG response, does not covey the size restriction applied by =
the server.
>>
>>    resp-text-code =3D/ toobig-response-code / badurl-response-code
>>    toobig-response-code =3D "TOOBIG"
>>
>> We feel APPENDLIMIT response can convey per mailbox size restriction and=
 it can overcome the limitation of TOOBIG response.
>>
>> Please share your thoughts.
>>
>> Regards,
>> Jay


From nobody Thu Dec 11 13:06:14 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 BC7EE1A879A for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 13:06:12 -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 rwhspW6yRJWS for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 13:06:10 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5AAB1A8797 for <imapext@ietf.org>; Thu, 11 Dec 2014 13:06:10 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 3DD2420862 for <imapext@ietf.org>; Thu, 11 Dec 2014 16:06:10 -0500 (EST)
Received: from web3 ([10.202.2.213]) by compute5.internal (MEProxy); Thu, 11 Dec 2014 16:06:10 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:x-sasl-enc:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=mesmtp; bh=bC5OfeuXTpsVAR1bCRDsBZM+5L0=; b=gM+H mHcKJClj5CZMg7s6OKEdEDSaXVGxz2ocSskjdpasVIvbIdO9kX4XAoeCBtWx/l7N XchJr/roz014yzVNMZ/aRGZ9BQeXC8qCGfQvbwld+GENJAM0QFpJq/ddSq4W6D8H idsvgl7CPLLt0DkzCdtL4XiznR7i7aEguQIDF50=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=bC5OfeuXTpsVAR1bCRDsBZM+ 5L0=; b=ebGNyz80RBAphQs1NzxQqVgWG9a5qcAEbTTTqK5MWy0azyQTrOBW7LBK SxcmtRsCR6eVqNYItZlqRTIT3JenXm0BCJhOVvYWpKsU1DUWMzVQCMIPQ92Ccqyb JH2tnHsfG0A/c6OF/ayzTCcxKpvJGD656sYf4hh1d3Cr+JwHt2M=
Received: by web3.nyi.internal (Postfix, from userid 99) id 1C68611B325; Thu, 11 Dec 2014 16:06:10 -0500 (EST)
Message-Id: <1418331970.2414903.201842429.24482F84@webmail.messagingengine.com>
X-Sasl-Enc: pirPxXEQ9Sb+IzwOW8znabu4FteMG3aSRIPUDpcrYPd+ 1418331970
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-c5cca857
In-Reply-To: <5489D431.9010705@aol.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org> <54899F1E.9030801@aol.com> <5489A0C6.4070807@pscs.co.uk> <5489BC96.2050104@aol.com> <5489CC26.9010002@pscs.co.uk> <5489D431.9010705@aol.com>
Date: Fri, 12 Dec 2014 08:06:10 +1100
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/t7eR2Yrn3d9AALc9bb8Mfr2gs3c
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 21:06:13 -0000

On Fri, Dec 12, 2014, at 04:28 AM, Stuart Brandt wrote:
> Inline...
> 
> On 12/11/14 11:53 AM, Paul Smith wrote:
> > does that really matter? Will it cause real problems if the client has
> > cached the old snippet and doesn't refresh it?
> 
> The real problem is an impact to the user experience.
> 
> Setting text/plain aside because in multipart/alternative cases the 
> text/html part is what's most useful for snippet generation...we see all 
> sorts of interesting malformed HTML variants that are expected to be 
> handled gracefully. Generation of snippet from such cases can yield some 
> pretty useless snippets. When such a case is found and a workaround is 
> released, it would be in the user's best interest if the prior ugly 
> snippet were "fixed".
> 
> When this sort of issue comes up today with client-side snippet 
> generation (or HTML rendering for that matter), a new app/client is 
> released and in some cases it's auto-updated on the user's device. In 
> the end, the user experience is made whole.

You know what, messages don't change that often overall.  I would be totally happy with the idea that every time the modseq changes, the snippet is stale and a client should refetch if it cares.  The whole point is that it's

a) small
b) cheap for the server to deliver

So it's going to cost barely anything in bandwidth or server time to resend the snippet for any message that's had a modseq bump.

Bron.

-- 
  Bron Gondwana
  brong@fastmail.fm


From nobody Thu Dec 11 14:05:48 2014
Return-Path: <stujenerin@aol.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 C32D61A6FA7 for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 14:05:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 h7MceXcXG-6z for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 14:05:44 -0800 (PST)
Received: from omr-m3.mx.aol.com (omr-m3.mx.aol.com [64.12.233.221]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 164C01A6FE2 for <imapext@ietf.org>; Thu, 11 Dec 2014 14:05:44 -0800 (PST)
Received: from mtaout-aae02.mx.aol.com (mtaout-aae02.mx.aol.com [172.27.1.98]) by omr-m3.mx.aol.com (Outbound Mail Relay) with ESMTP id 5C9803800015D for <imapext@ietf.org>; Thu, 11 Dec 2014 17:05:43 -0500 (EST)
Received: from [10.172.0.204] (unknown [10.172.0.204]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-aae02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id A81723800008F for <imapext@ietf.org>; Thu, 11 Dec 2014 17:05:42 -0500 (EST)
Message-ID: <548A1536.2090709@aol.com>
Date: Thu, 11 Dec 2014 17:05:42 -0500
From: Stuart Brandt <stujenerin@aol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: imapext@ietf.org
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org> <54899F1E.9030801@aol.com> <5489A0C6.4070807@pscs.co.uk> <5489BC96.2050104@aol.com> <5489CC26.9010002@pscs.co.uk> <5489D431.9010705@aol.com> <1418331970.2414903.201842429.24482F84@webmail.messagingengine.com>
In-Reply-To: <1418331970.2414903.201842429.24482F84@webmail.messagingengine.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1418335543; bh=g9N32P+oudiNNQqWkb2MiSWNzkIPFzric5PlfJXlzpU=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=uKkGWhHySAAQQbJA53AXa3vXUFdI7tzA1OVaRV2xBL9zRlJ+ljrfKF3DyJoul7z0Z VZkCspEH5boolOF2d/HAjSPOypEQkpf8mhVRu87G4lbdjp6Q03BYlxVpbGFW+LDL2N LMwS/NcYusfm7kF/SdZ1q+h4mmUN3W53E3qKUAew=
x-aol-sid: 3039ac1b0162548a15360c90
X-AOL-IP: 10.172.0.204
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/8puQzbT9QXe-1mfGS9hzCnqgEfM
Subject: Re: [imapext] Fetching short text snippet for mails
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, 11 Dec 2014 22:05:47 -0000

> You know what, messages don't change that often overall.  I would be totally happy with the idea that every time the modseq changes, the snippet is stale and a client should refetch if it cares.  The whole point is that it's
>
> a) small
> b) cheap for the server to deliver
>
> So it's going to cost barely anything in bandwidth or server time to resend the snippet for any message that's had a modseq bump.
>
> Bron.
>

Sounds good. I'm assuming a modseq change whenever snippet changes would 
be appropriate too?

- Stuart


From nobody Thu Dec 11 18:46:32 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 2E3831A916D for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 18:46:31 -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 WlIJgjObBqGC for <imapext@ietfa.amsl.com>; Thu, 11 Dec 2014 18:46:29 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BB981A9162 for <imapext@ietf.org>; Thu, 11 Dec 2014 18:46:29 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id B337420CF6 for <imapext@ietf.org>; Thu, 11 Dec 2014 21:46:28 -0500 (EST)
Received: from web3 ([10.202.2.213]) by compute5.internal (MEProxy); Thu, 11 Dec 2014 21:46:28 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:x-sasl-enc:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=mesmtp; bh=zTFzQFcGRODPCCVKc7Vx9g2Z1Nk=; b=VR+u 9BrEupLXJaf7HSw8I8FDRvnltV29Mf8s7QA8OL+kbb7jUoZxpz8to9qmXSqFsTwR u53Lg2NW9KLjgNCyTVpo1vLfr4qzzX7QyWvPkaoMk+7iTAqwbk5qkNAmX/ymDFKP IE7QxtDgkQzXRfw/cnE8lnLD+l7V7lyd93gLtyA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=zTFzQFcGRODPCCVKc7Vx9g2Z 1Nk=; b=Gj2bf1bDnvuQuucGKqr4WTqZI0IUHbB5iNtkkDcXZJyO15v5sqHSlPLA p93up80bS7Q5iVJgfzn2VFA8CjWmm99ib1rZxfLuJEhdqobWj6Y2G3AKnzjPDA86 LH7uVL5QywtEpHYntsidU3Mhmh1BD2SMvblkbbc18J7js/AzbJI=
Received: by web3.nyi.internal (Postfix, from userid 99) id 846FD100C26; Thu, 11 Dec 2014 21:46:28 -0500 (EST)
Message-Id: <1418352388.2848622.201944205.6D1B83DB@webmail.messagingengine.com>
X-Sasl-Enc: K1TIQCuurWs1gP5EYRtl4l4dAAqJyYEFYERN8XiEZmFn 1418352388
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-2cf234a9
In-Reply-To: <548A1536.2090709@aol.com>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi> <D1A7D6AA6F8659ECB96BD83A@caldav.corp.apple.com> <330724e6-c365-4eec-844a-57d16f174432@flaska.net> <20141205172538.Horde.ebZJKnejNJztXB6ATA8Eqw1@bigworm.curecanti.org> <54899F1E.9030801@aol.com> <5489A0C6.4070807@pscs.co.uk> <5489BC96.2050104@aol.com> <5489CC26.9010002@pscs.co.uk> <5489D431.9010705@aol.com> <1418331970.2414903.201842429.24482F84@webmail.messagingengine.com> <548A1536.2090709@aol.com>
Date: Fri, 12 Dec 2014 13:46:28 +1100
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/wyMOBTwcxniyktSt6SIsOMoJUy8
Subject: Re: [imapext] Fetching short text snippet for mails
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, 12 Dec 2014 02:46:31 -0000

On Fri, Dec 12, 2014, at 09:05 AM, Stuart Brandt wrote:
> > You know what, messages don't change that often overall.  I would be totally happy with the idea that every time the modseq changes, the snippet is stale and a client should refetch if it cares.  The whole point is that it's
> >
> > a) small
> > b) cheap for the server to deliver
> >
> > So it's going to cost barely anything in bandwidth or server time to resend the snippet for any message that's had a modseq bump.
> >
> > Bron.
> >
> 
> Sounds good. I'm assuming a modseq change whenever snippet changes would 
> be appropriate too?

Absolutely.  Right now at FastMail we just use the rfc 5257 annotation /vendor/messagingengine.com/preview, so we get a modseq change "for free" when we change it, it's just part of the data model.

Bron.

-- 
  Bron Gondwana
  brong@fastmail.fm


From nobody Fri Dec 12 02:25:03 2014
Return-Path: <alexey.melnikov@isode.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 D01801ACCDA for <imapext@ietfa.amsl.com>; Fri, 12 Dec 2014 02:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.111
X-Spam-Level: 
X-Spam-Status: No, score=-0.111 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 PWjaSUyPUSUA for <imapext@ietfa.amsl.com>; Fri, 12 Dec 2014 02:24:52 -0800 (PST)
Received: from statler.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 719821ACC7F for <imapext@ietf.org>; Fri, 12 Dec 2014 02:24:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418379891; d=isode.com; s=selector; i=@isode.com; bh=5vpdNRX2AUCev43sR7Odurb0VmIccgmSa+VoTy9gOqk=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=aw4AUuEXMV1UBYkarAPVrvV9jMIq4EpN6LTV41nokGI9FaBM09uw9JRyVtkPTWMfNamQoA Z6fsihZmQpBTklAml6QN2/y3ha+EPTKQJEJv8FoWAWOGt1YSI8EkEaQ7hLMmgAPK6u10G1 8muNfCWByEh/tPRyapidjq5W0LS3XUA=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <VIrCcgB3u7tk@statler.isode.com>; Fri, 12 Dec 2014 10:24:51 +0000
Message-ID: <548AC263.3080800@isode.com>
Date: Fri, 12 Dec 2014 10:24:35 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: Stuart Brandt <stujenerin@aol.com>, Jayantheesh S B <j.sb@sta.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <20141102184949.Horde.qakr4M6-mMtk2LS-NnDAmw2@bigworm.curecanti.org> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com>
In-Reply-To: <5488A5C9.9050904@aol.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/HhwzXQYnqHiZZNhRobaiVLO7f7g
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 12 Dec 2014 10:24:58 -0000

Hi Stuart,

On 10/12/2014 19:58, Stuart Brandt wrote:
> From a server perspective, the proposal solves my concern. From a 
> client perspective, I'm not sure whether the addition of [SP 
> nz-number] to the TOOBIG response would present problems for clients 
> that only implement CATENATE and not APPENDLIMIT. I too would like to 
> see others chime in on that part.
>
> From what I see, most IMAP sessions either precede an APPEND with a 
> SELECT/EXAMINE or LIST...likely to confirm the existence of the target 
> mailbox into which they're going to append.  The proposal already 
> covers SELECT/EXAMINE, so would it be reasonable to add the 
> APPENDLIMIT=x as an attribute to the LIST response data in order to 
> reflect any per-mailbox limit and avoid trying to convey the limit as 
> part of the TOOBIG response code to APPEND? Something along the line of:
>
> C: t1 LIST "" "%"
> S: * LIST (\Marked \HasNoChildren) "/" Inbox
> S: * LIST (\HasNoChildren) "/" ToDo
> S: * LIST (\HasChildren) "/" Projects
> S: * LIST (\Sent \HasNoChildren) "/" SentMail
> S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=257890) "/" 
> MyDrafts
> S: * LIST (\Trash \HasNoChildren) "/" Trash
All mailbox attributes are typically checked for equality, so this this 
a departure from this principle. (I know we started to violate this rule 
in CAPABILITY response)
So personally, I prefer if we add a new STATUS item for APPEND limit. 
Then we can use STATUS-in-LIST bridge 
(https://tools.ietf.org/html/rfc5819) to return this information.

As clients that want to obey APPENDLIMIT would need to be modified 
anyway, they might as well be modified to support RFC 5819 syntax.

But otherwise I am Ok with being able to return this information in LIST.
> S: t1 OK done
>
> Comments?
>
> - Stuart
>
> On 12/10/14 11:20 AM, Jayantheesh S B wrote:
>> Yes, I agree with your comments. Existing functionality should be 
>> broken with this new proposal.
>>
>> But the TOOBIG response syntax does not convey the size supported by 
>> the server
>>
>> resp-text-code =/ toobig-response-code / badurl-response-code
>> toobig-response-code = "TOOBIG"
>>
>> Reusing the TOOBIG response code with updated syntax like below 
>> solves the issue
>>
>> toobig-response-code = " TOOBIG " [SP nz-number]
>> resp-text-code /=  toobig-response-code
>>
>> Please share your comments.
>>
>> Regards,
>> Jay
>>
>> -----Original Message-----
>> From: Stuart Brandt [mailto:stujenerin@aol.com]
>> Sent: Tuesday, December 09, 2014 8:25 PM
>> To: Jayantheesh S B; 'Alexey Melnikov'
>> Cc: 'imapext@ietf.org'
>> Subject: Re: [imapext] [IMAP] APPEND Command Usage
>>
>> If I'm understanding the proposal correctly, a server that has 
>> already implemented CATENATE and now implements APPENDLIMIT is left 
>> in an ambiguous state whenever the limit is exceeded. If it returns 
>> [TOOBIG], then it's not compliant with the APPENDLIMIT 
>> recommendation. If it returns [APPENDLIMIT x] then it's returning an 
>> unexpected response to clients that have yet to implement 
>> APPENDLIMIT, thereby "breaking"
>> existing functionality.
>>
>>
>> On 12/9/14 5:16 PM, Jayantheesh S B wrote:
>>> Hi All,
>>>
>>> Thanks for your response.
>>>
>>> New response code APPENDLIMIT will be returned as part of SELECT 
>>> response to convey per mailbox limit
>>>    and APPEND command response, if the APPENTLIMIT size is exceeded.
>>>
>>> C: t2 SELECT INBOX
>>> S: * 172 EXISTS
>>> S: * OK [APPENDLIMIT 257890] Maximum upload limit
>>> S: [...]
>>> S: t2 OK [READ-WRITE] SELECT completed
>>>
>>> C: t1 APPEND "Draft" (\SEEN \DRAFT) {98994952}
>>> S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size
>>>
>>> Whereas TOOBIG response, does not covey the size restriction applied 
>>> by the server.
>>>
>>>    resp-text-code =/ toobig-response-code / badurl-response-code
>>>    toobig-response-code = "TOOBIG"
>>>
>>> We feel APPENDLIMIT response can convey per mailbox size restriction 
>>> and it can overcome the limitation of TOOBIG response.
>>>
>>> Please share your thoughts.
>>>
>>> Regards,
>>> Jay


From nobody Fri Dec 12 03:03:47 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 5E2131ACCDF for <imapext@ietfa.amsl.com>; Fri, 12 Dec 2014 03:03:45 -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 EKfOVt5JJ__R for <imapext@ietfa.amsl.com>; Fri, 12 Dec 2014 03:03:43 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 795D01A1A73 for <imapext@ietf.org>; Fri, 12 Dec 2014 03:03:43 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D87DF20648 for <imapext@ietf.org>; Fri, 12 Dec 2014 06:03:42 -0500 (EST)
Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Fri, 12 Dec 2014 06:03:42 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:x-sasl-enc:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=mesmtp; bh=WKE6o5cERopmych742NmrRJOMkc=; b=YTlg UrUIWivzQEKi6B/fU7TB6nfIaEV4Zu3R7+ktzoGfRYki+GoGNVfk0la8gGCHrPZu gxX6utKW1bA3KyzkWsDzT59BR3scq21ZZKfG5Oz2pxYaKHHza2G8YbYxTTeTSTx8 QCFn00DWTOpBATOo6nl8bHIG62Mm6wDX97w2YpU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=WKE6o5cERopmych742NmrRJO Mkc=; b=sEIYEJGkTNyYw27Dhw6ywrkPONGhnlxRyGZ3zqB3iwhy35t1Ba1Me71l bMXonuA0lSGZoODFM9a9Mlqy7Gv+d8/oCaB7dTy1HcJBRT6bcAfE1ifnTzm1f+C4 deKNl+uMXqPzcAsaCp2bIrflJSfgbxn9mcHgoYYbA8fpaxyJB1k=
Received: by web3.nyi.internal (Postfix, from userid 99) id 9F548105C06; Fri, 12 Dec 2014 06:03:42 -0500 (EST)
Message-Id: <1418382222.2991667.202054141.5AC5F4F5@webmail.messagingengine.com>
X-Sasl-Enc: e3KYqjppxVB3vF5tI5q4SZchtC5UtXN2uofIAMQkUCcp 1418382222
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-ebaa3f00
In-Reply-To: <548AC263.3080800@isode.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <20141102184949.Horde.qakr4M6-mMtk2LS-NnDAmw2@bigworm.curecanti.org> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com>
Date: Fri, 12 Dec 2014 22:03:42 +1100
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/8kSqsrQVUt0zKqLbzixW5AhBZKY
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 12 Dec 2014 11:03:45 -0000

On Fri, Dec 12, 2014, at 09:24 PM, Alexey Melnikov wrote:
> All mailbox attributes are typically checked for equality, so this this 
> a departure from this principle. (I know we started to violate this rule 
> in CAPABILITY response)
> So personally, I prefer if we add a new STATUS item for APPEND limit. 
> Then we can use STATUS-in-LIST bridge 
> (https://tools.ietf.org/html/rfc5819) to return this information.
> 
> As clients that want to obey APPENDLIMIT would need to be modified 
> anyway, they might as well be modified to support RFC 5819 syntax.
> 
> But otherwise I am Ok with being able to return this information in LIST.

Adding something in STATUS that doesn't also exist in the SELECT response
seems somewhat weird to me.

(speaking of STATUS-IN-LIST, I appear to have just pushed back my non-standard
MYRIGHTS-IN-LIST extension to Cyrus master.  It makes sense - while you're
grabbing the status, you also want to grab permissions for the purpose of UI display.
We should write that up too)

Bron.

-- 
  Bron Gondwana
  brong@fastmail.fm


From nobody Fri Dec 12 03:51:57 2014
Return-Path: <alexey.melnikov@isode.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 0F8B51ACD09 for <imapext@ietfa.amsl.com>; Fri, 12 Dec 2014 03:51:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 yoT4CxYe9V57 for <imapext@ietfa.amsl.com>; Fri, 12 Dec 2014 03:51:52 -0800 (PST)
Received: from statler.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id A196F1ACCEA for <imapext@ietf.org>; Fri, 12 Dec 2014 03:51:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418385081; d=isode.com; s=selector; i=@isode.com; bh=MJgDhP84NtI5ZD4n7zdiGocGrxkOme1rcd0iEf7zpvU=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=kpNG3KmHaJagHSZroXHA4kR9H6OSw/5BmhW7XTY133g+RTXytgAS70UyK972WeNWuPDAQv ezgxF1AAPbqeewt3pvyEmprtRVjKl5xFtg8DC9h5QkfYPrW/1hkYpUb4GA5FlZ+kLTy1qo VHTZNfBEoxvu8zCKk25cm6zqy3fB308=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <VIrWuAB3u4kP@statler.isode.com>; Fri, 12 Dec 2014 11:51:21 +0000
Message-ID: <548AD6A8.4070900@isode.com>
Date: Fri, 12 Dec 2014 11:51:04 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: Bron Gondwana <brong@fastmail.fm>, imapext@ietf.org
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <1418382222.2991667.202054141.5AC5F4F5@webmail.messagingengine.com>
In-Reply-To: <1418382222.2991667.202054141.5AC5F4F5@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/a6V-bI6NDf3L6P9tHGY34I5JqmM
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 12 Dec 2014 11:51:54 -0000

On 12/12/2014 11:03, Bron Gondwana wrote:
> On Fri, Dec 12, 2014, at 09:24 PM, Alexey Melnikov wrote:
>> All mailbox attributes are typically checked for equality, so this this
>> a departure from this principle. (I know we started to violate this rule
>> in CAPABILITY response)
>> So personally, I prefer if we add a new STATUS item for APPEND limit.
>> Then we can use STATUS-in-LIST bridge
>> (https://tools.ietf.org/html/rfc5819) to return this information.
>>
>> As clients that want to obey APPENDLIMIT would need to be modified
>> anyway, they might as well be modified to support RFC 5819 syntax.
>>
>> But otherwise I am Ok with being able to return this information in LIST.
> Adding something in STATUS that doesn't also exist in the SELECT response
> seems somewhat weird to me.
I think we already agreed that APPENDLIMIT response code will be 
returned on SELECT?
> (speaking of STATUS-IN-LIST, I appear to have just pushed back my non-standard
> MYRIGHTS-IN-LIST extension to Cyrus master.  It makes sense - while you're
> grabbing the status, you also want to grab permissions for the purpose of UI display.
> We should write that up too)
Sounds good. I would be happy to implement both client side and server side.


From nobody Fri Dec 12 07:40:27 2014
Return-Path: <stujenerin@aol.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 AFE3D1A1AEC for <imapext@ietfa.amsl.com>; Fri, 12 Dec 2014 07:40:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 FtlKU-1nP6J2 for <imapext@ietfa.amsl.com>; Fri, 12 Dec 2014 07:40:22 -0800 (PST)
Received: from omr-m5.mx.aol.com (omr-m5.mx.aol.com [64.12.232.237]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69EF31A8A15 for <imapext@ietf.org>; Fri, 12 Dec 2014 07:40:20 -0800 (PST)
Received: from mtaout-aah02.mx.aol.com (mtaout-aah02.mx.aol.com [172.27.1.142]) by omr-m5.mx.aol.com (Outbound Mail Relay) with ESMTP id 743E938000091; Fri, 12 Dec 2014 10:40:19 -0500 (EST)
Received: from [10.172.0.40] (unknown [10.172.0.40]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-aah02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 2264C38000095; Fri, 12 Dec 2014 10:40:19 -0500 (EST)
Message-ID: <548B0C59.1060907@aol.com>
Date: Fri, 12 Dec 2014 10:40:09 -0500
From: Stuart Brandt <stujenerin@aol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>,  Jayantheesh S B <j.sb@sta.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com>
In-Reply-To: <548AC263.3080800@isode.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1418398819; bh=n7VZZVq5Z6uxXQ/LfHG4amxVmp1WCXmPcqEQ3lFXMSE=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=TxHws4Lzy5IjGsqvICZ3gtJGsjlCQbE2Ot/ju/mx5kQYn/2tAfqAnYPreO91PtVGC +wEBxxlCl2XYQk9MGvY4Ir7adarPcEoJRbRvgSnZdpXosi/8h/daRZ5Js4R5CVesyK nWAYOK8/7YjTLZfdJ+GR88XSEi1HekXUnavegt6M=
x-aol-sid: 3039ac1b018e548b0c637388
X-AOL-IP: 10.172.0.40
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/L2KEOAWMtALOeXLFO_D_qfdLLCw
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 12 Dec 2014 15:40:25 -0000

Inline comments

On 12/12/14 5:24 AM, Alexey Melnikov wrote:
> Hi Stuart,
>
> On 10/12/2014 19:58, Stuart Brandt wrote:
>> From a server perspective, the proposal solves my concern. From a
>> client perspective, I'm not sure whether the addition of [SP
>> nz-number] to the TOOBIG response would present problems for clients
>> that only implement CATENATE and not APPENDLIMIT. I too would like to
>> see others chime in on that part.
>>
>> From what I see, most IMAP sessions either precede an APPEND with a
>> SELECT/EXAMINE or LIST...likely to confirm the existence of the target
>> mailbox into which they're going to append.  The proposal already
>> covers SELECT/EXAMINE, so would it be reasonable to add the
>> APPENDLIMIT=x as an attribute to the LIST response data in order to
>> reflect any per-mailbox limit and avoid trying to convey the limit as
>> part of the TOOBIG response code to APPEND? Something along the line of:
>>
>> C: t1 LIST "" "%"
>> S: * LIST (\Marked \HasNoChildren) "/" Inbox
>> S: * LIST (\HasNoChildren) "/" ToDo
>> S: * LIST (\HasChildren) "/" Projects
>> S: * LIST (\Sent \HasNoChildren) "/" SentMail
>> S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=257890) "/"
>> MyDrafts
>> S: * LIST (\Trash \HasNoChildren) "/" Trash
> All mailbox attributes are typically checked for equality, so this this
> a departure from this principle. (I know we started to violate this rule
> in CAPABILITY response)
> So personally, I prefer if we add a new STATUS item for APPEND limit.
> Then we can use STATUS-in-LIST bridge
> (https://tools.ietf.org/html/rfc5819) to return this information.
>
> As clients that want to obey APPENDLIMIT would need to be modified
> anyway, they might as well be modified to support RFC 5819 syntax.

And same goes for the server, because the client will want to query 
*every* server that supports APPENDLIMIT just in case it has per-mailbox 
limits. Unless I'm way off base here, a server with a simple 
mailbox-wide APPEND limit would need to implement APPENDLIMIT *plus* 
5819 and 5258 to support the client asking about per-mailbox limits -- 
unless we have the client assume that lack of support for 5819/5258 
implies that the server has no per-mailbox limits. Seems pretty involved.

>
> But otherwise I am Ok with being able to return this information in LIST.
>> S: t1 OK done
>>
>> Comments?
>>
>> - Stuart
>>
>> On 12/10/14 11:20 AM, Jayantheesh S B wrote:
>>> Yes, I agree with your comments. Existing functionality should be
>>> broken with this new proposal.
>>>
>>> But the TOOBIG response syntax does not convey the size supported by
>>> the server
>>>
>>> resp-text-code =/ toobig-response-code / badurl-response-code
>>> toobig-response-code = "TOOBIG"
>>>
>>> Reusing the TOOBIG response code with updated syntax like below
>>> solves the issue
>>>
>>> toobig-response-code = " TOOBIG " [SP nz-number]
>>> resp-text-code /=  toobig-response-code
>>>
>>> Please share your comments.
>>>
>>> Regards,
>>> Jay
>>>
>>> -----Original Message-----
>>> From: Stuart Brandt [mailto:stujenerin@aol.com]
>>> Sent: Tuesday, December 09, 2014 8:25 PM
>>> To: Jayantheesh S B; 'Alexey Melnikov'
>>> Cc: 'imapext@ietf.org'
>>> Subject: Re: [imapext] [IMAP] APPEND Command Usage
>>>
>>> If I'm understanding the proposal correctly, a server that has
>>> already implemented CATENATE and now implements APPENDLIMIT is left
>>> in an ambiguous state whenever the limit is exceeded. If it returns
>>> [TOOBIG], then it's not compliant with the APPENDLIMIT
>>> recommendation. If it returns [APPENDLIMIT x] then it's returning an
>>> unexpected response to clients that have yet to implement
>>> APPENDLIMIT, thereby "breaking"
>>> existing functionality.
>>>
>>>
>>> On 12/9/14 5:16 PM, Jayantheesh S B wrote:
>>>> Hi All,
>>>>
>>>> Thanks for your response.
>>>>
>>>> New response code APPENDLIMIT will be returned as part of SELECT
>>>> response to convey per mailbox limit
>>>>    and APPEND command response, if the APPENTLIMIT size is exceeded.
>>>>
>>>> C: t2 SELECT INBOX
>>>> S: * 172 EXISTS
>>>> S: * OK [APPENDLIMIT 257890] Maximum upload limit
>>>> S: [...]
>>>> S: t2 OK [READ-WRITE] SELECT completed
>>>>
>>>> C: t1 APPEND "Draft" (\SEEN \DRAFT) {98994952}
>>>> S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size
>>>>
>>>> Whereas TOOBIG response, does not covey the size restriction applied
>>>> by the server.
>>>>
>>>>    resp-text-code =/ toobig-response-code / badurl-response-code
>>>>    toobig-response-code = "TOOBIG"
>>>>
>>>> We feel APPENDLIMIT response can convey per mailbox size restriction
>>>> and it can overcome the limitation of TOOBIG response.
>>>>
>>>> Please share your thoughts.
>>>>
>>>> Regards,
>>>> Jay
>


From nobody Mon Dec 15 03:52:40 2014
Return-Path: <alexey.melnikov@isode.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 A39AB1A1B20 for <imapext@ietfa.amsl.com>; Mon, 15 Dec 2014 03:52:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 2_3O9hRL8K0V for <imapext@ietfa.amsl.com>; Mon, 15 Dec 2014 03:52:38 -0800 (PST)
Received: from statler.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0D21A1B34 for <imapext@ietf.org>; Mon, 15 Dec 2014 03:52:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418644356; d=isode.com; s=selector; i=@isode.com; bh=aHvM/qzVvvG5iq1K9YzwW6SfjTyLODFY+n1dmOsPQwg=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=wAr5+Ah7fZ+Y/ofghGRj/pqRJoqkNDUvq2nNgUhLdMWPjSerWhggkpQWj/0jO32fEsl4L4 RLFEYfNihWLchFyl8jG0U8N+abgsZP7kEZ1Og47BuIK/BqKpFbgMW45qKj16VY7Ehx86Mc 7CW/vueNfRORX+fLjPm1XJOw2/J1qGs=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <VI7LfwB3u3Qh@statler.isode.com>; Mon, 15 Dec 2014 11:52:35 +0000
Message-ID: <548ECB79.8000300@isode.com>
Date: Mon, 15 Dec 2014 11:52:25 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: Stuart Brandt <stujenerin@aol.com>, Jayantheesh S B <j.sb@sta.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com>
In-Reply-To: <548B0C59.1060907@aol.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/hkkYn2uvwXi94G1Pj131zutZhCY
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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: Mon, 15 Dec 2014 11:52:39 -0000

Hi Stuart,

On 12/12/2014 15:40, Stuart Brandt wrote:
> Inline comments
>
> On 12/12/14 5:24 AM, Alexey Melnikov wrote:
>> Hi Stuart,
>>
>> On 10/12/2014 19:58, Stuart Brandt wrote:
>>> From a server perspective, the proposal solves my concern. From a
>>> client perspective, I'm not sure whether the addition of [SP
>>> nz-number] to the TOOBIG response would present problems for clients
>>> that only implement CATENATE and not APPENDLIMIT. I too would like to
>>> see others chime in on that part.
>>>
>>> From what I see, most IMAP sessions either precede an APPEND with a
>>> SELECT/EXAMINE or LIST...likely to confirm the existence of the target
>>> mailbox into which they're going to append.  The proposal already
>>> covers SELECT/EXAMINE, so would it be reasonable to add the
>>> APPENDLIMIT=x as an attribute to the LIST response data in order to
>>> reflect any per-mailbox limit and avoid trying to convey the limit as
>>> part of the TOOBIG response code to APPEND? Something along the line 
>>> of:
>>>
>>> C: t1 LIST "" "%"
>>> S: * LIST (\Marked \HasNoChildren) "/" Inbox
>>> S: * LIST (\HasNoChildren) "/" ToDo
>>> S: * LIST (\HasChildren) "/" Projects
>>> S: * LIST (\Sent \HasNoChildren) "/" SentMail
>>> S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=257890) "/"
>>> MyDrafts
>>> S: * LIST (\Trash \HasNoChildren) "/" Trash
>> All mailbox attributes are typically checked for equality, so this this
>> a departure from this principle. (I know we started to violate this rule
>> in CAPABILITY response)
>> So personally, I prefer if we add a new STATUS item for APPEND limit.
>> Then we can use STATUS-in-LIST bridge
>> (https://tools.ietf.org/html/rfc5819) to return this information.
>>
>> As clients that want to obey APPENDLIMIT would need to be modified
>> anyway, they might as well be modified to support RFC 5819 syntax.
>
> And same goes for the server, because the client will want to query 
> *every* server that supports APPENDLIMIT just in case it has 
> per-mailbox limits. Unless I'm way off base here, a server with a 
> simple mailbox-wide APPEND limit would need to implement APPENDLIMIT 
> *plus* 5819 and 5258 to support the client asking about per-mailbox 
> limits -- unless we have the client assume that lack of support for 
> 5819/5258 implies that the server has no per-mailbox limits. Seems 
> pretty involved.
Actually, I was thinking of something simpler, which is syntactically 
compatible:

C: A01 LIST "" % RETURN (STATUS (APPENDLIMIT))
S: * LIST () "."  "INBOX"
S: * STATUS "INBOX" (APPENDLIMIT 1024000)

So basically server should recognize an extra "RETURN (STATUS (APPENDLIMIT))" at the end of a list command and emit an extra STATUS response for each matching mailbox. Support for RFC 5819 and RFC 5258 is optional.


My reason for recommending this (other than "compatibility with RFC 
5819/5258 is a good thing") is that if the limit is per mailbox, it 
might be stored with mailbox information and thus might be relatively 
expensive to retrieve. So a compliant server shouldn't try to retrieve 
it unless a client asks for this information. So basically we need a 
signalling mechanism for requesting this information.
>> But otherwise I am Ok with being able to return this information in 
>> LIST.


From nobody Mon Dec 15 07:07:17 2014
Return-Path: <stujenerin@aol.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 1FC711A6F5B for <imapext@ietfa.amsl.com>; Mon, 15 Dec 2014 07:07:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 OafYkovy9dfP for <imapext@ietfa.amsl.com>; Mon, 15 Dec 2014 07:07:09 -0800 (PST)
Received: from omr-m5.mx.aol.com (omr-m5.mx.aol.com [64.12.232.237]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F0A01A1B5A for <imapext@ietf.org>; Mon, 15 Dec 2014 07:07:09 -0800 (PST)
Received: from mtaout-aag01.mx.aol.com (mtaout-aag01.mx.aol.com [172.26.126.77]) by omr-m5.mx.aol.com (Outbound Mail Relay) with ESMTP id 96C3E3800015A; Mon, 15 Dec 2014 10:07:08 -0500 (EST)
Received: from [10.172.0.193] (unknown [10.172.0.193]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-aag01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 2DCEF38000099; Mon, 15 Dec 2014 10:07:07 -0500 (EST)
Message-ID: <548EF91A.5090202@aol.com>
Date: Mon, 15 Dec 2014 10:07:06 -0500
From: Stuart Brandt <stujenerin@aol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>,  Jayantheesh S B <j.sb@sta.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com>
In-Reply-To: <548ECB79.8000300@isode.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1418656028; bh=umGj9pqY5DpllQ/PHNya6x4DPuOq9I/oRUST0pRpTHE=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=M4PtrdkOjoUmGvOKEvkruK0vcNYNmbwgsFKeniSbGNEGYSeI3umRlXTamBt1xXJpu DzGmtSQQg+5L/Nm1usDeG6RaG14UEMJX/BJblKtf+p+rrnAPW09HcjLyLR96ONceo2 MdBIOz6pj5fJPCmzprK28ukuATbeKj0apsR6EytE=
x-aol-sid: 3039ac1a7e4d548ef91b45df
X-AOL-IP: 10.172.0.193
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/3dGyJGSk776rUkjZ26i4kOLLGYk
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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: Mon, 15 Dec 2014 15:07:15 -0000

Inline comments

On 12/15/14 6:52 AM, Alexey Melnikov wrote:
> Hi Stuart,
>
> On 12/12/2014 15:40, Stuart Brandt wrote:
>> Inline comments
>>
>> On 12/12/14 5:24 AM, Alexey Melnikov wrote:
>>> Hi Stuart,
>>>
>>> On 10/12/2014 19:58, Stuart Brandt wrote:
>>>> From a server perspective, the proposal solves my concern. From a
>>>> client perspective, I'm not sure whether the addition of [SP
>>>> nz-number] to the TOOBIG response would present problems for clients
>>>> that only implement CATENATE and not APPENDLIMIT. I too would like to
>>>> see others chime in on that part.
>>>>
>>>> From what I see, most IMAP sessions either precede an APPEND with a
>>>> SELECT/EXAMINE or LIST...likely to confirm the existence of the target
>>>> mailbox into which they're going to append.  The proposal already
>>>> covers SELECT/EXAMINE, so would it be reasonable to add the
>>>> APPENDLIMIT=x as an attribute to the LIST response data in order to
>>>> reflect any per-mailbox limit and avoid trying to convey the limit as
>>>> part of the TOOBIG response code to APPEND? Something along the line
>>>> of:
>>>>
>>>> C: t1 LIST "" "%"
>>>> S: * LIST (\Marked \HasNoChildren) "/" Inbox
>>>> S: * LIST (\HasNoChildren) "/" ToDo
>>>> S: * LIST (\HasChildren) "/" Projects
>>>> S: * LIST (\Sent \HasNoChildren) "/" SentMail
>>>> S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=257890) "/"
>>>> MyDrafts
>>>> S: * LIST (\Trash \HasNoChildren) "/" Trash
>>> All mailbox attributes are typically checked for equality, so this this
>>> a departure from this principle. (I know we started to violate this rule
>>> in CAPABILITY response)
>>> So personally, I prefer if we add a new STATUS item for APPEND limit.
>>> Then we can use STATUS-in-LIST bridge
>>> (https://tools.ietf.org/html/rfc5819) to return this information.
>>>
>>> As clients that want to obey APPENDLIMIT would need to be modified
>>> anyway, they might as well be modified to support RFC 5819 syntax.
>>
>> And same goes for the server, because the client will want to query
>> *every* server that supports APPENDLIMIT just in case it has
>> per-mailbox limits. Unless I'm way off base here, a server with a
>> simple mailbox-wide APPEND limit would need to implement APPENDLIMIT
>> *plus* 5819 and 5258 to support the client asking about per-mailbox
>> limits -- unless we have the client assume that lack of support for
>> 5819/5258 implies that the server has no per-mailbox limits. Seems
>> pretty involved.
> Actually, I was thinking of something simpler, which is syntactically
> compatible:
>
> C: A01 LIST "" % RETURN (STATUS (APPENDLIMIT))
> S: * LIST () "."  "INBOX"
> S: * STATUS "INBOX" (APPENDLIMIT 1024000)
>
> So basically server should recognize an extra "RETURN (STATUS
> (APPENDLIMIT))" at the end of a list command and emit an extra STATUS
> response for each matching mailbox. Support for RFC 5819 and RFC 5258 is
> optional.

That certainly simplifies things. Sounds good.

>
>
> My reason for recommending this (other than "compatibility with RFC
> 5819/5258 is a good thing") is that if the limit is per mailbox, it
> might be stored with mailbox information and thus might be relatively
> expensive to retrieve. So a compliant server shouldn't try to retrieve
> it unless a client asks for this information. So basically we need a
> signalling mechanism for requesting this information.

Makes complete sense.

>>> But otherwise I am Ok with being able to return this information in
>>> LIST.
>


From nobody Tue Dec 16 11:40:26 2014
Return-Path: <nicolson@google.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 A17721A874A for <imapext@ietfa.amsl.com>; Tue, 16 Dec 2014 11:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level: 
X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Ch56DVkm75GF for <imapext@ietfa.amsl.com>; Tue, 16 Dec 2014 11:40:23 -0800 (PST)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E37D11A1BD2 for <imapext@ietf.org>; Tue, 16 Dec 2014 11:40:22 -0800 (PST)
Received: by mail-ig0-f180.google.com with SMTP id h15so7675509igd.1 for <imapext@ietf.org>; Tue, 16 Dec 2014 11:40:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=l18HMj34/CD377G1sw4E9zDayTI7DvC68vu8gpHd7QI=; b=cnDydrjBrw9dPatsZVkS1etx7CGLBINMOINONZfLhDs2Xcn8MG0q67nuLPzFMMvYIs 0zbzx71nN+3PMaIN00s9ZPZZw4OmwRLzdAEzxypdx7XYWZ0gZvRS1q10oY0UsamTkJlH bS7bwW5RNGN3+ZDhTPi4cUeEUOkfLb0s1HyodRGICsX8A/jxsUTFdrOqNwIPhoFiJSvs uKY1QnPMS5hCC0iIyd4krcUdHY8ztLEiAzPXK0g2WDErMnrzymmwoP8agephUvrqmL9b +CwiAI58THH5/M03NX4Y/gWe83GeD45z/2VMon3ZkryWk/MeesOVNZMjcfego7BBbPXy rleQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=l18HMj34/CD377G1sw4E9zDayTI7DvC68vu8gpHd7QI=; b=LxJlwTlufA2PCraxWnhib20jAOvbiEZI/i/IYOi6g6oipPfh6p10lSGKc0nVmZqwaR 2abOp0rdpxhimLw//z7OPDZTCXKtLqF4sSj4dcxnGz4OrdHKzKVSCXL5VPSILU8mp27C WXTZl3xfpQYSvpLgnpKPcBG7dTl1pN7giq1lxCr7bo0lz+1G3Xn7uNLn81gxsQ5aMKgn uGcztMXHP841W3mZf2LM7bUisBoT/deQcxv9etfczoYY0q9zcm7h6SaZ7vffhDiSusdT cudXpm8LhwKcHWVVE0C4i1Ls16xtEqpTEjUxMjh3pnUEwwFoR+V6pM7cajmrordiPt1W H1Mw==
X-Gm-Message-State: ALoCoQk3Y0FtFCWXq+I1zK2l62tZ91+4Q/FugHJzJpjPPDN7jrdiFY+FxWJLVRcE5B0aEygnZCJS
X-Received: by 10.107.8.149 with SMTP id h21mr35656427ioi.74.1418758821967; Tue, 16 Dec 2014 11:40:21 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.168.134 with HTTP; Tue, 16 Dec 2014 11:39:50 -0800 (PST)
In-Reply-To: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi>
References: <C5DD1129-A4C0-4BD9-BAD7-664FBDF9E414@iki.fi>
From: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Date: Tue, 16 Dec 2014 11:39:50 -0800
Message-ID: <CACU8CfRNffYRZo7rpeM_KpBabg_rhV3=mDqk1cSKB166xDDWqg@mail.gmail.com>
To: Timo Sirainen <tss@iki.fi>
Content-Type: multipart/alternative; boundary=001a113f92109b2745050a5a8788
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/_oKdG8R4dKmtRouTRC9SoEubzBc
Cc: "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] Fetching short text snippet for mails
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, 16 Dec 2014 19:40:24 -0000

--001a113f92109b2745050a5a8788
Content-Type: text/plain; charset=UTF-8

Just weighing in from Gmail. We have snippets generated by our proprietary
algorithm, the ones we show in the web UI. We could implement proposal a),
returning our snippet as a new FETCH attribute, with the understanding that
snippet content is unspecified and determined by the server. We're not
likely to implement ANNOTATE or CONVERT.

On Mon, Dec 1, 2014 at 10:39 PM, Timo Sirainen <tss@iki.fi> wrote:
>
> Nowadays many mail clients want to show about 100 chars of the beginning
> of mail, so there should be a nice and efficient way for clients to request
> this. I'm now wondering what would be a nice IMAP way of implementing this.
> Does anyone have some suggestions? There's what I've come up with so far:
>
> a) FETCH n (SNIPPET)
>  - Would require writing a new RFC (or just use X-SNIPPET for internal use)
>
> b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))
>  - Would require implementing ANNOTATE, which is a lot of work. But it
> could also be implemented just minimally for this specific command.
>  - Standardizing vendor.dovecot.snippet would probably require new RFC
>
> c) CONVERT n ("text/vnd.dovecot.snippet" ("length" "100")) BINARY[BODY]
>  - Would require implementing CONVERT, which is a lot of work. But it
> could also be implemented just minimally for this specific command.
>  - Standardizing vnd.dovecot.snippet would probably require new RFC
>
> d) CONVERT n ("text/plain") BINARY[BODY]<0.100>
>  - CONVERT RFC says it's legal to convert entire multiparts, but doesn't
> say exactly what should be done with them. This is probably a valid use
> case though.
>  - Downside to this compared to others is that this always fetches the
> first 100 chars, while the others could also be smarter and skip over
> quoted text and such.
>
> I think I'm leaning towards b)
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext
>

--001a113f92109b2745050a5a8788
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Just weighing in from Gmail. We have snippets generated by=
 our proprietary algorithm, the ones we show in the web UI. We could implem=
ent proposal a), returning our snippet as a new FETCH attribute, with the u=
nderstanding that snippet content is unspecified and determined by the serv=
er. We&#39;re not likely to implement ANNOTATE or CONVERT.</div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Dec 1, 2014 at 10:3=
9 PM, Timo Sirainen <span dir=3D"ltr">&lt;<a href=3D"mailto:tss@iki.fi" tar=
get=3D"_blank">tss@iki.fi</a>&gt;</span> wrote:<blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">Nowadays many mail clients want to show about 100 chars of the beginning=
 of mail, so there should be a nice and efficient way for clients to reques=
t this. I&#39;m now wondering what would be a nice IMAP way of implementing=
 this. Does anyone have some suggestions? There&#39;s what I&#39;ve come up=
 with so far:<br>
<br>
a) FETCH n (SNIPPET)<br>
=C2=A0- Would require writing a new RFC (or just use X-SNIPPET for internal=
 use)<br>
<br>
b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))<br>
=C2=A0- Would require implementing ANNOTATE, which is a lot of work. But it=
 could also be implemented just minimally for this specific command.<br>
=C2=A0- Standardizing vendor.dovecot.snippet would probably require new RFC=
<br>
<br>
c) CONVERT n (&quot;text/vnd.dovecot.snippet&quot; (&quot;length&quot; &quo=
t;100&quot;)) BINARY[BODY]<br>
=C2=A0- Would require implementing CONVERT, which is a lot of work. But it =
could also be implemented just minimally for this specific command.<br>
=C2=A0- Standardizing vnd.dovecot.snippet would probably require new RFC<br=
>
<br>
d) CONVERT n (&quot;text/plain&quot;) BINARY[BODY]&lt;0.100&gt;<br>
=C2=A0- CONVERT RFC says it&#39;s legal to convert entire multiparts, but d=
oesn&#39;t say exactly what should be done with them. This is probably a va=
lid use case though.<br>
=C2=A0- Downside to this compared to others is that this always fetches the=
 first 100 chars, while the others could also be smarter and skip over quot=
ed text and such.<br>
<br>
I think I&#39;m leaning towards b)<br>
<br>
_______________________________________________<br>
imapext mailing list<br>
<a href=3D"mailto:imapext@ietf.org">imapext@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/imapext" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/imapext</a><br>
</blockquote></div></div>

--001a113f92109b2745050a5a8788--


From nobody Tue Dec 16 15:21:54 2014
Return-Path: <prvs=942766c794=j.sb@sta.samsung.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 512291A0174 for <imapext@ietfa.amsl.com>; Tue, 16 Dec 2014 15:21:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.896
X-Spam-Level: 
X-Spam-Status: No, score=0.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, 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 kn3_S359LH_l for <imapext@ietfa.amsl.com>; Tue, 16 Dec 2014 15:21:49 -0800 (PST)
Received: from smg1.telecom.sna.samsung.com (unknown [63.166.115.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C15AF1A0154 for <imapext@ietf.org>; Tue, 16 Dec 2014 15:21:48 -0800 (PST)
X-AuditID: 41a9fa1f-f79486d0000004ef-bc-5490be7edd41
Received: from exHub4.telecom.sna.samsung.com (Unknown_Domain [105.52.12.225]) by smg1.telecom.sna.samsung.com (SMGOUT STA) with SMTP id A5.07.01263.E7EB0945; Tue, 16 Dec 2014 17:21:34 -0600 (CST)
Received: from EXMB5.telecom.sna.samsung.com ([fe80::5f4:56d9:ea68:f480]) by exHub4.telecom.sna.samsung.com ([fe80::443f:7bc1:a09a:eb23%21]) with mapi id 14.03.0146.000; Tue, 16 Dec 2014 17:21:42 -0600
From: Jayantheesh S B <j.sb@sta.samsung.com>
To: 'Stuart Brandt' <stujenerin@aol.com>, 'Alexey Melnikov' <alexey.melnikov@isode.com>, "'imapext@ietf.org'" <imapext@ietf.org>
Thread-Topic: [imapext] [IMAP] APPEND Command Usage
Thread-Index: Ac/zikIaeRUU045cSKC+QFTd6ghr0ZxK6Vlg48oYyFOAAJQ50oAAgMAAgAB8E7CAKoibP4ABNvGtgALo/oCAAFgrgIAEd16AgAA2ZQD//kkMkA==
Date: Tue, 16 Dec 2014 23:21:41 +0000
Message-ID: <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com>
In-Reply-To: <548EF91A.5090202@aol.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [105.52.12.197]
Content-Type: multipart/mixed; boundary="_002_02454F842DD7B449B96715A2AD90C0363E99AFDCexMB5telecomsna_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsWSacLzULdu34QQg2mz+SxmrC6yeDyLy6Lr ZbgDs8f93SvZPZYs+cnkcarZMIA5itsmKbGkLDgzPU/fLoE749DnO8wFs9cyVkz5e565gbFr MWMXIyeHhICJxOyXe6BsMYkL99azdTFycQgJHGOUWHZvIjOEc5ZR4mXzJvYuRnYONgEdiSfB IGERgSZGiRd7u5hAmoUFjCQ2P98DVM8BlDCW+H/GEiQsIlAncWTTAxYQm0VAVeLK7Q9gu3gF QiRetN9ihBj/gF1i3ZWXYHM4BdQljmx5wQZiMwId9P3UGrA4s4C4xK0n85kgDhWReHjxNBuE LSrx8vE/VghbUWLur5vMEPWZElvfroZaJihxcuYTlgmMIrOQjJqFpGwWkrIFjMyrGGWKc9MN 9UpSc1KT83P1ivMS9YoTc4tL89L1gPxNjMC4cFz5S34H47rt9ocYmTg4DzFKcHBJiRSn5qWk FiWWlmTEg0I/vhgY/FINjJwZdiF/LZ8tlC/wOmX28uztBxoc8YYRMmlz2ued0vjlLPN5Sslu vpCt+aur1DxFP7fPUna++s4hP1H5g/Ja25Kdx1xCVDylGi5/P+1ScSHivLnTH6mOn/3Hmq7t 3f1Z/sebaIYsqahdRe8DtC6eale/m9SeleCYeOpg7Peij+ve+my7MpXDUYmlOCPRUIu5qDgR AJsHyDtWAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/nzs3BSBlC2YD1VDDFUioxYptUJ0
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 16 Dec 2014 23:21:52 -0000

--_002_02454F842DD7B449B96715A2AD90C0363E99AFDCexMB5telecomsna_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

Please find the updated version of the draft attached.

Changes in this version:

1.  APPEND command response handling changes (Reused TOOBIG response-text f=
rom rfc4469 )
2.  Retrieval of per mailbox limit in  authenticated state by using LIST an=
d STATUS command (Reference rfc5819)

Kindly share your comments.=20

Regards,
Jay

-----Original Message-----
From: Stuart Brandt [mailto:stujenerin@aol.com]=20
Sent: Monday, December 15, 2014 10:07 AM
To: Alexey Melnikov; Jayantheesh S B
Cc: 'imapext@ietf.org'
Subject: Re: [imapext] [IMAP] APPEND Command Usage

Inline comments

On 12/15/14 6:52 AM, Alexey Melnikov wrote:
> Hi Stuart,
>
> On 12/12/2014 15:40, Stuart Brandt wrote:
>> Inline comments
>>
>> On 12/12/14 5:24 AM, Alexey Melnikov wrote:
>>> Hi Stuart,
>>>
>>> On 10/12/2014 19:58, Stuart Brandt wrote:
>>>> From a server perspective, the proposal solves my concern. From a=20
>>>> client perspective, I'm not sure whether the addition of [SP=20
>>>> nz-number] to the TOOBIG response would present problems for=20
>>>> clients that only implement CATENATE and not APPENDLIMIT. I too=20
>>>> would like to see others chime in on that part.
>>>>
>>>> From what I see, most IMAP sessions either precede an APPEND with a=20
>>>> SELECT/EXAMINE or LIST...likely to confirm the existence of the=20
>>>> target mailbox into which they're going to append.  The proposal=20
>>>> already covers SELECT/EXAMINE, so would it be reasonable to add the=20
>>>> APPENDLIMIT=3Dx as an attribute to the LIST response data in order to=
=20
>>>> reflect any per-mailbox limit and avoid trying to convey the limit=20
>>>> as part of the TOOBIG response code to APPEND? Something along the=20
>>>> line
>>>> of:
>>>>
>>>> C: t1 LIST "" "%"
>>>> S: * LIST (\Marked \HasNoChildren) "/" Inbox
>>>> S: * LIST (\HasNoChildren) "/" ToDo
>>>> S: * LIST (\HasChildren) "/" Projects
>>>> S: * LIST (\Sent \HasNoChildren) "/" SentMail
>>>> S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=3D257890) "/"
>>>> MyDrafts
>>>> S: * LIST (\Trash \HasNoChildren) "/" Trash
>>> All mailbox attributes are typically checked for equality, so this=20
>>> this a departure from this principle. (I know we started to violate=20
>>> this rule in CAPABILITY response) So personally, I prefer if we add=20
>>> a new STATUS item for APPEND limit.
>>> Then we can use STATUS-in-LIST bridge
>>> (https://tools.ietf.org/html/rfc5819) to return this information.
>>>
>>> As clients that want to obey APPENDLIMIT would need to be modified=20
>>> anyway, they might as well be modified to support RFC 5819 syntax.
>>
>> And same goes for the server, because the client will want to query
>> *every* server that supports APPENDLIMIT just in case it has=20
>> per-mailbox limits. Unless I'm way off base here, a server with a=20
>> simple mailbox-wide APPEND limit would need to implement APPENDLIMIT
>> *plus* 5819 and 5258 to support the client asking about per-mailbox=20
>> limits -- unless we have the client assume that lack of support for
>> 5819/5258 implies that the server has no per-mailbox limits. Seems=20
>> pretty involved.
> Actually, I was thinking of something simpler, which is syntactically
> compatible:
>
> C: A01 LIST "" % RETURN (STATUS (APPENDLIMIT))
> S: * LIST () "."  "INBOX"
> S: * STATUS "INBOX" (APPENDLIMIT 1024000)
>
> So basically server should recognize an extra "RETURN (STATUS=20
> (APPENDLIMIT))" at the end of a list command and emit an extra STATUS=20
> response for each matching mailbox. Support for RFC 5819 and RFC 5258=20
> is optional.

That certainly simplifies things. Sounds good.

>
>
> My reason for recommending this (other than "compatibility with RFC
> 5819/5258 is a good thing") is that if the limit is per mailbox, it=20
> might be stored with mailbox information and thus might be relatively=20
> expensive to retrieve. So a compliant server shouldn't try to retrieve=20
> it unless a client asks for this information. So basically we need a=20
> signalling mechanism for requesting this information.

Makes complete sense.

>>> But otherwise I am Ok with being able to return this information in=20
>>> LIST.
>

--_002_02454F842DD7B449B96715A2AD90C0363E99AFDCexMB5telecomsna_
Content-Type: text/plain;
	name="draft-jayantheesh-imap-appendlimit-extension-01.txt"
Content-Description: draft-jayantheesh-imap-appendlimit-extension-01.txt
Content-Disposition: attachment;
	filename="draft-jayantheesh-imap-appendlimit-extension-01.txt"; size=12579;
	creation-date="Tue, 16 Dec 2014 00:14:55 GMT";
	modification-date="Tue, 16 Dec 2014 23:16:05 GMT"
Content-Transfer-Encoding: base64

SU5URVJORVQtRFJBRlQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
SmF5YW50aGVlc2ggUyBCIApJbnRlbmRlZCBzdGF0dXM6IFN0YW5kYXJkcyBUcmFjayAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIFNhbXN1bmcKRXhwaXJlczogSnVuZSAyMDE1ICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIE5hcmVuZHJhIFNpbmdoIEJpc2h0CiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
U2Ftc3VuZwogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgRGVjZW1iZXIgMTcsIDIwMTQKCiAgICAgICAgICAgICAgICAgICAgICBUaGUgSU1BUCBB
UFBFTkRMSU1JVCBFeHRlbnNpb24KICAgICAgICAgICAgICAgIGRyYWZ0LWpheWFudGhlZXNoLWlt
YXAtYXBwZW5kbGltaXQtZXh0ZW5zaW9uLTAxCgpBYnN0cmFjdAoKVGhpcyBtZW1vIGRlZmluZXMg
YW4gZXh0ZW5zaW9uIHRvIHRoZSBJTUFQIHNlcnZpY2Ugd2hlcmVieSBhIHNlcnZlciBjYW4KYWR2
ZXJ0aXNlIGl0cyBjYXBhYmlsaXR5LCB0byBzdXBwb3J0IG1heGltdW0gbWFpbCB1cGxvYWQgc2l6
ZSB1c2luZwpDQVBBQklMSVRZLCBTRUxFQ1QvRVhBTUlORSBhbmQgTElTVCBjb21tYW5kLgoKU3Rh
dHVzIG9mIHRoaXMgTWVtbwoKVGhpcyBJbnRlcm5ldC1EcmFmdCBpcyBzdWJtaXR0ZWQgaW4gZnVs
bCBjb25mb3JtYW5jZSB3aXRoIHRoZQpwcm92aXNpb25zIG9mIEJDUCA3OCBhbmQgQkNQIDc5LiBU
aGlzIGRvY3VtZW50IG1heSBub3QgYmUgbW9kaWZpZWQsIGFuZApkZXJpdmF0aXZlIHdvcmtzIG9m
IGl0IG1heSBub3QgYmUgY3JlYXRlZCwgZXhjZXB0IHRvIHB1Ymxpc2ggaXQgYXMgYW4KUkZDIGFu
ZCB0byB0cmFuc2xhdGUgaXQgaW50byBsYW5ndWFnZXMgb3RoZXIgdGhhbiBFbmdsaXNoLgoKSW50
ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5l
ZXJpbmcgVGFzawpGb3JjZSAoSUVURiksIGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vw
cy4gIE5vdGUgdGhhdCBvdGhlciBncm91cHMKbWF5IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRv
Y3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuCgpJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRv
Y3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHMKYW5kIG1heSBiZSB1cGRh
dGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnkKdGlt
ZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVu
Y2UgbWF0ZXJpYWwKb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4gYXMgIndvcmsgaW4gcHJvZ3Jl
c3MuIgoKVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC1EcmFmdHMgY2FuIGJlIGFjY2Vzc2Vk
IGF0Cmh0dHA6Ly93d3cuaWV0Zi5vcmcvaWV0Zi8xaWQtYWJzdHJhY3RzLnR4dAoKVGhlIGxpc3Qg
b2YgSW50ZXJuZXQtRHJhZnQgU2hhZG93IERpcmVjdG9yaWVzIGNhbiBiZSBhY2Nlc3NlZCBhdApo
dHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sCgpUaGlzIEludGVybmV0LURyYWZ0IHdpbGwg
ZXhwaXJlIG9uIEp1bmUsIDIwMTUuCgpDb3B5cmlnaHQgTm90aWNlCgpDb3B5cmlnaHQgKGMpIDIw
MTQgSUVURiBUcnVzdCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmllZCBhcyB0aGUKZG9jdW1lbnQg
YXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2ZWQuCgpUaGlzIGRvY3VtZW50IGlzIHN1YmplY3Qg
dG8gQkNQIDc4IGFuZCB0aGUgSUVURiBUcnVzdCdzIExlZ2FsClByb3Zpc2lvbnMgUmVsYXRpbmcg
dG8gSUVURiBEb2N1bWVudHMKKGh0dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vuc2UtaW5mbykg
aW4gZWZmZWN0IG9uIHRoZSBkYXRlIG9mCnB1YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuICBQ
bGVhc2UgcmV2aWV3IHRoZXNlIGRvY3VtZW50cyBjYXJlZnVsbHksCmFzIHRoZXkgZGVzY3JpYmUg
eW91ciByaWdodHMgYW5kIHJlc3RyaWN0aW9ucyB3aXRoIHJlc3BlY3QgdG8gdGhpcwpkb2N1bWVu
dC4KCkpheWFudGhlZXNoICYgTmFyZW5kcmEgICAgICAgRXhwaXJlcyBKdW5lLCAyMDE1ICAgICAg
ICAgICAgICAgW1BhZ2UgMV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIElNQVAgQVBQ
RU5ETElNSVQgICAgICAgICAgICBEZWNlbWJlciAyMDE0CgpUYWJsZSBvZiBDb250ZW50cwoKICAg
MS4gIEludHJvZHVjdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICAyCiAgICAgMS4xLiBDb252ZW50aW9ucyBhbmQgVGVybWlub2xvZ3kgLiAuIC4g
LiAuIC4gLiAuIC4gLiAgLiAuIC4gLiAuICAgMgogICAyLiBBUFBFTkRMSU1JVCBFeHRlbnNpb24g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDIKICAgMy4gTWFpbGJv
eCBzcGVjaWZpYyBBUFBFTkRMSU1JVCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAzCiAgICAgMy4xLiBTRUxFQ1QgcmVzcG9uc2UgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAgNAogICAgIDMuMi4gTElTVCByZXNwb25zZSAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDQKICAgNC4gQVBQRU5EIHJlc3BvbnNl
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA1CiAgIDUu
IEZvcm1hbCBzeW50YXggLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgNAogICA2LiBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDUKICAgNy4gSUFOQSBDb25zaWRlcmF0aW9ucyAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA1CiAgIDguIFJlZmVyZW5j
ZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
NgogICAgOC4xIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIDYKICAgIDguMiBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA2CiAgIDkuIEFja25vd2xlZGdlbWVudCAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNgogICAxMC4g
QXV0aG9yJ3MgQWRkcmVzcyAuIC4uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIDcKICAgCgoxLiBJbnRyb2R1Y3Rpb24KClNldmVyYWwgSU1BUCBzZXJ2ZXIgaGF2ZSBs
aW1pdGF0aW9uIGZvciBtYWlsIHVwbG9hZCBzaXplIHdoaWNoIGlzIG5vdApwdWJsaXNoZWQgdG8g
dGhlIGVtYWlsIGNsaWVudC4gIFdoZW4gZW1haWwgY2xpZW50IEFQUEVORCBhIG1haWwgd2l0aApo
dWdlIGF0dGFjaG1lbnRzLCBpdCBmYWlscyBkdWUgdG8gc2l6ZSByZXN0cmljdGlvbiBzZXQgYnkg
dGhlIElNQVAKc2VydmVyLiAgVGhpcyByZXN1bHRzIGluIHVubmVjZXNzYXJ5IHJlc291cmNlIHVz
YWdlLiAgRXNwZWNpYWxseSBpbiB0aGUgCm1vYmlsZSBkZXZpY2UgZW52aXJvbm1lbnQsIGFwcGVu
ZGluZyBtYWlsIHdpdGggaHVnZSBhdHRhY2htZW50IGNvbnN1bWVzCmRldmljZSByZXNvdXJjZXMg
bGlrZSBkZXZpY2UgYmF0dGVyeSBwb3dlciBhbmQgbW9iaWxlIGRhdGEuCgpUaGUgSU1BUCBBUFBF
TkRMSU1JVCBleHRlbnNpb24gcHJvdmlkZXMgYW4gYWJpbGl0eSB0byBhZHZlcnRpc2UgbWF4aW11
bQp1cGxvYWQgc2l6ZSBhbGxvd2VkIGJ5IHRoZSBJTUFQIHNlcnZlciwgc28gdGhhdCBlbWFpbCBj
bGllbnQga25vd3MgdGhlCnNpemUgbGltaXRhdGlvbiBiZWZvcmVoYW5kLgoKMS4xLiBDb252ZW50
aW9ucyBhbmQgVGVybWlub2xvZ3kKClRoZSBrZXkgd29yZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAi
UkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgCk5PVCIsIlNIT1VMRCIsICJTSE9VTEQgTk9UIiwg
IlJFQ09NTUVOREVEIiwgICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbgp0aGlzIGRvY3VtZW50IGFy
ZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQgaW4gUkZDIDIxMTkuCgpFeGFtcGxlIGxp
bmVzIHByZWZhY2VkIGJ5ICJDOiIgYXJlIHNlbnQgYnkgdGhlIGNsaWVudCBhbmQgb25lcyBwcmVm
YWNlZApieSAiUzoiIGJ5IHRoZSBzZXJ2ZXIuICBUaGUgZml2ZSBjaGFyYWN0ZXJzIFsuLi5dIG1l
YW5zIHRoYXQgc29tZXRoaW5nCmhhcyBiZWVuIGVsaWRlZC4KCjIuIEFQUEVORExJTUlUIEV4dGVu
c2lvbgoKQW4gSU1BUCBzZXJ2ZXIgdGhhdCBzdXBwb3J0cyBBUFBFTkRMSU1JVCBhZHZlcnRpc2Vz
IHRoaXMgYnkgaW5jbHVkaW5nCnRoZSB3b3JkIEFQUEVORExJTUlUIGluIGl0cyBjYXBhYmlsaXR5
IGxpc3QuICBJTUFQIHNlcnZlciBzaGFsbCBwdWJsaXNoCnRoZSBzdXBwb3J0ZWQgbWFpbCB1cGxv
YWQgc2l6ZSBhcyBwYXJ0IG9mIENBUEFCSUxJVFkgcmVzcG9uc2UuICBUaGUKCkpheWFudGhlZXNo
ICYgTmFyZW5kcmEgICAgICAgRXhwaXJlcyBKdW5lLCAyMDE1ICAgICAgICAgICAgICBbUGFnZSAy
XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgSU1BUCBBUFBFTkRMSU1JVCAgICAgICAg
ICAgRGVjZW1iZXIgMjAxNAoKYWR2ZXJ0aXNlZCB1cGxvYWQgbGltaXQgaXMgY29tbW9uIGFjcm9z
cyB0aGUgbWFpbGJveGVzLCBidXQgY2xpZW50CmNhbiBzdGlsbCBpc3N1ZSBTRUxFQ1QvRVhBTUlO
RSBvciBMSVNUIGNvbW1hbmQgdG8gZ2V0IHRoZSBtYWlsYm94CnNwZWNpZmljIHVwbG9hZCBsaW1p
dCBzZXQgYnkgdGhlIElNQVAgc2VydmVyLiAgSW4gdGhpcyBjYXNlLApBUFBFTkRMSU1JVCB2YWx1
ZSBvYnRhaW5lZCBhcyBwYXJ0IG9mIFNFTEVDVC9FWEFNSU5FIG9yIExJU1QgY29tbWFuZAp0YWtl
cyBwcmVjZWRlbmNlIG92ZXIgdGhlIHZhbHVlIHJldHVybmVkIGFzIHBhcnQgb2YgQ0FQQUJJTElU
WQpyZXNwb25zZS4KClRoZSBmb2xsb3dpbmcgZXhhbXBsZSwgZGVtb25zdHJhdGVzIHRoZSBBUFBF
TkRMSU1JVCBjYXBhYmlsaXR5IHdpdGgKbWFpbGJveCBsaW1pdC4KCkM6IHQxIENBUEFCSUxJVFkK
UzogKiBDQVBBQklMSVRZIElNQVA0cmV2MSBJRCBBUFBFTkRMSU1JVD0yNTc4OTAKUzogdDEgT0sg
Zm9vCgpJZiBBUFBFTkRMSU1JVCB2YWx1ZSBpcyBvbWl0dGVkIGluIENBUEFCSUxJVFkgcmVzcG9u
c2UsIHRoZW4gY2xpZW50ClNIT1VMRCBpc3N1ZSBTRUxFQ1QvRVhBTUlORSBvciBMSVNUIGNvbW1h
bmQgdG8gZ2V0IHRoZSBtYWlsYm94IHNwZWNpZmljCmxpbWl0IHNldCBieSB0aGUgc2VydmVyLiAg
TmV3IHJlc3BvbnNlIGNvZGUgQVBQRU5ETElNSVQgaXMgYWRkZWQgdG8gZ2V0CnRoZSBtYWlsYm94
IHNwZWNpZmljIGxpbWl0LiAgUmVmZXIgc2VjdGlvbiBbNV0gZm9yIHJlc3BvbnNlIGNvZGUgc3lu
dGF4LgoKVGhlIGZvbGxvd2luZyBleGFtcGxlIGRlbW9uc3RyYXRlcywgaXRzIHVzYWdlLgoKQzog
dDEgQ0FQQUJJTElUWQpTOiAqIENBUEFCSUxJVFkgSU1BUDRyZXYxIElEIEFQUEVORExJTUlUClM6
IHQxIE9LIGZvbwoKQzogdDIgU0VMRUNUIElOQk9YClM6ICogMTcyIEVYSVNUUwpTOiAqIE9LIFtB
UFBFTkRMSU1JVCAyNTc4OTBdIE1heGltdW0gdXBsb2FkIGxpbWl0ClM6ICogT0sgW1VJRFZBTElE
SVRZIDM4NTc1MjkwNDVdIFVJRHMgdmFsaWQKUzogKiBGTEFHUyAoXEFuc3dlcmVkIFxGbGFnZ2Vk
IFxEZWxldGVkIFxTZWVuIFxEcmFmdCkKUzogKiBPSyBbUEVSTUFORU5URkxBR1MgKFxEZWxldGVk
IFxTZWVuIFwqKV0gTGltaXRlZApTOiB0MiBPSyBbUkVBRC1XUklURV0gU0VMRUNUIGNvbXBsZXRl
ZAoKQnkgbG9va2luZyBhdCB0aGUgdXBsb2FkIHNpemUgcmVzdHJpY3Rpb24gc2V0IGJ5IHRoZSBJ
TUFQIHNlcnZlciwgY2xpZW50ClNIQUxMIG5vdCB0cnkgdG8gdXBsb2FkIG1haWwgbW9yZSB0aGFu
IGFkdmVydGlzZWQgbGltaXQgaW4gdGhlIEFQUEVORApjb21tYW5kLiAKCjMuIE1haWxib3ggc3Bl
Y2lmaWMgQVBQRU5ETElNSVQKCklNQVAgc2VydmVyIGNhbiBzdGlsbCBoYXZlIG1haWxib3ggc3Bl
Y2lmaWMgQVBQRU5ETElNSVQgcmVzdHJpY3Rpb24sCndoaWNoIG1heSBub3QgYmUgYWR2ZXJ0aXNl
ZCBhcyBwYXJ0IG9mIENBUEFCSUxJVFkgcmVzcG9uc2UuICBJbiB0aGlzCmNhc2UsIGNsaWVudCBj
YW4gaXNzdWUgU0VMRUNUL0VYQU1JTkUgY29tbWFuZCB0byBnZXQgdGhlIHBlciBtYWlsYm94CnNw
ZWNpZmljIGxpbWl0IHNldCBieSB0aGUgc2VydmVyLiAgU2ltaWxhcmx5LCBpZiBjbGllbnQgd2lz
aCB0byBrbm93CnRoZSBtYWlsYm94IHNwZWNpZmljIGxpbWl0IGluIGF1dGhlbnRpY2F0ZWQgc3Rh
dGUsIGNhbiBiZSBkb25lIGJ5Cmlzc3VpbmcgdGhlIExJU1QgY29tbWFuZCBpbiBjb21iaW5hdGlv
biB3aXRoIFNUQVRVUyBjb21tYW5kLgoKCgpKYXlhbnRoZWVzaCAmIE5hcmVuZHJhICAgICAgIEV4
cGlyZXMgSnVuZSwgMjAxNSAgICAgICAgICAgICAgW1BhZ2UgM10KDApJbnRlcm5ldC1EcmFmdCAg
ICAgICAgICAgICAgIElNQVAgQVBQRU5ETElNSVQgICAgICAgICAgIERlY2VtYmVyIDIwMTQKCjMu
MSBTRUxFQ1QgcmVzcG9uc2UKCkNsaWVudCBjYW4gZ2V0IHRoZSBwZXIgbWFpbGJveCBhcHBlbmQg
bGltaXQgYnkgaXNzdWluZyB0aGUgU0VMRUNULwpFWEFNSU5FIGNvbW1hbmQuICBBUFBFTkRMSU1J
VCBzaXplIHRvIHRoaXMgbWFpbGJveCBpcyBvYnRhaW5lZCBhcyBwYXJ0Cm9mIHVudGFnZ2VkIE9L
IHJlc3BvbnNlLgoKSW4gdGhpcyBjYXNlLCB0aGlzIEFQUEVORExJTUlUIHZhbHVlIHdpbGwgc3Vw
ZXJzZWRlIHRoZSB2YWx1ZSByZWNlaXZlZAphcyBwYXJ0IG9mIENBUEFCSUxJVFkgcmVzcG9uc2Uu
CgpDOiB0MiBTRUxFQ1QgSU5CT1gKUzogKiAxNzIgRVhJU1RTClM6ICogT0sgW0FQUEVORExJTUlU
IDI1Nzg5MF0gTWF4aW11bSB1cGxvYWQgbGltaXQKUzogWy4uLl0KUzogdDIgT0sgW1JFQUQtV1JJ
VEVdIFNFTEVDVCBjb21wbGV0ZWQKCgpJbiB0aGUgYWJvdmUgZXhhbXBsZSwgQVBQRU5ETElNSVQg
cmVwcmVzZW50cyB0aGUgbWF4aW11bSB1cGxvYWQgc2l6ZSBmb3IKdGhpcyBtYWlsYm94LgoKT0sg
W0FQUEVORExJTUlUIDxuPl0gTWF4aW11bSB1cGxvYWQgbGltaXQgZm9yIHRoaXMgbWFpbGJveCwg
aW4gYnl0ZXMuCiAgICAgICAgICAgICAgICAgICAgIFJlZmVyIHRvIHNlY3Rpb24gWzVdIGZvciBt
b3JlIGluZm9ybWF0aW9uLiAgSWYgdGhpcwogICAgICAgICAgICAgICAgICAgICBpcyBtaXNzaW5n
LCB0aGUgY2xpZW50IGNhbiBhbHdheXMgaG9ub3VyIHRoZQogICAgICAgICAgICAgICAgICAgICB2
YWx1ZSByZWNlaXZlZCBhcyBwYXJ0IG9mIENBUEFCSUxJVFkgcmVzcG9uc2UuCgoKMy4yIExJU1Qg
cmVzcG9uc2UKCklNQVAgY2xpZW50IGNhbiBnZXQgdGhlIG1haWxib3ggc3BlY2lmaWMgQVBQRU5E
TElNSVQgaW4gYXV0aGVudGljYXRlZApzdGF0ZSwgd2hlcmUgaXQgZG8gbm90IG5lZWQgdG8gaXNz
dWUgU0VMRUNUL0VYQU1JTkUgY29tbWFuZC4gIExJU1QKY29tbWFuZCBpbiBjb21iaW5hdGlvbiB3
aXRoIFNUQVRVUyBjb21tYW5kIGNhbiBiZSBpc3N1ZWQgdG8gZ2V0IHRoZSBwZXIKbWFpbGJveCBz
cGVjaWZpYyBBUFBFTkRMSU1JVCBzZXQgYnkgdGhlIHNlcnZlci4gIFJlZmVyIHJmYzU4MTkgZm9y
IHRoZQp1c2FnZSBvZiBMSVNUIGNvbW1hbmQgaW4gY29tYmluYXRpb24gd2l0aCBTVEFUVVMgY29t
bWFuZCB1c2FnZS4KClRoZSBmb2xsb3dpbmcgZXhhbXBsZSBkZW1vbnN0cmF0ZXMsIGl0cyB1c2Fn
ZS4KCkM6IHQxIExJU1QgIiIgJSBSRVRVUk4gKFNUQVRVUyAoQVBQRU5ETElNSVQpKQpTOiAqIExJ
U1QgKCkgIi4iICAiSU5CT1giClM6ICogU1RBVFVTICJJTkJPWCIgKEFQUEVORExJTUlUIDI1Nzg5
MCkKUzogdDEgT0sgTGlzdCBjb21wbGV0ZWQuCgpOZXcgYXR0cmlidXRlIEFQUE5ETElNSVQgaXMg
YWRkZWQgdG8gZ2V0IHRoZSBsaW1pdCBzZXQgYnkgdGhlIHNlcnZlciBmb3IKdGhpcyBtYWlsYm94
IGFzIHBhcnQgb2YgU1RBVFVTIGNvbW1hbmQuICBUaGUgU1RBVFVTIHJlc3BvbnNlIG9jY3VycyBh
cyBhCnJlc3VsdCBvZiBhbiBTVEFUVVMgY29tbWFuZC4gIEl0IHJldHVybnMgdGhlIG1haWxib3gg
bmFtZSB0aGF0IG1hdGNoZXMKdGhlIFNUQVRVUyBzcGVjaWZpY2F0aW9uIGFuZCB0aGUgcmVxdWVz
dGVkIG1haWxib3ggc3RhdHVzIGluZm9ybWF0aW9uLgpJTUFQIHNlcnZlciBzaG91bGQgcmVjb2du
aXplIGFuIGV4dHJhICJSRVRVUk4gKFNUQVRVUyhBUFBFTkRMSU1JVCkpIiBhdAp0aGUgZW5kIG9m
IGEgbGlzdCBjb21tYW5kIGFuZCBlbWl0IGFuIGV4dHJhIFNUQVRVUyByZXNwb25zZSBmb3IgZWFj
aAptYXRjaGluZyBtYWlsYm94LiAgUmVmZXIgdG8gc2VjdGlvbiBbNV0gZm9yIHRoZSBzeW50YXgu
CgpKYXlhbnRoZWVzaCAmIE5hcmVuZHJhICAgICAgIEV4cGlyZXMgSnVuZSwgMjAxNSAgICAgICAg
ICAgICAgW1BhZ2UgNF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIElNQVAgQVBQRU5E
TElNSVQgICAgICAgICAgIERlY2VtYmVyIDIwMTQKCjQuIEFQUEVORCByZXNwb25zZQoKSWYgY2xp
ZW50IHVwbG9hZHMgYSBtYWlsIHdoaWNoIGV4Y2VlZHMgdGhlIG1heGltdW0gdXBsb2FkIHNpemUg
c2V0CnRvIHRoYXQgbWFpbGJveCwgdGhlbiBzZXJ2ZXIgc2hhbGwgcmVqZWN0IHRoZSBBUFBFTkQg
Y29tbWFuZCB3aXRoIGEKdGFnZ2VkIFRPT0JJRyByZXNwb25zZSBjb2RlLiAgUmVmZXIgcmZjNDQ2
OSBTZWN0aW9uICg0KSBmb3IgdmFyaW91cwpBUFBFTkQgcmVzcG9uc2UgY29kZXMgYW5kIGl0cyBo
YW5kbGluZy4KCkNsaWVudCBjYW4gYXZvaWQgdXNlIG9mIExJVEVSQUwrLCB3aGVuIG1heGltdW0g
dXBsb2FkIHNpemUKc3VwcG9ydGVkIGJ5IHRoZSBJTUFQIHNlcnZlciBpcyB1bmtub3duLiAKCjUu
IEZvcm1hbCBzeW50YXgKClRoZSBmb2xsb3dpbmcgc3ludGF4IHNwZWNpZmljYXRpb24gdXNlcyB0
aGUgQXVnbWVudGVkIEJhY2t1cy1OYXVyCkZvcm0gKEFCTkYpIG5vdGF0aW9uIGFzIHNwZWNpZmll
ZCBpbiBbUkZDNTIzNF0gaW5jbHVkaW5nIHRoZSBjb3JlCnJ1bGVzIGluIEFwcGVuZGl4IEIuMS4g
IFtSRkMzNTAxXSBkZWZpbmVzIHRoZSBub24tdGVybWluYWxzCiJjYXBhYmlsaXR5IiwgInJlc3At
dGV4dC1jb2RlIiBhbmQgInN0YXR1cy1hdHQiLgpFeGNlcHQgYXMgbm90ZWQgb3RoZXJ3aXNlLCBh
bGwgYWxwaGFiZXRpYyBjaGFyYWN0ZXJzIGFyZSBjYXNlLQppbnNlbnNpdGl2ZS4gIFRoZSB1c2Ug
b2YgdXBwZXIgb3IgbG93ZXIgY2FzZSBjaGFyYWN0ZXJzIHRvIGRlZmluZQp0b2tlbiBzdHJpbmdz
IGlzIGZvciBlZGl0b3JpYWwgY2xhcml0eSBvbmx5LiAgSW1wbGVtZW50YXRpb25zIE1VU1QKYWNj
ZXB0IHRoZXNlIHN0cmluZ3MgaW4gYSBjYXNlLWluc2Vuc2l0aXZlIGZhc2hpb24uCiAgICAKYXBw
ZW5kbGltaXQtY2FwID0gIkFQUEVORExJTUlUIiBbIj0iIG56LW51bWJlcl0KY2FwYWJpbGl0eSAv
PSBhcHBlbmRsaW1pdC1jYXAKCmFwcGVuZGxpbWl0LXJlc3Bjb2RlID0gIkFQUEVORExJTUlUIiBT
UCBuei1udW1iZXIKcmVzcC10ZXh0LWNvZGUgLz0gYXBwZW5kbGltaXQtcmVzcGNvZGUKCmFwcGVu
ZGxpbWl0LXN0YXR1cy1hdHQgPSAiQVBQRU5ETElNSVQiCnN0YXR1cy1hdHQgLz1hcHBlbmRsaW1p
dC1zdGF0dXMtYXR0CgpBIG5vbi16ZXJvIG51bWJlciBpbmRpY2F0aW5nIHRoZSBmaXhlZCBtYXhp
bXVtIG1lc3NhZ2Ugc2l6ZSBpbiBieXRlcwp0aGF0IHRoZSBzZXJ2ZXIgd2lsbCBhY2NlcHQuICBU
aGUgc3ludGF4IG9mIHRoZSBwYXJhbWV0ZXIgZm9sbG93cyB0aGUKYXVnbWVudGVkIEJORiBub3Rh
dGlvbiBvZiBbUkZDIDUyMzRdLiAgSWYgdGhpcyBjYXBhYmlsaXR5IGlzCm9taXR0ZWQsIG5vIGlu
Zm9ybWF0aW9uIGlzIGNvbnZleWVkIGFib3V0IHRoZSBzZXJ2ZXIncyBmaXhlZCBtYXhpbXVtCm1h
aWwgdXBsb2FkIHNpemUuCgo2LiBTZWN1cml0eSBDb25zaWRlcmF0aW9uCgpJdCBpcyBiZWxpZXZl
ZCB0aGF0IHRoaXMgZXh0ZW5zaW9uIGRvZXNuJ3QgYWRkIGFueSBuZXcgc2VjdXJpdHkKY29uc2lk
ZXJhdGlvbnMgdGhhdCBhcmUgbm90IGFscmVhZHkgcHJlc2VudCBpbiB0aGUgYmFzZSBJTUFQCnBy
b3RvY29sIFtSRkMzNTAxXS4KCjcuIElBTkEgQ29uc2lkZXJhdGlvbnMKClRoZSBJQU5BIGlzIHJl
cXVlc3RlZCB0byBhZGQgQVBQRU5ETElNSVQgdG8gdGhlIElNQVA0IENhcGFiaWxpdGllcwpSZWdp
c3RyeS4gIFtbTm90ZSB0byBSRkMtZWRpdG9yOiBwbGVhc2UgcmVtb3ZlIHRoZSBmb2xsb3dpbmcg
YmVmb3JlCnB1YmxpY2F0aW9uOiBUaGlzIHJlZ2lzdHJhdGlvbiBzaG91bGQgdGFrZSBwbGFjZSBh
dCB0aGUgZm9sbG93aW5nCmxvY2F0aW9uOiBodHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRz
L2ltYXA0LWNhcGFiaWxpdGllc11dCkpheWFudGhlZXNoICYgTmFyZW5kcmEgICAgICAgRXhwaXJl
cyBKdW5lLCAyMDE1ICAgICAgICAgICAgICBbUGFnZSA1XQoMCkludGVybmV0LURyYWZ0ICAgICAg
ICAgICAgICAgSU1BUCBBUFBFTkRMSU1JVCAgICAgICAgICAgRGVjZW1iZXIgMjAxNAoKOC4gUmVm
ZXJlbmNlcwoKOC4xIE5vcm1hdGl2ZSBSZWZlcmVuY2VzCgpUaGUgZm9sbG93aW5nIGRvY3VtZW50
cyBjb250YWluIGRlZmluaXRpb25zIG9yIHNwZWNpZmljYXRpb25zIHRoYXQKYXJlIG5lY2Vzc2Fy
eSB0byB1bmRlcnN0YW5kIHRoaXMgZG9jdW1lbnQgcHJvcGVybHkKCltSRkMyMTE5XSAgQnJhZG5l
ciwgIktleSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5kaWNhdGUKICAgICAgICAgICBSZXF1
aXJlbWVudCBMZXZlbHMiLCBSRkMgMjExOSwgSGFydmFyZCBVbml2ZXJzaXR5LCBNYXJjaAogICAg
ICAgICAgIDE5OTcuCiAgICAgICAgICAgCltSRkMzNTAxXSAgQ3Jpc3BpbiwgIklOVEVSTkVUIE1F
U1NBR0UgQUNDRVNTIFBST1RPQ09MIC0gVkVSU0lPTiA0cmV2MSIsCiAgICAgICAgICAgVW5pdmVy
c2l0eSBvZiBXYXNoaW5ndG9uLCBNYXJjaCAyMDAzCgpbUkZDNTIzNF0gIENyb2NrZXIsIE92ZXJl
bGwsICJBdWdtZW50ZWQgQk5GIGZvciBTeW50YXgKICAgICAgICAgICBTcGVjaWZpY2F0aW9uczog
QUJORiIsIFJGQyA1MjM0LCBCcmFuZGVuYnVyZwogICAgICAgICAgIEludGVybmV0d29ya2luZywg
RGVtb24gSW50ZXJuZXQgTHRkLCBKYW51YXJ5IDIwMDgKCltSRkM1MzIyXSAgUC4gUmVzbmljaywg
RWQsICJJbnRlcm5ldCBNZXNzYWdlIEZvcm1hdCIsIFJGQyA1MzIyLAogICAgICAgICAgIFF1YWxj
b21tIEluY29ycG9yYXRlZCwgT2N0b2JlciAyMDA4CgpbUkZDMjA4OF0gIEouIE15ZXJzLCBDYXJu
ZWdpZSBNZWxsb24sICJJTUFQNCBub24tc3luY2hyb25pemluZwogICAgICAgICAgIGxpdGVyYWxz
IiwgIEphbnVhcnkgMTk5NwoJCSAgIApbUkZDNDQ2OV0gIFAuIFJlc25pY2ssICJJbnRlcm5ldCBN
ZXNzYWdlIEFjY2VzcyBQcm90b2NvbCAoSU1BUCkKICAgICAgICAgICBDQVRFTkFURSBFeHRlbnNp
b24iLCAgQXByaWwgMjAwNgoJCSAgIApbUkZDNTgxOV0gIEEuIE1lbG5pa292LCBULiBTaXJhaW5l
biwgIklNQVA0IEV4dGVuc2lvbiBmb3IgUmV0dXJuaW5nCiAgICAgICAgICAgU1RBVFVTIEluZm9y
bWF0aW9uIGluIEV4dGVuZGVkIExJU1QiLCAgTWFyY2ggMjAxMAoKOC4gMiBJbmZvcm1hdGl2ZSBS
ZWZlcmVuY2VzCgpUaGUgZm9sbG93aW5nIGRvY3VtZW50cyBkZXNjcmliZSByZWxhdGVkIHByb3Rv
Y29sczoKCltSRkMyMDg3XSAgTXllcnMsIEouLCAiSU1BUDQgUVVPVEEgZXh0ZW5zaW9uIiwgUkZD
IDIwODcsCiAgICAgICAgICAgSmFudWFyeSAxOTk3CgpbUkZDNzM3N10gIEIuIExlaWJhLCBBLiBN
ZWxuaWtvdiwgIklNQVA0IE11bHRpbWFpbGJveCBTRUFSQ0gKICAgICAgICAgICBFeHRlbnNpb24i
LCBSRkMgNzM3NywgT2N0b2JlciAyMDE0Cgo5LiBBY2tub3dsZWRnZW1lbnQKClRCRAoKCgoKCkph
eWFudGhlZXNoICYgTmFyZW5kcmEgICAgICAgRXhwaXJlcyBKdW5lLCAyMDE1ICAgICAgICAgICAg
ICAgW1BhZ2UgNl0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIElNQVAgQVBQRU5ETElN
SVQgICAgICAgICAgIERlY2VtYmVyIDIwMTQKCjEwLiBBdXRob3IncyBBZGRyZXNzCgpKYXlhbnRo
ZWVzaCBTIEIKU2Ftc3VuZyBUZWxlY29tbXVuaWNhdGlvbnMgQW1lcmljYSwKNjg1IFVTIEhpZ2h3
YXkgMjAyLzIwNiwKQnJpZGdld2F0ZXIsIE5KIDA4ODA3LgpVU0EKRW1haWw6IGpheWFudGhlZXNo
LnNiQGdtYWlsLmNvbQoKTmFyZW5kcmEgU2luZ2ggQmlzaHQKU2Ftc3VuZyBUZWxlY29tbXVuaWNh
dGlvbnMgQW1lcmljYSwKNjg1IFVTIEhpZ2h3YXkgMjAyLzIwNiwKQnJpZGdld2F0ZXIsIE5KIDA4
ODA3LgpVU0EKRW1haWw6IG5hcmVuZHJhc2luZ2guYmlzaHRAZ21haWwuY29tCgoKCgoKCgoKCgoK
CgoKCgoKCQoJCgkKCQoKCQoJCgkKCQoJCgkKSmF5YW50aGVlc2ggJiBOYXJlbmRyYSAgICAgICBF
eHBpcmVzIE1heSwgMjAxNSAgICAgICAgICAgICAgIFtQYWdlIDZd

--_002_02454F842DD7B449B96715A2AD90C0363E99AFDCexMB5telecomsna_--


From nobody Wed Dec 17 04:01:20 2014
Return-Path: <slusarz@horde.org>
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 BB5BC1A8935 for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 04:01:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 UPq7u9Ysv3J4 for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 04:01:06 -0800 (PST)
Received: from resqmta-po-04v.sys.comcast.net (resqmta-po-04v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:163]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 567E21A1AC6 for <imapext@ietf.org>; Wed, 17 Dec 2014 04:01:06 -0800 (PST)
Received: from resomta-po-03v.sys.comcast.net ([96.114.154.227]) by resqmta-po-04v.sys.comcast.net with comcast id Uc131p0014ueUHc01c15Uy; Wed, 17 Dec 2014 12:01:05 +0000
Received: from bigworm.curecanti.org ([67.176.83.228]) by resomta-po-03v.sys.comcast.net with comcast id Uc131p00N4vagWz01c13jl; Wed, 17 Dec 2014 12:01:05 +0000
Received: from bigworm.curecanti.org (localhost.localdomain [IPv6:::1]) (Authenticated sender: slusarz) by bigworm.curecanti.org (Postfix) with ESMTPSA id 1D086680B2 for <imapext@ietf.org>; Wed, 17 Dec 2014 05:01:03 -0700 (MST)
Received: from 88.128.80.170 ([88.128.80.170]) by bigworm.curecanti.org (Horde Framework) with HTTP; Wed, 17 Dec 2014 05:01:02 -0700
Date: Wed, 17 Dec 2014 05:01:02 -0700
Message-ID: <20141217050102.Horde.GWA4XtpoLlxANoaBg9l1cg1@bigworm.curecanti.org>
From: Michael M Slusarz <slusarz@horde.org>
To: imapext@ietf.org
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com>
In-Reply-To: <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com>
User-Agent: Horde Application Framework 5
Accept-Language: en
X-Originating-IP: 88.128.80.170
X-Remote-Browser: Mozilla/5.0 (X11; CrOS x86_64 6310.68.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.96 Safari/537.36
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418817665; bh=vLmVaV/Qu6gXfKW8eXcYxEqikvsz6NhpaX0otkYdWG4=; h=Received:Received:Received:Received:Date:Message-ID:From:To: Subject:Content-Type:MIME-Version; b=ti1bTm3X1tZyDgXel/K9NW0f2OeVApZDPDB1KDdA9VSY19uG3pTAJJiYwlxZ95nCx T/ITNRg18fCdx0awkKp++G1S4FQ2MtEJowjN/Rbz6NbbJif6rpQiDjsQj4xPNduzW3 YTDHGCVjkuvT7o/X/ZwNKqiHtyRIABxZjAlAmSIe5Gw3Y62quEoErG1HZmhE5NBBD/ dZPD5RIqNTQj6mQ21hi3JV27XoXh+twmuZ0AAqaqP1hFnSdk5jQ6Cc5UXYS1txVVNI Hhb7WGGUNfblRbbU2MskTCmCZXTxjYVHkWveBctdxtWVsI+FjJpSi0obP4Es/gk0CW y7GMQ7VrNJ42w==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/xZW78cas55otuJ5IQRtS5Lmm_W8
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 17 Dec 2014 12:01:12 -0000

Quoting Jayantheesh S B <j.sb@sta.samsung.com>:

> Please find the updated version of the draft attached.
>
> Changes in this version:
>
> 1.  APPEND command response handling changes (Reused TOOBIG  
> response-text from rfc4469 )
> 2.  Retrieval of per mailbox limit in  authenticated state by using  
> LIST and STATUS command (Reference rfc5819)
>
> Kindly share your comments.

Some quick thoughts:

- Section 2 says a "client SHALL not try to upload mail more than  
advertised limit in the APPEND command.".  I would think that should  
be MUST, not SHALL.  If a client understands APPENDLIMIT, it knows the  
maximum size the server would accept.  Sending data over this limit is  
explicitly ignoring process/resource limits advertised by the server.

- Section 4: It seems like a good place to reiterate that LITERAL+  
SHOULD NOT be used, even if APPENDLIMIT is available, since there may  
be other reasons why a server would reject an APPEND and the client  
should only proceed with APPENDs only when the initial "handshake" has  
been accepted by the server.  APPEND is a place where we probably need  
the extra round-trip in exchange for preventing potentially large  
amounts of bandwidth to be used.

- There's discussion of LIST + STATUS (RFC 5819).  But this is  
actually an addition to STATUS itself.  The spec should be written as  
extending STATUS, and then a discussion/example of how this can be  
used if 5819 is supported.  (If we want to force an APPENDLIMIT  
client/server to also be LIST-STATUS compliant for performance  
reasons, that's fine.  But seems to be a policy decision rather than a  
technical explanation.)

michael

___________________________________
Michael Slusarz [slusarz@horde.org]


From nobody Wed Dec 17 04:44:37 2014
Return-Path: <alexey.melnikov@isode.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 1A0241A897B for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 04:44:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 qHT1qiiVY2Sn for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 04:44:33 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 9A73E1A1EFF for <imapext@ietf.org>; Wed, 17 Dec 2014 04:44:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418820272; d=isode.com; s=selector; i=@isode.com; bh=ywN/DAWxPzNUPkaSpBQy0DWg+epSBWFUS8SWYp7iZqo=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=TbmFulbZJpXb/e4ZZMX+Z0KieC6680Wxh+PQymnFDf50fxQZg2LlPXqgZ6+I1N8JP6iXHh oEEDFU2rkbr1T8MYoQe6lkmdvF48xKqVSw4z3ISJaoyynqrVtVnejIWvSxnYarbRceBuy4 unDwV/zN/8IY7WrwXXDskQKccUglJQM=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <VJF6rwAKaI9b@waldorf.isode.com>; Wed, 17 Dec 2014 12:44:32 +0000
Message-ID: <54917A9F.1030101@isode.com>
Date: Wed, 17 Dec 2014 12:44:15 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: Michael M Slusarz <slusarz@horde.org>, imapext@ietf.org
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com> <20141217050102.Horde.GWA4XtpoLlxANoaBg9l1cg1@bigworm.curecanti.org>
In-Reply-To: <20141217050102.Horde.GWA4XtpoLlxANoaBg9l1cg1@bigworm.curecanti.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/njWAdEnQxt6d21QzmGKpMq0jd-U
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 17 Dec 2014 12:44:35 -0000

Hi Michael,

On 17/12/2014 12:01, Michael M Slusarz wrote:
> Quoting Jayantheesh S B <j.sb@sta.samsung.com>:
>
>> Please find the updated version of the draft attached.
>>
>> Changes in this version:
>>
>> 1.  APPEND command response handling changes (Reused TOOBIG 
>> response-text from rfc4469 )
>> 2.  Retrieval of per mailbox limit in  authenticated state by using 
>> LIST and STATUS command (Reference rfc5819)
>>
>> Kindly share your comments.
>
> Some quick thoughts:
>
> - Section 2 says a "client SHALL not try to upload mail more than 
> advertised limit in the APPEND command.".  I would think that should 
> be MUST, not SHALL.  If a client understands APPENDLIMIT, it knows the 
> maximum size the server would accept.  Sending data over this limit is 
> explicitly ignoring process/resource limits advertised by the server.
SHALL and MUST have the same meaning according to RFC 2119.
> - Section 4: It seems like a good place to reiterate that LITERAL+ 
> SHOULD NOT be used, even if APPENDLIMIT is available, since there may 
> be other reasons why a server would reject an APPEND and the client 
> should only proceed with APPENDs only when the initial "handshake" has 
> been accepted by the server.  APPEND is a place where we probably need 
> the extra round-trip in exchange for preventing potentially large 
> amounts of bandwidth to be used.
Right. Or I can add this text to my update to LITERAL+ (currently 
expired draft-melnikov-rfc2088bis-00.txt)
> - There's discussion of LIST + STATUS (RFC 5819).  But this is 
> actually an addition to STATUS itself.  The spec should be written as 
> extending STATUS, and then a discussion/example of how this can be 
> used if 5819 is supported.  (If we want to force an APPENDLIMIT 
> client/server to also be LIST-STATUS compliant for performance 
> reasons, that's fine.  But seems to be a policy decision rather than a 
> technical explanation.)
This section is not quite right, but I need to rereview it in more details.


From nobody Wed Dec 17 10:36:04 2014
Return-Path: <alexey.melnikov@isode.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 942A61A1B98 for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 10:36:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level: 
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 3eShGMXfbkdq for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 10:35:58 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 76A371A0055 for <imapext@ietf.org>; Wed, 17 Dec 2014 10:35:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418841356; d=isode.com; s=selector; i=@isode.com; bh=y7zucjFbVe1bUiZyBZ5Yj95GNVQcBGaQybUZz8AqdrE=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=gkwJNteFR4cL7eruWcaCFqJqXIxod5HRM7lMa2iJUgIxTvd/WMuglQHRe+UxBqYIcYFGV+ 3lIqT4CdvPBxKqRqsqS2bU64SEQadeiYts+EM7/t2HtE6ImOf6g3+MmED0bGx6lj9UXcCw ce6TFdUwadz/GW8D0RfJez1leC3tPm4=;
Received: from [192.168.0.5] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <VJHNCwAKaE1s@waldorf.isode.com>; Wed, 17 Dec 2014 18:35:56 +0000
Message-ID: <5491CD00.6010606@isode.com>
Date: Wed, 17 Dec 2014 18:35:44 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
To: "imapext@ietf.org" <imapext@ietf.org>
References: <20141217182929.25391.39686.idtracker@ietfa.amsl.com>
In-Reply-To: <20141217182929.25391.39686.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20141217182929.25391.39686.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------060203080008010805090009"
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/4iUqRG4IjvT7F9hCoiA_WT97ZHw
Subject: [imapext] Fwd: I-D Action: draft-melnikov-rfc2088bis-01.txt
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, 17 Dec 2014 18:36:03 -0000

This is a multi-part message in MIME format.
--------------060203080008010805090009
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I revived and updated LITERAL+ extension. I also added LITERAL- 
extension (same as LITERAL+, but disallowed in APPEND).

-------- Original Message --------
Subject: 	I-D Action: draft-melnikov-rfc2088bis-01.txt
Date: 	Wed, 17 Dec 2014 10:29:29 -0800
From: 	internet-drafts@ietf.org
Reply-To: 	internet-drafts@ietf.org
To: 	i-d-announce@ietf.org



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


         Title           : IMAP4 non-synchronizing literals
         Authors         : John G. Myers
                           Alexey Melnikov
	Filename        : draft-melnikov-rfc2088bis-01.txt
	Pages           : 7
	Date            : 2014-12-17

Abstract:
    The Internet Message Access Protocol (RFC 3501) contains the
    "literal" syntactic construct for communicating strings.  When
    sending a literal from client to server, IMAP requires the client to
    wait for the server to send a command continuation request between
    sending the octet count and the string data.  This document specifies
    an alternate form of literal which does not require this network
    round trip.

    This document specifies 2 IMAP extensions: LITERAL+ and LITERAL-.
    The former allows the alternate form of literals in all IMAP command.
    The latter is the same as LITERAL+, but disallow the alternate form
    in IMAP APPEND.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-melnikov-rfc2088bis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-melnikov-rfc2088bis-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-melnikov-rfc2088bis-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt




--------------060203080008010805090009
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    I revived and updated LITERAL+ extension. I also added LITERAL-
    extension (same as LITERAL+, but disallowed in APPEND).<br>
    <div class="moz-forward-container"><br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject:
            </th>
            <td>I-D Action: draft-melnikov-rfc2088bis-01.txt</td>
          </tr>
          <tr>
            <th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
            <td>Wed, 17 Dec 2014 10:29:29 -0800</td>
          </tr>
          <tr>
            <th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" align="RIGHT" nowrap="nowrap">Reply-To:
            </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : IMAP4 non-synchronizing literals
        Authors         : John G. Myers
                          Alexey Melnikov
	Filename        : draft-melnikov-rfc2088bis-01.txt
	Pages           : 7
	Date            : 2014-12-17

Abstract:
   The Internet Message Access Protocol (RFC 3501) contains the
   "literal" syntactic construct for communicating strings.  When
   sending a literal from client to server, IMAP requires the client to
   wait for the server to send a command continuation request between
   sending the octet count and the string data.  This document specifies
   an alternate form of literal which does not require this network
   round trip.

   This document specifies 2 IMAP extensions: LITERAL+ and LITERAL-.
   The former allows the alternate form of literals in all IMAP command.
   The latter is the same as LITERAL+, but disallow the alternate form
   in IMAP APPEND.


The IETF datatracker status page for this draft is:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-melnikov-rfc2088bis/">https://datatracker.ietf.org/doc/draft-melnikov-rfc2088bis/</a>

There's also a htmlized version available at:
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-melnikov-rfc2088bis-01">http://tools.ietf.org/html/draft-melnikov-rfc2088bis-01</a>

A diff from the previous version is available at:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/rfcdiff?url2=draft-melnikov-rfc2088bis-01">http://www.ietf.org/rfcdiff?url2=draft-melnikov-rfc2088bis-01</a>


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a>

_______________________________________________
I-D-Announce mailing list
<a class="moz-txt-link-abbreviated" href="mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/i-d-announce">https://www.ietf.org/mailman/listinfo/i-d-announce</a>
Internet-Draft directories: <a class="moz-txt-link-freetext" href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>
or <a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a>
</pre>
      <br>
    </div>
    <br>
  </body>
</html>

--------------060203080008010805090009--


From nobody Wed Dec 17 13:32:21 2014
Return-Path: <narendrasingh.bisht@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 E2B4E1A8784 for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 13:32:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 Qt4KJa0iw5qD for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 13:32:19 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 754BF1A871C for <imapext@ietf.org>; Wed, 17 Dec 2014 13:32:19 -0800 (PST)
Received: by mail-ob0-f173.google.com with SMTP id uy5so6191919obc.4 for <imapext@ietf.org>; Wed, 17 Dec 2014 13:32:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:content-type; bh=KwcCG/fOz+iSWW6jd3JzUhXkFIC1UecaEiGA584vIRA=; b=PBTuQdq8PmmKe0WlPyYsz4SZ532IEOIdHVRgCmA3SH5hDnlqsQ6WhSZVfQsvkZJO5e D5aPOHNI3tWnUPc+EahKje35JvGnWHm99Un5kpGDl/3Kx6frRC1mnuS6LHD7Wp4ZcMGh KkanD1P7Afpngv5jJwIJVPGpxM2zlNTYV9+GUJ8lI1Mo9Apfekrn2OouXS+i7Q7nrZSj Mi9Q+rCsv1p2ztgmVTpcGEb0XxweDeBi10uBzmkOSerPagWUyAm2z8qR/6WKsF74KwHA IKYXHjVniz+ibC2lBNQq+rZo5WX45RCMFQYYtSuHcwlfQjVGzbnNhYLR8WIiAzkw7kIR TGCw==
X-Received: by 10.202.227.82 with SMTP id a79mr25930849oih.59.1418851938672; Wed, 17 Dec 2014 13:32:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.198.17 with HTTP; Wed, 17 Dec 2014 13:31:58 -0800 (PST)
From: narendra singh bisht <narendrasingh.bisht@gmail.com>
Date: Wed, 17 Dec 2014 16:31:58 -0500
Message-ID: <CAHC+rVG3p81cSxr-orW2Huj1JEe_c-DnPWy4miY8xPfoBSJFtQ@mail.gmail.com>
To: imapext@ietf.org
Content-Type: multipart/alternative; boundary=001a11408a56cb2a82050a70357b
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/r3Dr9nzJ5BhS2Ss0ALBmTY2qBhM
Subject: [imapext] Deleting Gmail Starred mail.
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, 17 Dec 2014 21:32:21 -0000

--001a11408a56cb2a82050a70357b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hey Folks,

I am seeing the below behavior in case of Gmail Drafts mail.

Anyone know if it is an intended behavior?



I have a Drafts mail with subject M1.

M1 is *starred*.

When I edit M1 and change subject to M2 from client (mobile device), what I
do is APPEND the new M2 and set the /DELETE flag for M1.

But on the Gmail web client, I can still see the M1 intact in Drafts
mailbox, I also see M2.



Can=E2=80=99t we delete starred mail by setting /DELETE flag?

Thanks in advance

--=20
Thanks & Regards
-Narendra

--001a11408a56cb2a82050a70357b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hey Folks,<div><br><div><p class=3D"MsoNormal">I am seeing=
 the below behavior in case of Gmail Drafts mail.</p>

<p class=3D"MsoNormal">Anyone know if it is an intended behavior?</p>

<p class=3D"MsoNormal">=C2=A0</p>

<p class=3D"MsoNormal">I have a Drafts mail with subject M1. </p>

<p class=3D"MsoNormal">M1 is <b><i>starred</i></b>.</p>

<p class=3D"MsoNormal">When I edit M1 and change subject to M2 from client =
(mobile
device), what I do is APPEND the new M2 and set the /DELETE flag for M1.</p=
>

<p class=3D"MsoNormal">But on the Gmail web client, I can still see the M1 =
intact
in Drafts mailbox, I also see M2.</p>

<p class=3D"MsoNormal">=C2=A0</p>

<p class=3D"MsoNormal">Can=E2=80=99t we delete starred mail by setting /DEL=
ETE flag?</p><div><br></div><div>Thanks in advance</div><div><br></div>-- <=
br><div class=3D"gmail_signature">Thanks &amp; Regards<div>-Narendra</div><=
/div>
</div></div></div>

--001a11408a56cb2a82050a70357b--


From nobody Wed Dec 17 14:41:55 2014
Return-Path: <nicolson@google.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 947181A876D for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 14:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level: 
X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 wSrKaCg2y1la for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 14:41:53 -0800 (PST)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E433F1A8769 for <imapext@ietf.org>; Wed, 17 Dec 2014 14:41:52 -0800 (PST)
Received: by mail-ig0-f171.google.com with SMTP id z20so9607232igj.16 for <imapext@ietf.org>; Wed, 17 Dec 2014 14:41:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=CuNxv8uXJJlnVjM4J669aMh3ViRiC45vs/FAKbouQuw=; b=g0UgOE6obEjWvUXpFIXxJg1s4pz2AZlQGd8QG2gFzd0JDNWMZfLSivx6GSm4bEx7tB T4EV9iHqovZaZYemRpa0v/+Qk8TrMNeIUkjMne2MWf9xIi76EBbCIyYJ/ldPraKGuRBe SNlfG358YR5CLrb10ooEDZ+Wzd0VHgCvn67BTM0H5luj/ylAPYn8PUsxMt8N3u6hK2ay U+ONtx9dcCNyZbOei91ZmjWdIlQlMN1xChyUlW1kU4Km2TNlg8PK6MC7p5eqsVpC5xE5 efECaid3Vvyc4L30ZJRQnFEdoPIy6RGnDgLXhraMmEHbnaBokzujeDx37mmNwvVhpRns RsBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=CuNxv8uXJJlnVjM4J669aMh3ViRiC45vs/FAKbouQuw=; b=NVEUgZby7OU+Pi80Tq9cmj0HM25ZXWbvcMXb1HUxeSjgLf1ezo4XpUfrpbUUbWsBzS AvcWPGGR3NB6YVXJYQNbe1Y07J8PXbBddIPWyJVXT7UFO3mChMMILk7nrZKdL4xOb0xJ aLi+xxCFN8WbcbvN5LacEyROyOXsbruyTsImluEimTrG1XZTe7HSGd61kN/1DRL8QGAF SvpbZvfEQ5+1ePSXEsGQYFIjHZjTJF1McPYsy9IvuOJiKy1iX7nmIfkw5Fkc0f0hiaMW Ka4meQANfkeIZmsOkD2UHh/5+kuq/X1qF3b+YWQOgfvt8akLZpjZNLvwUrY2GImKnZOb M0xw==
X-Gm-Message-State: ALoCoQnYlrSrR1ecT073qW/vz009LnzQRu8mMFo34pdOm2DTO4h8fiPoR0xh708JodJiSUKnoNop
X-Received: by 10.50.142.104 with SMTP id rv8mr10664822igb.23.1418856111787; Wed, 17 Dec 2014 14:41:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.168.134 with HTTP; Wed, 17 Dec 2014 14:41:20 -0800 (PST)
In-Reply-To: <CAHC+rVG3p81cSxr-orW2Huj1JEe_c-DnPWy4miY8xPfoBSJFtQ@mail.gmail.com>
References: <CAHC+rVG3p81cSxr-orW2Huj1JEe_c-DnPWy4miY8xPfoBSJFtQ@mail.gmail.com>
From: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Date: Wed, 17 Dec 2014 14:41:20 -0800
Message-ID: <CACU8CfQcMdWtmHEPYrZAdvsuOR_mpW-We6oJL_qnerPjp-OVRQ@mail.gmail.com>
To: narendra singh bisht <narendrasingh.bisht@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3db0087fbb4050a712eb7
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/pJn1LnpzQ41F6Jg1HgT2oAnja8s
Cc: imapext@ietf.org
Subject: Re: [imapext] Deleting Gmail Starred mail.
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, 17 Dec 2014 22:41:54 -0000

--001a11c3db0087fbb4050a712eb7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

By "starred" I assume you mean the message has the \Flagged flag. In Gmail
IMAP, this is synonymous with being present in the [Gmail]/Starred folder.

The behavior you witnessed is a quirky Gmail-specific behavior for the
Drafts folder. When a message is expunged from an "ordinary" folder (not
All Mail, Spam, Trash, or Drafts), the effect is simply to remove the
message from that folder; this is analogous to Archive in the web view.
Because Drafts are intended to be temporary messages, when a message is
expunged from the Drafts folder, we take the additional step of moving it
to the Trash folder, where it will be automatically deleted after 30 days.
However, if the Draft message is also present in any other folder (such as
Starred), we do not move to Trash, because by putting the message in
another folder the user may have indicated that they wish to keep the
message around long-term.

The workaround is either to removed the \Flagged flag from the message, or
COPY it to the Trash folder.

On Wed, Dec 17, 2014 at 1:31 PM, narendra singh bisht <
narendrasingh.bisht@gmail.com> wrote:
>
> Hey Folks,
>
> I am seeing the below behavior in case of Gmail Drafts mail.
>
> Anyone know if it is an intended behavior?
>
>
>
> I have a Drafts mail with subject M1.
>
> M1 is *starred*.
>
> When I edit M1 and change subject to M2 from client (mobile device), what
> I do is APPEND the new M2 and set the /DELETE flag for M1.
>
> But on the Gmail web client, I can still see the M1 intact in Drafts
> mailbox, I also see M2.
>
>
>
> Can=E2=80=99t we delete starred mail by setting /DELETE flag?
>
> Thanks in advance
>
> --
> Thanks & Regards
> -Narendra
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext
>
>

--001a11c3db0087fbb4050a712eb7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>By &quot;starred&quot; I assume you mean the message =
has the \Flagged flag. In Gmail IMAP, this is synonymous with being present=
 in the [Gmail]/Starred folder.</div><div><br></div>The behavior you witnes=
sed is a quirky Gmail-specific behavior for the Drafts folder. When a messa=
ge is expunged from an &quot;ordinary&quot; folder (not All Mail, Spam, Tra=
sh, or Drafts), the effect is simply to remove the message from that folder=
; this is analogous to Archive in the web view. Because Drafts are intended=
 to be temporary messages, when a message is expunged from the Drafts folde=
r, we take the additional step of moving it to the Trash folder, where it w=
ill be automatically deleted after 30 days. However, if the Draft message i=
s also present in any other folder (such as Starred), we do not move to Tra=
sh, because by putting the message in another folder the user may have indi=
cated that they wish to keep the message around long-term.<div><div><br></d=
iv><div>The workaround is either to removed the \Flagged flag from the mess=
age, or COPY it to the Trash folder.</div></div></div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">On Wed, Dec 17, 2014 at 1:31 PM, naren=
dra singh bisht <span dir=3D"ltr">&lt;<a href=3D"mailto:narendrasingh.bisht=
@gmail.com" target=3D"_blank">narendrasingh.bisht@gmail.com</a>&gt;</span> =
wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hey Folks,<div><br><d=
iv><p class=3D"MsoNormal">I am seeing the below behavior in case of Gmail D=
rafts mail.</p>

<p class=3D"MsoNormal">Anyone know if it is an intended behavior?</p>

<p class=3D"MsoNormal">=C2=A0</p>

<p class=3D"MsoNormal">I have a Drafts mail with subject M1. </p>

<p class=3D"MsoNormal">M1 is <b><i>starred</i></b>.</p>

<p class=3D"MsoNormal">When I edit M1 and change subject to M2 from client =
(mobile
device), what I do is APPEND the new M2 and set the /DELETE flag for M1.</p=
>

<p class=3D"MsoNormal">But on the Gmail web client, I can still see the M1 =
intact
in Drafts mailbox, I also see M2.</p>

<p class=3D"MsoNormal">=C2=A0</p>

<p class=3D"MsoNormal">Can=E2=80=99t we delete starred mail by setting /DEL=
ETE flag?</p><div><br></div><div>Thanks in advance</div><span class=3D"HOEn=
Zb"><font color=3D"#888888"><div><br></div>-- <br><div>Thanks &amp; Regards=
<div>-Narendra</div></div>
</font></span></div></div></div>
<br>_______________________________________________<br>
imapext mailing list<br>
<a href=3D"mailto:imapext@ietf.org">imapext@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/imapext" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/imapext</a><br>
<br></blockquote></div></div>

--001a11c3db0087fbb4050a712eb7--


From nobody Wed Dec 17 15:23:05 2014
Return-Path: <narendrasingh.bisht@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 03DCA1A002F for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 15:23:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 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, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 qjc5Vipxxygs for <imapext@ietfa.amsl.com>; Wed, 17 Dec 2014 15:23:00 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ECB11A0008 for <imapext@ietf.org>; Wed, 17 Dec 2014 15:23:00 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id va8so6971109obc.3 for <imapext@ietf.org>; Wed, 17 Dec 2014 15:22:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7HQ2kCpILOXVsma1zIKf9/ULfIC/FKnVHFjE1VvVG08=; b=bvayyI57LCiw7s7s2/s5wGjDH5VQkySoeYUqJG9t3FhEXJwnqQbzuTBIC5fZO1h4+4 kypa301hsANjm5L6rqsuRGlElKYZZ9uvT4+2Zpw9kJaBpxfgWrXY8eZ/+MN8xBMuoWer N1OGfiv/fzrNk4Mpkptiy29Ms9r7rIGC0nlxbYdjmOR32/TuA2kCXLT7F7WjJtv8vYSm yMyshPmaQhvHbhPWM8S8gejzIFGeJLIp01xgY7MQRQUc2mJXW83tsKtXegmRuRl10u+Q THFozpB7+FBnLUzKHSyywZ/Qh3SV7fX8n6nemH8kucOiEHdDDp+2/sV5gfOE7JhJgWcd 2ywg==
X-Received: by 10.202.227.82 with SMTP id a79mr26216053oih.59.1418858579620; Wed, 17 Dec 2014 15:22:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.198.17 with HTTP; Wed, 17 Dec 2014 15:22:39 -0800 (PST)
In-Reply-To: <CACU8CfQcMdWtmHEPYrZAdvsuOR_mpW-We6oJL_qnerPjp-OVRQ@mail.gmail.com>
References: <CAHC+rVG3p81cSxr-orW2Huj1JEe_c-DnPWy4miY8xPfoBSJFtQ@mail.gmail.com> <CACU8CfQcMdWtmHEPYrZAdvsuOR_mpW-We6oJL_qnerPjp-OVRQ@mail.gmail.com>
From: narendra singh bisht <narendrasingh.bisht@gmail.com>
Date: Wed, 17 Dec 2014 18:22:39 -0500
Message-ID: <CAHC+rVFF4+AdZzGbuV730S65BJ0ZdX0b6McCxDM+Gu0m46JGkw@mail.gmail.com>
To: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Content-Type: multipart/alternative; boundary=001a11408a56a00173050a71c105
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/fz0L9QszBKJOVvS7oa2vvJ4y8xk
Cc: imapext@ietf.org
Subject: Re: [imapext] Deleting Gmail Starred mail.
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, 17 Dec 2014 23:23:02 -0000

--001a11408a56a00173050a71c105
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks Jamie...that answers my doubt......thank you...

On Wed, Dec 17, 2014 at 5:41 PM, Jamie Nicolson (=E5=80=AA=E5=BF=97=E6=98=
=8E) <nicolson@google.com>
wrote:
>
> By "starred" I assume you mean the message has the \Flagged flag. In Gmai=
l
> IMAP, this is synonymous with being present in the [Gmail]/Starred folder=
.
>
> The behavior you witnessed is a quirky Gmail-specific behavior for the
> Drafts folder. When a message is expunged from an "ordinary" folder (not
> All Mail, Spam, Trash, or Drafts), the effect is simply to remove the
> message from that folder; this is analogous to Archive in the web view.
> Because Drafts are intended to be temporary messages, when a message is
> expunged from the Drafts folder, we take the additional step of moving it
> to the Trash folder, where it will be automatically deleted after 30 days=
.
> However, if the Draft message is also present in any other folder (such a=
s
> Starred), we do not move to Trash, because by putting the message in
> another folder the user may have indicated that they wish to keep the
> message around long-term.
>
> The workaround is either to removed the \Flagged flag from the message, o=
r
> COPY it to the Trash folder.
>
> On Wed, Dec 17, 2014 at 1:31 PM, narendra singh bisht <
> narendrasingh.bisht@gmail.com> wrote:
>
>> Hey Folks,
>>
>> I am seeing the below behavior in case of Gmail Drafts mail.
>>
>> Anyone know if it is an intended behavior?
>>
>>
>>
>> I have a Drafts mail with subject M1.
>>
>> M1 is *starred*.
>>
>> When I edit M1 and change subject to M2 from client (mobile device), wha=
t
>> I do is APPEND the new M2 and set the /DELETE flag for M1.
>>
>> But on the Gmail web client, I can still see the M1 intact in Drafts
>> mailbox, I also see M2.
>>
>>
>>
>> Can=E2=80=99t we delete starred mail by setting /DELETE flag?
>>
>> Thanks in advance
>>
>> --
>> Thanks & Regards
>> -Narendra
>>
>> _______________________________________________
>> imapext mailing list
>> imapext@ietf.org
>> https://www.ietf.org/mailman/listinfo/imapext
>>
>>

--=20
Thanks & Regards
-Narendra

--001a11408a56a00173050a71c105
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Jamie...that answers my doubt......thank you...</di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Dec 17,=
 2014 at 5:41 PM, Jamie Nicolson (=E5=80=AA=E5=BF=97=E6=98=8E) <span dir=3D=
"ltr">&lt;<a href=3D"mailto:nicolson@google.com" target=3D"_blank">nicolson=
@google.com</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D=
"ltr"><div>By &quot;starred&quot; I assume you mean the message has the \Fl=
agged flag. In Gmail IMAP, this is synonymous with being present in the [Gm=
ail]/Starred folder.</div><div><br></div>The behavior you witnessed is a qu=
irky Gmail-specific behavior for the Drafts folder. When a message is expun=
ged from an &quot;ordinary&quot; folder (not All Mail, Spam, Trash, or Draf=
ts), the effect is simply to remove the message from that folder; this is a=
nalogous to Archive in the web view. Because Drafts are intended to be temp=
orary messages, when a message is expunged from the Drafts folder, we take =
the additional step of moving it to the Trash folder, where it will be auto=
matically deleted after 30 days. However, if the Draft message is also pres=
ent in any other folder (such as Starred), we do not move to Trash, because=
 by putting the message in another folder the user may have indicated that =
they wish to keep the message around long-term.<div><div><br></div><div>The=
 workaround is either to removed the \Flagged flag from the message, or COP=
Y it to the Trash folder.</div></div></div><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote"><div><div class=3D"h5">On Wed, Dec 17, 2014 at 1:=
31 PM, narendra singh bisht <span dir=3D"ltr">&lt;<a href=3D"mailto:narendr=
asingh.bisht@gmail.com" target=3D"_blank">narendrasingh.bisht@gmail.com</a>=
&gt;</span> wrote:</div></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div clas=
s=3D"h5"><div dir=3D"ltr">Hey Folks,<div><br><div><p class=3D"MsoNormal">I =
am seeing the below behavior in case of Gmail Drafts mail.</p>

<p class=3D"MsoNormal">Anyone know if it is an intended behavior?</p>

<p class=3D"MsoNormal">=C2=A0</p>

<p class=3D"MsoNormal">I have a Drafts mail with subject M1. </p>

<p class=3D"MsoNormal">M1 is <b><i>starred</i></b>.</p>

<p class=3D"MsoNormal">When I edit M1 and change subject to M2 from client =
(mobile
device), what I do is APPEND the new M2 and set the /DELETE flag for M1.</p=
>

<p class=3D"MsoNormal">But on the Gmail web client, I can still see the M1 =
intact
in Drafts mailbox, I also see M2.</p>

<p class=3D"MsoNormal">=C2=A0</p>

<p class=3D"MsoNormal">Can=E2=80=99t we delete starred mail by setting /DEL=
ETE flag?</p><div><br></div><div>Thanks in advance</div><span><font color=
=3D"#888888"><div><br></div>-- <br><div>Thanks &amp; Regards<div>-Narendra<=
/div></div>
</font></span></div></div></div>
<br></div></div>_______________________________________________<br>
imapext mailing list<br>
<a href=3D"mailto:imapext@ietf.org" target=3D"_blank">imapext@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/imapext" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/imapext</a><br>
<br></blockquote></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div class=3D"gm=
ail_signature">Thanks &amp; Regards<div>-Narendra</div></div>
</div>

--001a11408a56a00173050a71c105--


From nobody Thu Dec 18 03:57:14 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 77B381A6F53 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 03:57:11 -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, RCVD_IN_DNSWL_NONE=-0.0001] 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 m1mL82Lu2HZx for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 03:57:05 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3F4B1A6FB0 for <imapext@ietf.org>; Thu, 18 Dec 2014 03:57:04 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 91260FA0082; Thu, 18 Dec 2014 11:57:02 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1418903821-22718-22717/11/27; Thu, 18 Dec 2014 11:57:01 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Thu, 18 Dec 2014 12:57:00 +0100
User-Agent: Trojita/v0.4.1-243-g4a74770; Qt/4.8.6; X11; Linux; Ubuntu 14.04.1 LTS
Mime-Version: 1.0
Message-Id: <f84ea49d-c876-4133-8b05-a5354cb87d85@gulbrandsen.priv.no>
In-Reply-To: <5491CD00.6010606@isode.com>
References: <20141217182929.25391.39686.idtracker@ietfa.amsl.com> <5491CD00.6010606@isode.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/rrcbpsqgjcFJ0Hv2tBklYzk3lyM
Subject: Re: [imapext] Fwd: I-D Action: draft-melnikov-rfc2088bis-01.txt
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, 18 Dec 2014 11:57:11 -0000

On Wednesday, December 17, 2014 7:35:44 PM CEST, Alexey Melnikov wrote:
> I revived and updated LITERAL+ extension. I also added LITERAL- 
> extension (same as LITERAL+, but disallowed in APPEND).

Why is LITERAL- like that intead of being restricted to short literals? Say 
up to 16k.

The problem in RFC 1047 affects APPEND too. A limit comparable to typical 
TCP transmission windows would be appropriate, I think.

Arnt


From nobody Thu Dec 18 04:14:42 2014
Return-Path: <alexey.melnikov@isode.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 5C3981A8840 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 04:14:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 DbRc6PjEWazf for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 04:14:35 -0800 (PST)
Received: from statler.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id A88351A883B for <imapext@ietf.org>; Thu, 18 Dec 2014 04:14:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418904874; d=isode.com; s=selector; i=@isode.com; bh=sbZAxridUtvYVnyO6MSNEyDf1cq97o9FRB9eOygF4BQ=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=L6WZ8Y9WAbBCJpRE9VYBp1IpAUHuce9Q4C7B6+9yovWF56hzEGlidO/kMdcXHeXwtd4PZR ld+J+t91kXtmu8WVq9rNnbuuHrf0txzLBQkELFbUY3+4XWQhCj3x9koeQ8KF/gSKZvLrfr 9ioMbf3O5O3f9guQxtEw5UkmgLD59dQ=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <VJLFKgBz6SX4@statler.isode.com>; Thu, 18 Dec 2014 12:14:34 +0000
Message-ID: <5492C514.6080000@isode.com>
Date: Thu, 18 Dec 2014 12:14:12 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, imapext@ietf.org
References: <20141217182929.25391.39686.idtracker@ietfa.amsl.com> <5491CD00.6010606@isode.com> <f84ea49d-c876-4133-8b05-a5354cb87d85@gulbrandsen.priv.no>
In-Reply-To: <f84ea49d-c876-4133-8b05-a5354cb87d85@gulbrandsen.priv.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/Csl47UMezAj_MJpX6DZ1NDWPBxM
Subject: Re: [imapext] Fwd: I-D Action: draft-melnikov-rfc2088bis-01.txt
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, 18 Dec 2014 12:14:37 -0000

On 18/12/2014 11:57, Arnt Gulbrandsen wrote:
> On Wednesday, December 17, 2014 7:35:44 PM CEST, Alexey Melnikov wrote:
>> I revived and updated LITERAL+ extension. I also added LITERAL- 
>> extension (same as LITERAL+, but disallowed in APPEND).
> Why is LITERAL- like that intead of being restricted to short 
> literals? Say up to 16k.
Allowing smaller non synchronizing literal sizes in APPEND might work, 
but the problem is that this still allows for abuse if the limit is 
exceeded.

Are people interested in changing LITERAL- to allow smaller messages 
being uploaded with non synchronizing literals (bigger messages can 
still be uploaded using RFC 3501 synchronizing literals)?
> The problem in RFC 1047 affects APPEND too. A limit comparable to 
> typical TCP transmission windows would be appropriate, I think.


From nobody Thu Dec 18 04:31:55 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 777361A888B for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 04:31:54 -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 vLZqFSFRyR05 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 04:31:53 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC7C71A888A for <imapext@ietf.org>; Thu, 18 Dec 2014 04:31:52 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 4C903FA0082; Thu, 18 Dec 2014 12:31:49 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1418905908-22718-22717/12/81; Thu, 18 Dec 2014 12:31:48 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Thu, 18 Dec 2014 13:31:47 +0100
User-Agent: Trojita/v0.4.1-243-g4a74770; Qt/4.8.6; X11; Linux; Ubuntu 14.04.1 LTS
Mime-Version: 1.0
Message-Id: <846929b7-6381-4fb4-a9ee-6cf34d412900@gulbrandsen.priv.no>
In-Reply-To: <5492C514.6080000@isode.com>
References: <20141217182929.25391.39686.idtracker@ietfa.amsl.com> <5491CD00.6010606@isode.com> <f84ea49d-c876-4133-8b05-a5354cb87d85@gulbrandsen.priv.no> <5492C514.6080000@isode.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/_E2k9TJDFlV-hep4ZcypiToWMcI
Subject: Re: [imapext] Fwd: I-D Action: draft-melnikov-rfc2088bis-01.txt
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, 18 Dec 2014 12:31:54 -0000

On Thursday, December 18, 2014 1:14:12 PM CEST, Alexey Melnikov wrote:
> Allowing smaller non synchronizing literal sizes in APPEND 
> might work, but the problem is that this still allows for abuse 
> if the limit is exceeded.

Not really, not if the limit is comparable to typical TCP send windows. A 
badly behaving client can send one TCP window's worth of stuff to the 
server anyway.

Specifically, the client can send
    a append inbox () "01-01-2000" {9999999999999999999999999999+}
no matter whether which part of that line is forbidden, and the server has 
to eat one whole TCP window before it can throw the client out.

Arnt


From nobody Thu Dec 18 04:35:11 2014
Return-Path: <alexey.melnikov@isode.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 D439C1A888A for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 04:35:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level: 
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 u93mYw52ICMD for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 04:35:04 -0800 (PST)
Received: from statler.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 3E60A1A888B for <imapext@ietf.org>; Thu, 18 Dec 2014 04:35:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418906103; d=isode.com; s=selector; i=@isode.com; bh=kMdaX3rbfRlb2PnNlsTJ2qJd91txjxuVUNZHwEyjNCk=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=ppek9zJbpIEXFPuRyyW+EeWxFIDEkdgFCC5FNb8psHue5zPh/XLxLp5I0yPHJVbJyeCpv+ GbZYEjekeIuhb0dck5mw0jNfx//4yIQZjpzXJpXDDk2R2R22A+DsnjSModjN2TnH5BHOJT Zo/e+dn6w5EXUkx7ScOy61n1L6DHoQQ=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <VJLJ9ABz6aAc@statler.isode.com>; Thu, 18 Dec 2014 12:35:02 +0000
Message-ID: <5492C9DE.6070505@isode.com>
Date: Thu, 18 Dec 2014 12:34:38 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: Jayantheesh S B <j.sb@sta.samsung.com>, 'Stuart Brandt' <stujenerin@aol.com>, "'imapext@ietf.org'" <imapext@ietf.org>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com>
In-Reply-To: <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------070907070609010700000204"
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/Bowj7E2r04OWJJ5t11Gxdu-sXr0
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 18 Dec 2014 12:35:11 -0000

--------------070907070609010700000204
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit


On 16/12/2014 23:21, Jayantheesh S B wrote:
> Hi All,
>
> Please find the updated version of the draft attached.
>
> Changes in this version:
>
> 1.  APPEND command response handling changes (Reused TOOBIG response-text from rfc4469 )
> 2.  Retrieval of per mailbox limit in  authenticated state by using LIST and STATUS command (Reference rfc5819)
Comments on the new section 3.2 that you've added:
> 3.2 LIST response
>
> IMAP client can get the mailbox specific APPENDLIMIT in authenticated
> state, where it do not need to issue SELECT/EXAMINE command.  LIST
> command in combination with STATUS command can be issued to get the per
> mailbox specific APPENDLIMIT set by the server.  Refer rfc5819 for the
> usage of LIST command in combination with STATUS command usage.
Nit: drop the last "usage".

I suggest you add the following sentence after the one quoted above:

Note that a server implementing this extension, is syntactically 
compatible with RFC 5819, however support for RFC 5258 or RFC 5819 is 
not required when implementing this extension.
>
> The following example demonstrates, its usage.
>
> C: t1 LIST "" % RETURN (STATUS (APPENDLIMIT))
> S: * LIST () "."  "INBOX"
> S: * STATUS "INBOX" (APPENDLIMIT 257890)
> S: t1 OK List completed.
>
> New attribute APPNDLIMIT is added to get the limit set by the server for
Typo: APPENDLIMIT
> this mailbox as part of STATUS command.  The STATUS response occurs as a
> result of an STATUS command.  It returns the mailbox name that matches
> the STATUS specification and the requested mailbox status information.
> IMAP server should recognize an extra "RETURN (STATUS(APPENDLIMIT))" at
Please change "RETURN (STATUS(APPENDLIMIT))" to ""RETURN (STATUS 
(APPENDLIMIT))", as spaces are significant.
> the end of a list command and emit an extra STATUS response for each
> matching mailbox.  Refer to section [5] for the syntax.

How did you manage to generate [5]? This is going to be misinterpreted as a document reference by various IETF tools. Just use "5".

It might also be worth pointing out that just calling STATUS with APPENDLIMIT is also acceptable. It would be worth adding an example of that as well.

> Kindly share your comments.
>
> Regards,
> Jay
>
> -----Original Message-----
> From: Stuart Brandt [mailto:stujenerin@aol.com]
> Sent: Monday, December 15, 2014 10:07 AM
> To: Alexey Melnikov; Jayantheesh S B
> Cc: 'imapext@ietf.org'
> Subject: Re: [imapext] [IMAP] APPEND Command Usage
>
> Inline comments
>
> On 12/15/14 6:52 AM, Alexey Melnikov wrote:
>> Hi Stuart,
>>
>> On 12/12/2014 15:40, Stuart Brandt wrote:
>>> Inline comments
>>>
>>> On 12/12/14 5:24 AM, Alexey Melnikov wrote:
>>>> Hi Stuart,
>>>>
>>>> On 10/12/2014 19:58, Stuart Brandt wrote:
>>>>>  From a server perspective, the proposal solves my concern. From a
>>>>> client perspective, I'm not sure whether the addition of [SP
>>>>> nz-number] to the TOOBIG response would present problems for
>>>>> clients that only implement CATENATE and not APPENDLIMIT. I too
>>>>> would like to see others chime in on that part.
>>>>>
>>>>>  From what I see, most IMAP sessions either precede an APPEND with a
>>>>> SELECT/EXAMINE or LIST...likely to confirm the existence of the
>>>>> target mailbox into which they're going to append.  The proposal
>>>>> already covers SELECT/EXAMINE, so would it be reasonable to add the
>>>>> APPENDLIMIT=x as an attribute to the LIST response data in order to
>>>>> reflect any per-mailbox limit and avoid trying to convey the limit
>>>>> as part of the TOOBIG response code to APPEND? Something along the
>>>>> line
>>>>> of:
>>>>>
>>>>> C: t1 LIST "" "%"
>>>>> S: * LIST (\Marked \HasNoChildren) "/" Inbox
>>>>> S: * LIST (\HasNoChildren) "/" ToDo
>>>>> S: * LIST (\HasChildren) "/" Projects
>>>>> S: * LIST (\Sent \HasNoChildren) "/" SentMail
>>>>> S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=257890) "/"
>>>>> MyDrafts
>>>>> S: * LIST (\Trash \HasNoChildren) "/" Trash
>>>> All mailbox attributes are typically checked for equality, so this
>>>> this a departure from this principle. (I know we started to violate
>>>> this rule in CAPABILITY response) So personally, I prefer if we add
>>>> a new STATUS item for APPEND limit.
>>>> Then we can use STATUS-in-LIST bridge
>>>> (https://tools.ietf.org/html/rfc5819) to return this information.
>>>>
>>>> As clients that want to obey APPENDLIMIT would need to be modified
>>>> anyway, they might as well be modified to support RFC 5819 syntax.
>>> And same goes for the server, because the client will want to query
>>> *every* server that supports APPENDLIMIT just in case it has
>>> per-mailbox limits. Unless I'm way off base here, a server with a
>>> simple mailbox-wide APPEND limit would need to implement APPENDLIMIT
>>> *plus* 5819 and 5258 to support the client asking about per-mailbox
>>> limits -- unless we have the client assume that lack of support for
>>> 5819/5258 implies that the server has no per-mailbox limits. Seems
>>> pretty involved.
>> Actually, I was thinking of something simpler, which is syntactically
>> compatible:
>>
>> C: A01 LIST "" % RETURN (STATUS (APPENDLIMIT))
>> S: * LIST () "."  "INBOX"
>> S: * STATUS "INBOX" (APPENDLIMIT 1024000)
>>
>> So basically server should recognize an extra "RETURN (STATUS
>> (APPENDLIMIT))" at the end of a list command and emit an extra STATUS
>> response for each matching mailbox. Support for RFC 5819 and RFC 5258
>> is optional.
> That certainly simplifies things. Sounds good.
>
>>
>> My reason for recommending this (other than "compatibility with RFC
>> 5819/5258 is a good thing") is that if the limit is per mailbox, it
>> might be stored with mailbox information and thus might be relatively
>> expensive to retrieve. So a compliant server shouldn't try to retrieve
>> it unless a client asks for this information. So basically we need a
>> signalling mechanism for requesting this information.
> Makes complete sense.
>
>>>> But otherwise I am Ok with being able to return this information in
>>>> LIST.
>>
>>
>> _______________________________________________
>> imapext mailing list
>> imapext@ietf.org
>> https://www.ietf.org/mailman/listinfo/imapext


--------------070907070609010700000204
Content-Type: text/html; charset=windows-1252
Content-transfer-encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dwindows-1252"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <br>
    <div class=3D"moz-cite-prefix">On 16/12/2014 23:21, Jayantheesh S B
      wrote:<br>
    </div>
    <blockquote
cite=3D"mid:02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsu=
ng.com"
      type=3D"cite">
      <pre wrap=3D"">Hi All,

Please find the updated version of the draft attached.

Changes in this version:

1.  APPEND command response handling changes (Reused TOOBIG response-text fr=
om rfc4469 )
2.  Retrieval of per mailbox limit in  authenticated state by using LIST and=
 STATUS command (Reference rfc5819)</pre>
    </blockquote>
    Comments on the new section 3.2 that you've added:<br>
    <blockquote type=3D"cite">3.2 LIST response<br>
      <br>
      IMAP client can get the mailbox specific APPENDLIMIT in
      authenticated<br>
      state, where it do not need to issue SELECT/EXAMINE command.=A0 LIST<b=
r>
      command in combination with STATUS command can be issued to get
      the per<br>
      mailbox specific APPENDLIMIT set by the server.=A0 Refer rfc5819 for
      the<br>
      usage of LIST command in combination with STATUS command usage.<br>
    </blockquote>
    Nit: drop the last "usage".<br>
    <br>
    I suggest you add the following sentence after the one quoted above:<br>
    <br>
    Note that a server implementing this extension, is syntactically
    compatible with RFC 5819, however support for RFC 5258 or RFC 5819
    is not required when implementing this extension.<br>
    <blockquote type=3D"cite"><br>
      The following example demonstrates, its usage.<br>
      <br>
      C: t1 LIST "" % RETURN (STATUS (APPENDLIMIT))<br>
      S: * LIST () "."=A0 "INBOX"<br>
      S: * STATUS "INBOX" (APPENDLIMIT 257890)<br>
      S: t1 OK List completed.<br>
      <br>
      New attribute APPNDLIMIT is added to get the limit set by the
      server for<br>
    </blockquote>
    Typo: APPENDLIMIT<br>
    <blockquote type=3D"cite">this mailbox as part of STATUS command.=A0 The
      STATUS response occurs as a<br>
      result of an STATUS command.=A0 It returns the mailbox name that
      matches<br>
      the STATUS specification and the requested mailbox status
      information.<br>
      IMAP server should recognize an extra "RETURN
      (STATUS(APPENDLIMIT))" at<br>
    </blockquote>
    Please change "RETURN (STATUS(APPENDLIMIT))" to ""RETURN (STATUS
    (APPENDLIMIT))", as spaces are significant.<br>
    <blockquote type=3D"cite">the end of a list command and emit an extra
      STATUS response for each<br>
      matching mailbox.=A0 Refer to section [5] for the syntax.</blockquote>
    <pre wrap=3D"">How did you manage to generate [5]? This is going to be m=
isinterpreted as a document reference by various IETF tools. Just use "5".

It might also be worth pointing out that just calling STATUS with APPENDLIMI=
T is also acceptable. It would be worth adding an example of that as well.=
=20
</pre>
    <blockquote
cite=3D"mid:02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsu=
ng.com"
      type=3D"cite">
      <pre wrap=3D"">Kindly share your comments.=20

Regards,
Jay

-----Original Message-----
From: Stuart Brandt [<a class=3D"moz-txt-link-freetext" href=3D"mailto:stuje=
nerin@aol.com">mailto:stujenerin@aol.com</a>]=20
Sent: Monday, December 15, 2014 10:07 AM
To: Alexey Melnikov; Jayantheesh S B
Cc: '<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:imapext@ietf.org">=
imapext@ietf.org</a>'
Subject: Re: [imapext] [IMAP] APPEND Command Usage

Inline comments

On 12/15/14 6:52 AM, Alexey Melnikov wrote:
</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">Hi Stuart,

On 12/12/2014 15:40, Stuart Brandt wrote:
</pre>
        <blockquote type=3D"cite">
          <pre wrap=3D"">Inline comments

On 12/12/14 5:24 AM, Alexey Melnikov wrote:
</pre>
          <blockquote type=3D"cite">
            <pre wrap=3D"">Hi Stuart,

On 10/12/2014 19:58, Stuart Brandt wrote:
</pre>
            <blockquote type=3D"cite">
              <pre wrap=3D"">From a server perspective, the proposal solves =
my concern. From a=20
client perspective, I'm not sure whether the addition of [SP=20
nz-number] to the TOOBIG response would present problems for=20
clients that only implement CATENATE and not APPENDLIMIT. I too=20
would like to see others chime in on that part.

>From what I see, most IMAP sessions either precede an APPEND with a=20
SELECT/EXAMINE or LIST...likely to confirm the existence of the=20
target mailbox into which they're going to append.  The proposal=20
already covers SELECT/EXAMINE, so would it be reasonable to add the=20
APPENDLIMIT=3Dx as an attribute to the LIST response data in order to=20
reflect any per-mailbox limit and avoid trying to convey the limit=20
as part of the TOOBIG response code to APPEND? Something along the=20
line
of:

C: t1 LIST "" "%"
S: * LIST (\Marked \HasNoChildren) "/" Inbox
S: * LIST (\HasNoChildren) "/" ToDo
S: * LIST (\HasChildren) "/" Projects
S: * LIST (\Sent \HasNoChildren) "/" SentMail
S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=3D257890) "/"
MyDrafts
S: * LIST (\Trash \HasNoChildren) "/" Trash
</pre>
            </blockquote>
            <pre wrap=3D"">All mailbox attributes are typically checked for =
equality, so this=20
this a departure from this principle. (I know we started to violate=20
this rule in CAPABILITY response) So personally, I prefer if we add=20
a new STATUS item for APPEND limit.
Then we can use STATUS-in-LIST bridge
(<a class=3D"moz-txt-link-freetext" href=3D"https://tools.ietf.org/html/rfc5=
819">https://tools.ietf.org/html/rfc5819</a>) to return this information.

As clients that want to obey APPENDLIMIT would need to be modified=20
anyway, they might as well be modified to support RFC 5819 syntax.
</pre>
          </blockquote>
          <pre wrap=3D"">
And same goes for the server, because the client will want to query
*every* server that supports APPENDLIMIT just in case it has=20
per-mailbox limits. Unless I'm way off base here, a server with a=20
simple mailbox-wide APPEND limit would need to implement APPENDLIMIT
*plus* 5819 and 5258 to support the client asking about per-mailbox=20
limits -- unless we have the client assume that lack of support for
5819/5258 implies that the server has no per-mailbox limits. Seems=20
pretty involved.
</pre>
        </blockquote>
        <pre wrap=3D"">Actually, I was thinking of something simpler, which =
is syntactically
compatible:

C: A01 LIST "" % RETURN (STATUS (APPENDLIMIT))
S: * LIST () "."  "INBOX"
S: * STATUS "INBOX" (APPENDLIMIT 1024000)

So basically server should recognize an extra "RETURN (STATUS=20
(APPENDLIMIT))" at the end of a list command and emit an extra STATUS=20
response for each matching mailbox. Support for RFC 5819 and RFC 5258=20
is optional.
</pre>
      </blockquote>
      <pre wrap=3D"">
That certainly simplifies things. Sounds good.

</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">

My reason for recommending this (other than "compatibility with RFC
5819/5258 is a good thing") is that if the limit is per mailbox, it=20
might be stored with mailbox information and thus might be relatively=20
expensive to retrieve. So a compliant server shouldn't try to retrieve=20
it unless a client asks for this information. So basically we need a=20
signalling mechanism for requesting this information.
</pre>
      </blockquote>
      <pre wrap=3D"">
Makes complete sense.

</pre>
      <blockquote type=3D"cite">
        <blockquote type=3D"cite">
          <blockquote type=3D"cite">
            <pre wrap=3D"">But otherwise I am Ok with being able to return t=
his information in=20
LIST.
</pre>
          </blockquote>
        </blockquote>
        <pre wrap=3D"">
</pre>
        <br>
        <fieldset class=3D"mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap=3D"">_______________________________________________
imapext mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:imapext@ietf.org">imape=
xt@ietf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/list=
info/imapext">https://www.ietf.org/mailman/listinfo/imapext</a>
</pre>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>

--------------070907070609010700000204--


From nobody Thu Dec 18 09:04:18 2014
Return-Path: <alexey.melnikov@isode.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 2CA7A1A8BB0 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 09:04:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 QnPN7eIOoet4 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 09:04:15 -0800 (PST)
Received: from statler.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id E00711A8ABA for <imapext@ietf.org>; Thu, 18 Dec 2014 09:03:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418922227; d=isode.com; s=selector; i=@isode.com; bh=7N7Qlhq0oIBVg+S2RYOS8+Gb5MgJkmsUbKshkPoa9CQ=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=AQdoBklge2jNgdLSF1kMFVKGWaeXiP6NuAnsv2aLuYJInhkhBfzhgQhZTl9n1ZrlVCz+a8 fXdfWbTqaxR58kKvSNg/MAGxTG1Eb6hX9Ad8lWVDkL3hfidNfO4Lv9adAdD7zIgFLWlJJ+ D0KQBHUQcWbdADsxL1ZaibD4EaIbagk=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <VJMI8gBz6TH9@statler.isode.com>; Thu, 18 Dec 2014 17:03:46 +0000
Message-ID: <549308DC.8020106@isode.com>
Date: Thu, 18 Dec 2014 17:03:24 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: Stuart Brandt <stujenerin@aol.com>, Jayantheesh S B <j.sb@sta.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <1414826667.1966384.185790009.6548B0D1@webmail.messagingengine.com> <9EB51A28-A50B-4494-A895-BF2E2C71C46B@isode.com> <20141102184949.Horde.qakr4M6-mMtk2LS-NnDAmw2@bigworm.curecanti.org> <545CACEA.5050609@isode.com> <02454F842DD7B449B96715A2AD90C0361A26EC1E@exMB5.telecom.sna.samsung.com> <20141111165755.Horde.dr_GjeX63GcdKoHxNf7jpQ1@bigworm.curecanti.org> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com>
In-Reply-To: <5487A0EC.4070603@aol.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/knmA7zPam7P0kgrM_l01LRRpVhk
Cc: "'imapext@ietf.org'" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 18 Dec 2014 17:04:17 -0000

On 10/12/2014 01:25, Stuart Brandt wrote:
> If I'm understanding the proposal correctly, a server that has already 
> implemented CATENATE and now implements APPENDLIMIT is left in an 
> ambiguous state whenever the limit is exceeded. If it returns 
> [TOOBIG], then it's not compliant with the APPENDLIMIT recommendation. 
> If it returns [APPENDLIMIT x] then it's returning an unexpected 
> response to clients that have yet to implement APPENDLIMIT, thereby 
> "breaking" existing functionality.
Clients are supposed to ignore response codes they don't understand. I 
think this general rule from RFC 3501 works in practice.

As far as the APPENDLIMIT draft is concerned, I am wondering if it 
should mention CATENATE explicitly?
> On 12/9/14 5:16 PM, Jayantheesh S B wrote:
>> Hi All,
>>
>> Thanks for your response.
>>
>> New response code APPENDLIMIT will be returned as part of SELECT 
>> response to convey per mailbox limit
>>   and APPEND command response, if the APPENTLIMIT size is exceeded.
>>
>> C: t2 SELECT INBOX
>> S: * 172 EXISTS
>> S: * OK [APPENDLIMIT 257890] Maximum upload limit
>> S: [...]
>> S: t2 OK [READ-WRITE] SELECT completed
>>
>> C: t1 APPEND "Draft" (\SEEN \DRAFT) {98994952}
>> S: t1 NO [APPENDLIMIT 257890] Exceeds the maximum allowed size
>>
>> Whereas TOOBIG response, does not covey the size restriction applied 
>> by the server.
>>
>>   resp-text-code =/ toobig-response-code / badurl-response-code
>>   toobig-response-code = "TOOBIG"
>>
>> We feel APPENDLIMIT response can convey per mailbox size restriction 
>> and it can overcome the limitation of TOOBIG response.
>>
>> Please share your thoughts.
>>
>> Regards,
>> Jay


From nobody Thu Dec 18 09:20:34 2014
Return-Path: <nicolson@google.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 9CE971A8AD9 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 09:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level: 
X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 TsFzYnOV_lm6 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 09:20:29 -0800 (PST)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6DD71A8F49 for <imapext@ietf.org>; Thu, 18 Dec 2014 09:20:28 -0800 (PST)
Received: by mail-ie0-f170.google.com with SMTP id rd18so1556805iec.1 for <imapext@ietf.org>; Thu, 18 Dec 2014 09:20:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=2YJHg2j38G48BD1XxARwheDaXHaWSlEmRfM7pCxdtKw=; b=BOrEYAZcuexmXpDM5YkUQwwcITJD5WL0ZEzaZtLZptmEEaOSxaZ41ANgstkps0IOk9 9n8vfHCrcO8WPsh3gBtrtIS7hmVlUaV4LQRXepIPKGsjL/in7lB2v722cvYJB+jmh/D9 YjjTJzfqiOP+hf5BkdDRL0lNhle8hmHOBMNnyFbgrBfnoGnGXiujARRt02TjaE19eP41 6m0U0fvDEBIWkK0tFtU+LYxNO3ArpRG1GFQyQJftaveEvOiz4Cctm9RS5brUlWNcIZ6G V0Bf0D989n0zydXseNyQfXe8BvXvn9ORYKEF/34j9yTQyU4R6WjPLCd16Bh8xmEiIA/t wwYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=2YJHg2j38G48BD1XxARwheDaXHaWSlEmRfM7pCxdtKw=; b=gEEFfFzTatX26SQgB6NJfNEhgasOdgAhwZqC+q2entPowm1GbUr2CmCGqeriWJi1Ld BdA5N3ifLGSNpzPZRoguJVBes/9A70pH4Pp8ff9SEWaq4k8NfRceZtBgIi3t6DnNNt+X d0xLbCN3DlVj56IJgIRhaLEF5gwmuF3AnhxcvEF6JpJFE/Wnt6Hqfday2lUWhgr4qc7p fgmtReSwo8WtFRtJz5mD05VhEgvmCVVpY/Vg2M+ctHzd2AUnT/C7/YxtR37d2ZLaC8MQ WpT8nS1He+4Ixy2fZntp7UclQUKMS5gCHF05sdQutaXSb11ZUXxO/gtWqP8Q9s5b3b6x lC5Q==
X-Gm-Message-State: ALoCoQkZb3EdE/F/Ko0W0rFewroQIywuaYachGDSHEkqFBz3eOWwcynsfCmbSVUfrJr762pn+4WT
X-Received: by 10.107.3.37 with SMTP id 37mr2973860iod.82.1418923227811; Thu, 18 Dec 2014 09:20:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.168.134 with HTTP; Thu, 18 Dec 2014 09:19:57 -0800 (PST)
In-Reply-To: <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com>
From: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>
Date: Thu, 18 Dec 2014 09:19:57 -0800
Message-ID: <CACU8CfTfyTjdpA0bH5KU5=d27w0fayBVyinfa+7O+y_2M5yMKQ@mail.gmail.com>
To: Jayantheesh S B <j.sb@sta.samsung.com>
Content-Type: multipart/alternative; boundary=001a113fb894f556e4050a80cebf
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/IgfE4FytAvpDJ1xrhn0r0Yg0aw0
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, "imapext@ietf.org" <imapext@ietf.org>, Stuart Brandt <stujenerin@aol.com>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 18 Dec 2014 17:20:31 -0000

--001a113fb894f556e4050a80cebf
Content-Type: text/plain; charset=UTF-8

For servers that have a single APPENDLIMIT across all mailboxes, it's
easier (and saves bandwidth) to not have to specify any per-mailbox
APPENDLIMIT in the SELECT response. In this case the APPENDLIMIT specified
in the CAPABILITY should hold across all mailboxes. I think this is the
intent, but the only direct statement about this I see in the document is
for the APPENDLIMIT response code to SELECT in section 3.1: "If this is
missing, the client can always honour the value received as part of
CAPABILITY response." I'd like this to be a little more firm, so that the
server can choose to omit the per-mailbox APPENDLIMIT and know that the
client will respect the common limit.

Perhaps you could state this directly in the introduction to section 3,
something like, "If no per-mailbox APPENDLIMIT is specified for a folder,
but the server did specify a common APPENDLIMIT in the CAPABILITY response,
then the common APPENDLIMIT applies to that folder."

On Tue, Dec 16, 2014 at 3:21 PM, Jayantheesh S B <j.sb@sta.samsung.com>
wrote:
>
> Hi All,
>
> Please find the updated version of the draft attached.
>
> Changes in this version:
>
> 1.  APPEND command response handling changes (Reused TOOBIG response-text
> from rfc4469 )
> 2.  Retrieval of per mailbox limit in  authenticated state by using LIST
> and STATUS command (Reference rfc5819)
>
> Kindly share your comments.
>
> Regards,
> Jay
>
> -----Original Message-----
> From: Stuart Brandt [mailto:stujenerin@aol.com]
> Sent: Monday, December 15, 2014 10:07 AM
> To: Alexey Melnikov; Jayantheesh S B
> Cc: 'imapext@ietf.org'
> Subject: Re: [imapext] [IMAP] APPEND Command Usage
>
> Inline comments
>
> On 12/15/14 6:52 AM, Alexey Melnikov wrote:
> > Hi Stuart,
> >
> > On 12/12/2014 15:40, Stuart Brandt wrote:
> >> Inline comments
> >>
> >> On 12/12/14 5:24 AM, Alexey Melnikov wrote:
> >>> Hi Stuart,
> >>>
> >>> On 10/12/2014 19:58, Stuart Brandt wrote:
> >>>> From a server perspective, the proposal solves my concern. From a
> >>>> client perspective, I'm not sure whether the addition of [SP
> >>>> nz-number] to the TOOBIG response would present problems for
> >>>> clients that only implement CATENATE and not APPENDLIMIT. I too
> >>>> would like to see others chime in on that part.
> >>>>
> >>>> From what I see, most IMAP sessions either precede an APPEND with a
> >>>> SELECT/EXAMINE or LIST...likely to confirm the existence of the
> >>>> target mailbox into which they're going to append.  The proposal
> >>>> already covers SELECT/EXAMINE, so would it be reasonable to add the
> >>>> APPENDLIMIT=x as an attribute to the LIST response data in order to
> >>>> reflect any per-mailbox limit and avoid trying to convey the limit
> >>>> as part of the TOOBIG response code to APPEND? Something along the
> >>>> line
> >>>> of:
> >>>>
> >>>> C: t1 LIST "" "%"
> >>>> S: * LIST (\Marked \HasNoChildren) "/" Inbox
> >>>> S: * LIST (\HasNoChildren) "/" ToDo
> >>>> S: * LIST (\HasChildren) "/" Projects
> >>>> S: * LIST (\Sent \HasNoChildren) "/" SentMail
> >>>> S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=257890) "/"
> >>>> MyDrafts
> >>>> S: * LIST (\Trash \HasNoChildren) "/" Trash
> >>> All mailbox attributes are typically checked for equality, so this
> >>> this a departure from this principle. (I know we started to violate
> >>> this rule in CAPABILITY response) So personally, I prefer if we add
> >>> a new STATUS item for APPEND limit.
> >>> Then we can use STATUS-in-LIST bridge
> >>> (https://tools.ietf.org/html/rfc5819) to return this information.
> >>>
> >>> As clients that want to obey APPENDLIMIT would need to be modified
> >>> anyway, they might as well be modified to support RFC 5819 syntax.
> >>
> >> And same goes for the server, because the client will want to query
> >> *every* server that supports APPENDLIMIT just in case it has
> >> per-mailbox limits. Unless I'm way off base here, a server with a
> >> simple mailbox-wide APPEND limit would need to implement APPENDLIMIT
> >> *plus* 5819 and 5258 to support the client asking about per-mailbox
> >> limits -- unless we have the client assume that lack of support for
> >> 5819/5258 implies that the server has no per-mailbox limits. Seems
> >> pretty involved.
> > Actually, I was thinking of something simpler, which is syntactically
> > compatible:
> >
> > C: A01 LIST "" % RETURN (STATUS (APPENDLIMIT))
> > S: * LIST () "."  "INBOX"
> > S: * STATUS "INBOX" (APPENDLIMIT 1024000)
> >
> > So basically server should recognize an extra "RETURN (STATUS
> > (APPENDLIMIT))" at the end of a list command and emit an extra STATUS
> > response for each matching mailbox. Support for RFC 5819 and RFC 5258
> > is optional.
>
> That certainly simplifies things. Sounds good.
>
> >
> >
> > My reason for recommending this (other than "compatibility with RFC
> > 5819/5258 is a good thing") is that if the limit is per mailbox, it
> > might be stored with mailbox information and thus might be relatively
> > expensive to retrieve. So a compliant server shouldn't try to retrieve
> > it unless a client asks for this information. So basically we need a
> > signalling mechanism for requesting this information.
>
> Makes complete sense.
>
> >>> But otherwise I am Ok with being able to return this information in
> >>> LIST.
> >
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext
>
>

--001a113fb894f556e4050a80cebf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">For servers that have a single APPENDLIMIT across all mail=
boxes, it&#39;s easier (and saves bandwidth) to not have to specify any per=
-mailbox APPENDLIMIT in the SELECT response. In this case the APPENDLIMIT s=
pecified in the CAPABILITY should hold across all mailboxes. I think this i=
s the intent, but the only direct statement about this I see in the documen=
t is for the APPENDLIMIT response code to SELECT in section 3.1: &quot;If t=
his is missing, the client can always honour the value received as part of =
CAPABILITY response.&quot; I&#39;d like this to be a little more firm, so t=
hat the server can choose to omit the per-mailbox APPENDLIMIT and know that=
 the client will respect the common limit.<div><br></div><div>Perhaps you c=
ould state this directly in the introduction to section 3, something like, =
&quot;If no per-mailbox APPENDLIMIT is specified for a folder, but the serv=
er did specify a common APPENDLIMIT in the CAPABILITY response, then the co=
mmon APPENDLIMIT applies to that folder.&quot;</div></div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Tue, Dec 16, 2014 at 3:21 PM, J=
ayantheesh S B <span dir=3D"ltr">&lt;<a href=3D"mailto:j.sb@sta.samsung.com=
" target=3D"_blank">j.sb@sta.samsung.com</a>&gt;</span> wrote:<blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">Hi All,<br>
<br>
Please find the updated version of the draft attached.<br>
<br>
Changes in this version:<br>
<br>
1.=C2=A0 APPEND command response handling changes (Reused TOOBIG response-t=
ext from rfc4469 )<br>
2.=C2=A0 Retrieval of per mailbox limit in=C2=A0 authenticated state by usi=
ng LIST and STATUS command (Reference rfc5819)<br>
<br>
Kindly share your comments.<br>
<span class=3D"im HOEnZb"><br>
Regards,<br>
Jay<br>
<br>
-----Original Message-----<br>
From: Stuart Brandt [mailto:<a href=3D"mailto:stujenerin@aol.com">stujeneri=
n@aol.com</a>]<br>
</span><span class=3D"im HOEnZb">Sent: Monday, December 15, 2014 10:07 AM<b=
r>
To: Alexey Melnikov; Jayantheesh S B<br>
Cc: &#39;<a href=3D"mailto:imapext@ietf.org">imapext@ietf.org</a>&#39;<br>
Subject: Re: [imapext] [IMAP] APPEND Command Usage<br>
<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">Inline comments<br>
<br>
On 12/15/14 6:52 AM, Alexey Melnikov wrote:<br>
&gt; Hi Stuart,<br>
&gt;<br>
&gt; On 12/12/2014 15:40, Stuart Brandt wrote:<br>
&gt;&gt; Inline comments<br>
&gt;&gt;<br>
&gt;&gt; On 12/12/14 5:24 AM, Alexey Melnikov wrote:<br>
&gt;&gt;&gt; Hi Stuart,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On 10/12/2014 19:58, Stuart Brandt wrote:<br>
&gt;&gt;&gt;&gt; From a server perspective, the proposal solves my concern.=
 From a<br>
&gt;&gt;&gt;&gt; client perspective, I&#39;m not sure whether the addition =
of [SP<br>
&gt;&gt;&gt;&gt; nz-number] to the TOOBIG response would present problems f=
or<br>
&gt;&gt;&gt;&gt; clients that only implement CATENATE and not APPENDLIMIT. =
I too<br>
&gt;&gt;&gt;&gt; would like to see others chime in on that part.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; From what I see, most IMAP sessions either precede an APPE=
ND with a<br>
&gt;&gt;&gt;&gt; SELECT/EXAMINE or LIST...likely to confirm the existence o=
f the<br>
&gt;&gt;&gt;&gt; target mailbox into which they&#39;re going to append.=C2=
=A0 The proposal<br>
&gt;&gt;&gt;&gt; already covers SELECT/EXAMINE, so would it be reasonable t=
o add the<br>
&gt;&gt;&gt;&gt; APPENDLIMIT=3Dx as an attribute to the LIST response data =
in order to<br>
&gt;&gt;&gt;&gt; reflect any per-mailbox limit and avoid trying to convey t=
he limit<br>
&gt;&gt;&gt;&gt; as part of the TOOBIG response code to APPEND? Something a=
long the<br>
&gt;&gt;&gt;&gt; line<br>
&gt;&gt;&gt;&gt; of:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; C: t1 LIST &quot;&quot; &quot;%&quot;<br>
&gt;&gt;&gt;&gt; S: * LIST (\Marked \HasNoChildren) &quot;/&quot; Inbox<br>
&gt;&gt;&gt;&gt; S: * LIST (\HasNoChildren) &quot;/&quot; ToDo<br>
&gt;&gt;&gt;&gt; S: * LIST (\HasChildren) &quot;/&quot; Projects<br>
&gt;&gt;&gt;&gt; S: * LIST (\Sent \HasNoChildren) &quot;/&quot; SentMail<br=
>
&gt;&gt;&gt;&gt; S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=3D2=
57890) &quot;/&quot;<br>
&gt;&gt;&gt;&gt; MyDrafts<br>
&gt;&gt;&gt;&gt; S: * LIST (\Trash \HasNoChildren) &quot;/&quot; Trash<br>
&gt;&gt;&gt; All mailbox attributes are typically checked for equality, so =
this<br>
&gt;&gt;&gt; this a departure from this principle. (I know we started to vi=
olate<br>
&gt;&gt;&gt; this rule in CAPABILITY response) So personally, I prefer if w=
e add<br>
&gt;&gt;&gt; a new STATUS item for APPEND limit.<br>
&gt;&gt;&gt; Then we can use STATUS-in-LIST bridge<br>
&gt;&gt;&gt; (<a href=3D"https://tools.ietf.org/html/rfc5819" target=3D"_bl=
ank">https://tools.ietf.org/html/rfc5819</a>) to return this information.<b=
r>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; As clients that want to obey APPENDLIMIT would need to be modi=
fied<br>
&gt;&gt;&gt; anyway, they might as well be modified to support RFC 5819 syn=
tax.<br>
&gt;&gt;<br>
&gt;&gt; And same goes for the server, because the client will want to quer=
y<br>
&gt;&gt; *every* server that supports APPENDLIMIT just in case it has<br>
&gt;&gt; per-mailbox limits. Unless I&#39;m way off base here, a server wit=
h a<br>
&gt;&gt; simple mailbox-wide APPEND limit would need to implement APPENDLIM=
IT<br>
&gt;&gt; *plus* 5819 and 5258 to support the client asking about per-mailbo=
x<br>
&gt;&gt; limits -- unless we have the client assume that lack of support fo=
r<br>
&gt;&gt; 5819/5258 implies that the server has no per-mailbox limits. Seems=
<br>
&gt;&gt; pretty involved.<br>
&gt; Actually, I was thinking of something simpler, which is syntactically<=
br>
&gt; compatible:<br>
&gt;<br>
&gt; C: A01 LIST &quot;&quot; % RETURN (STATUS (APPENDLIMIT))<br>
&gt; S: * LIST () &quot;.&quot;=C2=A0 &quot;INBOX&quot;<br>
&gt; S: * STATUS &quot;INBOX&quot; (APPENDLIMIT 1024000)<br>
&gt;<br>
&gt; So basically server should recognize an extra &quot;RETURN (STATUS<br>
&gt; (APPENDLIMIT))&quot; at the end of a list command and emit an extra ST=
ATUS<br>
&gt; response for each matching mailbox. Support for RFC 5819 and RFC 5258<=
br>
&gt; is optional.<br>
<br>
That certainly simplifies things. Sounds good.<br>
<br>
&gt;<br>
&gt;<br>
&gt; My reason for recommending this (other than &quot;compatibility with R=
FC<br>
&gt; 5819/5258 is a good thing&quot;) is that if the limit is per mailbox, =
it<br>
&gt; might be stored with mailbox information and thus might be relatively<=
br>
&gt; expensive to retrieve. So a compliant server shouldn&#39;t try to retr=
ieve<br>
&gt; it unless a client asks for this information. So basically we need a<b=
r>
&gt; signalling mechanism for requesting this information.<br>
<br>
Makes complete sense.<br>
<br>
&gt;&gt;&gt; But otherwise I am Ok with being able to return this informati=
on in<br>
&gt;&gt;&gt; LIST.<br>
&gt;<br>
</div></div><br>_______________________________________________<br>
imapext mailing list<br>
<a href=3D"mailto:imapext@ietf.org">imapext@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/imapext" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/imapext</a><br>
<br></blockquote></div></div>

--001a113fb894f556e4050a80cebf--


From nobody Thu Dec 18 09:25:58 2014
Return-Path: <alexey.melnikov@isode.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 71A781A911B for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 09:25:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.71
X-Spam-Level: 
X-Spam-Status: No, score=-1.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 SWJaCK83_Z36 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 09:25:53 -0800 (PST)
Received: from statler.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE6D1A90EE for <imapext@ietf.org>; Thu, 18 Dec 2014 09:25:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418923543; d=isode.com; s=selector; i=@isode.com; bh=963OJdqK4IoP7ylFxnD2XCbCIMZN58jzf/lp7f+WKl8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=KXlemGvIUH0HlV5+MzGPLq4Pbvv1Qzht5LWCmAGeCpiqzb4h6/9j527adEIbO/8IB23VQx MolIYQGKMqncU6LDgVvKDTC0xEoxBFPHpzewLQ/KVP2mKAw+lRbVrxXaCsYdtx8zDDQz8k pPgnrSslQtsjWDSeU8cqKJgsHQ+h/nc=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <VJMOFgBz6bcg@statler.isode.com>; Thu, 18 Dec 2014 17:25:43 +0000
Message-ID: <54930E00.60709@isode.com>
Date: Thu, 18 Dec 2014 17:25:20 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
To: =?UTF-8?B?IkphbWllIE5pY29sc29uICjlgKrlv5fmmI4pIg==?= <nicolson@google.com>,  Jayantheesh S B <j.sb@sta.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com> <CACU8CfTfyTjdpA0bH5KU5=d27w0fayBVyinfa+7O+y_2M5yMKQ@mail.gmail.com>
In-Reply-To: <CACU8CfTfyTjdpA0bH5KU5=d27w0fayBVyinfa+7O+y_2M5yMKQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-transfer-encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/akEemy57W2kQOoZhAFI8bctqZYw
Cc: Stuart Brandt <stujenerin@aol.com>, "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 18 Dec 2014 17:25:54 -0000

On 18/12/2014 17:19, Jamie Nicolson (=E5=80=AA=E5=BF=97=E6=98=8E) wrote:
> For servers that have a single APPENDLIMIT across all mailboxes, it's=20
> easier (and saves bandwidth) to not have to specify any per-mailbox=20
> APPENDLIMIT in the SELECT response. In this case the APPENDLIMIT=20
> specified in the CAPABILITY should hold across all mailboxes. I think=20
> this is the intent, but the only direct statement about this I see in=20
> the document is for the APPENDLIMIT response code to SELECT in section=20
> 3.1: "If this is missing, the client can always honour the value=20
> received as part of CAPABILITY response." I'd like this to be a little=20
> more firm, so that the server can choose to omit the per-mailbox=20
> APPENDLIMIT and know that the client will respect the common limit.
>
> Perhaps you could state this directly in the introduction to section=20
> 3, something like, "If no per-mailbox APPENDLIMIT is specified for a=20
> folder, but the server did specify a common APPENDLIMIT in the=20
> CAPABILITY response, then the common APPENDLIMIT applies to that folder."
+1.


From nobody Thu Dec 18 09:31:36 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 6FF3A1A90EB for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 09:31:34 -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 TFWbbfO8ns-9 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 09:31:33 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DA221A90DE for <imapext@ietf.org>; Thu, 18 Dec 2014 09:31:33 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 8D002FA0082; Thu, 18 Dec 2014 17:31:31 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1418923890-6028-6027/12/1; Thu, 18 Dec 2014 17:31:30 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Jamie Nicolson <nicolson@google.com>, Jayantheesh S B <j.sb@sta.samsung.com>, Stuart Brandt <stujenerin@aol.com>, imapext@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>
Message-Id: <635039a0c39f9dce2f1befe3df5c0cc5d88fd214a412d74f79eef63c7ed45dbd.sha-256@android.antelope.email>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com> <CACU8CfTfyTjdpA0bH5KU5=d27w0fayBVyinfa+7O+y_2M5yMKQ@mail.gmail.com> <54930E00.60709@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Date: Thu, 18 Dec 2014 17:31:30 +0000
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/IY7FsFgoawXJ_B-Erped3QlBF9g
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 18 Dec 2014 17:31:34 -0000

5530's codes are sent by many, many deployed servers. If a  significant =
number of clients have a  problem with unknown codes, we would have =
heard about it by now.

Arnt


From nobody Thu Dec 18 09:33:24 2014
Return-Path: <prvs=942935a7ed=j.sb@sta.samsung.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 ED7491A9077 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 09:33:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.897
X-Spam-Level: 
X-Spam-Status: No, score=0.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.793, 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 aUWlcwzZvLZX for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 09:33:19 -0800 (PST)
Received: from smg1.telecom.sna.samsung.com (unknown [63.166.115.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3CF61A9127 for <imapext@ietf.org>; Thu, 18 Dec 2014 09:33:13 -0800 (PST)
X-AuditID: 41a9fa1f-f79486d0000004ef-2f-54930fcf57b3
Received: from exHub2.telecom.sna.samsung.com (Unknown_Domain [105.52.12.243]) by smg1.telecom.sna.samsung.com (SMGOUT STA) with SMTP id 73.F9.01263.FCF03945; Thu, 18 Dec 2014 11:33:03 -0600 (CST)
Received: from EXMB5.telecom.sna.samsung.com ([fe80::5f4:56d9:ea68:f480]) by exHub2.telecom.sna.samsung.com ([fe80::348a:877:72e7:524b%22]) with mapi id 14.03.0146.000; Thu, 18 Dec 2014 11:33:12 -0600
From: Jayantheesh S B <j.sb@sta.samsung.com>
To: 'Alexey Melnikov' <alexey.melnikov@isode.com>, 'Stuart Brandt' <stujenerin@aol.com>, "'imapext@ietf.org'" <imapext@ietf.org>
Thread-Topic: [imapext] [IMAP] APPEND Command Usage
Thread-Index: Ac/zikIaeRUU045cSKC+QFTd6ghr0ZxK6Vlg48oYyFOAAJQ50oAAgMAAgAB8E7CAKoibP4ABNvGtgALo/oCAAFgrgIAEd16AgAA2ZQCABCguxv//rSxw
Date: Thu, 18 Dec 2014 17:33:11 +0000
Message-ID: <02454F842DD7B449B96715A2AD90C0363E99C894@exMB5.telecom.sna.samsung.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com> <5492C9DE.6070505@isode.com>
In-Reply-To: <5492C9DE.6070505@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [105.52.12.197]
Content-Type: multipart/alternative; boundary="_000_02454F842DD7B449B96715A2AD90C0363E99C894exMB5telecomsna_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsWSacLzWfc8/+QQg28XhCxmrC6yeDyLy6Lr ZbgDs8f93SvZPZYs+cnkcarZMIA5itsmKbGkLDgzPU/fLoE7Y9eNd2wFt1YxVnStWs/WwHhl ImMXIyeHhICJxI+zN1ghbDGJC/fWs3UxcnEICRxjlPjXspwZwjnDKLH+Ujd7FyM7B5uAjsST YJCwiEATo8SDlX9YQJqFBYwkNj/fA1TPAZQwlvh/xhKu5tKDNrAaFgFViT9/VjKB1PAKhEic +qwGMf4Bh8SvaZOZQGo4BTQlet7/ZwexGYEO+n5qDVicWUBc4taT+UwQhwpILNlznhnCFpV4 +fgf1AOKEnN/3WSGqM+X+HX4Olg9r4CgxMmZT1gmMIrMQjJqFpKyWUjKFjAyr2KUKc5NN9Qr Sc1JTc7P1SvOS9QrTswtLs1L1wPyNzEC48Jx5S/5HYzrttsfYmTi4DzEKMHBJSVSnJqXklqU WFqSEQ8K/fhiYPBLNTB2XrFg7S/j/nsi/a4b1+4+i3n3eXlf+bzzeLuFyydKqG7qKvPNKsU7 /+kGWV/OKHnc8+Drs96sskUaXRZxliL/XSQ+bnxSLF/H9t5Hu+rWWl4Byek5C9iFLTinzOP5 Eyi21K4nrujQrOTYqrM3jh3d9TDZUTya+3/w9lU2JrZS1geWGL+cPleJpTgj0VCLuag4EQD+ OOaMVgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/g4sAIA1cMmeq9fyDvTtFTKn8zEg
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 18 Dec 2014 17:33:22 -0000

--_000_02454F842DD7B449B96715A2AD90C0363E99C894exMB5telecomsna_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for your comments.

I will update the review comments in the next version.

Regards,
Jay
From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]
Sent: Thursday, December 18, 2014 7:35 AM
To: Jayantheesh S B; 'Stuart Brandt'; 'imapext@ietf.org'
Subject: Re: [imapext] [IMAP] APPEND Command Usage


On 16/12/2014 23:21, Jayantheesh S B wrote:

Hi All,



Please find the updated version of the draft attached.



Changes in this version:



1.  APPEND command response handling changes (Reused TOOBIG response-text f=
rom rfc4469 )

2.  Retrieval of per mailbox limit in  authenticated state by using LIST an=
d STATUS command (Reference rfc5819)
Comments on the new section 3.2 that you've added:

3.2 LIST response

IMAP client can get the mailbox specific APPENDLIMIT in authenticated
state, where it do not need to issue SELECT/EXAMINE command.  LIST
command in combination with STATUS command can be issued to get the per
mailbox specific APPENDLIMIT set by the server.  Refer rfc5819 for the
usage of LIST command in combination with STATUS command usage.
Nit: drop the last "usage".

I suggest you add the following sentence after the one quoted above:

Note that a server implementing this extension, is syntactically compatible=
 with RFC 5819, however support for RFC 5258 or RFC 5819 is not required wh=
en implementing this extension.


The following example demonstrates, its usage.

C: t1 LIST "" % RETURN (STATUS (APPENDLIMIT))
S: * LIST () "."  "INBOX"
S: * STATUS "INBOX" (APPENDLIMIT 257890)
S: t1 OK List completed.

New attribute APPNDLIMIT is added to get the limit set by the server for
Typo: APPENDLIMIT

this mailbox as part of STATUS command.  The STATUS response occurs as a
result of an STATUS command.  It returns the mailbox name that matches
the STATUS specification and the requested mailbox status information.
IMAP server should recognize an extra "RETURN (STATUS(APPENDLIMIT))" at
Please change "RETURN (STATUS(APPENDLIMIT))" to ""RETURN (STATUS (APPENDLIM=
IT))", as spaces are significant.

the end of a list command and emit an extra STATUS response for each
matching mailbox.  Refer to section [5] for the syntax.

How did you manage to generate [5]? This is going to be misinterpreted as a=
 document reference by various IETF tools. Just use "5".



It might also be worth pointing out that just calling STATUS with APPENDLIM=
IT is also acceptable. It would be worth adding an example of that as well.

Kindly share your comments.



Regards,

Jay



-----Original Message-----

From: Stuart Brandt [mailto:stujenerin@aol.com]

Sent: Monday, December 15, 2014 10:07 AM

To: Alexey Melnikov; Jayantheesh S B

Cc: 'imapext@ietf.org<mailto:imapext@ietf.org>'

Subject: Re: [imapext] [IMAP] APPEND Command Usage



Inline comments



On 12/15/14 6:52 AM, Alexey Melnikov wrote:

Hi Stuart,



On 12/12/2014 15:40, Stuart Brandt wrote:

Inline comments



On 12/12/14 5:24 AM, Alexey Melnikov wrote:

Hi Stuart,



On 10/12/2014 19:58, Stuart Brandt wrote:

>From a server perspective, the proposal solves my concern. From a

client perspective, I'm not sure whether the addition of [SP

nz-number] to the TOOBIG response would present problems for

clients that only implement CATENATE and not APPENDLIMIT. I too

would like to see others chime in on that part.



>From what I see, most IMAP sessions either precede an APPEND with a

SELECT/EXAMINE or LIST...likely to confirm the existence of the

target mailbox into which they're going to append.  The proposal

already covers SELECT/EXAMINE, so would it be reasonable to add the

APPENDLIMIT=3Dx as an attribute to the LIST response data in order to

reflect any per-mailbox limit and avoid trying to convey the limit

as part of the TOOBIG response code to APPEND? Something along the

line

of:



C: t1 LIST "" "%"

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

S: * LIST (\HasNoChildren) "/" ToDo

S: * LIST (\HasChildren) "/" Projects

S: * LIST (\Sent \HasNoChildren) "/" SentMail

S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=3D257890) "/"

MyDrafts

S: * LIST (\Trash \HasNoChildren) "/" Trash

All mailbox attributes are typically checked for equality, so this

this a departure from this principle. (I know we started to violate

this rule in CAPABILITY response) So personally, I prefer if we add

a new STATUS item for APPEND limit.

Then we can use STATUS-in-LIST bridge

(https://tools.ietf.org/html/rfc5819) to return this information.



As clients that want to obey APPENDLIMIT would need to be modified

anyway, they might as well be modified to support RFC 5819 syntax.



And same goes for the server, because the client will want to query

*every* server that supports APPENDLIMIT just in case it has

per-mailbox limits. Unless I'm way off base here, a server with a

simple mailbox-wide APPEND limit would need to implement APPENDLIMIT

*plus* 5819 and 5258 to support the client asking about per-mailbox

limits -- unless we have the client assume that lack of support for

5819/5258 implies that the server has no per-mailbox limits. Seems

pretty involved.

Actually, I was thinking of something simpler, which is syntactically

compatible:



C: A01 LIST "" % RETURN (STATUS (APPENDLIMIT))

S: * LIST () "."  "INBOX"

S: * STATUS "INBOX" (APPENDLIMIT 1024000)



So basically server should recognize an extra "RETURN (STATUS

(APPENDLIMIT))" at the end of a list command and emit an extra STATUS

response for each matching mailbox. Support for RFC 5819 and RFC 5258

is optional.



That certainly simplifies things. Sounds good.







My reason for recommending this (other than "compatibility with RFC

5819/5258 is a good thing") is that if the limit is per mailbox, it

might be stored with mailbox information and thus might be relatively

expensive to retrieve. So a compliant server shouldn't try to retrieve

it unless a client asks for this information. So basically we need a

signalling mechanism for requesting this information.



Makes complete sense.



But otherwise I am Ok with being able to return this information in

LIST.






_______________________________________________

imapext mailing list

imapext@ietf.org<mailto:imapext@ietf.org>

https://www.ietf.org/mailman/listinfo/imapext


--_000_02454F842DD7B449B96715A2AD90C0363E99C894exMB5telecomsna_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks for your comments.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I will update the review =
comments in the next version.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jay<o:p></o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> Alexey Melnikov [mailto:alexey.melnikov@isode.com=
]
<br>
<b>Sent:</b> Thursday, December 18, 2014 7:35 AM<br>
<b>To:</b> Jayantheesh S B; 'Stuart Brandt'; 'imapext@ietf.org'<br>
<b>Subject:</b> Re: [imapext] [IMAP] APPEND Command Usage<o:p></o:p></span>=
</p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On 16/12/2014 23:21, Jayantheesh S B wrote:<o:p></o:=
p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Hi All,<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Please find the updated version of the draft attached.<o:p></o:p></pre=
>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Changes in this version:<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>1.&nbsp; APPEND command response handling changes (Reused TOOBIG respo=
nse-text from rfc4469 )<o:p></o:p></pre>
<pre>2.&nbsp; Retrieval of per mailbox limit in&nbsp; authenticated state b=
y using LIST and STATUS command (Reference rfc5819)<o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal">Comments on the new section 3.2 that you've added:<b=
r>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">3.2 LIST response<br>
<br>
IMAP client can get the mailbox specific APPENDLIMIT in authenticated<br>
state, where it do not need to issue SELECT/EXAMINE command.&nbsp; LIST<br>
command in combination with STATUS command can be issued to get the per<br>
mailbox specific APPENDLIMIT set by the server.&nbsp; Refer rfc5819 for the=
<br>
usage of LIST command in combination with STATUS command usage.<o:p></o:p><=
/p>
<p class=3D"MsoNormal">Nit: drop the last &quot;usage&quot;.<br>
<br>
I suggest you add the following sentence after the one quoted above:<br>
<br>
Note that a server implementing this extension, is syntactically compatible=
 with RFC 5819, however support for RFC 5258 or RFC 5819 is not required wh=
en implementing this extension.<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal"><br>
The following example demonstrates, its usage.<br>
<br>
C: t1 LIST &quot;&quot; % RETURN (STATUS (APPENDLIMIT))<br>
S: * LIST () &quot;.&quot;&nbsp; &quot;INBOX&quot;<br>
S: * STATUS &quot;INBOX&quot; (APPENDLIMIT 257890)<br>
S: t1 OK List completed.<br>
<br>
New attribute APPNDLIMIT is added to get the limit set by the server for<o:=
p></o:p></p>
<p class=3D"MsoNormal">Typo: APPENDLIMIT<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">this mailbox as part of STATUS command.&nbsp; The ST=
ATUS response occurs as a<br>
result of an STATUS command.&nbsp; It returns the mailbox name that matches=
<br>
the STATUS specification and the requested mailbox status information.<br>
IMAP server should recognize an extra &quot;RETURN (STATUS(APPENDLIMIT))&qu=
ot; at<o:p></o:p></p>
<p class=3D"MsoNormal">Please change &quot;RETURN (STATUS(APPENDLIMIT))&quo=
t; to &quot;&quot;RETURN (STATUS (APPENDLIMIT))&quot;, as spaces are signif=
icant.<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">the end of a list command and emit an extra STATUS r=
esponse for each<br>
matching mailbox.&nbsp; Refer to section [5] for the syntax.<o:p></o:p></p>
<pre>How did you manage to generate [5]? This is going to be misinterpreted=
 as a document reference by various IETF tools. Just use &quot;5&quot;.<o:p=
></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>It might also be worth pointing out that just calling STATUS with APPE=
NDLIMIT is also acceptable. It would be worth adding an example of that as =
well. <o:p></o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Kindly share your comments. <o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Regards,<o:p></o:p></pre>
<pre>Jay<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: Stuart Brandt [<a href=3D"mailto:stujenerin@aol.com">mailto:stuj=
enerin@aol.com</a>] <o:p></o:p></pre>
<pre>Sent: Monday, December 15, 2014 10:07 AM<o:p></o:p></pre>
<pre>To: Alexey Melnikov; Jayantheesh S B<o:p></o:p></pre>
<pre>Cc: '<a href=3D"mailto:imapext@ietf.org">imapext@ietf.org</a>'<o:p></o=
:p></pre>
<pre>Subject: Re: [imapext] [IMAP] APPEND Command Usage<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Inline comments<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>On 12/15/14 6:52 AM, Alexey Melnikov wrote:<o:p></o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Hi Stuart,<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>On 12/12/2014 15:40, Stuart Brandt wrote:<o:p></o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Inline comments<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>On 12/12/14 5:24 AM, Alexey Melnikov wrote:<o:p></o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Hi Stuart,<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>On 10/12/2014 19:58, Stuart Brandt wrote:<o:p></o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>From a server perspective, the proposal solves my concern. From a <o:p=
></o:p></pre>
<pre>client perspective, I'm not sure whether the addition of [SP <o:p></o:=
p></pre>
<pre>nz-number] to the TOOBIG response would present problems for <o:p></o:=
p></pre>
<pre>clients that only implement CATENATE and not APPENDLIMIT. I too <o:p><=
/o:p></pre>
<pre>would like to see others chime in on that part.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>From what I see, most IMAP sessions either precede an APPEND with a <o=
:p></o:p></pre>
<pre>SELECT/EXAMINE or LIST...likely to confirm the existence of the <o:p><=
/o:p></pre>
<pre>target mailbox into which they're going to append.&nbsp; The proposal =
<o:p></o:p></pre>
<pre>already covers SELECT/EXAMINE, so would it be reasonable to add the <o=
:p></o:p></pre>
<pre>APPENDLIMIT=3Dx as an attribute to the LIST response data in order to =
<o:p></o:p></pre>
<pre>reflect any per-mailbox limit and avoid trying to convey the limit <o:=
p></o:p></pre>
<pre>as part of the TOOBIG response code to APPEND? Something along the <o:=
p></o:p></pre>
<pre>line<o:p></o:p></pre>
<pre>of:<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>C: t1 LIST &quot;&quot; &quot;%&quot;<o:p></o:p></pre>
<pre>S: * LIST (\Marked \HasNoChildren) &quot;/&quot; Inbox<o:p></o:p></pre=
>
<pre>S: * LIST (\HasNoChildren) &quot;/&quot; ToDo<o:p></o:p></pre>
<pre>S: * LIST (\HasChildren) &quot;/&quot; Projects<o:p></o:p></pre>
<pre>S: * LIST (\Sent \HasNoChildren) &quot;/&quot; SentMail<o:p></o:p></pr=
e>
<pre>S: * LIST (\Marked \Drafts \HasNoChildren \APPENDLIMIT=3D257890) &quot=
;/&quot;<o:p></o:p></pre>
<pre>MyDrafts<o:p></o:p></pre>
<pre>S: * LIST (\Trash \HasNoChildren) &quot;/&quot; Trash<o:p></o:p></pre>
</blockquote>
<pre>All mailbox attributes are typically checked for equality, so this <o:=
p></o:p></pre>
<pre>this a departure from this principle. (I know we started to violate <o=
:p></o:p></pre>
<pre>this rule in CAPABILITY response) So personally, I prefer if we add <o=
:p></o:p></pre>
<pre>a new STATUS item for APPEND limit.<o:p></o:p></pre>
<pre>Then we can use STATUS-in-LIST bridge<o:p></o:p></pre>
<pre>(<a href=3D"https://tools.ietf.org/html/rfc5819">https://tools.ietf.or=
g/html/rfc5819</a>) to return this information.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>As clients that want to obey APPENDLIMIT would need to be modified <o:=
p></o:p></pre>
<pre>anyway, they might as well be modified to support RFC 5819 syntax.<o:p=
></o:p></pre>
</blockquote>
<pre><o:p>&nbsp;</o:p></pre>
<pre>And same goes for the server, because the client will want to query<o:=
p></o:p></pre>
<pre>*every* server that supports APPENDLIMIT just in case it has <o:p></o:=
p></pre>
<pre>per-mailbox limits. Unless I'm way off base here, a server with a <o:p=
></o:p></pre>
<pre>simple mailbox-wide APPEND limit would need to implement APPENDLIMIT<o=
:p></o:p></pre>
<pre>*plus* 5819 and 5258 to support the client asking about per-mailbox <o=
:p></o:p></pre>
<pre>limits -- unless we have the client assume that lack of support for<o:=
p></o:p></pre>
<pre>5819/5258 implies that the server has no per-mailbox limits. Seems <o:=
p></o:p></pre>
<pre>pretty involved.<o:p></o:p></pre>
</blockquote>
<pre>Actually, I was thinking of something simpler, which is syntactically<=
o:p></o:p></pre>
<pre>compatible:<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>C: A01 LIST &quot;&quot; % RETURN (STATUS (APPENDLIMIT))<o:p></o:p></p=
re>
<pre>S: * LIST () &quot;.&quot;&nbsp; &quot;INBOX&quot;<o:p></o:p></pre>
<pre>S: * STATUS &quot;INBOX&quot; (APPENDLIMIT 1024000)<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>So basically server should recognize an extra &quot;RETURN (STATUS <o:=
p></o:p></pre>
<pre>(APPENDLIMIT))&quot; at the end of a list command and emit an extra ST=
ATUS <o:p></o:p></pre>
<pre>response for each matching mailbox. Support for RFC 5819 and RFC 5258 =
<o:p></o:p></pre>
<pre>is optional.<o:p></o:p></pre>
</blockquote>
<pre><o:p>&nbsp;</o:p></pre>
<pre>That certainly simplifies things. Sounds good.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>My reason for recommending this (other than &quot;compatibility with R=
FC<o:p></o:p></pre>
<pre>5819/5258 is a good thing&quot;) is that if the limit is per mailbox, =
it <o:p></o:p></pre>
<pre>might be stored with mailbox information and thus might be relatively =
<o:p></o:p></pre>
<pre>expensive to retrieve. So a compliant server shouldn't try to retrieve=
 <o:p></o:p></pre>
<pre>it unless a client asks for this information. So basically we need a <=
o:p></o:p></pre>
<pre>signalling mechanism for requesting this information.<o:p></o:p></pre>
</blockquote>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Makes complete sense.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>But otherwise I am Ok with being able to return this information in <o=
:p></o:p></pre>
<pre>LIST.<o:p></o:p></pre>
</blockquote>
</blockquote>
<pre><o:p>&nbsp;</o:p></pre>
<p class=3D"MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>imapext mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:imapext@ietf.org">imapext@ietf.org</a><o:p></o:p></p=
re>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/imapext">https://www.=
ietf.org/mailman/listinfo/imapext</a><o:p></o:p></pre>
</blockquote>
</blockquote>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_02454F842DD7B449B96715A2AD90C0363E99C894exMB5telecomsna_--


From nobody Thu Dec 18 11:23:22 2014
Return-Path: <slusarz@horde.org>
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 2B74A1A9308 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 11:23:20 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 m3b1DDuOV9UG for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 11:23:18 -0800 (PST)
Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:161]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA22C1A911A for <imapext@ietf.org>; Thu, 18 Dec 2014 11:23:18 -0800 (PST)
Received: from resomta-po-16v.sys.comcast.net ([96.114.154.240]) by resqmta-po-02v.sys.comcast.net with comcast id V7PJ1p0025BUCh4017PJLk; Thu, 18 Dec 2014 19:23:18 +0000
Received: from bigworm.curecanti.org ([67.176.83.228]) by resomta-po-16v.sys.comcast.net with comcast id V7PH1p0074vagWz017PHbH; Thu, 18 Dec 2014 19:23:18 +0000
Received: from bigworm.curecanti.org (localhost.localdomain [IPv6:::1]) (Authenticated sender: slusarz) by bigworm.curecanti.org (Postfix) with ESMTPSA id A7777680B2 for <imapext@ietf.org>; Thu, 18 Dec 2014 12:22:46 -0700 (MST)
Received: from dangerzone.curecanti.org (dangerzone.curecanti.org [172.18.5.4]) by bigworm.curecanti.org (Horde Framework) with HTTP; Thu, 18 Dec 2014 12:22:46 -0700
Date: Thu, 18 Dec 2014 12:22:46 -0700
Message-ID: <20141218122246.Horde.9kvC-_thX4wwso7qwAfvVw1@bigworm.curecanti.org>
From: Michael M Slusarz <slusarz@horde.org>
To: imapext@ietf.org
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com> <20141217050102.Horde.GWA4XtpoLlxANoaBg9l1cg1@bigworm.curecanti.org> <54917A9F.1030101@isode.com>
In-Reply-To: <54917A9F.1030101@isode.com>
User-Agent: Horde Application Framework 5
Accept-Language: en
X-Originating-IP: 172.18.5.4
X-Remote-Browser: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418930598; bh=RJNqCOU81C1gqv7rQ0VxKmDZkm9X712BOihfdgh4heY=; h=Received:Received:Received:Received:Date:Message-ID:From:To: Subject:Content-Type:MIME-Version; b=ktE1ckjQ4aPElX+X8IEaVVhnv1l4PIcdxWMIYH7bPDivPLZlIeVY+pLEflO83K99k rAE6Dw3Elwa0p3d4IxTkk4lhnF5aAmOR4dxWNa8VMRUsfcQ31ZTf9fbNKss2lbX7zZ s0EKcuhboQLxupKypP8E/3eUFSOWFnfgqpFq9d1wp6W2PEJ48nZ2KqyxVOPfBSWqHF 5ZD5TFLo9zRwShwmxHBFiY/3vseVQZv3TSxpma/kCvfnhlmyLp9BATOfeqRRHDmDj5 lnIL4ytwvEu6aTsCJpJ1AMvSTYPh4Aoc8ebu7BXU6WHvlCavXSxqENB0L2lUBgz5a2 3plWuJK6teLqQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/RGfRxbc0uJs1iOv5andOrh8hTxw
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 18 Dec 2014 19:23:20 -0000

Quoting Alexey Melnikov <alexey.melnikov@isode.com>:

> On 17/12/2014 12:01, Michael M Slusarz wrote:
>
>> - Section 2 says a "client SHALL not try to upload mail more than  
>> advertised limit in the APPEND command.".  I would think that  
>> should be MUST, not SHALL.  If a client understands APPENDLIMIT, it  
>> knows the maximum size the server would accept.  Sending data over  
>> this limit is explicitly ignoring process/resource limits  
>> advertised by the server.
> SHALL and MUST have the same meaning according to RFC 2119.

That is what I get for sending my message as I'm about to board a plane.

You are correct, although FWIW it's one man's opinion that MUST is  
clearer than SHALL for this kind of language.

>> - There's discussion of LIST + STATUS (RFC 5819).  But this is  
>> actually an addition to STATUS itself.  The spec should be written  
>> as extending STATUS, and then a discussion/example of how this can  
>> be used if 5819 is supported.  (If we want to force an APPENDLIMIT  
>> client/server to also be LIST-STATUS compliant for performance  
>> reasons, that's fine.  But seems to be a policy decision rather  
>> than a technical explanation.)
> This section is not quite right, but I need to rereview it in more details.

Looks like you covered this in your subsequent review.

In short, APPENDLIMIT status selector needs to be added to status-att,  
which is extending 3501.

 From an implementation point of view, the STATUS case makes more  
sense than the LIST-STATUS case anyway.  A client /could/ add the  
APPENDLIMIT status return when creating the folder tree, but that's  
probably just wasted bandwidth since generally a client is only going  
to be appending to a small number of those mailboxes (i.e. a sent-mail  
mailbox).

I would imagine the most common behavior is that a client would grab  
the append limit before it's first append, and it is less expensive to  
issue "STATUS mailbox (APPENDLIMIT)" than a LIST command with  
APPENDLIMIT return in that situation since the status info is all that  
is needed.

michael

___________________________________
Michael Slusarz [slusarz@horde.org]


From nobody Thu Dec 18 11:49:57 2014
Return-Path: <stujenerin@aol.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 2850F1A6F2C for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 11:49:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.51
X-Spam-Level: 
X-Spam-Status: No, score=-0.51 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 vBXKa2ePg4ov for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 11:49:54 -0800 (PST)
Received: from omr-m5.mx.aol.com (omr-m5.mx.aol.com [64.12.232.237]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D86D1A6F17 for <imapext@ietf.org>; Thu, 18 Dec 2014 11:49:54 -0800 (PST)
Received: from mtaout-aak01.mx.aol.com (mtaout-aak01.mx.aol.com [172.27.2.225]) by omr-m5.mx.aol.com (Outbound Mail Relay) with ESMTP id B67123800041D; Thu, 18 Dec 2014 14:49:53 -0500 (EST)
Received: from [10.172.0.123] (unknown [10.172.0.123]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-aak01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 663183800008E; Thu, 18 Dec 2014 14:49:53 -0500 (EST)
Message-ID: <54932FE0.3020506@aol.com>
Date: Thu, 18 Dec 2014 14:49:52 -0500
From: Stuart Brandt <stujenerin@aol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: imapext@ietf.org
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com> <20141217050102.Horde.GWA4XtpoLlxANoaBg9l1cg1@bigworm.curecanti.org> <54917A9F.1030101@isode.com> <20141218122246.Horde.9kvC-_thX4wwso7qwAfvVw1@bigworm.curecanti.org>
In-Reply-To: <20141218122246.Horde.9kvC-_thX4wwso7qwAfvVw1@bigworm.curecanti.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1418932193; bh=ZMAgeF203RDfpWil0C2r6Hlfh4EY/S0jkOW8X2NRD8E=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=EkF/AcXrAixQn340BmKgt/66kEBKxndnBRVl4LEIJ64JC69Oah/Nm6O21xmWXc/vJ +N+SupraMDv+LUTCPy2E3zxOnrr5ocXpcTF77pUKyUprbriZIeXWjW0a/+ECq0IVnY GYHvYUVzIvHy+y1HlwTuAwxE+syoI4F6QfGpWkts=
x-aol-sid: 3039ac1b02e154932fe16fd6
X-AOL-IP: 10.172.0.123
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/gQi37jsucjKJjw_HxknA2p9DT8U
Cc: slusarz@horde.org
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 18 Dec 2014 19:49:56 -0000

Inline

On 12/18/14 2:22 PM, Michael M Slusarz wrote:
> Quoting Alexey Melnikov <alexey.melnikov@isode.com>:
>
>> On 17/12/2014 12:01, Michael M Slusarz wrote:
>>
>>> - Section 2 says a "client SHALL not try to upload mail more than
>>> advertised limit in the APPEND command.".  I would think that should
>>> be MUST, not SHALL.  If a client understands APPENDLIMIT, it knows
>>> the maximum size the server would accept.  Sending data over this
>>> limit is explicitly ignoring process/resource limits advertised by
>>> the server.
>> SHALL and MUST have the same meaning according to RFC 2119.
>
> That is what I get for sending my message as I'm about to board a plane.
>
> You are correct, although FWIW it's one man's opinion that MUST is
> clearer than SHALL for this kind of language.
>
>>> - There's discussion of LIST + STATUS (RFC 5819).  But this is
>>> actually an addition to STATUS itself.  The spec should be written as
>>> extending STATUS, and then a discussion/example of how this can be
>>> used if 5819 is supported.  (If we want to force an APPENDLIMIT
>>> client/server to also be LIST-STATUS compliant for performance
>>> reasons, that's fine.  But seems to be a policy decision rather than
>>> a technical explanation.)
>> This section is not quite right, but I need to rereview it in more
>> details.
>
> Looks like you covered this in your subsequent review.
>
> In short, APPENDLIMIT status selector needs to be added to status-att,
> which is extending 3501.
>
>  From an implementation point of view, the STATUS case makes more sense
> than the LIST-STATUS case anyway.  A client /could/ add the APPENDLIMIT
> status return when creating the folder tree, but that's probably just
> wasted bandwidth since generally a client is only going to be appending
> to a small number of those mailboxes (i.e. a sent-mail mailbox).

Additional bandwidth would only be consumed in the case of per-mailbox 
limits, and only for those mailboxes that have a limit that is different 
than the global limit. I would imagine this condition will be pretty rare.

>
> I would imagine the most common behavior is that a client would grab the
> append limit before it's first append, and it is less expensive to issue
> "STATUS mailbox (APPENDLIMIT)" than a LIST command with APPENDLIMIT
> return in that situation since the status info is all that is needed.

My preference for the LIST-STATUS case over STATUS case comes from the 
following statement in section 6.3.10 of RFC3501:

       Unlike the LIST command, the STATUS command is not guaranteed to
       be fast in its response.  Under certain circumstances, it can be
       quite slow.  In some implementations, the server is obliged to
       open the mailbox read-only internally to obtain certain status
       information.  Also unlike the LIST command, the STATUS command
       does not accept wildcards.

This hints at LIST being both more responsive and more efficient on 
server resources.

>
> michael
>
> ___________________________________
> Michael Slusarz [slusarz@horde.org]
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext


From nobody Thu Dec 18 12:03:05 2014
Return-Path: <slusarz@horde.org>
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 60B801A802A for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 12:03:01 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 BvfJFOX9apab for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 12:03:00 -0800 (PST)
Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:161]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AA691AC3E4 for <imapext@ietf.org>; Thu, 18 Dec 2014 12:02:23 -0800 (PST)
Received: from resomta-po-05v.sys.comcast.net ([96.114.154.229]) by resqmta-po-02v.sys.comcast.net with comcast id V81s1p0054xDoy80182NEu; Thu, 18 Dec 2014 20:02:22 +0000
Received: from bigworm.curecanti.org ([67.176.83.228]) by resomta-po-05v.sys.comcast.net with comcast id V82N1p00B4vagWz0182Ntc; Thu, 18 Dec 2014 20:02:22 +0000
Received: from bigworm.curecanti.org (localhost.localdomain [IPv6:::1]) (Authenticated sender: slusarz) by bigworm.curecanti.org (Postfix) with ESMTPSA id BE133680B2 for <imapext@ietf.org>; Thu, 18 Dec 2014 13:02:21 -0700 (MST)
Received: from dangerzone.curecanti.org (dangerzone.curecanti.org [172.18.5.4]) by bigworm.curecanti.org (Horde Framework) with HTTP; Thu, 18 Dec 2014 13:02:21 -0700
Date: Thu, 18 Dec 2014 13:02:21 -0700
Message-ID: <20141218130221.Horde.j2jaNiGEXzaJKblLXJArwA4@bigworm.curecanti.org>
From: Michael M Slusarz <slusarz@horde.org>
To: imapext@ietf.org
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com> <20141217050102.Horde.GWA4XtpoLlxANoaBg9l1cg1@bigworm.curecanti.org> <54917A9F.1030101@isode.com> <20141218122246.Horde.9kvC-_thX4wwso7qwAfvVw1@bigworm.curecanti.org> <54932FE0.3020506@aol.com>
In-Reply-To: <54932FE0.3020506@aol.com>
User-Agent: Horde Application Framework 5
Accept-Language: en
X-Originating-IP: 172.18.5.4
X-Remote-Browser: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418932942; bh=Az7DMe3p76iytqQGnExFM01lW9b7jtURCYm83hn+lvU=; h=Received:Received:Received:Received:Date:Message-ID:From:To: Subject:Content-Type:MIME-Version; b=q2IHFuTwSjvEifPwdmr5rq1S5742jA+X8VraldRUs2/KhS8gTnXcnbk5Y8SxMcH0+ qHH7si4p/xYg12aT3ZxY+LzP26nwBMq0JRkYZJt8elLkRCn8AzZR5R1Hyk7FbYtJGa vaXdBC4l/LWXI2irSdx7ULh3SR+6/+vZnYw9EN7o0bsp25cfRV9T3QE7RB6OCbNVxG Tlv8xQ8ZpzJv67abBd8A7IXE2FZ/xNAo83/fUZwdsmZTui03FuHjvqdABDAXxdH2Cq G1xXjNzoNrO00cVaqKGmLrsr+3MG84adxWZ0Sn9cVspnZZSvexf5ogWHIJqrhY9XXw NxPB6Yrvd6njw==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/kbcE6qrFCtf16PXR067aMQkZrss
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 18 Dec 2014 20:03:02 -0000

Quoting Stuart Brandt <stujenerin@aol.com>:

> On 12/18/14 2:22 PM, Michael M Slusarz wrote:
>
>> I would imagine the most common behavior is that a client would grab the
>> append limit before it's first append, and it is less expensive to issue
>> "STATUS mailbox (APPENDLIMIT)" than a LIST command with APPENDLIMIT
>> return in that situation since the status info is all that is needed.
>
> My preference for the LIST-STATUS case over STATUS case comes from  
> the following statement in section 6.3.10 of RFC3501:
>
>       Unlike the LIST command, the STATUS command is not guaranteed to
>       be fast in its response.  Under certain circumstances, it can be
>       quite slow.  In some implementations, the server is obliged to
>       open the mailbox read-only internally to obtain certain status
>       information.  Also unlike the LIST command, the STATUS command
>       does not accept wildcards.

I believe this references calculation of data like unseen and total  
message counts, where you potentially need to parse the mail store to  
determine the information.  APPENDLIMIT will almost certainly be a  
static configuration value that doesn't depend on the actual mailbox  
contents so performance concerns should be negligible.

LIST-STATUS suffers from the same concerns as the 3501 text: backend  
status calculations do not magically get any faster piped through  
LIST-STATUS rather than a STATUS.  LIST-STATUS brings advantages in  
that you can get status information from a list of mailboxes, or from  
a list of mailboxes that you do not yet know, and you save on having  
to deal with the pipelining of multiple mailboxes yourself which  
potentially allows a server to optimize the lookups, but it isn't any  
faster in returning the results from a single mailbox as far as I know.

michael


___________________________________
Michael Slusarz [slusarz@horde.org]


From nobody Thu Dec 18 12:16:40 2014
Return-Path: <slusarz@horde.org>
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 7CCCA1AC3B3 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 12:16:26 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 uGnTai1NXBYn for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 12:16:21 -0800 (PST)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB44C1AC3D2 for <imapext@ietf.org>; Thu, 18 Dec 2014 12:15:54 -0800 (PST)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-01v.sys.comcast.net with comcast id V8F91p0032TL4Rh018FtrV; Thu, 18 Dec 2014 20:15:53 +0000
Received: from bigworm.curecanti.org ([67.176.83.228]) by resomta-ch2-17v.sys.comcast.net with comcast id V8Fs1p00K4vagWz018Ft96; Thu, 18 Dec 2014 20:15:53 +0000
Received: from bigworm.curecanti.org (localhost.localdomain [IPv6:::1]) (Authenticated sender: slusarz) by bigworm.curecanti.org (Postfix) with ESMTPSA id 5D876680B2 for <imapext@ietf.org>; Thu, 18 Dec 2014 13:15:52 -0700 (MST)
Received: from dangerzone.curecanti.org (dangerzone.curecanti.org [172.18.5.4]) by bigworm.curecanti.org (Horde Framework) with HTTP; Thu, 18 Dec 2014 13:15:52 -0700
Date: Thu, 18 Dec 2014 13:15:52 -0700
Message-ID: <20141218131552.Horde.m08XVgcG3aDfjNuxwQJupA1@bigworm.curecanti.org>
From: Michael M Slusarz <slusarz@horde.org>
To: imapext@ietf.org
References: <20141217182929.25391.39686.idtracker@ietfa.amsl.com> <5491CD00.6010606@isode.com> <f84ea49d-c876-4133-8b05-a5354cb87d85@gulbrandsen.priv.no> <5492C514.6080000@isode.com> <846929b7-6381-4fb4-a9ee-6cf34d412900@gulbrandsen.priv.no>
In-Reply-To: <846929b7-6381-4fb4-a9ee-6cf34d412900@gulbrandsen.priv.no>
User-Agent: Horde Application Framework 5
Accept-Language: en
X-Originating-IP: 172.18.5.4
X-Remote-Browser: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418933753; bh=r6cDtvTxQA8HzoXmUCvUqu4qsi/AcHh0M6thZQkSCVY=; h=Received:Received:Received:Received:Date:Message-ID:From:To: Subject:Content-Type:MIME-Version; b=c5/wiKlNxXVssLC4YRZoHK9Ux4H3rWy4Ve0bVx6ruEJzb5LDBWAC7sUk5lhla6q36 cunA4ajfHC2q3oO0fivOUa6UZ0/xbd5Iwkaisq+BOcwRYyJOVRk7u2gLx/BjMNUq2K tyTyvLrUk1RPuQTuXMv8Bw83kyxMnJTIv1ml3L7iD/hHjKBe+6tNolmXhlFngn6Mq9 +e2w5VsjztIwBrf+hWAcQiG4g4H0ZqA4tUIDWpPs7sU9zrp083hAC2qKvBnBKEyAeg 6MmneERuueiAl8ooihtfpOovzFkP0CJgmIVXOpoWOrkMrPnXo148KX7q3+ZRN/NnQ0 0V+Z7roHZNwBA==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/fEEz8XODxxommq6Krxg0xJAHczA
Subject: Re: [imapext] Fwd: I-D Action: draft-melnikov-rfc2088bis-01.txt
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, 18 Dec 2014 20:16:27 -0000

Quoting Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>:

> On Thursday, December 18, 2014 1:14:12 PM CEST, Alexey Melnikov wrote:
>> Allowing smaller non synchronizing literal sizes in APPEND might  
>> work, but the problem is that this still allows for abuse if the  
>> limit is exceeded.
>
> Not really, not if the limit is comparable to typical TCP send  
> windows. A badly behaving client can send one TCP window's worth of  
> stuff to the server anyway.
>
> Specifically, the client can send
>    a append inbox () "01-01-2000" {9999999999999999999999999999+}
> no matter whether which part of that line is forbidden, and the  
> server has to eat one whole TCP window before it can throw the  
> client out.

I do like having the option of allowing small messages to be directly  
appended with LITERAL+.  That's the way I've coded APPENDs currently.

Arnt's selection of 16k seems reasonable when viewed through the  
network lens.  Although with multipart/alternative and/or HTML  
messages being more prevalent these days, this probably means that the  
majority of sent-mail like APPENDs won't fall under this 16k  
exception.  So wondering if that means a large limit is needed (64k?)  
or whether we are adding complexity for optimizing only a limited  
number of APPEND transactions and this would be overkill.

michael

___________________________________
Michael Slusarz [slusarz@horde.org]


From nobody Thu Dec 18 12:22:31 2014
Return-Path: <alexey.melnikov@isode.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 264871A907C for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 12:22:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 F5ljRAWXep1B for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 12:22:27 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 115EB1A1B16 for <imapext@ietf.org>; Thu, 18 Dec 2014 12:22:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418934146; d=isode.com; s=selector; i=@isode.com; bh=CPfocFQp8qNd4VHw2i3z7HvYO4SQgHyoOgJjN2Okq8U=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=LV68WP/hpqeGWrxuzOCaDrhe0Xu/nSo76gN/MmPVf2Nga2N6ZT3Nd96C5mIdS0QNx9GJE5 yAQcLhl7ZK9XGG+HARDF8hVwc5GcdMUo7sPkUmmeTpncu/bTFdJeoE4Ayi9yZouwujABAj yZz/k1vN2RZsESkpa5AV5HTbPf8aymM=;
Received: from [192.168.0.12] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <VJM3gQAKaI2E@waldorf.isode.com>; Thu, 18 Dec 2014 20:22:25 +0000
X-SMTP-Protocol-Errors: PIPELINING
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (12B435)
In-Reply-To: <20141218122246.Horde.9kvC-_thX4wwso7qwAfvVw1@bigworm.curecanti.org>
Date: Thu, 18 Dec 2014 20:26:31 +0000
Message-Id: <9BE0EBFF-3D9A-4878-839F-222F44D2AA30@isode.com>
References: <02454F842DD7B449B96715A2AD90C0361A2530E7@exMB5.telecom.sna.samsung.com> <018bc48dc97c509d4e6f67e49b2ca4889b18e3c95f557d06a12c50a8e79fb1f6.sha-256@android.antelope.email> <CAKHUCzzOGoFOBc1ifzjm=Q2JzCa0Df62vXRYET3C_eg9aY=Tfg@mail.gmail.com> <02454F842DD7B449B96715A2AD90C0361A27805D@exMB5.telecom.sna.samsung.com> <C805B6E4-93B6-4EF4-977F-6A4F3E42ADA2@isode.com> <02454F842DD7B449B96715A2AD90C0361A28445B@exMB5.telecom.sna.samsung.com> <546EABA2.5060404@aol.com> <1E445AB3-7D54-4CA0-BFE9-3B0F97A45580@isode.com> <02454F842DD7B449B96715A2AD90C0363E986B16@exMB5.telecom.sna.samsung.com> <5487A0EC.4070603@aol.com> <02454F842DD7B449B96715A2AD90C0363E988D7A@exMB5.telecom.sna.samsung.com> <5488A5C9.9050904@aol.com> <548AC263.3080800@isode.com> <548B0C59.1060907@aol.com> <548ECB79.8000300@isode.com> <548EF91A.5090202@aol.com> <02454F842DD7B449B96715A2AD90C0363E99AFDC@exMB5.telecom.sna.samsung.com> <20141217050102.Horde.GWA4XtpoLlxANoaBg9l1cg1@bigworm.curecanti.org> <54917A9F.1030101@isode.com> <20141218122246.Horde.9kvC-_thX4wwso7qwAfvVw1@bigworm.curecanti.org>
To: Michael M Slusarz <slusarz@horde.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/ER15remZLjXFQp6PTnxrHvxK8w4
Cc: "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] [IMAP] APPEND Command Usage
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, 18 Dec 2014 20:22:29 -0000

Hi Michael,

> On 18 Dec 2014, at 19:22, Michael M Slusarz <slusarz@horde.org> wrote:
>=20
> Quoting Alexey Melnikov <alexey.melnikov@isode.com>:
>=20
>>> On 17/12/2014 12:01, Michael M Slusarz wrote:
>>>=20
>>> - Section 2 says a "client SHALL not try to upload mail more than advert=
ised limit in the APPEND command.".  I would think that should be MUST, not S=
HALL.  If a client understands APPENDLIMIT, it knows the maximum size the se=
rver would accept.  Sending data over this limit is explicitly ignoring proc=
ess/resource limits advertised by the server.
>> SHALL and MUST have the same meaning according to RFC 2119.
>=20
> That is what I get for sending my message as I'm about to board a plane.
>=20
> You are correct, although FWIW it's one man's opinion that MUST is clearer=
 than SHALL for this kind of language.
>=20
>>> - There's discussion of LIST + STATUS (RFC 5819).  But this is actually a=
n addition to STATUS itself.  The spec should be written as extending STATUS=
, and then a discussion/example of how this can be used if 5819 is supported=
.  (If we want to force an APPENDLIMIT client/server to also be LIST-STATUS c=
ompliant for performance reasons, that's fine.  But seems to be a policy dec=
ision rather than a technical explanation.)
>> This section is not quite right, but I need to rereview it in more detail=
s.
>=20
> Looks like you covered this in your subsequent review.
>=20
> In short, APPENDLIMIT status selector needs to be added to status-att, whi=
ch is extending 3501.
>=20
> =46rom an implementation point of view, the STATUS case makes more sense t=
han the LIST-STATUS case anyway.  A client /could/ add the APPENDLIMIT statu=
s return when creating the folder tree, but that's probably just wasted band=
width since generally a client is only going to be appending to a small numb=
er of those mailboxes (i.e. a sent-mail mailbox).
>=20
> I would imagine the most common behavior is that a client would grab the a=
ppend limit before it's first append, and it is less expensive to issue "STA=
TUS mailbox (APPENDLIMIT)" than a LIST command with APPENDLIMIT return in th=
at situation since the status info is all that is needed.

My implementation would probably issue a single LIST command with all option=
s that might be needed and caching results.

But yes, issuing a couple of extra STATUS calls might be more efficient.


From nobody Thu Dec 18 12:51:01 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 15C741A6FD6 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 12:50:58 -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 Nb8EGfxfRwlv for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 12:50:56 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B294D1A1B94 for <imapext@ietf.org>; Thu, 18 Dec 2014 12:50:56 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 2288FFA0082; Thu, 18 Dec 2014 20:50:55 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1418935854-6028-6027/11/1; Thu, 18 Dec 2014 20:50:54 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Thu, 18 Dec 2014 21:50:53 +0100
User-Agent: Trojita/v0.4.1-243-g4a74770; Qt/4.8.6; X11; Linux; Ubuntu 14.04.1 LTS
Mime-Version: 1.0
Message-Id: <a45bca2d-100d-4935-930f-edb4344e61fa@gulbrandsen.priv.no>
In-Reply-To: <20141218131552.Horde.m08XVgcG3aDfjNuxwQJupA1@bigworm.curecanti.org>
References: <20141217182929.25391.39686.idtracker@ietfa.amsl.com> <5491CD00.6010606@isode.com> <f84ea49d-c876-4133-8b05-a5354cb87d85@gulbrandsen.priv.no> <5492C514.6080000@isode.com> <846929b7-6381-4fb4-a9ee-6cf34d412900@gulbrandsen.priv.no> <20141218131552.Horde.m08XVgcG3aDfjNuxwQJupA1@bigworm.curecanti.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/zss1c-IxedjsouqiSasyN1kkocw
Subject: Re: [imapext] Fwd: I-D Action: draft-melnikov-rfc2088bis-01.txt
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, 18 Dec 2014 20:50:58 -0000

If the limit is larger than typical TCP windows the gain isn't large any 
more.

Once you're out of the send-window range, you already have several 
roundtrips, and adding one for the literal isn't that much. 5 is only 20% 
more than 4, but 2 is 100% more than 1.

A limit of 32k may make sense. (I wrote 16k because it's a nice binary 
number around halfway between 4500 and 32k.)

BTW, do you have the impression that the mail people sent has grown in size 
that much? The mail people receive, sure, but the mail people (humans) 
send, particularly from mobile devices, seems rather like ten years ago to 
me. A bit bigger, not much. I admit I have no dependable data on that.

Arnt


From nobody Thu Dec 18 17:41:03 2014
Return-Path: <slusarz@horde.org>
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 7870C1A8A05 for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 17:41:00 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 BvRZ_-YFLppn for <imapext@ietfa.amsl.com>; Thu, 18 Dec 2014 17:40:59 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2E1C1A0067 for <imapext@ietf.org>; Thu, 18 Dec 2014 17:40:58 -0800 (PST)
Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-08v.sys.comcast.net with comcast id VDgo1p0022N9P4d01DgxnC; Fri, 19 Dec 2014 01:40:57 +0000
Received: from bigworm.curecanti.org ([67.176.83.228]) by resomta-ch2-13v.sys.comcast.net with comcast id VDgw1p00e4vagWz01DgwgZ; Fri, 19 Dec 2014 01:40:57 +0000
Received: from bigworm.curecanti.org (localhost.localdomain [IPv6:::1]) (Authenticated sender: slusarz) by bigworm.curecanti.org (Postfix) with ESMTPSA id D88F36809B for <imapext@ietf.org>; Thu, 18 Dec 2014 18:40:55 -0700 (MST)
Received: from curecanti-gw.curecanti.org (curecanti-gw.curecanti.org [172.18.5.1]) by bigworm.curecanti.org (Horde Framework) with HTTP; Thu, 18 Dec 2014 18:40:55 -0700
Date: Thu, 18 Dec 2014 18:40:55 -0700
Message-ID: <20141218184055.Horde.OGPLlLcoGOJ8fGgP-dM0Yg2@bigworm.curecanti.org>
From: Michael M Slusarz <slusarz@horde.org>
To: imapext@ietf.org
References: <20141217182929.25391.39686.idtracker@ietfa.amsl.com> <5491CD00.6010606@isode.com> <f84ea49d-c876-4133-8b05-a5354cb87d85@gulbrandsen.priv.no> <5492C514.6080000@isode.com> <846929b7-6381-4fb4-a9ee-6cf34d412900@gulbrandsen.priv.no> <20141218131552.Horde.m08XVgcG3aDfjNuxwQJupA1@bigworm.curecanti.org> <a45bca2d-100d-4935-930f-edb4344e61fa@gulbrandsen.priv.no>
In-Reply-To: <a45bca2d-100d-4935-930f-edb4344e61fa@gulbrandsen.priv.no>
User-Agent: Horde Application Framework 5
Accept-Language: en
X-Originating-IP: 172.18.5.1
X-Remote-Browser: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418953257; bh=Tz3dbJQUQt7b0qGlDTO1/Opm7JXwV1KdyevbRMPgakY=; h=Received:Received:Received:Received:Date:Message-ID:From:To: Subject:Content-Type:MIME-Version; b=T0IF10mH00M/6rq8MSa1SSNX9uh9m7MD9ntFxTJHsegbeqOTojK6XECB68rWLLU7x tSDcSyj7K0GHrjEltbclIDRbetgl3ihGYLpkQVa9y91AzCkFI3b9+beVbZl4uvATaI lqBW+iF7/RiERsKyNGVH5PXm4BNk+PQr6Lo3NY1vY0DujFD+4apXwGcT3qxRQNDEbM RK0vi6TM/LlhHGf1t0ezuzD4wO28m5oZKaZ37xXdmlu2UPCaqdmjnfX1ZC3EtxUYXb aY/2kcHpc1c1bq9xXnbLZM+x21a8FgRXVm8ryIydu45qEgu9Gn6sTUW9ssBkl8Jezo 1dH9DaKh7eujA==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/qmSdSOx0LhIWIri_SmO24knr28Q
Subject: Re: [imapext] Fwd: I-D Action: draft-melnikov-rfc2088bis-01.txt
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, 19 Dec 2014 01:41:00 -0000

Quoting Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>:

> If the limit is larger than typical TCP windows the gain isn't large  
> any more.
>
> Once you're out of the send-window range, you already have several  
> roundtrips, and adding one for the literal isn't that much. 5 is  
> only 20% more than 4, but 2 is 100% more than 1.
>
> A limit of 32k may make sense. (I wrote 16k because it's a nice  
> binary number around halfway between 4500 and 32k.)

How much slower is a level 7 roundtrip than a level 4 roundtrip?   
(That question is probably dependent on the quality of both the server  
and client's IMAP protocol implementation, so there might not be a  
satisfactory answer.)

> BTW, do you have the impression that the mail people sent has grown  
> in size that much? The mail people receive, sure, but the mail  
> people (humans) send, particularly from mobile devices, seems rather  
> like ten years ago to me. A bit bigger, not much. I admit I have no  
> dependable data on that.

I thought I had data on that from a large ISP I work with, but I don't  
have it handy of course.

My personal experience is that I seem to be replying to HTML-ish  
messages a bunch these days that contain about 9 duplicated 20-line  
signatures (sigh).  Most users are just going to include all of that  
without trimming so once a thread reaches several replies I feel that  
message is easily nearing the 16k limit.  (Or think of HTML signatures  
that include a small embedded image, which is fairly common in  
business usage.)

Although a quick check of my personal sent-mail mailbox shows that  
only about 4% of my messages are over 16k.  With the caveat that I  
have much more text/plain mailing list activity, and reply trimming,  
than a "normal" user.

But even if that number is 50%, I guess I am convinced that this is  
enough of a savings to make a LITERAL- exception optimization useful.   
Especially since the place where saving a network packet helps the  
most -- mobile -- is precisely the location where the message lengths  
are likely smaller and thus more likely to fall under the exception.

michael

___________________________________
Michael Slusarz [slusarz@horde.org]


From nobody Fri Dec 19 01:20:24 2014
Return-Path: <thomas.dressler@1und1.de>
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 27E141A1EEE for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 01:20:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.1
X-Spam-Level: *
X-Spam-Status: No, score=1.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, 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 NCarX1T9TB77 for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 01:20:15 -0800 (PST)
Received: from moi.1and1.com (moi001.1and1.com [212.227.126.208]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D3451A0120 for <imapext@ietf.org>; Fri, 19 Dec 2014 01:20:15 -0800 (PST)
Received: from [172.28.13.5] by mri.1and1.com with esmtp (Exim 4.80) (envelope-from <thomas.dressler@1und1.de>) id 1Y1tjJ-0000gW-7u for imapext@ietf.org; Fri, 19 Dec 2014 10:20:13 +0100
Message-ID: <5493EDCB.2040303@1und1.de>
Date: Fri, 19 Dec 2014 10:20:11 +0100
From: =?ISO-8859-1?Q?Thomas_Dre=DFler?= <thomas.dressler@1und1.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: imapext@ietf.org
References: <mailman.1347.1418817673.2953.imapext@ietf.org>
In-Reply-To: <mailman.1347.1418817673.2953.imapext@ietf.org>
Content-Type: multipart/alternative; boundary="------------000202080807020908050800"
X-Virus-Scanned: ClamAV@mvs-ha-bs
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/mihZ83v9in_20WBTSB3Tq0xqatI
Subject: Re: [imapext] imapext Digest, Vol 29, Issue 17
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, 19 Dec 2014 09:20:18 -0000

This is a multi-part message in MIME format.
--------------000202080807020908050800
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

hi,

what is the meaning of th capability responses?

(1a) one limit for all folders

a client receive an capability response with "global" appendlimit.

C: t1 CAPABILITY
S: * CAPABILITY IMAP4rev1 ID APPENDLIMIT=257890 LIST-EXTENDED LIST-STATUS
S: t1 OK foo

are "a LIST "" % RETURN (STATUS (APPENDLIMIT))" or "a STATUS 
(APPENDLIMIT)" valid command's for the client?
must an server implement it? must an server reply APPENDLIMIT in 
SELECT/EXAMINE?
is it allowed for an server to return other APPENDLIMIT's in later 
SELECT/LIST/STATUS commands? if yes
change this the global limit, or overwrite it the local limit?

(1b)

a client receive an capability response with "local" append-limit (no 
LIST-STATUS capability).

C: t1 CAPABILITY
S: * CAPABILITY IMAP4rev1 ID APPENDLIMIT
S: t1 OK foo

is "a LIST "" % RETURN (STATUS (APPENDLIMIT))" realy an valid command, 
also if the server don't support extended list?
must an server return APPENDLIMIT on every SELECT/EXAMINE command? also 
on read-only folders? is an APPENDLIMIT other than zero on EXAMINE not 
an false idea?

example:

A932 EXAMINE blurdybloop
S: * 17 EXISTS
S: * 2 RECENT
S: * OK [UNSEEN 8] Message 8 is first unseen
S: * OK [UIDVALIDITY 3857529045] UIDs valid
S: * OK [UIDNEXT 4392] Predicted next UID
S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
S: * OK [PERMANENTFLAGS ()] No permanent flags permitted
S: * OK [APPENDLIMIT 0] Maximum upload limit
S: A932 OK [READ-ONLY] EXAMINE completed



Regards,
ThomasD









On 17.12.2014 13:01, imapext-request@ietf.org wrote:
> Send imapext mailing list submissions to
> 	imapext@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.ietf.org/mailman/listinfo/imapext
> or, via email, send a message with subject or body 'help' to
> 	imapext-request@ietf.org
>
> You can reach the person managing the list at
> 	imapext-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of imapext digest..."
>
>
> Today's Topics:
>
>     1. Re: [IMAP] APPEND Command Usage (Jayantheesh S B)
>     2. Re: [IMAP] APPEND Command Usage (Michael M Slusarz)
>
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext


-- 
Thomas Dreßler

Software-Entwickler
Mail System Development

1&1 Internet AG | Brauerstraße 48 | 76135 Karlsruhe | Germany
Phone: +49 721 91374-6790
E-Mail: thomas.dressler@1und1.de | Web: www.1und1.de

Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 6484

Vorstand: Ralph Dommermuth, Frank Einhellinger, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Uwe Lamnek, Christian Würst

Member of United Internet

Diese E-Mail kann vertrauliche und/oder gesetzlich geschützte Informationen enthalten. Wenn Sie nicht der bestimmungsgemäße Adressat sind oder diese E-Mail irrtümlich erhalten haben, unterrichten Sie bitte den Absender und vernichten Sie diese E-Mail. Anderen als dem bestimmungsgemäßen Adressaten ist untersagt, diese E-Mail zu speichern, weiterzuleiten oder ihren Inhalt auf welche Weise auch immer zu verwenden.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient of this e-mail, you are hereby notified that saving, distribution or use of the content of this e-mail in any way is prohibited. If you have received this e-mail in error, please notify the sender and delete the e-mail.


--------------000202080807020908050800
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    hi,<br>
    <br>
    what is the meaning of th capability responses?<br>
    <br>
    (1a) one limit for all folders<br>
    <br>
    a client receive an capability response with "global" appendlimit.<br>
    <br>
    C: t1 CAPABILITY<br>
    S: * CAPABILITY IMAP4rev1 ID APPENDLIMIT=257890 LIST-EXTENDED
    LIST-STATUS<br>
    S: t1 OK foo<br>
    <br>
    are "a LIST "" % RETURN (STATUS (APPENDLIMIT))" or "a STATUS
    (APPENDLIMIT)" valid command's for the client?<br>
    must an server implement it? must an server reply APPENDLIMIT in
    SELECT/EXAMINE?<br>
    is it allowed for an server to return other APPENDLIMIT's in later
    SELECT/LIST/STATUS commands? if yes<br>
    change this the global limit, or overwrite it the local limit?<br>
    <br>
    (1b)<br>
    <br>
    a client receive an capability response with "local" append-limit
    (no LIST-STATUS capability).<br>
    <br>
    C: t1 CAPABILITY<br>
    S: * CAPABILITY IMAP4rev1 ID APPENDLIMIT<br>
    S: t1 OK foo<br>
    <br>
    is "a LIST "" % RETURN (STATUS (APPENDLIMIT))" realy an valid
    command, also if the server don't support extended list?<br>
    must an server return APPENDLIMIT on every SELECT/EXAMINE command?
    also on read-only folders? is an APPENDLIMIT other than zero on
    EXAMINE not an false idea?<br>
    <br>
    example:<br>
    <pre class="newpage">A932 EXAMINE blurdybloop
S: * 17 EXISTS
S: * 2 RECENT
S: * OK [UNSEEN 8] Message 8 is first unseen
S: * OK [UIDVALIDITY 3857529045] UIDs valid
S: * OK [UIDNEXT 4392] Predicted next UID
S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
S: * OK [PERMANENTFLAGS ()] No permanent flags permitted
S: * OK [APPENDLIMIT 0] Maximum upload limit
S: A932 OK [READ-ONLY] EXAMINE completed


</pre>
    Regards,<br>
    ThomasD<br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    On 17.12.2014 13:01, <a class="moz-txt-link-abbreviated" href="mailto:imapext-request@ietf.org">imapext-request@ietf.org</a> wrote:
    <blockquote cite="mid:mailman.1347.1418817673.2953.imapext@ietf.org"
      type="cite">
      <pre wrap="">Send imapext mailing list submissions to
	<a class="moz-txt-link-abbreviated" href="mailto:imapext@ietf.org">imapext@ietf.org</a>

To subscribe or unsubscribe via the World Wide Web, visit
	<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/imapext">https://www.ietf.org/mailman/listinfo/imapext</a>
or, via email, send a message with subject or body 'help' to
	<a class="moz-txt-link-abbreviated" href="mailto:imapext-request@ietf.org">imapext-request@ietf.org</a>

You can reach the person managing the list at
	<a class="moz-txt-link-abbreviated" href="mailto:imapext-owner@ietf.org">imapext-owner@ietf.org</a>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of imapext digest..."
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">Today's Topics:

   1. Re: [IMAP] APPEND Command Usage (Jayantheesh S B)
   2. Re: [IMAP] APPEND Command Usage (Michael M Slusarz)
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
imapext mailing list
<a class="moz-txt-link-abbreviated" href="mailto:imapext@ietf.org">imapext@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/imapext">https://www.ietf.org/mailman/listinfo/imapext</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Thomas Dre&szlig;ler

Software-Entwickler
Mail System Development

1&amp;1 Internet AG | Brauerstra&szlig;e 48 | 76135 Karlsruhe | Germany
Phone: +49 721 91374-6790
E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:thomas.dressler@1und1.de">thomas.dressler@1und1.de</a> | Web: <a class="moz-txt-link-abbreviated" href="http://www.1und1.de">www.1und1.de</a>

Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 6484
 
Vorstand: Ralph Dommermuth, Frank Einhellinger, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Uwe Lamnek, Christian W&uuml;rst

Member of United Internet

Diese E-Mail kann vertrauliche und/oder gesetzlich gesch&uuml;tzte Informationen enthalten. Wenn Sie nicht der bestimmungsgem&auml;&szlig;e Adressat sind oder diese E-Mail irrt&uuml;mlich erhalten haben, unterrichten Sie bitte den Absender und vernichten Sie diese E-Mail. Anderen als dem bestimmungsgem&auml;&szlig;en Adressaten ist untersagt, diese E-Mail zu speichern, weiterzuleiten oder ihren Inhalt auf welche Weise auch immer zu verwenden.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient of this e-mail, you are hereby notified that saving, distribution or use of the content of this e-mail in any way is prohibited. If you have received this e-mail in error, please notify the sender and delete the e-mail.</pre>
  </body>
</html>

--------------000202080807020908050800--


From nobody Fri Dec 19 01:26:41 2014
Return-Path: <dave@cridland.net>
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 919521A6F3D for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 01:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 klfGc-OZ1JRA for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 01:26:35 -0800 (PST)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 825C11A212D for <imapext@ietf.org>; Fri, 19 Dec 2014 01:26:35 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id wo20so11583046obc.13 for <imapext@ietf.org>; Fri, 19 Dec 2014 01:26:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sGb/8tC0R2GYEYvY7ZvKmxBFfmhWZYBMHrPLY1kwLsE=; b=HMpmRVO6HKQPPfbn1083g1usXi56n23qipskVArfZiHAILsrPQirfAMHX6Ofyam3cO W3ajrnnor99oQvgzFfneRr7TSqOHdxHbb30z+H/KwZqGbhiEnhokYUBNaL97wqBEbkhE 0nliic23TAuSoiAfkoz3M9E9+rKiL25P8QboQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=sGb/8tC0R2GYEYvY7ZvKmxBFfmhWZYBMHrPLY1kwLsE=; b=an9YfqfmhR6XkC2pdfN3mgG2FeCb7mZO2mE6Nc1Bw4BmXkpjsTs6r/SuGA3E3Z3rNB dMTtXVxuZDJap5AVkO0YJY1DBj7XQG3AWYiatG9+CFgPPNK+dcm37hfaHcIEgNBL7pYV KO3M4h3oL9jzvPQy44yv4szOKEuhuMmWfqWcurQtBFFOPmv2Mnq2XNjWEy30wpK09Uyg U6w6SIvpZY3JMBfBqhDVgkh7JbmORs/VhwKTJMx0Dp8VeALvo0pEI9x3eImbCQYWtEws czQvabIsA8anF4HhCCUlZMV0J6qdR8CVVHfcdgw3nwT+1t1VBKX+DPAfsa4WTZJVSGRw wx7A==
X-Gm-Message-State: ALoCoQnW2Vu0ntLYOe0jqrvrtkZGIWtQLS3+Q/C8azwXUbjNAzgNti9fdU+JWXdu7VDKvP2Opm3M
MIME-Version: 1.0
X-Received: by 10.202.185.69 with SMTP id j66mr3961747oif.86.1418981194582; Fri, 19 Dec 2014 01:26:34 -0800 (PST)
Received: by 10.60.160.72 with HTTP; Fri, 19 Dec 2014 01:26:34 -0800 (PST)
In-Reply-To: <5491CD00.6010606@isode.com>
References: <20141217182929.25391.39686.idtracker@ietfa.amsl.com> <5491CD00.6010606@isode.com>
Date: Fri, 19 Dec 2014 09:26:34 +0000
Message-ID: <CAKHUCzwU+RJ1xPn_S4_yBhveb+55JYp51TXras877w=4aao1bg@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: multipart/alternative; boundary=001a113ce6120c0882050a8e4e02
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/qh-v3K81FzqFqWYi-exx82F9w_8
Cc: "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] Fwd: I-D Action: draft-melnikov-rfc2088bis-01.txt
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, 19 Dec 2014 09:26:37 -0000

--001a113ce6120c0882050a8e4e02
Content-Type: text/plain; charset=UTF-8

On 17 December 2014 at 18:35, Alexey Melnikov <alexey.melnikov@isode.com>
wrote:
>
>  I revived and updated LITERAL+ extension. I also added LITERAL- extension
> (same as LITERAL+, but disallowed in APPEND).
>
>
Given the current discussions, wouldn't LITERAL- be better expressed as a
LITERAL+ with a limited size? I accept that the normal case for a large
literal is APPEND,  but the issue is a general one with the size of the
literal rather than the specific case of APPEND, isn't it?

This could even be an advertised token-sequence limit, but that's probably
too hard to express. Possible, though, to limit the amount of
non-synchronized literal data with an entire command, which'd handle the
MULTIAPPEND case as well.

To give an specific case, a client can always side-step a simple APPEND
LITERAL+ limit by just using CATENATE in a fairly abusive manner.

Dave.

--001a113ce6120c0882050a8e4e02
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 17 December 2014 at 18:35, Alexey Melnikov <span dir=3D"ltr">&lt;<a =
href=3D"mailto:alexey.melnikov@isode.com" target=3D"_blank">alexey.melnikov=
@isode.com</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20

   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    I revived and updated LITERAL+ extension. I also added LITERAL-
    extension (same as LITERAL+, but disallowed in APPEND).<br>
    <div><br></div></div></blockquote><div><br></div><div>Given the current=
 discussions, wouldn&#39;t LITERAL- be better expressed as a LITERAL+ with =
a limited size? I accept that the normal case for a large literal is APPEND=
, =C2=A0but the issue is a general one with the size of the literal rather =
than the specific case of APPEND, isn&#39;t it?</div><div><br></div><div>Th=
is could even be an advertised token-sequence limit, but that&#39;s probabl=
y too hard to express. Possible, though, to limit the amount of non-synchro=
nized literal data with an entire command, which&#39;d handle the MULTIAPPE=
ND case as well.</div><div><br></div><div>To give an specific case, a clien=
t can always side-step a simple APPEND LITERAL+ limit by just using CATENAT=
E in a fairly abusive manner.</div><div><br></div><div>Dave.</div></div></d=
iv></div>

--001a113ce6120c0882050a8e4e02--


From nobody Fri Dec 19 11:07:00 2014
Return-Path: <slusarz@horde.org>
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 74B351A89B9 for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 11:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 xQQTFe3uaCvb for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 11:06:57 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 793AA1A897C for <imapext@ietf.org>; Fri, 19 Dec 2014 11:06:57 -0800 (PST)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-06v.sys.comcast.net with comcast id VX6f1p00B2Bo0NV01X6wPP; Fri, 19 Dec 2014 19:06:56 +0000
Received: from bigworm.curecanti.org ([IPv6:2002:43b0:53e4:0:21e:68ff:fe1e:2860]) by resomta-ch2-05v.sys.comcast.net with comcast id VX6v1p00T3cyTSr01X6wzs; Fri, 19 Dec 2014 19:06:56 +0000
Received: from bigworm.curecanti.org (localhost.localdomain [IPv6:::1]) (Authenticated sender: slusarz) by bigworm.curecanti.org (Postfix) with ESMTPSA id 01C936809B for <imapext@ietf.org>; Fri, 19 Dec 2014 12:06:51 -0700 (MST)
Received: from ip-64-134-124-51.public.wayport.net (ip-64-134-124-51.public.wayport.net [64.134.124.51]) by bigworm.curecanti.org (Horde Framework) with HTTP; Fri, 19 Dec 2014 12:06:51 -0700
Date: Fri, 19 Dec 2014 12:06:51 -0700
Message-ID: <20141219120651.Horde.Rn44KuYQyc2iQlzc5-_fsw1@bigworm.curecanti.org>
From: Michael M Slusarz <slusarz@horde.org>
To: imapext@ietf.org
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com> <3b213806-8498-40d5-90fa-bb5483a96879@flaska.net> <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca>
In-Reply-To: <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca>
User-Agent: Horde Application Framework 5
Accept-Language: en
X-Originating-IP: 64.134.124.51
X-Remote-Browser: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1419016016; bh=8uDTBg49MSOY3qAx9/pN/7oQYxU2zdsMJ4/OKYqXRg0=; h=Received:Received:Received:Received:Date:Message-ID:From:To: Subject:Content-Type:MIME-Version; b=iRZBRWD067k8mRCEQMHWsNbdjN+/5AF0b6jAlMu155lMUak4tJYAAROCN8KwhVEt5 LVJrnSKlZGBoP1vAQ1G1bQJqZy7fXMqQead3JyA6pmFRhycZpmcBj/knkFERY2Q0an PMLhmeXeJO5mWOmTowaHXx4mGiFCGcoxupsmtEltSMdMzOO6pVhl2Dmus+3/ay5Yrx xXq4def0l6bxBO0GHzHjt+XZ2o0n9BMoM3H73Vt9YdemI/pEFq739j4CpUbVm1d3Ot 7K2czuLj/BnYbxOTB63E68kDvJacq0yGdUjO1k5qmuT236W7p6lsmTRdMFgrcnwEap hl+CJ+F7WBJxw==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/j275Y8fQpo52VFXK1oKt-jmc1xU
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 19 Dec 2014 19:06:59 -0000

Quoting Lyndon Nerenberg <lyndon@orthanc.ca>:

> I think the changes to add that restriction might be a bit too  
> substantive for an errata.  (Barry, are you lurking  out there?)   
> Also, others have complained about parts of the document that are  
> ambiguous or just not clear, so maybe it's time for an update.

A real world BINARY issue, that was brought to my attention today, is  
the list behavior at vger.kernel.org.  I was told that incoming  
messages have mailing list information appended to them, regardless of  
the transfer-encoding of the content.

So a message with single base64 encoded part is sent like:

=====
Content-Type: text/plain
Content-Transfer-Encoding: base64

<base64 data>

<Plaintext Mailing List Trailer>
=====

Issuing a FETCH BINARY[] on this data produces inconsistent results.   
A NO [UNKNOWN-CTE] is possible, as well as trying to base64 decode as  
much as possible while stripping the rest, and finally base64 decoding  
and leaving the plaintext as is.

If 3516 is getting updated, might be useful to have a more consistent  
definition of what it means to be "unable to trasfer decode" so that  
this data is displayed consistently across servers.  i.e. Is it ok to  
do a best-guess decoding?

Additionally, it might be useful to add implementation note that a  
client should fallback to using FETCH BODY[] if the server returns NO.  
  The MUA that the original reporter is using (I don't know what it  
is) is simply showing a blank body for these kind of messages when a  
FETCH BINARY[] is unsuccessful.

michael

___________________________________
Michael Slusarz [slusarz@horde.org]


From nobody Fri Dec 19 11:15:54 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 7E0A01A8A06 for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 11:15:52 -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, RCVD_IN_DNSWL_NONE=-0.0001] 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 324S9k6sEw2F for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 11:15:51 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B59781ACD62 for <imapext@ietf.org>; Fri, 19 Dec 2014 11:15:50 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 854BEFA0079; Fri, 19 Dec 2014 19:15:48 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1419016547-3758-3757/12/1; Fri, 19 Dec 2014 19:15:47 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org, Michael M Slusarz <slusarz@horde.org>
Message-Id: <cec001013dad7592b7dd4d72aadfc80aaa19c970df812c5e549d559c85b70989.sha-256@android.antelope.email>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com> <3b213806-8498-40d5-90fa-bb5483a96879@flaska.net> <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca> <20141219120651.Horde.Rn44KuYQyc2iQlzc5-_fsw1@bigworm.curecanti.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Date: Fri, 19 Dec 2014 19:15:47 +0000
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/hXWqcblJ6gG20UP6ily6IFeuuvk
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 19 Dec 2014 19:15:52 -0000

As I recall, the base64 spec says to skip unknown input bytes, so if =
there are no padding bytes (=3D), that list adds well-defined data. If =
there is padding, I don't know what the spec days.

Arnt


From nobody Fri Dec 19 11:58:13 2014
Return-Path: <lyndon@orthanc.ca>
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 C0F041A6FD4 for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 11:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 2twz6ZegezHj for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 11:58:11 -0800 (PST)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05BA41A6FF3 for <imapext@ietf.org>; Fri, 19 Dec 2014 11:58:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by orthanc.ca (8.14.7/8.14.7) with ESMTP id sBJJw3ww076848 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Dec 2014 11:58:03 -0800 (PST) (envelope-from lyndon@orthanc.ca)
Date: Fri, 19 Dec 2014 11:58:03 -0800 (PST)
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Michael M Slusarz <slusarz@horde.org>
In-Reply-To: <20141219120651.Horde.Rn44KuYQyc2iQlzc5-_fsw1@bigworm.curecanti.org>
Message-ID: <alpine.BSF.2.11.1412191113180.58714@orthanc.ca>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com> <3b213806-8498-40d5-90fa-bb5483a96879@flaska.net> <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca> <20141219120651.Horde.Rn44KuYQyc2iQlzc5-_fsw1@bigworm.curecanti.org>
User-Agent: Alpine 2.11 (BSF 23 2013-08-11)
Organization: The Frobozz Magic Homing Pigeon Company
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/tCGuMdMq1NnczZRttzFp-4zGGkM
Cc: imapext@ietf.org
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 19 Dec 2014 19:58:12 -0000

> So a message with single base64 encoded part is sent like:
>
> =====
> Content-Type: text/plain
> Content-Transfer-Encoding: base64
>
> <base64 data>
>
> <Plaintext Mailing List Trailer>
> =====

> Issuing a FETCH BINARY[] on this data produces inconsistent results.  A NO 
> [UNKNOWN-CTE] is possible, as well as trying to base64 decode as much as 
> possible while stripping the rest, and finally base64 decoding and leaving 
> the plaintext as is.

As a purist I would argue the IMAP server should never have accepted the 
message to begin with, but most implementations take it on faith the 
content matches what the metadata says is in there.

In this case, I'm not sure what to do.  The problem here is not a BINARY 
issue as such, but more of a general issue as to what a server should do 
when it discovers invalid data part way through a transaction.  The 
protocol in general doesn't provide a framework for dealing with this type 
of scenario.

My strong preference is for the server fully validate the message when 
it's being injected into the store, and reject these sorts of 
non-complaint messages at that time.  Most any IMAP store these days is 
already parsing the MIME structure at injection time, so it's really not a 
lot of extra work to validate the stated encodings match the body content 
as you're copying the message through.

> If 3516 is getting updated, might be useful to have a more consistent 
> definition of what it means to be "unable to trasfer decode" so that this 
> data is displayed consistently across servers.  i.e. Is it ok to do a 
> best-guess decoding?

Absolutely not.  You must follow the directive in the MIME header (in this 
case, perform a bese64 decode).

RFC3501 section 7.4.2 talks about ENcoding binary content as base64, but 
since this transformation cannot fail there is no provision for a failure 
mode.  For BINARY, that's not the case, as your example points out.  And 
it was a situation I never anticipated when I wrote 3516 (most likely 
because I am quite fascist about rejecting invalid content up front before 
it becomes a problem).

At the moment, I'm not sure there is any way out of this other than for a 
server supporting BINARY to validate the CTEs at injection time, and 
reject any messages with content encoding violations.  I don't think there 
is any way for a server that discovers bad base64 in the middle of a 
BINARY FETCH to recover gracefully.

I *adamantly* oppose any notion of passing through anything that fails the 
CTE decoding, as this presents a wonderful opportunity for malicious code 
injection into a naive client implementation.  In light of that security 
concern alone, I don't think there is any alternative but to add a "server 
MUST validate the body content correctly decodes before transmitting the 
decoded content to the client" or words to that effect to the BINARY 
specification.  If this is done at message injection time, the overhead 
will be minimal, and would allow the server to refuse to accept the 
message.  If implementers are insistent about accepting such malformed 
content, then we will have to add something like an [INVALID-CTE-SYNTAX] 
respose code so the server can send back "foo NO [INVALID-CTE-SYNTAX]" 
when the runtime check fails.

> Additionally, it might be useful to add implementation note that a client 
> should fallback to using FETCH BODY[] if the server returns NO.  The MUA that 
> the original reporter is using (I don't know what it is) is simply showing a 
> blank body for these kind of messages when a FETCH BINARY[] is unsuccessful.

This is so stunningly obvious it doesn't deserve mentioning.

--lyndon


From nobody Fri Dec 19 14:12:29 2014
Return-Path: <prvs=543042c286=j.sb@sta.samsung.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 1EFD71ACDC4 for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 14:12:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.796
X-Spam-Level: **
X-Spam-Status: No, score=2.796 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.793, 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 dTBSxeSf9_hh for <imapext@ietfa.amsl.com>; Fri, 19 Dec 2014 14:12:24 -0800 (PST)
Received: from smg1.telecom.sna.samsung.com (unknown [63.166.115.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B8CE1ACDDD for <imapext@ietf.org>; Fri, 19 Dec 2014 14:12:23 -0800 (PST)
X-AuditID: 41a9fa1f-f79486d0000004ef-ae-5494a2ba8e91
Received: from exHub2.telecom.sna.samsung.com (Unknown_Domain [105.52.12.243]) by smg1.telecom.sna.samsung.com (SMGOUT STA) with SMTP id A1.BC.01263.AB2A4945; Fri, 19 Dec 2014 16:12:10 -0600 (CST)
Received: from EXMB5.telecom.sna.samsung.com ([fe80::5f4:56d9:ea68:f480]) by exHub2.telecom.sna.samsung.com ([fe80::348a:877:72e7:524b%22]) with mapi id 14.03.0146.000; Fri, 19 Dec 2014 16:12:22 -0600
From: Jayantheesh S B <j.sb@sta.samsung.com>
To: "'imapext@ietf.org'" <imapext@ietf.org>
Thread-Topic: The IMAP APPENDLIMIT Extension
Thread-Index: AdAb2Bf//z0eh4nfQhiMiDetjLkX+g==
Date: Fri, 19 Dec 2014 22:12:21 +0000
Message-ID: <02454F842DD7B449B96715A2AD90C0363E99E411@exMB5.telecom.sna.samsung.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [105.52.12.197]
Content-Type: multipart/mixed; boundary="_004_02454F842DD7B449B96715A2AD90C0363E99E411exMB5telecomsna_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMLMWRmVeSWpSXmKPExsWSacLzWXfXoikhBre75C0ez+JyYPRYsuQn UwBjFLdNUmJJWXBmep6+XQJ3xr3WJywFF1YxVqz4dIS5gfH1YsYuRg4OCQETidUPJboYOYFM MYkL99azgdhCAscYJf416XUxcgHZZxglXu39xd7FyM7BJqAj8SQYpFNEQFtiwnEPEFNYQF3i 1npLiKiOxNG1QRCmnsS8O0Eg41gEVCUePT7DBGLzCoRITJj2lh3EZgRa+f3UGrA4s4C4xK0n 85kgThGReHjxNBuELSrx8vE/VghbUWLur5vMEPWZEscuT2KBmCkocXLmE5YJjEKzkIyahaRs FpKyBYzMqxhlinPTDfVKUnNSk/Nz9YrzEvWKE3OLS/PS9YD8TYzAsHVc+Ut+B+O67faHGJk4 OA8xSnBwSYkUp+alpBYllpZkxIOCN74YGL5SDYyqZeJvn15fH8dYsSnUXiJt4Y7z160VStYd nG6Vej/9jsNN1gkVMbF5l+9n/Z/9PV6Mo3n6NOMLn9P+vtl3+NC99Jtv8w9HyX05K2x46ZXp vXu79glzaSsd2Jov5cLgOOlZzIKvUw1S2tr/PQpg1PApyHDRvbdJPXN+sKTzm4MdYqsbl5aH SvQosRRnJBpqMRcVJwIArs/kOSYCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/MdPi3cinWA_foxF3vGSANXp7S_g
Subject: [imapext] The IMAP APPENDLIMIT Extension
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, 19 Dec 2014 22:12:27 -0000

--_004_02454F842DD7B449B96715A2AD90C0363E99E411exMB5telecomsna_
Content-Type: multipart/alternative;
	boundary="_000_02454F842DD7B449B96715A2AD90C0363E99E411exMB5telecomsna_"

--_000_02454F842DD7B449B96715A2AD90C0363E99E411exMB5telecomsna_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

Please find the next version of the draft attached with all the review comm=
ents addressed.

If you have any comments/suggestions in the attached version, kindly share =
it.

Regards,
Jay

--_000_02454F842DD7B449B96715A2AD90C0363E99E411exMB5telecomsna_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi All,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please find the next version of the draft attached w=
ith all the review comments addressed.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If you have any comments/suggestions in the attached=
 version, kindly share it.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Jay<o:p></o:p></p>
</div>
</body>
</html>

--_000_02454F842DD7B449B96715A2AD90C0363E99E411exMB5telecomsna_--

--_004_02454F842DD7B449B96715A2AD90C0363E99E411exMB5telecomsna_
Content-Type: text/plain;
	name="draft-jayantheesh-imap-appendlimit-extension-02.txt"
Content-Description: draft-jayantheesh-imap-appendlimit-extension-02.txt
Content-Disposition: attachment;
	filename="draft-jayantheesh-imap-appendlimit-extension-02.txt"; size=13288;
	creation-date="Thu, 18 Dec 2014 17:36:12 GMT";
	modification-date="Fri, 19 Dec 2014 20:48:28 GMT"
Content-Transfer-Encoding: base64

SU5URVJORVQtRFJBRlQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
SmF5YW50aGVlc2ggUyBCIApJbnRlbmRlZCBzdGF0dXM6IFN0YW5kYXJkcyBUcmFjayAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIFNhbXN1bmcKRXhwaXJlczogSnVuZSAyMDE1ICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIE5hcmVuZHJhIFNpbmdoIEJpc2h0CiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
U2Ftc3VuZwogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgRGVjZW1iZXIgMTksIDIwMTQKCiAgICAgICAgICAgICAgICAgICAgICBUaGUgSU1BUCBB
UFBFTkRMSU1JVCBFeHRlbnNpb24KICAgICAgICAgICAgICAgIGRyYWZ0LWpheWFudGhlZXNoLWlt
YXAtYXBwZW5kbGltaXQtZXh0ZW5zaW9uLTAyCgpBYnN0cmFjdAoKVGhpcyBtZW1vIGRlZmluZXMg
YW4gZXh0ZW5zaW9uIHRvIHRoZSBJTUFQIHNlcnZpY2Ugd2hlcmVieSBhIHNlcnZlciBjYW4KYWR2
ZXJ0aXNlIGl0cyBjYXBhYmlsaXR5LCB0byBzdXBwb3J0IG1heGltdW0gbWFpbCB1cGxvYWQgc2l6
ZSB1c2luZwpDQVBBQklMSVRZLCBTRUxFQ1QvRVhBTUlORSBhbmQgTElTVCBjb21tYW5kLgoKU3Rh
dHVzIG9mIHRoaXMgTWVtbwoKVGhpcyBJbnRlcm5ldC1EcmFmdCBpcyBzdWJtaXR0ZWQgaW4gZnVs
bCBjb25mb3JtYW5jZSB3aXRoIHRoZQpwcm92aXNpb25zIG9mIEJDUCA3OCBhbmQgQkNQIDc5LiBU
aGlzIGRvY3VtZW50IG1heSBub3QgYmUgbW9kaWZpZWQsIGFuZApkZXJpdmF0aXZlIHdvcmtzIG9m
IGl0IG1heSBub3QgYmUgY3JlYXRlZCwgZXhjZXB0IHRvIHB1Ymxpc2ggaXQgYXMgYW4KUkZDIGFu
ZCB0byB0cmFuc2xhdGUgaXQgaW50byBsYW5ndWFnZXMgb3RoZXIgdGhhbiBFbmdsaXNoLgoKSW50
ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5l
ZXJpbmcgVGFzawpGb3JjZSAoSUVURiksIGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vw
cy4gIE5vdGUgdGhhdCBvdGhlciBncm91cHMKbWF5IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRv
Y3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuCgpJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRv
Y3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHMKYW5kIG1heSBiZSB1cGRh
dGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnkKdGlt
ZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVu
Y2UgbWF0ZXJpYWwKb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4gYXMgIndvcmsgaW4gcHJvZ3Jl
c3MuIgoKVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC1EcmFmdHMgY2FuIGJlIGFjY2Vzc2Vk
IGF0Cmh0dHA6Ly93d3cuaWV0Zi5vcmcvaWV0Zi8xaWQtYWJzdHJhY3RzLnR4dAoKVGhlIGxpc3Qg
b2YgSW50ZXJuZXQtRHJhZnQgU2hhZG93IERpcmVjdG9yaWVzIGNhbiBiZSBhY2Nlc3NlZCBhdApo
dHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sCgpUaGlzIEludGVybmV0LURyYWZ0IHdpbGwg
ZXhwaXJlIG9uIEp1bmUsIDIwMTUuCgpDb3B5cmlnaHQgTm90aWNlCgpDb3B5cmlnaHQgKGMpIDIw
MTQgSUVURiBUcnVzdCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmllZCBhcyB0aGUKZG9jdW1lbnQg
YXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2ZWQuCgpUaGlzIGRvY3VtZW50IGlzIHN1YmplY3Qg
dG8gQkNQIDc4IGFuZCB0aGUgSUVURiBUcnVzdCdzIExlZ2FsClByb3Zpc2lvbnMgUmVsYXRpbmcg
dG8gSUVURiBEb2N1bWVudHMKKGh0dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vuc2UtaW5mbykg
aW4gZWZmZWN0IG9uIHRoZSBkYXRlIG9mCnB1YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuICBQ
bGVhc2UgcmV2aWV3IHRoZXNlIGRvY3VtZW50cyBjYXJlZnVsbHksCmFzIHRoZXkgZGVzY3JpYmUg
eW91ciByaWdodHMgYW5kIHJlc3RyaWN0aW9ucyB3aXRoIHJlc3BlY3QgdG8gdGhpcwpkb2N1bWVu
dC4KCkpheWFudGhlZXNoICYgTmFyZW5kcmEgICAgICAgRXhwaXJlcyBKdW5lLCAyMDE1ICAgICAg
ICAgICAgICAgW1BhZ2UgMV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIElNQVAgQVBQ
RU5ETElNSVQgICAgICAgICAgICBEZWNlbWJlciAyMDE0CgpUYWJsZSBvZiBDb250ZW50cwoKICAg
MS4gIEludHJvZHVjdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICAyCiAgICAgMS4xLiBDb252ZW50aW9ucyBhbmQgVGVybWlub2xvZ3kgLiAuIC4g
LiAuIC4gLiAuIC4gLiAgLiAuIC4gLiAuICAgMgogICAyLiBBUFBFTkRMSU1JVCBFeHRlbnNpb24g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDIKICAgMy4gTWFpbGJv
eCBzcGVjaWZpYyBBUFBFTkRMSU1JVCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAzCiAgICAgMy4xLiBTRUxFQ1QgcmVzcG9uc2UgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAgNAogICAgIDMuMi4gTElTVCByZXNwb25zZSAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDQKICAgNC4gQVBQRU5EIHJlc3BvbnNl
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA1CiAgIDUu
IEZvcm1hbCBzeW50YXggLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgNQogICA2LiBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDYKICAgNy4gSUFOQSBDb25zaWRlcmF0aW9ucyAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA2CiAgIDguIFJlZmVyZW5j
ZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
NgogICAgOC4xIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIDYKICAgIDguMiBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA3CiAgIDkuIEFja25vd2xlZGdlbWVudCAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNwogICAxMC4g
QXV0aG9yJ3MgQWRkcmVzcyAuIC4uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIDcKICAgCgoxLiBJbnRyb2R1Y3Rpb24KClNldmVyYWwgSU1BUCBzZXJ2ZXIgaGF2ZSBs
aW1pdGF0aW9uIGZvciBtYWlsIHVwbG9hZCBzaXplIHdoaWNoIGlzIG5vdApwdWJsaXNoZWQgdG8g
dGhlIGVtYWlsIGNsaWVudC4gIFdoZW4gZW1haWwgY2xpZW50IEFQUEVORCBhIG1haWwgd2l0aApo
dWdlIGF0dGFjaG1lbnRzLCBpdCBmYWlscyBkdWUgdG8gc2l6ZSByZXN0cmljdGlvbiBzZXQgYnkg
dGhlIElNQVAKc2VydmVyLiAgVGhpcyByZXN1bHRzIGluIHVubmVjZXNzYXJ5IHJlc291cmNlIHVz
YWdlLiAgRXNwZWNpYWxseSBpbiB0aGUgCm1vYmlsZSBkZXZpY2UgZW52aXJvbm1lbnQsIGFwcGVu
ZGluZyBtYWlsIHdpdGggaHVnZSBhdHRhY2htZW50IGNvbnN1bWVzCmRldmljZSByZXNvdXJjZXMg
bGlrZSBkZXZpY2UgYmF0dGVyeSBwb3dlciBhbmQgbW9iaWxlIGRhdGEuCgpUaGUgSU1BUCBBUFBF
TkRMSU1JVCBleHRlbnNpb24gcHJvdmlkZXMgYW4gYWJpbGl0eSB0byBhZHZlcnRpc2UgbWF4aW11
bQp1cGxvYWQgc2l6ZSBhbGxvd2VkIGJ5IHRoZSBJTUFQIHNlcnZlciwgc28gdGhhdCBlbWFpbCBj
bGllbnQga25vd3MgdGhlCnNpemUgbGltaXRhdGlvbiBiZWZvcmVoYW5kLgoKMS4xLiBDb252ZW50
aW9ucyBhbmQgVGVybWlub2xvZ3kKClRoZSBrZXkgd29yZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAi
UkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgCk5PVCIsIlNIT1VMRCIsICJTSE9VTEQgTk9UIiwg
IlJFQ09NTUVOREVEIiwgICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbgp0aGlzIGRvY3VtZW50IGFy
ZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQgaW4gUkZDIDIxMTkuCgpFeGFtcGxlIGxp
bmVzIHByZWZhY2VkIGJ5ICJDOiIgYXJlIHNlbnQgYnkgdGhlIGNsaWVudCBhbmQgb25lcyBwcmVm
YWNlZApieSAiUzoiIGJ5IHRoZSBzZXJ2ZXIuICBUaGUgZml2ZSBjaGFyYWN0ZXJzIFsuLi5dIG1l
YW5zIHRoYXQgc29tZXRoaW5nCmhhcyBiZWVuIGVsaWRlZC4KCjIuIEFQUEVORExJTUlUIEV4dGVu
c2lvbgoKQW4gSU1BUCBzZXJ2ZXIgdGhhdCBzdXBwb3J0cyBBUFBFTkRMSU1JVCBhZHZlcnRpc2Vz
IHRoaXMgYnkgaW5jbHVkaW5nCnRoZSB3b3JkIEFQUEVORExJTUlUIGluIGl0cyBjYXBhYmlsaXR5
IGxpc3QuICBJTUFQIHNlcnZlciBzaGFsbCBwdWJsaXNoCnRoZSBzdXBwb3J0ZWQgbWFpbCB1cGxv
YWQgc2l6ZSBhcyBwYXJ0IG9mIENBUEFCSUxJVFkgcmVzcG9uc2UuICBUaGUKCkpheWFudGhlZXNo
ICYgTmFyZW5kcmEgICAgICAgRXhwaXJlcyBKdW5lLCAyMDE1ICAgICAgICAgICAgICBbUGFnZSAy
XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgSU1BUCBBUFBFTkRMSU1JVCAgICAgICAg
ICAgRGVjZW1iZXIgMjAxNAoKYWR2ZXJ0aXNlZCB1cGxvYWQgbGltaXQgaXMgY29tbW9uIGFjcm9z
cyB0aGUgbWFpbGJveGVzLCBidXQgY2xpZW50CmNhbiBzdGlsbCBpc3N1ZSBTRUxFQ1QvRVhBTUlO
RSBvciBMSVNUIGNvbW1hbmQgdG8gZ2V0IHRoZSBtYWlsYm94CnNwZWNpZmljIHVwbG9hZCBsaW1p
dCBzZXQgYnkgdGhlIElNQVAgc2VydmVyLiAgSW4gdGhpcyBjYXNlLApBUFBFTkRMSU1JVCB2YWx1
ZSBvYnRhaW5lZCBhcyBwYXJ0IG9mIFNFTEVDVC9FWEFNSU5FIG9yIExJU1QgY29tbWFuZAp0YWtl
cyBwcmVjZWRlbmNlIG92ZXIgdGhlIHZhbHVlIHJldHVybmVkIGFzIHBhcnQgb2YgQ0FQQUJJTElU
WQpyZXNwb25zZS4KClRoZSBmb2xsb3dpbmcgZXhhbXBsZSwgZGVtb25zdHJhdGVzIHRoZSBBUFBF
TkRMSU1JVCBjYXBhYmlsaXR5IHdpdGgKbWFpbGJveCBsaW1pdC4KCkM6IHQxIENBUEFCSUxJVFkK
UzogKiBDQVBBQklMSVRZIElNQVA0cmV2MSBJRCBBUFBFTkRMSU1JVD0yNTc4OTAKUzogdDEgT0sg
Zm9vCgpJZiBBUFBFTkRMSU1JVCB2YWx1ZSBpcyBvbWl0dGVkIGluIENBUEFCSUxJVFkgcmVzcG9u
c2UsIHRoZW4gY2xpZW50ClNIT1VMRCBpc3N1ZSBTRUxFQ1QvRVhBTUlORSBvciBMSVNUIGNvbW1h
bmQgdG8gZ2V0IHRoZSBtYWlsYm94IHNwZWNpZmljCmxpbWl0IHNldCBieSB0aGUgc2VydmVyLiAg
TmV3IHJlc3BvbnNlIGNvZGUgQVBQRU5ETElNSVQgaXMgYWRkZWQgdG8gZ2V0CnRoZSBtYWlsYm94
IHNwZWNpZmljIGxpbWl0LiAgUmVmZXIgc2VjdGlvbiA1IGZvciByZXNwb25zZSBjb2RlIHN5bnRh
eC4KClRoZSBmb2xsb3dpbmcgZXhhbXBsZSBkZW1vbnN0cmF0ZXMsIGl0cyB1c2FnZS4KCkM6IHQx
IENBUEFCSUxJVFkKUzogKiBDQVBBQklMSVRZIElNQVA0cmV2MSBJRCBBUFBFTkRMSU1JVApTOiB0
MSBPSyBmb28KCkM6IHQyIFNFTEVDVCBJTkJPWApTOiAqIDE3MiBFWElTVFMKUzogKiBPSyBbQVBQ
RU5ETElNSVQgMjU3ODkwXSBNYXhpbXVtIHVwbG9hZCBsaW1pdApTOiAqIE9LIFtVSURWQUxJRElU
WSAzODU3NTI5MDQ1XSBVSURzIHZhbGlkClM6ICogRkxBR1MgKFxBbnN3ZXJlZCBcRmxhZ2dlZCBc
RGVsZXRlZCBcU2VlbiBcRHJhZnQpClM6ICogT0sgW1BFUk1BTkVOVEZMQUdTIChcRGVsZXRlZCBc
U2VlbiBcKildIExpbWl0ZWQKUzogdDIgT0sgW1JFQUQtV1JJVEVdIFNFTEVDVCBjb21wbGV0ZWQK
CkJ5IGxvb2tpbmcgYXQgdGhlIHVwbG9hZCBzaXplIHJlc3RyaWN0aW9uIHNldCBieSB0aGUgSU1B
UCBzZXJ2ZXIsIGNsaWVudApNVVNUIG5vdCB0cnkgdG8gdXBsb2FkIG1haWwgbW9yZSB0aGFuIGFk
dmVydGlzZWQgbGltaXQgaW4gdGhlIEFQUEVORApjb21tYW5kLiAKCjMuIE1haWxib3ggc3BlY2lm
aWMgQVBQRU5ETElNSVQKCklNQVAgc2VydmVyIGNhbiBzdGlsbCBoYXZlIG1haWxib3ggc3BlY2lm
aWMgQVBQRU5ETElNSVQgcmVzdHJpY3Rpb24sCndoaWNoIG1heSBub3QgYmUgYWR2ZXJ0aXNlZCBh
cyBwYXJ0IG9mIENBUEFCSUxJVFkgcmVzcG9uc2UuICBJbiB0aGlzCmNhc2UsIGNsaWVudCBjYW4g
aXNzdWUgU0VMRUNUL0VYQU1JTkUgY29tbWFuZCB0byBnZXQgdGhlIHBlciBtYWlsYm94CnNwZWNp
ZmljIGxpbWl0IHNldCBieSB0aGUgc2VydmVyLiAgU2ltaWxhcmx5LCBpZiBjbGllbnQgd2lzaCB0
byBrbm93CnRoZSBtYWlsYm94IHNwZWNpZmljIGxpbWl0IGluIGF1dGhlbnRpY2F0ZWQgc3RhdGUs
IGNhbiBiZSBkb25lIGJ5Cmlzc3VpbmcgdGhlIExJU1QgY29tbWFuZCBpbiBjb21iaW5hdGlvbiB3
aXRoIFNUQVRVUyBjb21tYW5kLgoKCgpKYXlhbnRoZWVzaCAmIE5hcmVuZHJhICAgICAgIEV4cGly
ZXMgSnVuZSwgMjAxNSAgICAgICAgICAgICAgW1BhZ2UgM10KDApJbnRlcm5ldC1EcmFmdCAgICAg
ICAgICAgICAgIElNQVAgQVBQRU5ETElNSVQgICAgICAgICAgIERlY2VtYmVyIDIwMTQKCjMuMSBT
RUxFQ1QgcmVzcG9uc2UKCkNsaWVudCBjYW4gZ2V0IHRoZSBwZXIgbWFpbGJveCBhcHBlbmQgbGlt
aXQgYnkgaXNzdWluZyB0aGUgU0VMRUNULwpFWEFNSU5FIGNvbW1hbmQuICBBUFBFTkRMSU1JVCBz
aXplIHRvIHRoaXMgbWFpbGJveCBpcyBvYnRhaW5lZCBhcyBwYXJ0Cm9mIHVudGFnZ2VkIE9LIHJl
c3BvbnNlLiAgSW4gdGhpcyBjYXNlLCB0aGlzIEFQUEVORExJTUlUIHZhbHVlIHdpbGwKc3VwZXJz
ZWRlIHRoZSB2YWx1ZSByZWNlaXZlZCBhcyBwYXJ0IG9mIENBUEFCSUxJVFkgcmVzcG9uc2UuICBJ
ZiBubwpwZXItbWFpbGJveCBBUFBFTkRMSU1JVCBpcyBzcGVjaWZpZWQgZm9yIGEgZm9sZGVyLCBi
dXQgdGhlIHNlcnZlciBkaWQKc3BlY2lmeSBhIGNvbW1vbiBBUFBFTkRMSU1JVCBpbiB0aGUgQ0FQ
QUJJTElUWSByZXNwb25zZSwgdGhlbiB0aGUKY29tbW9uIEFQUEVORExJTUlUIGFwcGxpZXMgdG8g
dGhhdCBmb2xkZXIuCgpDOiB0MiBTRUxFQ1QgSU5CT1gKUzogKiAxNzIgRVhJU1RTClM6ICogT0sg
W0FQUEVORExJTUlUIDI1Nzg5MF0gTWF4aW11bSB1cGxvYWQgbGltaXQKUzogWy4uLl0KUzogdDIg
T0sgW1JFQUQtV1JJVEVdIFNFTEVDVCBjb21wbGV0ZWQKCgpJbiB0aGUgYWJvdmUgZXhhbXBsZSwg
QVBQRU5ETElNSVQgcmVwcmVzZW50cyB0aGUgbWF4aW11bSB1cGxvYWQgc2l6ZSBmb3IKdGhpcyBt
YWlsYm94LgoKT0sgW0FQUEVORExJTUlUIDxuPl0gTWF4aW11bSB1cGxvYWQgbGltaXQgZm9yIHRo
aXMgbWFpbGJveCwgaW4gYnl0ZXMuCiAgICAgICAgICAgICAgICAgICAgIFJlZmVyIHRvIHNlY3Rp
b24gNSBmb3IgbW9yZSBpbmZvcm1hdGlvbi4gIElmIHRoaXMKICAgICAgICAgICAgICAgICAgICAg
aXMgbWlzc2luZywgdGhlIGNsaWVudCBjYW4gYWx3YXlzIGhvbm91ciB0aGUKICAgICAgICAgICAg
ICAgICAgICAgdmFsdWUgcmVjZWl2ZWQgYXMgcGFydCBvZiBDQVBBQklMSVRZIHJlc3BvbnNlLgoK
CjMuMiBMSVNUIHJlc3BvbnNlCgpJTUFQIGNsaWVudCBjYW4gZ2V0IHRoZSBtYWlsYm94IHNwZWNp
ZmljIEFQUEVORExJTUlUIGluIGF1dGhlbnRpY2F0ZWQKc3RhdGUsIHdoZXJlIGl0IGRvIG5vdCBu
ZWVkIHRvIGlzc3VlIFNFTEVDVC9FWEFNSU5FIGNvbW1hbmQuICBMSVNUCmNvbW1hbmQgaW4gY29t
YmluYXRpb24gd2l0aCBTVEFUVVMgY29tbWFuZCBjYW4gYmUgaXNzdWVkIHRvIGdldCB0aGUgcGVy
Cm1haWxib3ggc3BlY2lmaWMgQVBQRU5ETElNSVQgc2V0IGJ5IHRoZSBzZXJ2ZXIuICBSZWZlciBS
RkMgNTgxOSBmb3IgdGhlCnVzYWdlIG9mIExJU1QgY29tbWFuZCBpbiBjb21iaW5hdGlvbiB3aXRo
IFNUQVRVUyBjb21tYW5kLiAgTm90ZSB0aGF0IGEKc2VydmVyIGltcGxlbWVudGluZyB0aGlzIGV4
dGVuc2lvbiwgaXMgc3ludGFjdGljYWxseSBjb21wYXRpYmxlIHdpdGgKUkZDIDU4MTksIGhvd2V2
ZXIgc3VwcG9ydCBmb3IgUkZDIDUyNTggb3IgUkZDIDU4MTkgaXMgbm90IHJlcXVpcmVkLAp3aGVu
IGltcGxlbWVudGluZyB0aGlzIGV4dGVuc2lvbi4KClRoZSBmb2xsb3dpbmcgZXhhbXBsZSBkZW1v
bnN0cmF0ZXMsIGl0cyB1c2FnZS4KCkM6IHQxIExJU1QgIiIgJSBSRVRVUk4gKFNUQVRVUyAoQVBQ
RU5ETElNSVQpKQpTOiAqIExJU1QgKCkgIi4iICAiSU5CT1giClM6ICogU1RBVFVTICJJTkJPWCIg
KEFQUEVORExJTUlUIDI1Nzg5MCkKUzogdDEgT0sgTGlzdCBjb21wbGV0ZWQuCgpOZXcgYXR0cmli
dXRlIEFQUEVORExJTUlUIGlzIGFkZGVkIHRvIGdldCB0aGUgbGltaXQgc2V0IGJ5IHRoZSBzZXJ2
ZXIKZm9yIHRoaXMgbWFpbGJveCBhcyBwYXJ0IG9mIFNUQVRVUyBjb21tYW5kLiAgVGhlIFNUQVRV
UyByZXNwb25zZSBvY2N1cnMKYXMgYSByZXN1bHQgb2YgYW4gU1RBVFVTIGNvbW1hbmQuICBJdCBy
ZXR1cm5zIHRoZSBtYWlsYm94IG5hbWUgdGhhdAoKSmF5YW50aGVlc2ggJiBOYXJlbmRyYSAgICAg
ICBFeHBpcmVzIEp1bmUsIDIwMTUgICAgICAgICAgICAgIFtQYWdlIDRdCgwKSW50ZXJuZXQtRHJh
ZnQgICAgICAgICAgICAgICBJTUFQIEFQUEVORExJTUlUICAgICAgICAgICBEZWNlbWJlciAyMDE0
CgptYXRjaGVzIHRoZSBTVEFUVVMgc3BlY2lmaWNhdGlvbiBhbmQgdGhlIHJlcXVlc3RlZCBtYWls
Ym94IHN0YXR1cwppbmZvcm1hdGlvbi4gIElNQVAgc2VydmVyIHNob3VsZCByZWNvZ25pemUgYW4g
ZXh0cmEgIlJFVFVSTiAoU1RBVFVTCiAoQVBQRU5ETElNSVQpKSIgYXQgdGhlIGVuZCBvZiBhIExJ
U1QgY29tbWFuZCBhbmQgZW1pdCBhbiBleHRyYSBTVEFUVVMKcmVzcG9uc2UgZm9yIGVhY2ggbWF0
Y2hpbmcgbWFpbGJveC4gIFJlZmVyIHRvIHNlY3Rpb24gNSBmb3IgdGhlIHN5bnRheC4KCkludm9r
aW5nIFNUQVRVUyBjb21tYW5kIHdpdGggQVBQRU5ETElNSVQgaXMgYWxzbyBhY2NlcHRhYmxlLiAg
QmVsb3cKZXhhbXBsZSBkZW1vbnN0cmF0ZXMsIGl0cyB1c2FnZS4KCkM6IHQxIFNUQVRVUyBJTkJP
WCAoQVBQRU5ETElNSVQpClM6ICogU1RBVFVTIElOQk9YIChBUFBFTkRMSU1JVCAyNTc4OTApClM6
IHQxIE9LIFNUQVRVUyBjb21wbGV0ZWQKCjQuIEFQUEVORCByZXNwb25zZQoKSWYgY2xpZW50IHVw
bG9hZHMgYSBtYWlsIHdoaWNoIGV4Y2VlZHMgdGhlIG1heGltdW0gdXBsb2FkIHNpemUgc2V0CnRv
IHRoYXQgbWFpbGJveCwgdGhlbiBzZXJ2ZXIgU0hBTEwgcmVqZWN0IHRoZSBBUFBFTkQgY29tbWFu
ZCB3aXRoIGEKdGFnZ2VkIFRPT0JJRyByZXNwb25zZSBjb2RlLiAgUmVmZXIgUkZDIDQ0NjkgU2Vj
dGlvbiAoNCkgZm9yIHZhcmlvdXMKQVBQRU5EIHJlc3BvbnNlIGNvZGVzIGFuZCBpdHMgaGFuZGxp
bmcuCgpDbGllbnQgY2FuIGF2b2lkIHVzZSBvZiBMSVRFUkFMKywgd2hlbiBtYXhpbXVtIHVwbG9h
ZCBzaXplCnN1cHBvcnRlZCBieSB0aGUgSU1BUCBzZXJ2ZXIgaXMgdW5rbm93bi4gCgo1LiBGb3Jt
YWwgc3ludGF4CgpUaGUgZm9sbG93aW5nIHN5bnRheCBzcGVjaWZpY2F0aW9uIHVzZXMgdGhlIEF1
Z21lbnRlZCBCYWNrdXMtTmF1cgpGb3JtIChBQk5GKSBub3RhdGlvbiBhcyBzcGVjaWZpZWQgaW4g
W1JGQzUyMzRdIGluY2x1ZGluZyB0aGUgY29yZQpydWxlcyBpbiBBcHBlbmRpeCBCLjEuICBbUkZD
MzUwMV0gZGVmaW5lcyB0aGUgbm9uLXRlcm1pbmFscwoiY2FwYWJpbGl0eSIsICJyZXNwLXRleHQt
Y29kZSIgYW5kICJzdGF0dXMtYXR0Ii4KRXhjZXB0IGFzIG5vdGVkIG90aGVyd2lzZSwgYWxsIGFs
cGhhYmV0aWMgY2hhcmFjdGVycyBhcmUgY2FzZS0KaW5zZW5zaXRpdmUuICBUaGUgdXNlIG9mIHVw
cGVyIG9yIGxvd2VyIGNhc2UgY2hhcmFjdGVycyB0byBkZWZpbmUKdG9rZW4gc3RyaW5ncyBpcyBm
b3IgZWRpdG9yaWFsIGNsYXJpdHkgb25seS4gIEltcGxlbWVudGF0aW9ucyBNVVNUCmFjY2VwdCB0
aGVzZSBzdHJpbmdzIGluIGEgY2FzZS1pbnNlbnNpdGl2ZSBmYXNoaW9uLgogICAgCmFwcGVuZGxp
bWl0LWNhcCA9ICJBUFBFTkRMSU1JVCIgWyI9IiBuei1udW1iZXJdCmNhcGFiaWxpdHkgLz0gYXBw
ZW5kbGltaXQtY2FwCgphcHBlbmRsaW1pdC1yZXNwY29kZSA9ICJBUFBFTkRMSU1JVCIgU1Agbnot
bnVtYmVyCnJlc3AtdGV4dC1jb2RlIC89IGFwcGVuZGxpbWl0LXJlc3Bjb2RlCgphcHBlbmRsaW1p
dC1zdGF0dXMtYXR0ID0gIkFQUEVORExJTUlUIgpzdGF0dXMtYXR0IC89YXBwZW5kbGltaXQtc3Rh
dHVzLWF0dAoKQSBub24temVybyBudW1iZXIgaW5kaWNhdGluZyB0aGUgZml4ZWQgbWF4aW11bSBt
ZXNzYWdlIHNpemUgaW4gYnl0ZXMKdGhhdCB0aGUgc2VydmVyIHdpbGwgYWNjZXB0LiAgVGhlIHN5
bnRheCBvZiB0aGUgcGFyYW1ldGVyIGZvbGxvd3MgdGhlCmF1Z21lbnRlZCBCTkYgbm90YXRpb24g
b2YgW1JGQzUyMzRdLiAgSWYgdGhpcyBjYXBhYmlsaXR5IGlzCm9taXR0ZWQsIG5vIGluZm9ybWF0
aW9uIGlzIGNvbnZleWVkIGFib3V0IHRoZSBzZXJ2ZXIncyBmaXhlZCBtYXhpbXVtCm1haWwgdXBs
b2FkIHNpemUuCgpKYXlhbnRoZWVzaCAmIE5hcmVuZHJhICAgICAgIEV4cGlyZXMgSnVuZSwgMjAx
NSAgICAgICAgICAgICAgW1BhZ2UgNV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIElN
QVAgQVBQRU5ETElNSVQgICAgICAgICAgIERlY2VtYmVyIDIwMTQKCjYuIFNlY3VyaXR5IENvbnNp
ZGVyYXRpb24KCkl0IGlzIGJlbGlldmVkIHRoYXQgdGhpcyBleHRlbnNpb24gZG9lc24ndCBhZGQg
YW55IG5ldyBzZWN1cml0eQpjb25zaWRlcmF0aW9ucyB0aGF0IGFyZSBub3QgYWxyZWFkeSBwcmVz
ZW50IGluIHRoZSBiYXNlIElNQVAKcHJvdG9jb2wgW1JGQzM1MDFdLgoKNy4gSUFOQSBDb25zaWRl
cmF0aW9ucwoKVGhlIElBTkEgaXMgcmVxdWVzdGVkIHRvIGFkZCBBUFBFTkRMSU1JVCB0byB0aGUg
SU1BUDQgQ2FwYWJpbGl0aWVzClJlZ2lzdHJ5LiAgW1tOb3RlIHRvIFJGQy1lZGl0b3I6IHBsZWFz
ZSByZW1vdmUgdGhlIGZvbGxvd2luZyBiZWZvcmUKcHVibGljYXRpb246IFRoaXMgcmVnaXN0cmF0
aW9uIHNob3VsZCB0YWtlIHBsYWNlIGF0IHRoZSBmb2xsb3dpbmcKbG9jYXRpb246IGh0dHA6Ly93
d3cuaWFuYS5vcmcvYXNzaWdubWVudHMvaW1hcDQtY2FwYWJpbGl0aWVzXV0KCjguIFJlZmVyZW5j
ZXMKCjguMSBOb3JtYXRpdmUgUmVmZXJlbmNlcwoKVGhlIGZvbGxvd2luZyBkb2N1bWVudHMgY29u
dGFpbiBkZWZpbml0aW9ucyBvciBzcGVjaWZpY2F0aW9ucyB0aGF0CmFyZSBuZWNlc3NhcnkgdG8g
dW5kZXJzdGFuZCB0aGlzIGRvY3VtZW50IHByb3Blcmx5CgpbUkZDMjExOV0gIEJyYWRuZXIsICJL
ZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNzIHRvIEluZGljYXRlCiAgICAgICAgICAgUmVxdWlyZW1l
bnQgTGV2ZWxzIiwgUkZDIDIxMTksIEhhcnZhcmQgVW5pdmVyc2l0eSwgTWFyY2gKICAgICAgICAg
ICAxOTk3LgogICAgICAgICAgIApbUkZDMzUwMV0gIENyaXNwaW4sICJJTlRFUk5FVCBNRVNTQUdF
IEFDQ0VTUyBQUk9UT0NPTCAtIFZFUlNJT04gNHJldjEiLAogICAgICAgICAgIFVuaXZlcnNpdHkg
b2YgV2FzaGluZ3RvbiwgTWFyY2ggMjAwMwoKW1JGQzUyMzRdICBDcm9ja2VyLCBPdmVyZWxsLCAi
QXVnbWVudGVkIEJORiBmb3IgU3ludGF4CiAgICAgICAgICAgU3BlY2lmaWNhdGlvbnM6IEFCTkYi
LCBSRkMgNTIzNCwgQnJhbmRlbmJ1cmcKICAgICAgICAgICBJbnRlcm5ldHdvcmtpbmcsIERlbW9u
IEludGVybmV0IEx0ZCwgSmFudWFyeSAyMDA4CgpbUkZDNTMyMl0gIFAuIFJlc25pY2ssIEVkLCAi
SW50ZXJuZXQgTWVzc2FnZSBGb3JtYXQiLCBSRkMgNTMyMiwKICAgICAgICAgICBRdWFsY29tbSBJ
bmNvcnBvcmF0ZWQsIE9jdG9iZXIgMjAwOAoKW1JGQzIwODhdICBKLiBNeWVycywgQ2FybmVnaWUg
TWVsbG9uLCAiSU1BUDQgbm9uLXN5bmNocm9uaXppbmcKICAgICAgICAgICBsaXRlcmFscyIsICBK
YW51YXJ5IDE5OTcKCQkgICAKW1JGQzQ0NjldICBQLiBSZXNuaWNrLCAiSW50ZXJuZXQgTWVzc2Fn
ZSBBY2Nlc3MgUHJvdG9jb2wgKElNQVApCiAgICAgICAgICAgQ0FURU5BVEUgRXh0ZW5zaW9uIiwg
IEFwcmlsIDIwMDYKCQkgICAKW1JGQzU4MTldICBBLiBNZWxuaWtvdiwgVC4gU2lyYWluZW4sICJJ
TUFQNCBFeHRlbnNpb24gZm9yIFJldHVybmluZwogICAgICAgICAgIFNUQVRVUyBJbmZvcm1hdGlv
biBpbiBFeHRlbmRlZCBMSVNUIiwgIE1hcmNoIDIwMTAKCQkgICAKW1JGQzUyNThdICBBLiBNZWxu
aWtvdiwgQi4gTGVpYmEsICJJbnRlcm5ldCBNZXNzYWdlIEFjY2VzcyBQcm90b2NvbAogICAgICAg
ICAgIHZlcnNpb24gNCAtIExJU1QgQ29tbWFuZCBFeHRlbnNpb25zIiwgIE1hcmNoIDIwMTAKCgoJ
CSAgIApKYXlhbnRoZWVzaCAmIE5hcmVuZHJhICAgICAgIEV4cGlyZXMgSnVuZSwgMjAxNSAgICAg
ICAgICAgICAgIFtQYWdlIDZdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICBJTUFQIEFQ
UEVORExJTUlUICAgICAgICAgICBEZWNlbWJlciAyMDE0CgkJICAgCjguIDIgSW5mb3JtYXRpdmUg
UmVmZXJlbmNlcwoKVGhlIGZvbGxvd2luZyBkb2N1bWVudHMgZGVzY3JpYmUgcmVsYXRlZCBwcm90
b2NvbHM6CgpbUkZDMjA4N10gIE15ZXJzLCBKLiwgIklNQVA0IFFVT1RBIGV4dGVuc2lvbiIsIFJG
QyAyMDg3LAogICAgICAgICAgIEphbnVhcnkgMTk5NwoKW1JGQzczNzddICBCLiBMZWliYSwgQS4g
TWVsbmlrb3YsICJJTUFQNCBNdWx0aW1haWxib3ggU0VBUkNICiAgICAgICAgICAgRXh0ZW5zaW9u
IiwgUkZDIDczNzcsIE9jdG9iZXIgMjAxNAoKOS4gQWNrbm93bGVkZ2VtZW50CgpUQkQKCgoxMC4g
QXV0aG9yJ3MgQWRkcmVzcwoKSmF5YW50aGVlc2ggUyBCClNhbXN1bmcgVGVsZWNvbW11bmljYXRp
b25zIEFtZXJpY2EsCjY4NSBVUyBIaWdod2F5IDIwMi8yMDYsCkJyaWRnZXdhdGVyLCBOSiAwODgw
Ny4KVVNBCkVtYWlsOiBqYXlhbnRoZWVzaC5zYkBnbWFpbC5jb20KCk5hcmVuZHJhIFNpbmdoIEJp
c2h0ClNhbXN1bmcgVGVsZWNvbW11bmljYXRpb25zIEFtZXJpY2EsCjY4NSBVUyBIaWdod2F5IDIw
Mi8yMDYsCkJyaWRnZXdhdGVyLCBOSiAwODgwNy4KVVNBCkVtYWlsOiBuYXJlbmRyYXNpbmdoLmJp
c2h0QGdtYWlsLmNvbQoKCgoKCgoKCgoKCgoKCgoKCgkKCQoJCgkKCgkKCQoJCgkKCQoJCkpheWFu
dGhlZXNoICYgTmFyZW5kcmEgICAgICAgRXhwaXJlcyBNYXksIDIwMTUgICAgICAgICAgICAgICBb
UGFnZSA2XQ==

--_004_02454F842DD7B449B96715A2AD90C0363E99E411exMB5telecomsna_--


From nobody Sat Dec 20 02:44:28 2014
Return-Path: <jkt@flaska.net>
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 A65461A6F3A for <imapext@ietfa.amsl.com>; Sat, 20 Dec 2014 02:44:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.609
X-Spam-Level: 
X-Spam-Status: No, score=-1.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 vgAR4pgmHnVu for <imapext@ietfa.amsl.com>; Sat, 20 Dec 2014 02:44:24 -0800 (PST)
Received: from latimerie.flaska.net (latimerie.flaska.net [IPv6:2a02:2b88:2:1::4a7:333]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A20961A6F30 for <imapext@ietf.org>; Sat, 20 Dec 2014 02:44:24 -0800 (PST)
Received: by latimerie.flaska.net (Postfix, from userid 1000) id CC44D61BC1; Sat, 20 Dec 2014 11:44:19 +0100 (CET)
From: =?iso-8859-1?Q?Jan_Kundr=E1t?= <jkt@flaska.net>
To: <imapext@ietf.org>
Date: Sat, 20 Dec 2014 11:44:20 +0100
User-Agent: Trojita/v0.4.1-435-g0816cec; Qt/4.8.5; X11; Linux; 
MIME-Version: 1.0
Message-ID: <0a852fc9-ad67-4f26-ac3e-68317f5f5d20@flaska.net>
In-Reply-To: <alpine.BSF.2.11.1412191113180.58714@orthanc.ca>
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com> <3b213806-8498-40d5-90fa-bb5483a96879@flaska.net> <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca> <20141219120651.Horde.Rn44KuYQyc2iQlzc5-_fsw1@bigworm.curecanti.org> <alpine.BSF.2.11.1412191113180.58714@orthanc.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/H7uhzUlopeHL30FqVGFYGOcMPLE
Subject: Re: [imapext] =?iso-8859-1?q?client_support_for_RFC_3516_=28BINARY=29?= =?iso-8859-1?q?=3F?=
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, 20 Dec 2014 10:44:26 -0000

On Friday, 19 December 2014 20:58:03 CEST, Lyndon Nerenberg wrote:
> As a purist I would argue the IMAP server should never have=20
> accepted the message to begin with

At the time you do it, your users won't be able to receive mail from the=20
Linux Kernel Mailing Lists. (Actually, just a random portion of these=20
e-mails when the original MUA decided to use the base64 CTE. That's gonna=20
be fun.)

The vger's configuration is of course broken, and unfortunately I've been=20
forwarded a message where they said that they aren't going to fix this=20
after 20 years of operation. I believe Linus has a word for this attitude.

>> Additionally, it might be useful to add implementation note=20
>> that a client should fallback to using FETCH BODY[] if the=20
>> server returns NO.  The MUA that the original reporter is using=20
>> (I don't know what it is) is simply showing a blank body for=20
>> these kind of messages when a FETCH BINARY[] is unsuccessful.

I'm not sure whether you received that report from the same user as I did.=20=

If that is the case, the MUA is Trojita and there was a bug where the error=20=

in FETCH operation wasn't propagated to the GUI in a clear manner, but a=20
spinner was kept running. It now at least shows an error message.

> This is so stunningly obvious it doesn't deserve mentioning.

Is it? There are just two widely used CTEs which require decoding, the=20
base64 and the quoted-printable, and RFC2045 contains a pretty strong=20
language against developing any additional CTEs.

Is there a realistic assumption that there's an IMAP server which:

- declares support for BINARY,
- cannot decode base64 or quoted-printable encoding,
- can handle that situation gracefully, without crashing,
- and client's local decoder would be able to cope with the malformed=20
content?

By all means, sure, it will improve robustness to retry with a FETCH after=20=

a BINARY failed. I'm just saying that it was sufficiently non-obvious at=20
the time I added BINARY support, and even now I have my doubts on whether=20
my local decoder is going to be any better than e.g. Dovecot's.

On a quick look at its source, the decoder library which Trojita uses (Qt's=20=

QByteArray::fromBase64) appears to handle garbage in base64 data in=20
accordance with RFC2045 which calls for ignoring any character that cannot=20=

be decoded. It doesn't appear to have any special handling of the =3D=3D=20
padding, which is in strong constrast to Python where the base64 module=20
stops decoding when it hits the first padding. I wonder which approach is=20
better.

With kind regards,
Jan

--=20
Trojit=C3=A1, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/


From nobody Sat Dec 20 09:26:41 2014
Return-Path: <slusarz@horde.org>
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 2DBDF1A8A28 for <imapext@ietfa.amsl.com>; Sat, 20 Dec 2014 09:26:38 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=unavailable
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 0sxljKwi7bpM for <imapext@ietfa.amsl.com>; Sat, 20 Dec 2014 09:26:27 -0800 (PST)
Received: from resqmta-po-07v.sys.comcast.net (resqmta-po-07v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:166]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CEB31A1AA0 for <imapext@ietf.org>; Sat, 20 Dec 2014 09:26:26 -0800 (PST)
Received: from resomta-po-19v.sys.comcast.net ([96.114.154.243]) by resqmta-po-07v.sys.comcast.net with comcast id VtSD1p0025FMDhs01tSSLl; Sat, 20 Dec 2014 17:26:26 +0000
Received: from bigworm.curecanti.org ([67.176.83.228]) by resomta-po-19v.sys.comcast.net with comcast id VtSR1p00E4vagWz01tSRlV; Sat, 20 Dec 2014 17:26:26 +0000
Received: from bigworm.curecanti.org (localhost.localdomain [IPv6:::1]) (Authenticated sender: slusarz) by bigworm.curecanti.org (Postfix) with ESMTPSA id 188DF6809B for <imapext@ietf.org>; Sat, 20 Dec 2014 10:26:25 -0700 (MST)
Received: from dangerzone.curecanti.org (dangerzone.curecanti.org [172.18.5.4]) by bigworm.curecanti.org (Horde Framework) with HTTP; Sat, 20 Dec 2014 10:26:24 -0700
Date: Sat, 20 Dec 2014 10:26:24 -0700
Message-ID: <20141220102624.Horde.yvI5fnFlM6Dzk53oMKLT3A1@bigworm.curecanti.org>
From: Michael M Slusarz <slusarz@horde.org>
To: imapext@ietf.org
References: <CACU8CfQCv6KfZudHreUkvZWBDh94DcgLAL6mRK8PTx3yTbiTNg@mail.gmail.com> <CACU8CfRev=un=YL+bZ4RikynepWdeEhJKGFRRiQ0tsFT_TOXug@mail.gmail.com> <3b213806-8498-40d5-90fa-bb5483a96879@flaska.net> <40B54DF7-701F-4259-84C2-ED8D57CD3CE9@orthanc.ca> <20141219120651.Horde.Rn44KuYQyc2iQlzc5-_fsw1@bigworm.curecanti.org> <alpine.BSF.2.11.1412191113180.58714@orthanc.ca>
In-Reply-To: <alpine.BSF.2.11.1412191113180.58714@orthanc.ca>
User-Agent: Horde Application Framework 5
Accept-Language: en
X-Originating-IP: 172.18.5.4
X-Remote-Browser: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1419096386; bh=qlfUFsW/21ByUSloNOVhKZ5LKCQLAldyd9BtJmE3IWE=; h=Received:Received:Received:Received:Date:Message-ID:From:To: Subject:Content-Type:MIME-Version; b=kHDu1YFimt5lZhq6OFwQUPjlQCY49hOIRlSP5rBdlnZyW6xfH8clXboSPFvEJ2POC VXMgNzkrTvdOfnPE0W2I/DYTEg5/KeFMuV+KGwbZVoeFp24EXyGzCe0K4qq5/FJwIo KqwAhu+Tx1gB1sLIfNgXnUSft4lQnRzuUfihJZpSIhlTxOuYMontURl1MFj796+9Cp rAr5ONyj12O0r0NaXind6yi6eDMDqzL9i99LLsVce5deKLmMvQOaa1RJ9Xm0tdoZEu PmFpK1HYxDTc5fTjPnITNh9Ho66BhapJ5ecKurUNKNDCAej+aaXpEOh5c90pihHYAG NS01FvfBo4aLg==
Archived-At: http://mailarchive.ietf.org/arch/msg/imapext/QpX_N5gJqPK5BAP22FYPNuS0mqo
Subject: Re: [imapext] client support for RFC 3516 (BINARY)?
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, 20 Dec 2014 17:26:38 -0000

Quoting Lyndon Nerenberg <lyndon@orthanc.ca>:

> At the moment, I'm not sure there is any way out of this other than  
> for a server supporting BINARY to validate the CTEs at injection  
> time, and reject any messages with content encoding violations.  I  
> don't think there is any way for a server that discovers bad base64  
> in the middle of a BINARY FETCH to recover gracefully.

For performance reasons, I would assume most servers are scanning for  
RFC 822 structure but not parsing the actual MIME data until a BINARY  
command is received.  So requiring rejection at injection time would  
be quite a performance hit, with no guarantee that the client will  
ever use BINARY.

> I *adamantly* oppose any notion of passing through anything that  
> fails the CTE decoding, as this presents a wonderful opportunity for  
> malicious code injection into a naive client implementation.  In  
> light of that security concern alone, I don't think there is any  
> alternative but to add a "server MUST validate the body content  
> correctly decodes before transmitting the decoded content to the  
> client" or words to that effect to the BINARY specification.  If  
> this is done at message injection time, the overhead will be  
> minimal, and would allow the server to refuse to accept the message.  
>  If implementers are insistent about accepting such malformed  
> content, then we will have to add something like an  
> [INVALID-CTE-SYNTAX] respose code so the server can send back "foo  
> NO [INVALID-CTE-SYNTAX]" when the runtime check fails.

I would think that many/most server implementers would take this  
approach instead, since it is much easier.  And I'm not sure I would  
disagree for performance reasons, not to mention that this appears to  
be the way that many of the BINARY servers currently operate.

As far as INVALID-CTE-SYNTAX ... do we need an additional response  
code?  I feel that UNKNOWN-CTE works here also (although the semantics  
might be a bit off).

 From a client perspective it just needs to know that data does exist  
in that part but it is due to some sort of decoding error, rather than  
the fact that the part doesn't exist for example, that is causing the  
data to not be displayed.  The actual reason the data can't be decoded  
is irrelevant for the client; it just needs to know that it may be  
able to display the content somehow using it's own algorithms to deal  
with broken data.

michael

___________________________________
Michael Slusarz [slusarz@horde.org]

