From atlauren@uci.edu Fri May 31 14:35:11 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 115C121F8651 for ; Fri, 31 May 2013 14:35:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.185 X-Spam-Level: X-Spam-Status: No, score=-4.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFw3NR0oEI41 for ; Fri, 31 May 2013 14:35:03 -0700 (PDT) Received: from exchange.uci.edu (cas10.ad.uci.edu [128.200.73.80]) by ietfa.amsl.com (Postfix) with ESMTP id BD21E21F8607 for ; Fri, 31 May 2013 14:34:57 -0700 (PDT) Received: from MBS2.ad.uci.edu ([128.200.73.76]) by CAS10.ad.uci.edu ([128.200.73.80]) with mapi id 14.02.0328.011; Fri, 31 May 2013 14:34:53 -0700 From: Andrew Laurence To: "imapext@ietf.org" Thread-Topic: Microsoft invites input on standards for Exchange/Outlook Thread-Index: Ac5eRqx3S2UG+hIaSMm5tpqdLvVuHw== Date: Fri, 31 May 2013 21:34:52 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.195.168.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 01 Jun 2013 18:03:49 -0700 Subject: [imapext] Microsoft invites input on standards for Exchange/Outlook X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 21:49:39 -0000 Hi all, I thought this would be noteworthy in this group: http://blogs.technet.com/b/openness/archive/2013/05/31/feedback-exchange-se= rver-and-outlook-standards.aspx --=20 Andrew Laurence Office of Information Technology=20 atlauren@uci.edu University of California, Irvine From atlauren@me.com Tue Jun 4 14:46:02 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6338821F8B04 for ; Tue, 4 Jun 2013 14:46:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.391 X-Spam-Level: X-Spam-Status: No, score=-5.391 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fs0zF-lxmnwI for ; Tue, 4 Jun 2013 14:45:55 -0700 (PDT) Received: from st11p01mm-asmtp001.mac.com (st11p01mm-asmtpout001.mac.com [17.172.204.236]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB5121F9989 for ; Tue, 4 Jun 2013 14:44:14 -0700 (PDT) Received: from st11p01mm-spool002.mac.com ([17.172.204.247]) by st11p01mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.05(7.0.4.27.4) 64bit (built Apr 23 2013)) with ESMTP id <0MNW006YR1PB4Y40@st11p01mm-asmtp001.mac.com> for imapext@ietf.org; Tue, 04 Jun 2013 21:44:10 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626,1.0.431,0.0.0000 definitions=2013-06-04_08:2013-06-04, 2013-06-04, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=2 spamscore=2 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1305010000 definitions=main-1306040220 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_7e9oYIDRKclQSV2rLLMb+w)" Received: from localhost ([17.172.205.17]) by st11p01mm-spool002.mac.com (Oracle Communications Messaging Server 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNW00D8X1PF6R10@st11p01mm-spool002.mac.com> for imapext@ietf.org; Tue, 04 Jun 2013 21:44:03 +0000 (GMT) To: imapext@ietf.org From: Andrew Laurence Date: Tue, 04 Jun 2013 21:44:03 +0000 (GMT) X-Mailer: iCloud Mail (1Q) X-Originating-IP: [128.195.168.36] Message-id: <8abc3ae3-a966-46f2-a36a-193e750d463d@me.com> Subject: [imapext] Support for RFC 2971 "ID" X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 21:46:02 -0000 --Boundary_(ID_7e9oYIDRKclQSV2rLLMb+w) Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: quoted-printable Hi all, Which servers and clients are known to support the 2971 "ID" extension? I= can tell that Gmail supports it, not sure about other servers, nor client= s.=EF=BB=BF --=20 Andrew Laurence atlauren@me.com (Lists) atlauren@uci.edu (Main email)= --Boundary_(ID_7e9oYIDRKclQSV2rLLMb+w) Content-type: multipart/related; boundary="Boundary_(ID_UZxcE/7md9FYijBCbPfnUg)"; type="text/html" --Boundary_(ID_UZxcE/7md9FYijBCbPfnUg) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT
Hi all,

Which servers and clients are known to support the 2971 "ID" extension?  I can tell that Gmail supports it, not sure about other servers, nor clients.
-- 
Andrew Laurence
atlauren@me.com (Lists)
atlauren@uci.edu (Main email)
--Boundary_(ID_UZxcE/7md9FYijBCbPfnUg)-- --Boundary_(ID_7e9oYIDRKclQSV2rLLMb+w)-- From adrien@qbik.com Tue Jun 4 14:49:02 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D834F21F8B04 for ; Tue, 4 Jun 2013 14:49:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.739 X-Spam-Level: X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wSD+kEJHdqmo for ; Tue, 4 Jun 2013 14:48:56 -0700 (PDT) Received: from smtp.qbik.com (smtp.qbik.com [210.55.214.35]) by ietfa.amsl.com (Postfix) with ESMTP id 4B9D221F8168 for ; Tue, 4 Jun 2013 14:48:56 -0700 (PDT) Received: From SCREECH.qbik.local (unverified [192.168.0.4]) by SMTP Server [192.168.0.1] (WinGate SMTP Receiver v8.0.0 (Build 4556)) with SMTP id <0019708862@smtp.qbik.com>; Wed, 05 Jun 2013 09:48:54 +1200 Received: From [192.168.0.23] (unverified [192.168.0.23]) by SMTP Server [192.168.0.4] (WinGate SMTP Receiver v8.0.0 (Build 4555)) with SMTP id <0000218392@SCREECH.qbik.local>; Wed, 05 Jun 2013 09:48:53 +1200 From: "Adrien W. de Croy" To: "Andrew Laurence" , "imapext@ietf.org" Date: Tue, 04 Jun 2013 21:48:51 +0000 Content-Type: multipart/alternative; boundary="------=_MB110D076C-C576-43C2-958D-18ADD3994A44" In-Reply-To: <8abc3ae3-a966-46f2-a36a-193e750d463d@me.com> Message-Id: Mime-Version: 1.0 User-Agent: eM_Client/5.0.18025.0 Subject: Re: [imapext] Support for RFC 2971 "ID" X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: "Adrien W. de Croy" List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 21:49:03 -0000 --------=_MB110D076C-C576-43C2-958D-18ADD3994A44 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; format=flowed; charset=utf-8 we (WinGate) do. Also iOS clients, and emClient for clients I know that do. Adrien ------ Original Message ------ From: "Andrew Laurence" To: "imapext@ietf.org" Sent: 5/06/2013 9:44:03 a.m. Subject: [imapext] Support for RFC 2971 "ID" >Hi all, > >Which servers and clients are known to support the 2971 "ID" extension?= =20 > I can tell that Gmail supports it, not sure about other servers, nor=20 >clients. >-- Andrew Laurence atlauren@me.com (Lists) atlauren@uci.edu (Main=20 >email) --------=_MB110D076C-C576-43C2-958D-18ADD3994A44 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
we (WinGate) do.
 
Also iOS clients, and emClient for clients I know that do.
 
Adrien
 
 
------ Original Message ------
From: "Andrew Laurence" <atlaure= n@me.com>
To: "imapext@ietf.org" <imapext= @ietf.org>
Sent: 5/06/2013 9:44:03 a.m.
Subject: [imapext] Support for RFC 2971 "ID"
Hi all,

Which servers and clients are known to support the 2971= "ID" extension?  I can tell that Gmail supports it, not sure about= other servers, nor clients.
atlauren@me.com (Lists)
atlauren@uci.edu (Main email)
=
--------=_MB110D076C-C576-43C2-958D-18ADD3994A44-- From bienvenu@davidbienvenu.org Tue Jun 4 15:00:56 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A57E421F9339 for ; Tue, 4 Jun 2013 15:00:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id amq+HW-amSWw for ; Tue, 4 Jun 2013 15:00:51 -0700 (PDT) Received: from homiemail-a32.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB1021F96DF for ; Tue, 4 Jun 2013 15:00:41 -0700 (PDT) Received: from homiemail-a32.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a32.g.dreamhost.com (Postfix) with ESMTP id B9D84584076 for ; Tue, 4 Jun 2013 15:00:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=davidbienvenu.org; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type; s=davidbienvenu.org; bh=gqcBTfv8T4KfA P2Ndn5bdIFKpuk=; b=zy3W+TMDcWNSs91YpgpMu3R/D0nOjNXdnb7o2u5NEvOqM OtQcMprH93KCDjpQvbbs3OQaxNKWY5Ujxk/JgfhKXCLyylcEvjrLcSFcjeQAvQA3 G3NPNUCxtaUk0eHe93qlnei9GlJkQ8QQfXZAyUkH8Cx7O9PuPSltrprW60dBzU= Received: from davidbienvenu.sfo.corp.google.com (unknown [72.14.229.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: bienvenu@davidbienvenu.org) by homiemail-a32.g.dreamhost.com (Postfix) with ESMTPSA id A84ED584058 for ; Tue, 4 Jun 2013 15:00:26 -0700 (PDT) Message-ID: <51AE6378.40701@davidbienvenu.org> Date: Tue, 04 Jun 2013 15:00:24 -0700 From: David Bienvenu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: imapext@ietf.org References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------030402040804030007090904" Subject: Re: [imapext] Support for RFC 2971 "ID" X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 22:00:56 -0000 This is a multi-part message in MIME format. --------------030402040804030007090904 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thunderbird client supports it. - David On 06/04/2013 02:48 PM, Adrien W. de Croy wrote: > we (WinGate) do. > Also iOS clients, and emClient for clients I know that do. > Adrien > ------ Original Message ------ > From: "Andrew Laurence" > > To: "imapext@ietf.org" > > Sent: 5/06/2013 9:44:03 a.m. > Subject: [imapext] Support for RFC 2971 "ID" >> Hi all, >> >> Which servers and clients are known to support the 2971 "ID" >> extension? I can tell that Gmail supports it, not sure about other >> servers, nor clients. >> -- >> Andrew Laurence >> atlauren@me.com (Lists) >> atlauren@uci.edu (Main email) > > > _______________________________________________ > imapext mailing list > imapext@ietf.org > https://www.ietf.org/mailman/listinfo/imapext --------------030402040804030007090904 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Thunderbird client supports it.

- David

On 06/04/2013 02:48 PM, Adrien W. de Croy wrote:
we (WinGate) do.
 
Also iOS clients, and emClient for clients I know that do.
 
Adrien
 
 
------ Original Message ------
From: "Andrew Laurence" <atlauren@me.com>
Sent: 5/06/2013 9:44:03 a.m.
Subject: [imapext] Support for RFC 2971 "ID"
Hi all,

Which servers and clients are known to support the 2971 "ID" extension?  I can tell that Gmail supports it, not sure about other servers, nor clients.
-- 
Andrew Laurence
atlauren@me.com (Lists)
atlauren@uci.edu (Main email)


_______________________________________________
imapext mailing list
imapext@ietf.org
https://www.ietf.org/mailman/listinfo/imapext

--------------030402040804030007090904-- From blong@google.com Tue Jun 4 15:14:52 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 640DB21F999C for ; Tue, 4 Jun 2013 15:14:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.976 X-Spam-Level: X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hPan-6GW1FVN for ; Tue, 4 Jun 2013 15:14:48 -0700 (PDT) Received: from mail-qe0-f44.google.com (mail-qe0-f44.google.com [209.85.128.44]) by ietfa.amsl.com (Postfix) with ESMTP id 04E7521F96F2 for ; Tue, 4 Jun 2013 15:14:47 -0700 (PDT) Received: by mail-qe0-f44.google.com with SMTP id 6so605867qeb.3 for ; Tue, 04 Jun 2013 15:14:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LEBGriyuyF4hWKbzc4P23mkSiROP3MTKt+Tl6rL4NIs=; b=LE9upRKKYSp5OAo3ckeDCb07lvF2zGibte1CCJI2b+q2w/GWTNXP8qs3ob1F+4iH2a FDg6AbggJAGoPBdKrETgmRAPiPAgGGKtQYlmu0Ui8Y8niZ9F0jL5Wayebi+8NwNUhwlb gb7oWFD0kVVr9yAUNXpNPi+uCVZ3WOyqwiGF8+pXiGOuIdvh64uxLX2ZrsAypfZm5z+d 0CKVQcILfBB+u71Wc024rlXFf9mzR1gTHOjUrE9TJYoBenIBViZeBRys2BpJnzq8jN07 oOwcsg3jBSvORuFMeEld9MKV7bL60dcl7ICuni9UJ2IMJSzbN1qpGt4jzS3HlUlpf1MG tQig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=LEBGriyuyF4hWKbzc4P23mkSiROP3MTKt+Tl6rL4NIs=; b=hVuPzxkxvO1BdgvGWYdmkjlKhi58qwIkNNNzGkNOXqcZa/qOPQ1PWUr8iLza80I94g dvJZ0AR10KMloAhHi6B51gDC/w9FUd6S1lmOSRM+GKzJndNZdTh/Q4rRBEPGTBquD4zA fIP3hLesQZpI6TtAbIPfIz1Oawx/UgQIk9ha33iQ0jco1JTzrjPDVQa9iCFGoBOoGbMz yN3T15HjwsG2F9r1+o8I4RNztij68rOwWJfRbDi+HwVxDKwVc3d3Yznydg8DJMAJ8jMz rsXKg/pUSbBOJSKGqO0cZS0nt7ppCSKzcJnyCJ3uJTuxAiqOtTZm+NvZkGyEnT4VVKmA ezZw== MIME-Version: 1.0 X-Received: by 10.229.154.207 with SMTP id p15mr654634qcw.57.1370384087286; Tue, 04 Jun 2013 15:14:47 -0700 (PDT) Received: by 10.229.182.209 with HTTP; Tue, 4 Jun 2013 15:14:47 -0700 (PDT) In-Reply-To: References: <8abc3ae3-a966-46f2-a36a-193e750d463d@me.com> Date: Tue, 4 Jun 2013 15:14:47 -0700 Message-ID: From: Brandon Long To: "Adrien W. de Croy" Content-Type: multipart/alternative; boundary=f46d0446325abb5e9704de5b68be X-Gm-Message-State: ALoCoQlIAfv/kEsEoZ6SuzdektYktlr17oKy7t2DX2ipiWv5Gi2qUOAl7Sv45K7YV7QKb49YCJL7blQerh2+xaPhWv+aMUiVrPWyElw5aBtCawHN1TBgJH/OdfKRUEIaJ0MnISKGOuoHKzt2SZQ/rvU/INZSdd3cx524yki7QQdyAQ2TCIuCGEiKx8m+tVSIu2/QraWVl0oJ Cc: "imapext@ietf.org" , Andrew Laurence Subject: Re: [imapext] Support for RFC 2971 "ID" X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 22:14:52 -0000 --f46d0446325abb5e9704de5b68be Content-Type: text/plain; charset=ISO-8859-1 Clients Windows 8, both the "live tile" and Windows Live Mail or whatever its called this version (ie, the latest Outlook Express). Windows Mobile 5.x & 6.x, and Windows Phone 7 & 8. Android Mail app as of 2.1 or 2.2. This will also include a bunch of the vendor skin mail apps or mail inboxes. Mac OS Mail as of 5.0 Blackberry 10 (but not earlier versions which relied on BIS/BES) Thunderbird Trojita Zimbra I think its become pretty common among the more popular clients, except Outlook... though, its possible the latest version of Outlook supports it and I haven't noticed. Brandon On Tue, Jun 4, 2013 at 2:48 PM, Adrien W. de Croy wrote: > we (WinGate) do. > > Also iOS clients, and emClient for clients I know that do. > > Adrien > > > ------ Original Message ------ > From: "Andrew Laurence" > To: "imapext@ietf.org" > Sent: 5/06/2013 9:44:03 a.m. > Subject: [imapext] Support for RFC 2971 "ID" > > Hi all, > > Which servers and clients are known to support the 2971 "ID" extension? I > can tell that Gmail supports it, not sure about other servers, nor clients. > > -- > Andrew Laurenceatlauren@me.com (Lists)atlauren@uci.edu (Main email) > > > _______________________________________________ > imapext mailing list > imapext@ietf.org > https://www.ietf.org/mailman/listinfo/imapext > > --f46d0446325abb5e9704de5b68be Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Clients

Windows 8, both the "live = tile" and Windows Live Mail or whatever its called this version (ie, t= he latest Outlook Express).

Windows Mobile 5.x &am= p; 6.x, and Windows Phone 7 & 8.

Android Mail app as of 2.1 or 2.2. =A0This will a= lso include a bunch of the vendor skin mail apps or mail inboxes.

Mac OS Mail as of 5.0

Blackberry 10 (but not earlier versions which relied on BIS/BES)=

Thunderbird

Trojita

Zimbra

I think its become pretty common amon= g the more popular clients, except Outlook... though, its possible the late= st version of Outlook supports it and I haven't noticed.

Brandon



On Tue, Jun 4, 2013 at 2:48= PM, Adrien W. de Croy <adrien@qbik.com> wrote:
we (WinGate) do.
=A0
Also iOS clients, and emClient for clients I know that do.
=A0
Adrien
=A0
=A0
------ Original Message ------
From: "Andrew Laurence" <atlauren@me.com>
Sent: 5/06/2013 9:44:03 a.m.
Subject: [imapext] Support for RFC 2971 "ID"
Hi all,

Which servers and clients are known to support the 2971= "ID" extension?=A0 I can tell that Gmail supports it, not sure a= bout other servers, nor clients.
--=20
Andrew Laurence
atlauren@me.com (L=
ists)
atlauren@uci.edu =
(Main email)

__________= _____________________________________
imapext mailing list
imapext@ietf.org
https://www.ietf.org/mailman/listinfo/imapext


--f46d0446325abb5e9704de5b68be-- From tss@iki.fi Tue Jun 4 15:15:28 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF7C21F99AF for ; Tue, 4 Jun 2013 15:15:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4EKaDUqs9xgu for ; Tue, 4 Jun 2013 15:15:23 -0700 (PDT) Received: from dovecot.org (dovecot.org [193.210.130.67]) by ietfa.amsl.com (Postfix) with ESMTP id DB2B921F9993 for ; Tue, 4 Jun 2013 15:15:16 -0700 (PDT) Received: from [192.168.10.100] (cs27091020.pp.htv.fi [89.27.91.20]) by dovecot.org (Postfix) with ESMTP id 4AB0B1AE837B; Wed, 5 Jun 2013 01:15:14 +0300 (EEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Timo Sirainen In-Reply-To: <8abc3ae3-a966-46f2-a36a-193e750d463d@me.com> Date: Wed, 5 Jun 2013 01:15:12 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <2590B088-BE43-45B6-BADD-6C2AB1B6F2D7@iki.fi> References: <8abc3ae3-a966-46f2-a36a-193e750d463d@me.com> To: Andrew Laurence X-Mailer: Apple Mail (2.1503) Cc: imapext@ietf.org Subject: Re: [imapext] Support for RFC 2971 "ID" X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 22:15:28 -0000 On 5.6.2013, at 0.44, Andrew Laurence wrote: > Which servers and clients are known to support the 2971 "ID" = extension? I can tell that Gmail supports it, not sure about other = servers, nor clients. Servers: http://imapwiki.org/Specs From murch@andrew.cmu.edu Tue Jun 4 16:21:34 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D06521F9936 for ; Tue, 4 Jun 2013 16:21:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSZW-eqwOiXd for ; Tue, 4 Jun 2013 16:21:28 -0700 (PDT) Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.11.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5955B21F9997 for ; Tue, 4 Jun 2013 16:21:24 -0700 (PDT) Received: from 10.67.166.15 (36.sub-174-255-97.myvzw.com [174.255.97.36]) (user=murch mech=LOGIN (0 bits)) by smtp.andrew.cmu.edu (8.14.4/8.14.4) with ESMTP id r54NLLf9020052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 4 Jun 2013 19:21:23 -0400 Message-Id: <201306042321.r54NLLf9020052@smtp.andrew.cmu.edu> From: "Ken Murchison" To: "Andrew Laurence" , imapext@ietf.org Date: Tue, 4 Jun 2013 18:21:21 -0500 User-Agent: LogicMail/2.2.0.81 In-Reply-To: <19769_1370382366_r54Lk5WP021696_8abc3ae3-a966-46f2-a36a-193e750d463d@me.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.3.18.170322 X-SMTP-Spam-Clean: 8% ( BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_600_699 0, BODY_SIZE_7000_LESS 0, NO_MESSAGE_ID 0, RDNS_POOLED 0, RDNS_SUSP 0, RDNS_SUSP_SPECIFIC 0, RDNS_WIRELESS 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __RDNS_POOLED_6 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 0) X-SMTP-Spam-Score: 8% X-Scanned-By: MIMEDefang 2.60 on 128.2.11.61 Subject: Re: [imapext] Support for RFC 2971 "ID" X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 23:21:34 -0000 SGkgQW5kcmV3LAoKDQpPbiBUdWUsIDQgSnVuIDIwMTMgMTY6NDQ6MDMgLTA1MDAsIGltYXBleHQt Ym91bmNlc0BpZXRmLm9yZyB3cm90ZToNCj4gSGkgYWxsLA0KPiANCj4gV2hpY2ggc2VydmVycyBh bmQgY2xpZW50cyBhcmUga25vd24gdG8gc3VwcG9ydCB0aGUgMjk3MSAiSUQiIGV4dGVuc2lvbj8g IEkgY2FuIHRlbGwgdGhhdCBHbWFpbCBzdXBwb3J0cyBpdCwgbm90IHN1cmUgYWJvdXQgb3RoZXIg c2VydmVycywgbm9yIGNsaWVudHMu77u/DQoKQXMgbm90ZWQgaW4gdGhlIHdpa2kgdGhhdCBUaW1v IGRpcmVjdGVkIHlvdSB0bywgQ3lydXMgSU1BUCBoYXMgc3VwcG9ydGVkIElEIGZvciBhIHdoaWxl LiBJIGNhbiBjb25maXJtIHRoYXQgVGJpcmQgc3VwcG9ydHMgaXQgYXMgd2UgbG9nIElEIHJlcXVl c3RzLgoKLS0gDQpLZW5uZXRoIE11cmNoaXNvbgpQcmluY2lwYWwgU3lzdGVtcyBTb2Z0d2FyZSBF bmdpbmVlciAKQ2FybmVnaWUgTWVsbG9uIFVuaXZlcnNpdHk= From internet-drafts@ietf.org Thu Jun 6 06:34:23 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDE5121F9A21; Thu, 6 Jun 2013 06:34:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.356 X-Spam-Level: X-Spam-Status: No, score=-102.356 tagged_above=-999 required=5 tests=[AWL=0.244, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D2bqCjUIBDVt; Thu, 6 Jun 2013 06:34:23 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F42B21F9675; Thu, 6 Jun 2013 06:34:21 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.50 Message-ID: <20130606133420.10917.73022.idtracker@ietfa.amsl.com> Date: Thu, 06 Jun 2013 06:34:20 -0700 Cc: imapext@ietf.org Subject: [imapext] I-D Action: draft-ietf-qresync-rfc4551bis-01.txt X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jun 2013 13:34:23 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the IMAP QRESYNC Extension Working Group of t= he IETF. Title : IMAP Extension for Conditional STORE Operation or Quick = Flag Changes Resynchronization Author(s) : Alexey Melnikov Filename : draft-ietf-qresync-rfc4551bis-01.txt Pages : 24 Date : 2013-06-06 Abstract: Often, multiple IMAP (RFC 3501) clients need to coordinate changes to a common IMAP mailbox. Examples include different clients working on behalf of the same user, and multiple users accessing shared mailboxes. These clients need a mechanism to synchronize state changes for messages within the mailbox. They must be able to guarantee that only one client can change message state (e.g., message flags) at any time. An example of such an application is use of an IMAP mailbox as a message queue with multiple dequeueing clients. The Conditional Store facility provides a protected update mechanism for message state information that can detect and resolve conflicts between multiple writing mail clients. The Conditional Store facility also allows a client to quickly resynchronize mailbox flag changes. This document defines an extension to IMAP (RFC 3501). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-qresync-rfc4551bis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-qresync-rfc4551bis-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-qresync-rfc4551bis-01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From alexey.melnikov@isode.com Thu Jun 6 07:25:45 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46B3321F9A11 for ; Thu, 6 Jun 2013 07:25:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yi8xSG4RmWVW for ; Thu, 6 Jun 2013 07:25:02 -0700 (PDT) Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id D9A1521F99C7 for ; Thu, 6 Jun 2013 07:24:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1370528677; d=isode.com; s=selector; i=@isode.com; bh=ICCfWet8BFCS4RcAvwNaF0WYjohvuQDZbfLuxh00HfI=; 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=NWmmcFHAlzJwKbxGkN3BF+le5xhFhCIhXFnyFwkMdyArkAC19hR+MtnxpYHJ2W17R4yg+Y 13aFVDP7obI+y3pEOTRH7lSkzguB2pxhXK2atzM+i3hHXCta88ZaZ9kzDFB/Lvw6pEvbtZ kf3esG38X7m54tq2wqmaOaqc4kX8DIw=; Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by statler.isode.com (submission channel) via TCP with ESMTPA id ; Thu, 6 Jun 2013 15:24:37 +0100 Message-ID: <51B09BA5.9040309@isode.com> Date: Thu, 06 Jun 2013 15:24:37 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 To: imapext@ietf.org References: <20130606133420.10917.73022.idtracker@ietfa.amsl.com> In-Reply-To: <20130606133420.10917.73022.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [imapext] I-D Action: draft-ietf-qresync-rfc4551bis-01.txt X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jun 2013 14:25:49 -0000 On 06/06/2013 14:34, internet-drafts@ietf.org wrote: > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-qresync-rfc4551bis > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-qresync-rfc4551bis-01 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-qresync-rfc4551bis-01 This version fixed internal references (I just spotted another problem and will fix it in -02). It also added some text to increase the recommended client side line length limit from RFC 2683 to 8Kb. From cyrus@daboo.name Fri Jun 7 09:59:56 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C9CB21F92E3 for ; Fri, 7 Jun 2013 09:59:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.185 X-Spam-Level: X-Spam-Status: No, score=-100.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SmEJSlrTsFgl for ; Fri, 7 Jun 2013 09:59:50 -0700 (PDT) Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC2E21F9079 for ; Fri, 7 Jun 2013 09:59:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id E2C4144E55B1 for ; Fri, 7 Jun 2013 12:59:49 -0400 (EDT) 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 XXSrJaU1DAdU for ; Fri, 7 Jun 2013 12:59:49 -0400 (EDT) Received: from dyn-72-33-212-232.uwnet.wisc.edu (dyn-72-33-212-232.uwnet.wisc.edu [72.33.212.232]) by daboo.name (Postfix) with ESMTPSA id C415D44E55A1 for ; Fri, 7 Jun 2013 12:59:48 -0400 (EDT) Date: Fri, 07 Jun 2013 11:59:53 -0500 From: Cyrus Daboo To: imapext@ietf.org Message-ID: <6291FAD2FBE3593797DEC90C@dyn-72-33-212-232.uwnet.wisc.edu> X-Mailer: Mulberry/4.1.0a3 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=747 Subject: [imapext] LOGINDISABLED X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jun 2013 16:59:56 -0000 Hi, RFC3501 defines a LOGINDISABLED property that is used prior to STARTTLS (or some out of band security) being in place to ensure the LOGIN command is not used in an insecure environment. Some servers also offer configuration to also disable plain text authentication even when a security layer is in place. In that situation, should (must) the server advertise LOGINDISABLED in capabilities sent after STARTTLS? The spec really does not cover that case explicitly. Personally I think anytime the server is going to reject LOGIN it ought to advertise LOGINDISABLED to ensure clients don't "blindly" send the clear text credentials - because the purpose of disabling LOGIN is to stop that happening in the first place. -- Cyrus Daboo From murch@andrew.cmu.edu Fri Jun 7 10:02:40 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41DEC21F90CC for ; Fri, 7 Jun 2013 10:02:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.599 X-Spam-Level: X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AmeEJFFpm0WI for ; Fri, 7 Jun 2013 10:02:31 -0700 (PDT) Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.11.95]) by ietfa.amsl.com (Postfix) with ESMTP id C80C721F8FA4 for ; Fri, 7 Jun 2013 10:02:30 -0700 (PDT) Received: from [192.168.137.22] (cpe-76-180-197-142.buffalo.res.rr.com [76.180.197.142]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.14.4/8.14.4) with ESMTP id r57H2SCs002112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 7 Jun 2013 13:02:29 -0400 Message-ID: <51B21224.8060808@andrew.cmu.edu> Date: Fri, 07 Jun 2013 13:02:28 -0400 From: Ken Murchison Organization: Carnegie Mellon University User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6 MIME-Version: 1.0 To: imapext@ietf.org References: <14830_1370624399_r57GxvRc017415_6291FAD2FBE3593797DEC90C@dyn-72-33-212-232.uwnet.wisc.edu> In-Reply-To: <14830_1370624399_r57GxvRc017415_6291FAD2FBE3593797DEC90C@dyn-72-33-212-232.uwnet.wisc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.5.19.222118 X-SMTP-Spam-Clean: 10% ( TO_IN_SUBJECT 0.5, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, BODY_SIZE_900_999 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, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __RDNS_POOLED_2 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __USER_AGENT 0) X-SMTP-Spam-Score: 10% X-Scanned-By: MIMEDefang 2.60 on 128.2.11.95 Subject: Re: [imapext] LOGINDISABLED X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jun 2013 17:02:40 -0000 On 06/07/2013 12:59 PM, Cyrus Daboo wrote: > Hi, > RFC3501 defines a LOGINDISABLED property that is used prior to > STARTTLS (or some out of band security) being in place to ensure the > LOGIN command is not used in an insecure environment. Some servers > also offer configuration to also disable plain text authentication > even when a security layer is in place. In that situation, should > (must) the server advertise LOGINDISABLED in capabilities sent after > STARTTLS? The spec really does not cover that case explicitly. > > Personally I think anytime the server is going to reject LOGIN it > ought to advertise LOGINDISABLED to ensure clients don't "blindly" > send the clear text credentials - because the purpose of disabling > LOGIN is to stop that happening in the first place +1 -- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University From tss@iki.fi Fri Jun 7 10:13:20 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F7DA21F96F4 for ; Fri, 7 Jun 2013 10:13:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eoUwfjm5Us3g for ; Fri, 7 Jun 2013 10:13:14 -0700 (PDT) Received: from dovecot.org (dovecot.org [193.210.130.67]) by ietfa.amsl.com (Postfix) with ESMTP id 39CC921F9488 for ; Fri, 7 Jun 2013 10:13:14 -0700 (PDT) Received: from [192.168.10.100] (cs181255018.pp.htv.fi [82.181.255.18]) by dovecot.org (Postfix) with ESMTP id 7F43D1AE837B for ; Fri, 7 Jun 2013 20:13:12 +0300 (EEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Timo Sirainen In-Reply-To: <6291FAD2FBE3593797DEC90C@dyn-72-33-212-232.uwnet.wisc.edu> Date: Fri, 7 Jun 2013 20:13:13 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <29B47AC5-8F45-4EC9-8C18-2BF29E3E7732@iki.fi> References: <6291FAD2FBE3593797DEC90C@dyn-72-33-212-232.uwnet.wisc.edu> To: "imapext@ietf.org" X-Mailer: Apple Mail (2.1503) Subject: Re: [imapext] LOGINDISABLED X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jun 2013 17:13:20 -0000 On 7.6.2013, at 19.59, Cyrus Daboo wrote: > Hi, > RFC3501 defines a LOGINDISABLED property that is used prior to = STARTTLS (or some out of band security) being in place to ensure the = LOGIN command is not used in an insecure environment. Some servers also = offer configuration to also disable plain text authentication even when = a security layer is in place. In that situation, should (must) the = server advertise LOGINDISABLED in capabilities sent after STARTTLS? The = spec really does not cover that case explicitly. >=20 > Personally I think anytime the server is going to reject LOGIN it = ought to advertise LOGINDISABLED to ensure clients don't "blindly" send = the clear text credentials - because the purpose of disabling LOGIN is = to stop that happening in the first place. Yeah, good idea. Added to Dovecot v2.2. From dave@cridland.net Fri Jun 7 14:33:07 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B56E21F996D for ; Fri, 7 Jun 2013 14:33:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lsF7K7WyUjAv for ; Fri, 7 Jun 2013 14:33:06 -0700 (PDT) Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id C6E5621F9961 for ; Fri, 7 Jun 2013 14:33:06 -0700 (PDT) Received: by mail-ob0-f169.google.com with SMTP id up14so7388905obb.14 for ; Fri, 07 Jun 2013 14:33:06 -0700 (PDT) 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=weUHBUq+MnuFxmH/4xpvBtrItJ2J7BxC/+K1oEMrDEU=; b=GYtJ1EQxtlhU2b3UupOWU4FekwH/ioVG1v9EKDpcbSPRQ12TCXbZ7S8k24SGaQPulH 4vbZqJE7DcvdpO5aqBeS+aXCGEqvq/6RcU8bc0Hak6k5s0qUYfZhBLDgC55rAnhdIHlP VWpdW6JBE6LV26rpc6m61GCPJ3lR9HJSyNVro= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=weUHBUq+MnuFxmH/4xpvBtrItJ2J7BxC/+K1oEMrDEU=; b=C21nAkDwWhD+k4nurDlhWUuSumVXF92Lah4sxeSO26MIA+oN4NSwRIj4+yO/Cl4+8X YfoiT3qw+KU1W5kIsSWht8dmm5NU4AJZchqF4DUs4dmul9cme88/2fUiG8Q/GDRFTT9q kqS5XaNd+N9QRFSPg5yX14I2gqEXewqcINpQHLxa1N0XACoDq3rVaUgrKij9zGjpcCeG IR3iAT8qMq0XegeywQ72n9gGo0LIB2uX/69T6/NvRIEDj80SA9C/SuSKZiRhNqiXGVwM PgTN/q1laUXg8I6lqZgszRJfB6KVRoUUA66V2cg4cHp7RIHgP44jeRHi9ZTbcaVniGya 6f0g== MIME-Version: 1.0 X-Received: by 10.182.47.129 with SMTP id d1mr417373obn.42.1370640786228; Fri, 07 Jun 2013 14:33:06 -0700 (PDT) Received: by 10.60.8.40 with HTTP; Fri, 7 Jun 2013 14:33:06 -0700 (PDT) In-Reply-To: <29B47AC5-8F45-4EC9-8C18-2BF29E3E7732@iki.fi> References: <6291FAD2FBE3593797DEC90C@dyn-72-33-212-232.uwnet.wisc.edu> <29B47AC5-8F45-4EC9-8C18-2BF29E3E7732@iki.fi> Date: Fri, 7 Jun 2013 22:33:06 +0100 Message-ID: From: Dave Cridland To: Timo Sirainen Content-Type: multipart/alternative; boundary=089e0158b0b62d9e4e04de972d99 X-Gm-Message-State: ALoCoQkJbw7BHG5StE9RNMXC7b6YZfds3V6ZhPjYWneFJ7A/NQWvTY1qIIGYijVnxzxcx5KSyUqt Cc: "imapext@ietf.org" Subject: Re: [imapext] LOGINDISABLED X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jun 2013 21:33:07 -0000 --089e0158b0b62d9e4e04de972d99 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Jun 7, 2013 at 6:13 PM, Timo Sirainen wrote: > Yeah, good idea. Added to Dovecot v2.2. > > RFC 3501 =A77.2.1, para 4: The LOGINDISABLED capability indicates that the LOGIN command is disabled, and that the server will respond with a tagged NO response to any attempt to use the LOGIN command even if the user name and password are valid. An IMAP client MUST NOT issue the LOGIN command if the server advertises the LOGINDISABLED capability. No mention of STARTTLS. So yes, if the LOGIN command is disabled for any reason, then advertising LOGINDISABLED seems to be the right thing to do according to the specification. --089e0158b0b62d9e4e04de972d99 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Fri, Jun 7, 2013 at 6:13 PM, Timo Sirainen <= ;tss@iki.fi> = wrote:
Yeah= , good idea. Added to Dovecot v2.2.


RFC 3501 =A77.2.1, para 4:

      The LOGINDISABLED capability indicates that the LOGIN command is
      disabled, and that the server will respond with a tagged NO
      response to any attempt to use the LOGIN command even if the user
      name and password are valid.  An IMAP client MUST NOT issue the
      LOGIN command if the server advertises the LOGINDISABLED
      capability.
No mention of STARTTLS.

So yes, if the LOGIN command is disabled for any reason, then advertisin= g LOGINDISABLED seems to be the right thing to do according to the specific= ation.
--089e0158b0b62d9e4e04de972d99-- From murch@andrew.cmu.edu Mon Jun 10 10:31:32 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45D0F21F93E1 for ; Mon, 10 Jun 2013 10:31:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.56 X-Spam-Level: X-Spam-Status: No, score=-6.56 tagged_above=-999 required=5 tests=[AWL=-2.038, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJ_ALL_CAPS=2.077] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RHPLRZKVcjx3 for ; Mon, 10 Jun 2013 10:31:26 -0700 (PDT) Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.11.96]) by ietfa.amsl.com (Postfix) with ESMTP id 532C821F93D4 for ; Mon, 10 Jun 2013 10:31:25 -0700 (PDT) Received: from [192.168.137.22] (cpe-76-180-197-142.buffalo.res.rr.com [76.180.197.142]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.14.4/8.14.4) with ESMTP id r5AHVOQQ002242 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 10 Jun 2013 13:31:24 -0400 Message-ID: <51B60D6C.8040400@andrew.cmu.edu> Date: Mon, 10 Jun 2013 13:31:24 -0400 From: Ken Murchison Organization: Carnegie Mellon University User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6 MIME-Version: 1.0 To: imapext@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.4.9.4220 X-SMTP-Spam-Clean: 8% ( BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, BODY_SIZE_900_999 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_RESIDENTIAL 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, TO_NO_NAME 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_SUBJ_ALLCAPS 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __RDNS_POOLED_2 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __USER_AGENT 0) X-SMTP-Spam-Score: 8% X-Scanned-By: MIMEDefang 2.60 on 128.2.11.96 Subject: [imapext] CONDSTORE / QRESYNC X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jun 2013 17:31:32 -0000 I have quickly read Alexey's refresh of these specs and they both seems to capture the relevant errata and implementation experience. I think that we might want to consider combining both specs into one document since they are so tightly coupled to one another, especially given that we really want clients to support QRESYNC (and not just CONDSTORE) as mentioned in the last 2 paragraphs of section 1 or QRESYNC. FWIW, Cyrus IMAP fully supports both extensions including errata 1807-1809, with the exception of the MODIFIED response code. Cyrus does not support separate per-metadata modseq, and always returns unsolicited FETCH responses for changed messages, so I don't know if the lack of a MODIFIED response code is an issue for client implementations. I don't recall why we didn't add MODIFIED to Cyrus, but I don't believe that it would be a heavy lift to do so. -- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University From murch@andrew.cmu.edu Mon Jun 10 12:48:13 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D807421F9A7C for ; Mon, 10 Jun 2013 12:48:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.881 X-Spam-Level: X-Spam-Status: No, score=-5.881 tagged_above=-999 required=5 tests=[AWL=-1.359, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJ_ALL_CAPS=2.077] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IZgx42RuXTPs for ; Mon, 10 Jun 2013 12:48:08 -0700 (PDT) Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.11.61]) by ietfa.amsl.com (Postfix) with ESMTP id D941821F95DD for ; Mon, 10 Jun 2013 12:48:07 -0700 (PDT) Received: from [192.168.137.22] (cpe-76-180-197-142.buffalo.res.rr.com [76.180.197.142]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.14.4/8.14.4) with ESMTP id r5AJm59X030901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 10 Jun 2013 15:48:06 -0400 Message-ID: <51B62D75.8040001@andrew.cmu.edu> Date: Mon, 10 Jun 2013 15:48:05 -0400 From: Ken Murchison Organization: Carnegie Mellon University User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6 MIME-Version: 1.0 To: imapext@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.3.18.170322 X-SMTP-Spam-Clean: 8% ( BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, BODY_SIZE_900_999 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_RESIDENTIAL 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_SUBJ_ALLCAPS 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __RDNS_POOLED_2 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __USER_AGENT 0) X-SMTP-Spam-Score: 8% X-Scanned-By: MIMEDefang 2.60 on 128.2.11.61 Subject: [imapext] CONDSTORE / QRESYNC X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jun 2013 19:48:14 -0000 I have quickly read Alexey's refresh of these specs and they both seems to capture the relevant errata and implementation experience. I think that we might want to consider combining both specs into one document since they are so tightly coupled to one another, especially given that we really want clients to support QRESYNC (and not just CONDSTORE) as mentioned in the last 2 paragraphs of section 1 or QRESYNC. FWIW, Cyrus IMAP fully supports both extensions including errata 1807-1809, with the exception of the MODIFIED response code. Cyrus does not support separate per-metadata modseq, and always returns unsolicited FETCH responses for changed messages, so I don't know if the lack of a MODIFIED response code is an issue for client implementations. I don't believe that it would be a heavy lift to add MODIFIED to Cyrus. -- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University From dave@cridland.net Tue Jun 11 03:39:35 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98E8421F8C20 for ; Tue, 11 Jun 2013 03:39:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.477 X-Spam-Level: X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hfOwhHikwyha for ; Tue, 11 Jun 2013 03:39:30 -0700 (PDT) Received: from mail-lb0-f178.google.com (mail-lb0-f178.google.com [209.85.217.178]) by ietfa.amsl.com (Postfix) with ESMTP id 4C31621F8C1A for ; Tue, 11 Jun 2013 03:39:30 -0700 (PDT) Received: by mail-lb0-f178.google.com with SMTP id y6so5810743lbh.9 for ; Tue, 11 Jun 2013 03:39:28 -0700 (PDT) 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=1FRUPPqfjhZETT8UyMmAEqHidt2ftpZp2FUogfxoegI=; b=J8V6TF83CU4HNK9ganRgIpUyelWs7fVX/wtcKYlC5wBNLd7fUoTyoHUEOVOUWyN/lm msZSCzXjf2p/0SdzBR8/ECPQ8AF3MFLKO1zTbqyP5Ez/V1G+ufQPWilF2BcVjqc0trTo lv9rmJVAhkieLXRxxSz1Tm71MicaxWKsvZouE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=1FRUPPqfjhZETT8UyMmAEqHidt2ftpZp2FUogfxoegI=; b=McArvBj4nzKhQxDbGY66CWhcLHCOjDcZPv44CfIuUM9ZqEnM5bYcLr/d2Lhw7f3Ok8 NJlWL7LTWUfKQDP2EDSyApmwFwkfWL76Vl8nPnsgCVaYXQ7U+VFeb7ycWHZkPlqDoSsG 82ky+IAGUm6uzXp/oz2TNa0Dh1KLjwFGSlmzALY/hmVrP3vEYj5UbCpC2zFhjMv9MNhB mRLK4g3vZM/CHvIiqkk0Y9NLw5XIWCMDk8OnXqSTqC6SBxXLuAOdDZyWErwFgcHlHHPt H8dFMOuud5TRh3PcYZ+va/7t5iYl9Dzi+KuP5D/7MW6Y7ydkOY82Jg1Myq941g02qcjO BCmA== MIME-Version: 1.0 X-Received: by 10.152.4.137 with SMTP id k9mr7147947lak.11.1370947168831; Tue, 11 Jun 2013 03:39:28 -0700 (PDT) Received: by 10.114.7.42 with HTTP; Tue, 11 Jun 2013 03:39:28 -0700 (PDT) In-Reply-To: <51B62D75.8040001@andrew.cmu.edu> References: <51B62D75.8040001@andrew.cmu.edu> Date: Tue, 11 Jun 2013 11:39:28 +0100 Message-ID: From: Dave Cridland To: Ken Murchison Content-Type: multipart/alternative; boundary=089e013d1cf801187804dede83b4 X-Gm-Message-State: ALoCoQkwcclynEXAUzMSC5Ica01bFpNg4LHD6H9hSHWNpdSZMjmlT93gb0Mt636dzpazMEmIv3Zy Cc: "imapext@ietf.org" Subject: Re: [imapext] CONDSTORE / QRESYNC X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jun 2013 10:39:35 -0000 --089e013d1cf801187804dede83b4 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Jun 10, 2013 at 8:48 PM, Ken Murchison wrote: > FWIW, Cyrus IMAP fully supports both extensions including errata > 1807-1809, with the exception of the MODIFIED response code. Cyrus does > not support separate per-metadata modseq, and always returns unsolicited > FETCH responses for changed messages, so I don't know if the lack of a > MODIFIED response code is an issue for client implementations. I don't > believe that it would be a heavy lift to add MODIFIED to Cyrus. > > As a client developer, I've never actually used UNCHANGEDSINCE, but I could understand the need to, and I'd prefer to have the MODIFIED response code present for this case. On the other hand, I cannot think of a case when I'd actually want per-metadata MODSEQ - it's also not clear to me that any extant servers actually support this anyway. In the absence of per-metadata MODSEQ, then a client can add a flag if the message is still unseen (for example), which seems to me to be a more useful case. Does any server actually implement per-metadata MODSEQ? Does anyone want this? --089e013d1cf801187804dede83b4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Mon, Jun 10, 2013 at 8:48 PM, Ken Murchison <murc= h@andrew.cmu.edu> wrote:
FWIW, Cyrus IMAP fully supports both extensions including errata 1807-1809,= with the exception of the MODIFIED response code. =A0Cyrus does not suppor= t separate per-metadata modseq, and always returns unsolicited FETCH respon= ses for changed messages, so I don't know if the lack of a MODIFIED res= ponse code is an issue for client implementations. =A0I don't believe t= hat it would be a heavy lift to add MODIFIED to Cyrus.


As= a client developer, I've never actually used UNCHANGEDSINCE, but I cou= ld understand the need to, and I'd prefer to have the MODIFIED response= code present for this case.

On the other hand, I cannot think of a case= when I'd actually want per-metadata MODSEQ - it's also not clear t= o me that any extant servers actually support this anyway. In the absence o= f per-metadata MODSEQ, then a client can add a flag if the message is still= unseen (for example), which seems to me to be a more useful case.

Does any server actually implement per-meta= data MODSEQ? Does anyone want this?
--089e013d1cf801187804dede83b4-- From tss@iki.fi Tue Jun 11 05:38:22 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E31B721F998B for ; Tue, 11 Jun 2013 05:38:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uS2gfl2lvsDc for ; Tue, 11 Jun 2013 05:38:17 -0700 (PDT) Received: from dovecot.org (dovecot.org [193.210.130.67]) by ietfa.amsl.com (Postfix) with ESMTP id 6EDAE21F996F for ; Tue, 11 Jun 2013 05:38:05 -0700 (PDT) Received: from [192.168.10.100] (cs181255018.pp.htv.fi [82.181.255.18]) by dovecot.org (Postfix) with ESMTP id 5D7631AE8825; Tue, 11 Jun 2013 15:38:03 +0300 (EEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Timo Sirainen In-Reply-To: Date: Tue, 11 Jun 2013 15:38:03 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <83FFBF44-0FF9-4195-AA45-5BE6179A48E0@iki.fi> References: <51B62D75.8040001@andrew.cmu.edu> To: Dave Cridland X-Mailer: Apple Mail (2.1508) Cc: imapext@ietf.org Subject: Re: [imapext] CONDSTORE / QRESYNC X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jun 2013 12:38:23 -0000 On 11.6.2013, at 13.39, Dave Cridland wrote: > On the other hand, I cannot think of a case when I'd actually want = per-metadata MODSEQ - it's also not clear to me that any extant servers = actually support this anyway. In the absence of per-metadata MODSEQ, = then a client can add a flag if the message is still unseen (for = example), which seems to me to be a more useful case. >=20 > Does any server actually implement per-metadata MODSEQ? Does anyone = want this? Perhaps it could be a useful difference for message flag changes vs. = annotation changes. But I haven't implemented annotation support yet, so = I'm not really sure. From dave@cridland.net Tue Jun 11 06:49:57 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 238CE21F99FA for ; Tue, 11 Jun 2013 06:49:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.931 X-Spam-Level: X-Spam-Status: No, score=-1.931 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UUBgMxFOgYoP for ; Tue, 11 Jun 2013 06:49:56 -0700 (PDT) Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 7DAB921F99F8 for ; Tue, 11 Jun 2013 06:49:56 -0700 (PDT) Received: by mail-oa0-f44.google.com with SMTP id l10so1864284oag.3 for ; Tue, 11 Jun 2013 06:49:56 -0700 (PDT) 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=TYDCxCqLdtqRpstyIoH+a9ZLXCl4iKNJOcB5lBs0e+I=; b=BqQjVHjmOM0WPmz6lM0y5xSTQ8bAOAE/gNMTbPzDenmfsiY+tLwtgVUTnBrP9n8bQ2 0pk/+1VH80t803ZhsCcFcZzb6oJAvh5632L6sNsDklUJ6AmEjsy8L0x+RltuXS6LTHBV XCIOrMOeoJy24yzoRvZjX6no7aSpsGMt9rKfc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=TYDCxCqLdtqRpstyIoH+a9ZLXCl4iKNJOcB5lBs0e+I=; b=pU1c0bLdCu/QOgl7TSAHjfkoAsdYv43DrMkr/SNNpovNXGriSqYTBKUFWiqc8UItUH NEeO2ghJskkXhghDtdY44mKbEXPXr/HdnC8UvuO3+LXJEjsJygUeJEeG9bBB/0vlzjwJ EXP42EJASHxtj1ajg7glvlqFze1IZKSXWzZbE4bBsNRmD8ROyBCe1XNjaFYp1hhmBCMG fQi8qS9XAw5zUwGP91LY62j4NaoibZlhKprLEr/IMWH8M11AYRHdVfdGnjad3UVUmpmy 4hz7JAOw93I6dYPXFAtLJMxFoaKxPz+wrPpflu0Bw6bn6LISTAmiRqlFZaKotb1ViZp6 r73w== MIME-Version: 1.0 X-Received: by 10.60.54.194 with SMTP id l2mr11798308oep.52.1370958596067; Tue, 11 Jun 2013 06:49:56 -0700 (PDT) Received: by 10.60.139.212 with HTTP; Tue, 11 Jun 2013 06:49:56 -0700 (PDT) In-Reply-To: <83FFBF44-0FF9-4195-AA45-5BE6179A48E0@iki.fi> References: <51B62D75.8040001@andrew.cmu.edu> <83FFBF44-0FF9-4195-AA45-5BE6179A48E0@iki.fi> Date: Tue, 11 Jun 2013 14:49:56 +0100 Message-ID: From: Dave Cridland To: Timo Sirainen Content-Type: multipart/alternative; boundary=089e011841c81ee1ab04dee12cbf X-Gm-Message-State: ALoCoQnCgwIiN7kJX9/dm47YcHvbLdQsn0O0B1i+4uFP2rBp5QSvhwoV2SSCvtvd3wqJhu6xTWKV Cc: "imapext@ietf.org" Subject: Re: [imapext] CONDSTORE / QRESYNC X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jun 2013 13:49:57 -0000 --089e011841c81ee1ab04dee12cbf Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jun 11, 2013 at 1:38 PM, Timo Sirainen wrote: > On 11.6.2013, at 13.39, Dave Cridland wrote: > > > On the other hand, I cannot think of a case when I'd actually want > per-metadata MODSEQ - it's also not clear to me that any extant servers > actually support this anyway. In the absence of per-metadata MODSEQ, then a > client can add a flag if the message is still unseen (for example), which > seems to me to be a more useful case. > > > > Does any server actually implement per-metadata MODSEQ? Does anyone want > this? > > Perhaps it could be a useful difference for message flag changes vs. > annotation changes. But I haven't implemented annotation support yet, so > I'm not really sure. > > One possible option there would be to call this out as out of scope, and require the annotation extension to have its own modification sequence. Dave. --089e011841c81ee1ab04dee12cbf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Jun 11, 2013 at 1:38 PM, Timo Sirainen <tss@iki.fi= > wrote:
On 11.6.2013, at 13.39, Dave Cridland <dave@cridland.net> wrote:

> On the other hand, I cannot think of a case when I'd actually want= per-metadata MODSEQ - it's also not clear to me that any extant server= s actually support this anyway. In the absence of per-metadata MODSEQ, then= a client can add a flag if the message is still unseen (for example), whic= h seems to me to be a more useful case.
>
> Does any server actually implement per-metadata MODSEQ? Does anyone wa= nt this?

Perhaps it could be a useful difference for message flag changes vs. = annotation changes. But I haven't implemented annotation support yet, s= o I'm not really sure.



One possible opti= on there would be to call this out as out of scope, and require the annotat= ion extension to have its own modification sequence.

Dave.
--089e011841c81ee1ab04dee12cbf-- From alexey.melnikov@isode.com Wed Jun 12 03:40:00 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07A4521F99BB for ; Wed, 12 Jun 2013 03:40:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.102 X-Spam-Level: X-Spam-Status: No, score=-102.102 tagged_above=-999 required=5 tests=[AWL=-0.497, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I69hNntOO9ij for ; Wed, 12 Jun 2013 03:39:54 -0700 (PDT) Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 82B0421F9675 for ; Wed, 12 Jun 2013 03:39:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1371033591; d=isode.com; s=selector; i=@isode.com; bh=8LD52Y4jawsc9N1jAvzckyn9UHE4X/qNiitEKaBc+XU=; 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=uCDAUXEybRuWWawKgpWRoppRbwmtoQAWyfclzsQZuGI667rIEO02plVSNIrKz1AzWCv1dO JfoFx7jULPayQDCnJaKxzFKhQyhBM1B3Dh3kh0gi1B20+E1x2b4i3JEJ+y3Y8ZH5Q2rizt 6J95WY3suqUrBvmHysqeGWUCMrWoOw4=; Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by statler.isode.com (submission channel) via TCP with ESMTPA id ; Wed, 12 Jun 2013 11:39:51 +0100 Message-ID: <51B776D5.5010703@isode.com> Date: Tue, 11 Jun 2013 20:13:25 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 To: Dave Cridland References: <51B62D75.8040001@andrew.cmu.edu> <83FFBF44-0FF9-4195-AA45-5BE6179A48E0@iki.fi> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------000506010207080000040703" Cc: Timo Sirainen , "imapext@ietf.org" Subject: Re: [imapext] CONDSTORE / QRESYNC X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jun 2013 10:40:00 -0000 This is a multi-part message in MIME format. --------------000506010207080000040703 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 11/06/2013 14:49, Dave Cridland wrote: > On Tue, Jun 11, 2013 at 1:38 PM, Timo Sirainen > wrote: > > On 11.6.2013, at 13.39, Dave Cridland > wrote: > > > On the other hand, I cannot think of a case when I'd actually > want per-metadata MODSEQ - it's also not clear to me that any > extant servers actually support this anyway. In the absence of > per-metadata MODSEQ, then a client can add a flag if the message > is still unseen (for example), which seems to me to be a more > useful case. > > > > Does any server actually implement per-metadata MODSEQ? Does > anyone want this? > > Perhaps it could be a useful difference for message flag changes > vs. annotation changes. But I haven't implemented annotation > support yet, so I'm not really sure. > > > > One possible option there would be to call this out as out of scope, > and require the annotation extension to have its own modification > sequence. If this is a question of what to say in CONDSTORE, I would be Ok with that. For example saying something like "CONDSTORE requires one modseq per all flags/keywords. Other IMAP extensions might add additional modseqs for other metadata (or might reuse the flag one)." would be Ok. I would be less happy with modifying existing syntax (apart from removing something which is already optional) or requiring other extensions to use their own per-metadata modseqs. --------------000506010207080000040703 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 11/06/2013 14:49, Dave Cridland wrote:
On Tue, Jun 11, 2013 at 1:38 PM, Timo Sirainen <tss@iki.fi> wrote:
On 11.6.2013, at 13.39, Dave Cridland <dave@cridland.net> wrote:

> On the other hand, I cannot think of a case when I'd actually want per-metadata MODSEQ - it's also not clear to me that any extant servers actually support this anyway. In the absence of per-metadata MODSEQ, then a client can add a flag if the message is still unseen (for example), which seems to me to be a more useful case.
>
> Does any server actually implement per-metadata MODSEQ? Does anyone want this?

Perhaps it could be a useful difference for message flag changes vs. annotation changes. But I haven't implemented annotation support yet, so I'm not really sure.



One possible option there would be to call this out as out of scope, and require the annotation extension to have its own modification sequence.
If this is a question of what to say in CONDSTORE, I would be Ok with that. For example saying something like "CONDSTORE requires one modseq per all flags/keywords. Other IMAP extensions might add additional modseqs for other metadata (or might reuse the flag one)." would be Ok. I would be less happy with modifying existing syntax (apart from removing something which is already optional) or requiring other extensions to use their own per-metadata modseqs.

--------------000506010207080000040703-- From dave@cridland.net Fri Jun 14 07:33:11 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D22421F9CB5 for ; Fri, 14 Jun 2013 07:33:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.957 X-Spam-Level: X-Spam-Status: No, score=-1.957 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BtfsG6vs5PMU for ; Fri, 14 Jun 2013 07:33:10 -0700 (PDT) Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF5021F9CB3 for ; Fri, 14 Jun 2013 07:33:10 -0700 (PDT) Received: by mail-oa0-f42.google.com with SMTP id n12so774842oag.29 for ; Fri, 14 Jun 2013 07:33:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:date:message-id:subject:from:to:content-type; bh=kU6JzS0rX9MFBHCrU+qq60WqPQAwv2AxkVb7YAm+tw8=; b=L1N5YPXmraAvBm1itC9ygk8qFrMuPhcZpu+SozU9B7KXf5FvQl/INkriVWOScAKaZV 0+C3vW6mgXhoQtY+cqzvqIp6UZv8Ju8n2wzT1ctCCKhTTYhapUincFpvkUWfoovCp+Qk tZ+mFrRRhb+ZEGVe5XuoM1JxK13DSfA+Hvzv4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=kU6JzS0rX9MFBHCrU+qq60WqPQAwv2AxkVb7YAm+tw8=; b=dG9AEQqts9Cxj4n/nzHxAiOHJOxsmLiirMuY/DJIYHdp98F5vBgWTCL4XnkefsC7GB UdSof1MHkL5FcsnJrNVqGe4/TGiM0DT0b9AuaKwczS8/r5oXDRo50h3X7/fLJBmUP7d+ nZghiERJjj8MNlNEWRCpFQiB+b9lyjDYYFSo/cAQvxGwj8nFgk79SM65HjyYMoPtbQtV NfNsGdt1RC87zS3jO+i2OyzMg+9ABDRmF0vkk5vWg5Y+sre7TgvQ4jEhZ5LqMxH1bVz/ 1RZiZFyR5ytA8+2S1oEjUKmhn73RZFDOvDL86/TpC+QjSnF9AxjggvDR1dtisy4xGZ0T zh6Q== MIME-Version: 1.0 X-Received: by 10.182.115.134 with SMTP id jo6mr1636828obb.84.1371220389845; Fri, 14 Jun 2013 07:33:09 -0700 (PDT) Received: by 10.60.139.212 with HTTP; Fri, 14 Jun 2013 07:33:09 -0700 (PDT) Date: Fri, 14 Jun 2013 15:33:09 +0100 Message-ID: From: Dave Cridland To: "imapext@ietf.org" Content-Type: multipart/alternative; boundary=089e0102fb063eebcf04df1e2056 X-Gm-Message-State: ALoCoQnL0DmEpB3zUb6duYkR/5smpfh3qMf1pwflOZTsl8fm5TdA6Xa6TcAcZ4inNy4QG3t660db Subject: [imapext] qresync - State Of The Working Group 2013-06-14 X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2013 14:33:11 -0000 --089e0102fb063eebcf04df1e2056 Content-Type: text/plain; charset=ISO-8859-1 (Ex Cathedra*) Just to summarize where we are and next steps: - Ken Murchison reviewed the two drafts, comparing them to the implementation in Cyrus IMAP. - Short discussion afterward concerning per-metadata modification sequences (and whether we need them). As chairmen, we'd like to see more reviews, and any opinions on whether per-metadata modification sequences can be removed entirely or not. If you're intending checking the current drafts against your implementation, writing an implementation against the current drafts, or simply would like to volunteer to read through the drafts and point out areas they can be improved. Our impression is that there's an overall feeling that the two drafts should be combined; if anyone has strong feelings either way it'd be useful to make these known. Thanks, Eliot / Dave * - From The Chair --089e0102fb063eebcf04df1e2056 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
(Ex Cathedra*)

Just to= summarize where we are and next steps:

=A0- Ken M= urchison reviewed the two drafts, comparing them to the implementation in C= yrus IMAP.
=A0- Short discussion afterward concerning per-metadata modification s= equences (and whether we need them).

As chairmen, = we'd like to see more reviews, and any opinions on whether per-metadata= modification sequences can be removed entirely or not. If you're inten= ding checking the current drafts against your implementation, writing an im= plementation against the current drafts, or simply would like to volunteer = to read through the drafts and point out areas they can be improved.

Our impression is that there's an overall feeling t= hat the two drafts should be combined; if anyone has strong feelings either= way it'd be useful to make these known.

Thank= s,

Eliot / Dave
* - From The Chair
--089e0102fb063eebcf04df1e2056-- From jkt@flaska.net Fri Jun 14 07:48:45 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 483AA21F9C9F for ; Fri, 14 Jun 2013 07:48:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.3 X-Spam-Level: X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ny2mig0KZvCr for ; Fri, 14 Jun 2013 07:48:44 -0700 (PDT) Received: from latimerie.flaska.net (latimerie.flaska.net [IPv6:2a02:2b88:2:1::4a7:333]) by ietfa.amsl.com (Postfix) with ESMTP id 735CF21F9BD1 for ; Fri, 14 Jun 2013 07:48:44 -0700 (PDT) Received: by latimerie.flaska.net (Postfix, from userid 1000) id 92FE460C7A; Fri, 14 Jun 2013 16:48:42 +0200 (CEST) From: =?iso-8859-1?Q?Jan_Kundr=E1t?= To: Date: Fri, 14 Jun 2013 16:48:42 +0200 User-Agent: trojita/v0.3.93-176-ge0ca405; Qt/4.8.4; X11; Linux; MIME-Version: 1.0 Message-ID: <82ff2ed9-0555-415e-8d5c-633e7670c722@flaska.net> In-Reply-To: References: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Subject: [imapext] Re: qresync - State Of The Working Group 2013-06-14 X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2013 14:48:45 -0000 On Friday, 14 June 2013 16:33:09 CEST, Dave Cridland wrote:=0A> As chai= rmen, we'd like to see more reviews, and any opinions on whether=0A> pe= r-metadata modification sequences can be removed entirely or not. If=0A= > you're intending checking the current drafts against your implementat= ion,=0A> writing an implementation against the current drafts, or simpl= y would like=0A> to volunteer to read through the drafts and point out = areas they can be=0A> improved.=0A=0AAre the XML sources of these draft= s available somewhere, preferably in some kind of a SCM?=0A=0AWith kind= regards,=0AJan=0A=0A-- =0ATrojit=C3=A1, a fast Qt IMAP e-mail client -= - http://trojita.flaska.net/ From alexey.melnikov@isode.com Fri Jun 14 10:21:49 2013 Return-Path: X-Original-To: imapext@ietfa.amsl.com Delivered-To: imapext@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 519CC21F9B77 for ; Fri, 14 Jun 2013 10:21:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.385 X-Spam-Level: X-Spam-Status: No, score=-102.385 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H3iZYRU194On for ; Fri, 14 Jun 2013 10:21:48 -0700 (PDT) Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE4521F9D21 for ; Fri, 14 Jun 2013 10:21:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1371230507; d=isode.com; s=selector; i=@isode.com; bh=28YWFpdUCvhHH0b2bPCtX1JNktMiBPDlr+9diRsx25c=; 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=o3wGZnjr1roc2MekV8ZSLgi6kvZoe9z/9Ab1pmq4PJLFIZ1jNHAfesXTjEueYYTIPb759k 2EJgVIVkIkQhrNkdEm46v1IEtcxRJFv+i4DYUzJcZbvliZszTQ+kbnRnwVreDoj2pplBlJ 7lSpT1irVExAmq3KPqt7kt0Cr9fT5iM=; Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by waldorf.isode.com (submission channel) via TCP with ESMTPA id ; Fri, 14 Jun 2013 18:21:47 +0100 Message-ID: <51BB5132.5050400@isode.com> Date: Fri, 14 Jun 2013 18:21:54 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 To: =?ISO-8859-1?Q?Jan_Kundr=E1t?= References: <82ff2ed9-0555-415e-8d5c-633e7670c722@flaska.net> In-Reply-To: <82ff2ed9-0555-415e-8d5c-633e7670c722@flaska.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: quoted-printable Cc: imapext@ietf.org Subject: Re: [imapext] qresync - State Of The Working Group 2013-06-14 X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2013 17:21:49 -0000 Hi Jan, On 14/06/2013 15:48, Jan Kundr=E1t wrote: > On Friday, 14 June 2013 16:33:09 CEST, Dave Cridland wrote: >> As chairmen, we'd like to see more reviews, and any opinions on whether >> per-metadata modification sequences can be removed entirely or not. If >> you're intending checking the current drafts against your=20 >> implementation, >> writing an implementation against the current drafts, or simply would=20 >> like >> to volunteer to read through the drafts and point out areas they can be >> improved. > Are the XML sources of these drafts available somewhere, preferably in=20 > some kind of a SCM? At the moment they are only available from the editor (me).