From nobody Tue Oct 1 22:48:50 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09094120077 for ; Tue, 1 Oct 2019 22:48:48 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=BFAmT6ud; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PV8xEgpI 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 bsbBeF0rFVEw for ; Tue, 1 Oct 2019 22:48:46 -0700 (PDT) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 249C4120041 for ; Tue, 1 Oct 2019 22:48:46 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 47E556BB for ; Wed, 2 Oct 2019 01:48:45 -0400 (EDT) Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Wed, 02 Oct 2019 01:48:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm3; bh=z3FAmQz auwUhrD9txzc+/p0Bx0Z7+KVduRJbvwsa0PA=; b=BFAmT6udENlxeSU8LpqNRNA zzvOe5o37EALa1raOcUdjcm7d+j0zjgccOVTd0Jd06CCNY54hZxZki5BEtQHY8rV xGX6UD/WBZ/VYVBZPsXh1v07pl84P+P6GdC0gdV+aJeiUZ0xDmBt9l9TxK9mPWdk 7HicYhUFQP9Q249A3qIpo8Ji7qhbnVql/J8gVJp6RUaDytgKJtNpvw2MDCgCIJdt tNh42uw5o92+I8wTFrUEckyhq0Z3omHLrFP/BjwHC2OxEhwQZmboKSeYTjs5mq5E 6ZUx2S36jt2+zagV3fc8o1cyLY/vFnLymhz3W0JlXka2Kc5BJTO6GsH3oflXhqA= = DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=z3FAmQ zauwUhrD9txzc+/p0Bx0Z7+KVduRJbvwsa0PA=; b=PV8xEgpI72Sl/mvZhVfy2B HA/q/M3fLYWmJtAAR3K+qAhrvX/rwu30Dbq+yTUv4AoFVEEc8ksLtnm3qpxL7y+h yty/O3pmJ7RlXZ/QGSRvxLO5SeaZ8oo2zBMUsMWUdRt+YoiudL/dKlA7aMzM/D+z sUKU9eGFBkuYZcHpV16yZAInVDeKsyltfeGxrxGd3Xs7zGq2oTigqJKxACBoOZAL xqFYXWrts+GgXGNfZIU8AdmOY/kbFdOP65iip6Utf+s80d1Yr7vV5kUI9m2ZHwmo r6Da5kZkmKUoyrWIperD6r4HGCQRazJE+qYBJWdg3gTXPy+BmfsjlT1ACcOr4xkg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrgeehgdellecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuffhomhgrihhnpehivghtfhdrohhrghenuc frrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgt ohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 772A6300073; Wed, 2 Oct 2019 01:48:44 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-359-g64bf1af-fmstable-20191002v2 Mime-Version: 1.0 Message-Id: <3e9f6f5f-24a7-4bc4-bcbf-3bb5b35b5dd2@beta.fastmail.com> In-Reply-To: <06bee04e-a943-4415-90b1-9b15f33952c7@beta.fastmail.com> References: <06bee04e-a943-4415-90b1-9b15f33952c7@beta.fastmail.com> Date: Wed, 02 Oct 2019 15:48:24 +1000 From: "Bron Gondwana" To: extra@ietf.org Content-Type: multipart/alternative; boundary=44e9074f76e646f6b0f8abfab7af1e59 Archived-At: Subject: Re: [Extra] Shall we meet in Singapore? X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2019 05:48:48 -0000 --44e9074f76e646f6b0f8abfab7af1e59 Content-Type: text/plain You've got 2 days to speak up, or forever hold your peace! (until Vancouver in March at least) On Tue, Oct 1, 2019, at 15:14, Bron Gondwana wrote: > I'll be there this time! Looking at our outstanding work, the two bits are: > > * IMAP4rev2 > * QUOTA-BIS > > I suspect we'll be talking about QUOTA-BIS a bit over in JMAP as well as we try to align the newly accepted jmap-quotas draft. > > fetch-preview is underway, and we don't have any other proposed work showing up except for the outstanding question of "where should CLIENTID" go. > > So the question really is: is there something productive we could achieve in Singapore meeting face to face? If so, I'll ask for a session. If not, we'll free up the time for other IETF uses. > > Cheers, > > Bron. > > -- > Bron Gondwana, CEO, Fastmail Pty Ltd > brong@fastmailteam.com > > > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra > -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com --44e9074f76e646f6b0f8abfab7af1e59 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
You've got 2 days to speak up, or forever hold your p= eace!

(until Vancouver in March at least)

On Tue, Oct 1, 2019, at 15:14= , Bron Gondwana wrote:
I'll be there this time!  Looking at = our outstanding work, the two bits are:

* IMAP4rev2
* QUOTA-BIS

I suspe= ct we'll be talking about QUOTA-BIS a bit over in JMAP as well as we try= to align the newly accepted jmap-quotas draft.

fetch-pre= view is underway, and we don't have any other proposed work showing up e= xcept for the outstanding question of "where should CLIENTID" go.

So the question really is: is there something productive we cou= ld achieve in Singapore meeting face to face?  If so, I'll ask for = a session.  If not, we'll free up the time for other IETF uses.
=

Cheers,

Bro= n.

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


_______________________________________________
Ex= tra mailing list
Extra@ietf.org
https://www.= ietf.org/mailman/listinfo/extra


--
  Bron Gondw= ana, CEO, Fastmail Pty Ltd
  bron= g@fastmailteam.com


--44e9074f76e646f6b0f8abfab7af1e59-- From nobody Wed Oct 2 01:58:49 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA89D1200FF for ; Wed, 2 Oct 2019 01:58:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com 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 vV5UH8Scf0yH for ; Wed, 2 Oct 2019 01:58:45 -0700 (PDT) Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 631DE1200D7 for ; Wed, 2 Oct 2019 01:58:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1570006724; d=isode.com; s=june2016; i=@isode.com; bh=WjUWsFlJ5L7ik6UhPzaG9sSjS19/MWBDdAdPBfPoOEg=; 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=ezjSqCRBcMXw+7XQBp4qrYvi0a4tuanafUfPlPH+hQapcbri0gv9xwvGQ6CT5MjQ3D83Xl mL6ZFuiZ9FkVvn6Q91ObJzzjC7hZNRuYgCiS1wZmQzlum2pLeA9ihaSY9/P54Oi9Gc0uqM RS1ZMMn9NQUkcBz2p4YORyypUzZ8+ms=; Received: from [192.168.0.12] (cpc121086-nmal24-2-0-cust54.19-2.cable.virginm.net [77.97.145.55]) by statler.isode.com (submission channel) via TCP with ESMTPSA id ; Wed, 2 Oct 2019 09:58:44 +0100 From: Alexey Melnikov X-Mailer: iPad Mail (16G102) In-Reply-To: <3e9f6f5f-24a7-4bc4-bcbf-3bb5b35b5dd2@beta.fastmail.com> Date: Wed, 2 Oct 2019 09:58:43 +0100 Cc: extra@ietf.org Message-Id: <58420E9B-348D-4A0A-99FB-715622F29458@isode.com> References: <06bee04e-a943-4415-90b1-9b15f33952c7@beta.fastmail.com> <3e9f6f5f-24a7-4bc4-bcbf-3bb5b35b5dd2@beta.fastmail.com> To: Bron Gondwana MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=Apple-Mail-8E6A5CA8-1A84-4A38-A819-6E11990C8FCC Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Extra] Shall we meet in Singapore? X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2019 08:58:47 -0000 --Apple-Mail-8E6A5CA8-1A84-4A38-A819-6E11990C8FCC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hi Bron, > On 2 Oct 2019, at 06:48, Bron Gondwana wrote: >=20 > You've got 2 days to speak up, or forever hold your peace! >=20 > (until Vancouver in March at least) >=20 >> On Tue, Oct 1, 2019, at 15:14, Bron Gondwana wrote: >> I'll be there this time! Looking at our outstanding work, the two bits a= re: >>=20 >> * IMAP4rev2 >> * QUOTA-BIS I will have revisions of both of these before Singapore to discuss remaining= issues. So I would like to discuss them. If we can have a short slot, that w= ould be great. Best Regards, Alexey >>=20 >> I suspect we'll be talking about QUOTA-BIS a bit over in JMAP as well as w= e try to align the newly accepted jmap-quotas draft. >>=20 >> fetch-preview is underway, and we don't have any other proposed work show= ing up except for the outstanding question of "where should CLIENTID" go. >>=20 >> So the question really is: is there something productive we could achieve= in Singapore meeting face to face? If so, I'll ask for a session. If not,= we'll free up the time for other IETF uses. >>=20 >> Cheers, >>=20 >> Bron. >>=20 >> -- >> Bron Gondwana, CEO, Fastmail Pty Ltd >> brong@fastmailteam.com >>=20 >>=20 >> _______________________________________________ >> Extra mailing list >> Extra@ietf.org >> https://www.ietf.org/mailman/listinfo/extra >>=20 >=20 > -- > Bron Gondwana, CEO, Fastmail Pty Ltd > brong@fastmailteam.com >=20 >=20 > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra --Apple-Mail-8E6A5CA8-1A84-4A38-A819-6E11990C8FCC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi B= ron,

On 2 Oct 2019, at 06:48, Bron Gondwana <brong@fastmailteam.com> wrote= :

You've got 2 days to speak up, or forever hol= d your peace!

(until Vancouver in March at least)

On Tue, Oct 1, 2019, at 15:14, Br= on Gondwana wrote:
I'll be there this time!  Looking at our outstandi= ng work, the two bits are:

* IMAP4rev2
* QUOTA-BIS
<= br>
I will have revisions of both of these before Singapore to discuss r= emaining issues. So I would like to discuss them. If we can have a short slo= t, that would be great.

Best Regards,
Alexey

I suspect we'll be talking about QUOTA-BIS a bit over in JMAP as well a= s we try to align the newly accepted jmap-quotas draft.

fetch-previ= ew is underway, and we don't have any other proposed work showing up except f= or the outstanding question of "where should CLIENTID" go.

So the= question really is: is there something productive we could achieve in Singa= pore meeting face to face?  If so, I'll ask for a session.  If not= , we'll free up the time for other IETF uses.

Cheers,

=
Bron.

--
  Bron Gondwana, CEO, Fastmai= l Pty Ltd
  brong@fastmailteam.com


___= ____________________________________________
Extra mailing lis= t

--
  Bron Gondwana, CEO, = Fastmail Pty Ltd
  brong@fastmailteam.com


<= /blockquote>
_______________= ________________________________
Extra mailing listExtra@ietf.org
https://www.ietf.or= g/mailman/listinfo/extra
= --Apple-Mail-8E6A5CA8-1A84-4A38-A819-6E11990C8FCC-- From nobody Wed Oct 2 01:59:56 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 532AB12010C for ; Wed, 2 Oct 2019 01:59:55 -0700 (PDT) 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=NX9r39m1; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=zq80zGz1 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 vPdEqe7rVAzy for ; Wed, 2 Oct 2019 01:59:53 -0700 (PDT) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 338E6120106 for ; Wed, 2 Oct 2019 01:59:53 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 62EF25C8 for ; Wed, 2 Oct 2019 04:59:52 -0400 (EDT) Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Wed, 02 Oct 2019 04:59:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm3; bh=9292WUz DbP6I53Jshpxut5B+N9SkeWRRlwAO89m0wZQ=; b=NX9r39m1X+9/3oTDhRsUXCp 6znbTgUSQbLjEa+fXndzdBDBkLI4rK/mZYwtddqK+3o691b9wEhCtliuS/UCZzi1 iS4hXYvaOLrrqxfQnGbI1iJoxUWHaCWTOi0ZuFmkU1tIXMvphn2aNTQY+YmQ8a09 DhZSPIB+2PqGHLdJjVUqZ08028yUhUfuM2cHHcTE4WbAEIohOj2nB6pT+WlsTC0I /rUgrIdWHGjpesw/dm7tcsfYJ0f1AhfpZlQdxTSOcgv9Scduz4hF49nSb12pEp2P KLZiY6l1TVMw6RWYmTWwUL3dGxmSuYA/vdYlBcCHKUEpxw8n9OaZoSj+Xs0drrA= = DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=9292WU zDbP6I53Jshpxut5B+N9SkeWRRlwAO89m0wZQ=; b=zq80zGz14IP2IfxbLSwNyr gAAVDX6EetkZGlVK2DhNaH2QkG4oi151KVlM4iF3Tb56bmY931+AJ299iUxe7/75 MTTID/UDzBuE/XKuz7Rw3F4dS8zOlhk+960To0jgPmRh3Cu1Wbr/lnY39ZSOC7h3 LeJm65wSprk5ID3fJJ3GwkU4qzbWZI3C4wpVRU0yAuhh+rjoVIQNBqFof6Rj5a8+ dOEZ3rYiwUVPB/0zYyhrQBNHkp3a2lN/HjfXmJEC6LJJ0jGoFR6OKQEDX+9BNhKr 3NYU3Y3qXvOPnPFwNpZ1wSYWh91bQo0Eo/+CVZARYodveH6pZN62NxmdgDl87scQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrgeeigdduudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuffhomhgrihhnpehivghtfhdrohhrghenuc frrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgt ohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id AD267300073; Wed, 2 Oct 2019 04:59:51 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-359-g64bf1af-fmstable-20191002v2 Mime-Version: 1.0 Message-Id: In-Reply-To: <58420E9B-348D-4A0A-99FB-715622F29458@isode.com> References: <06bee04e-a943-4415-90b1-9b15f33952c7@beta.fastmail.com> <3e9f6f5f-24a7-4bc4-bcbf-3bb5b35b5dd2@beta.fastmail.com> <58420E9B-348D-4A0A-99FB-715622F29458@isode.com> Date: Wed, 02 Oct 2019 18:59:29 +1000 From: "Bron Gondwana" To: extra@ietf.org Content-Type: multipart/alternative; boundary=dc7d03d98d744381a2fd3e513f61dd54 Archived-At: Subject: Re: [Extra] Shall we meet in Singapore? X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2019 08:59:56 -0000 --dc7d03d98d744381a2fd3e513f61dd54 Content-Type: text/plain Excellent, I'll put in for an hour then. On Wed, Oct 2, 2019, at 18:58, Alexey Melnikov wrote: > > Hi Bron, > > On 2 Oct 2019, at 06:48, Bron Gondwana wrote: >> You've got 2 days to speak up, or forever hold your peace! >> >> (until Vancouver in March at least) >> >> On Tue, Oct 1, 2019, at 15:14, Bron Gondwana wrote: >>> I'll be there this time! Looking at our outstanding work, the two bits are: >>> >>> * IMAP4rev2 >>> * QUOTA-BIS > > I will have revisions of both of these before Singapore to discuss remaining issues. So I would like to discuss them. If we can have a short slot, that would be great. > > Best Regards, > Alexey >>> >>> I suspect we'll be talking about QUOTA-BIS a bit over in JMAP as well as we try to align the newly accepted jmap-quotas draft. >>> >>> fetch-preview is underway, and we don't have any other proposed work showing up except for the outstanding question of "where should CLIENTID" go. >>> >>> So the question really is: is there something productive we could achieve in Singapore meeting face to face? If so, I'll ask for a session. If not, we'll free up the time for other IETF uses. >>> >>> Cheers, >>> >>> Bron. >>> >>> -- >>> Bron Gondwana, CEO, Fastmail Pty Ltd >>> brong@fastmailteam.com >>> >>> >>> _______________________________________________ >>> Extra mailing list >>> Extra@ietf.org >>> https://www.ietf.org/mailman/listinfo/extra >>> >> >> -- >> Bron Gondwana, CEO, Fastmail Pty Ltd >> brong@fastmailteam.com >> >> >> _______________________________________________ >> Extra mailing list >> Extra@ietf.org >> https://www.ietf.org/mailman/listinfo/extra > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra > -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com --dc7d03d98d744381a2fd3e513f61dd54 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Excellent, I'll put in for an hour then.

On Wed, Oct 2, 2019, at 18:58, Alexe= y Melnikov wrote:

Hi Bron,

On 2 Oct 2019, at 06:48, Bron Gondwana <brong@fastmailteam.com> wrote:
You've got 2 days to speak up, or forever hold your peace!

(until Vancouver in March at least)

On Tue, Oct 1, 2019, at 15:14, Bron Gondwana wr= ote:
I'll be there this time!  Looking at our outstanding= work, the two bits are:

=
* IMAP4rev2
* QUOTA-BIS

I will have revisions= of both of these before Singapore to discuss remaining issues. So I wou= ld like to discuss them. If we can have a short slot, that would be grea= t.

Best Regards,
Alexey

I suspect we'll be ta= lking about QUOTA-BIS a bit over in JMAP as well as we try to align the = newly accepted jmap-quotas draft.

fetch-preview is underw= ay, and we don't have any other proposed work showing up except for the = outstanding question of "where should CLIENTID" go.

So the = question really is: is there something productive we could achieve in Si= ngapore meeting face to face?  If so, I'll ask for a session. = If not, we'll free up the time for other IETF uses.

Chee= rs,

Bron.

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong= @fastmailteam.com

=

_________________= ______________________________


--
  = Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.co= m


___________= ____________________________________
Extra mailing list
_____= __________________________________________
Extra mailing l= ist
Extra@ietf.org
https://www.ietf.org/mail= man/listinfo/extra


--
  Bron Gondwana, CEO, Fas= tmail Pty Ltd
  brong@fastmailtea= m.com

--dc7d03d98d744381a2fd3e513f61dd54-- From nobody Wed Oct 2 14:06:12 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86E6812002F for ; Wed, 2 Oct 2019 14:06:10 -0700 (PDT) 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_05=-0.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 GlfSC4eWuyAw for ; Wed, 2 Oct 2019 14:06:08 -0700 (PDT) Received: from fe1.cityemail.com (mail-ob1.cityemail.com [104.128.152.18]) by ietfa.amsl.com (Postfix) with ESMTP id 7B0FE120018 for ; Wed, 2 Oct 2019 14:06:08 -0700 (PDT) Received: (qmail 28785 invoked from network); 2 Oct 2019 21:06:06 -0000 Received: from riddle.wizard.ca (HELO [192.168.1.55]) (michael@wizard.ca@104.128.144.8) by fe1.cityemail.com with (AES128-SHA encrypted) SMTP (732fb79a-e558-11e9-af7f-97f6a1ce26ae); Wed, 02 Oct 2019 14:06:06 -0700 To: extra@ietf.org References: <06bee04e-a943-4415-90b1-9b15f33952c7@beta.fastmail.com> <3e9f6f5f-24a7-4bc4-bcbf-3bb5b35b5dd2@beta.fastmail.com> <58420E9B-348D-4A0A-99FB-715622F29458@isode.com> From: Michael Peddemors Organization: LinuxMagic Inc. Message-ID: <322929df-28ea-8bf8-05cc-af88cad9ff3f@linuxmagic.com> Date: Wed, 2 Oct 2019 14:06:06 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <58420E9B-348D-4A0A-99FB-715622F29458@isode.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-MagicMail-OS: Linux 3.11 and newer X-MagicMail-UUID: 732fb79a-e558-11e9-af7f-97f6a1ce26ae X-MagicMail-Authenticated: michael@wizard.ca X-MagicMail-SourceIP: 104.128.144.8 X-MagicMail-RegexMatch: 0 X-MagicMail-EnvelopeFrom: X-Archive: Yes Archived-At: Subject: Re: [Extra] Shall we meet in Singapore? X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2019 21:06:11 -0000 On 2019-10-02 1:58 a.m., Alexey Melnikov wrote: > You've got 2 days to speak up, or forever hold your peace! > > (until Vancouver in March at least) I guess we will have to start thinking about a sponsorship event during Vancouver.. Doubt I can make Singapore at this late notice. But have a few other things would look forward to having some informal conversations, as well as pushing the CLIENTID more towards formal standards review, given that more and more parties are engaging and discussing implementation. -- "Catch the Magic of Linux..." ------------------------------------------------------------------------ Michael Peddemors, President/CEO LinuxMagic Inc. Visit us at http://www.linuxmagic.com @linuxmagic A Wizard IT Company - For More Info http://www.wizard.ca "LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd. ------------------------------------------------------------------------ 604-682-0300 Beautiful British Columbia, Canada This email and any electronic data contained are confidential and intended solely for the use of the individual or entity to which they are addressed. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company. From nobody Wed Oct 2 17:11:29 2019 Return-Path: X-Original-To: extra@ietf.org Delivered-To: extra@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B58AC120896; Wed, 2 Oct 2019 17:11:19 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: extra@ietf.org, brong@fastmailteam.com, barryleiba@computer.org, extra-chairs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.104.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <157006147973.8961.7437940413228893489.idtracker@ietfa.amsl.com> Date: Wed, 02 Oct 2019 17:11:19 -0700 Archived-At: Subject: [Extra] extra - New Meeting Session Request for IETF 106 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2019 00:11:27 -0000 A new meeting session request has just been submitted by Bron Gondwana, a Chair of the extra working group. --------------------------------------------------------- Working Group Name: Email mailstore and eXtensions To Revise or Amend Area Name: Applications and Real-Time Area Session Requester: Bron Gondwana Number of Sessions: 1 Length of Session(s): 1 Hour Number of Attendees: 15 Conflicts to Avoid: Chair Conflict: jmap calext dispatch People who must be present: Barry Leiba Alexey Melnikov Jiankang Yao Bron Gondwana Resources Requested: Special Requests: --------------------------------------------------------- From nobody Fri Oct 18 01:56:07 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9049212087C for ; Fri, 18 Oct 2019 01:56:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 uO3DeyjiCVwO for ; Fri, 18 Oct 2019 01:56:04 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21BDD120106 for ; Fri, 18 Oct 2019 01:56:04 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id C6DE2B80119; Fri, 18 Oct 2019 01:55:59 -0700 (PDT) To: stephan.bosch@open-xchange.com, barryleiba@computer.org, aamelnikov@fastmail.fm, adam@nostrum.com, brong@fastmailteam.com, yaojk@cnnic.cn X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: stephan.bosch@open-xchange.com, extra@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20191018085559.C6DE2B80119@rfc-editor.org> Date: Fri, 18 Oct 2019 01:55:59 -0700 (PDT) Archived-At: Subject: [Extra] [Technical Errata Reported] RFC8579 (5877) X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Oct 2019 08:56:06 -0000 The following errata report has been submitted for RFC8579, "Sieve Email Filtering: Delivering to Special-Use Mailboxes". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid5877 -------------------------------------- Type: Technical Reported by: Stephan Bosch Section: 6 Original Text ------------- require "imapsieve"; require "special-use"; require "environment"; require "variables"; if environment :contains "imap.mailbox" "*" { set "mailbox" ""; } if allof( environment "imap.cause" "COPY", specialuse_exists "${mailbox}" "\Junk") { redirect "spam-report@example.org"; } Corrected Text -------------- require "imapsieve"; require "special-use"; require "environment"; require "variables"; if environment :matches "imap.mailbox" "*" { set "mailbox" ""; } if allof( environment "imap.cause" "COPY", specialuse_exists "${mailbox}" "\Junk") { redirect "spam-report@example.org"; } Notes ----- The final example is using the ":contains" match type to extract a match variable, which will not work. It should use ":matches" instead. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8579 (draft-ietf-extra-sieve-special-use-05) -------------------------------------- Title : Sieve Email Filtering: Delivering to Special-Use Mailboxes Publication Date : May 2019 Author(s) : S. Bosch Category : PROPOSED STANDARD Source : Email mailstore and eXtensions To Revise or Amend Area : Applications and Real-Time Stream : IETF Verifying Party : IESG From nobody Fri Oct 18 09:30:20 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7652B1200F9 for ; Fri, 18 Oct 2019 09:30:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 amFXFD6xSEwW for ; Fri, 18 Oct 2019 09:30:15 -0700 (PDT) Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (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 A489912000F for ; Fri, 18 Oct 2019 09:30:15 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RCQVKSOTNK00RJWX@mauve.mrochek.com> for extra@ietf.org; Fri, 18 Oct 2019 09:25:09 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: TEXT/PLAIN; CHARSET=us-ascii Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RCQ16MSFR400Z8EC@mauve.mrochek.com>; Fri, 18 Oct 2019 09:25:06 -0700 (PDT) Cc: stephan.bosch@open-xchange.com, barryleiba@computer.org, aamelnikov@fastmail.fm, adam@nostrum.com, brong@fastmailteam.com, yaojk@cnnic.cn, extra@ietf.org, rfc-editor@rfc-editor.org Message-id: <01RCQVKQX0I600Z8EC@mauve.mrochek.com> Date: Fri, 18 Oct 2019 09:20:31 -0700 (PDT) From: Ned Freed In-reply-to: "Your message dated Fri, 18 Oct 2019 01:55:59 -0700 (PDT)" <20191018085559.C6DE2B80119@rfc-editor.org> Sender: Ned Freed References: <20191018085559.C6DE2B80119@rfc-editor.org> To: RFC Errata System Archived-At: Subject: Re: [Extra] [Technical Errata Reported] RFC8579 (5877) X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Oct 2019 16:30:18 -0000 The issue and fix are both correct, however, there's an error in both the original and corrected text, noted below. Ned > The following errata report has been submitted for RFC8579, > "Sieve Email Filtering: Delivering to Special-Use Mailboxes". > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid5877 > -------------------------------------- > Type: Technical > Reported by: Stephan Bosch > Section: 6 > Original Text > ------------- > require "imapsieve"; > require "special-use"; > require "environment"; > require "variables"; > if environment :contains "imap.mailbox" "*" { > set "mailbox" ""; This line should read: set "mailbox" "${1}"; > } > if allof( > environment "imap.cause" "COPY", > specialuse_exists "${mailbox}" "\Junk") { > redirect "spam-report@example.org"; > } > Corrected Text > -------------- > require "imapsieve"; > require "special-use"; > require "environment"; > require "variables"; > if environment :matches "imap.mailbox" "*" { > set "mailbox" ""; Same thing: set "mailbox" "${1}"; > } > if allof( > environment "imap.cause" "COPY", > specialuse_exists "${mailbox}" "\Junk") { > redirect "spam-report@example.org"; > } > Notes > ----- > The final example is using the ":contains" match type to extract a match variable, which will not work. It should use ":matches" instead. > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > can log in to change the status and edit the report, if necessary. > -------------------------------------- > RFC8579 (draft-ietf-extra-sieve-special-use-05) > -------------------------------------- > Title : Sieve Email Filtering: Delivering to Special-Use Mailboxes > Publication Date : May 2019 > Author(s) : S. Bosch > Category : PROPOSED STANDARD > Source : Email mailstore and eXtensions To Revise or Amend > Area : Applications and Real-Time > Stream : IETF > Verifying Party : IESG > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra From nobody Fri Oct 18 18:55:17 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A64412012E for ; Fri, 18 Oct 2019 18:55:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.478 X-Spam-Level: X-Spam-Status: No, score=-1.478 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.172, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=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 ECPlYAjHGieD for ; Fri, 18 Oct 2019 18:55:15 -0700 (PDT) Received: from mail-io1-f65.google.com (mail-io1-f65.google.com [209.85.166.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CDA4120020 for ; Fri, 18 Oct 2019 18:55:15 -0700 (PDT) Received: by mail-io1-f65.google.com with SMTP id b136so9637228iof.3 for ; Fri, 18 Oct 2019 18:55:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c1fb9lQaqLHO8N8zBPsuX82OlodxeT5XRkqRwbdvCOE=; b=hFB3dIjLZr3j9Ni+r9XylhUsEYUCj2tmqkfoyX7coE0V48XBbZ3ugBlUyU7Yw/q+Rh WPQlkhh4y0/af+xbwn5Wh/zGpv4KgyizWBkfHu90JOMsFbGIT1uNNkzJfIVBMw/cLtai BC6SoPsiHTvLXm/ZSd9MUutcqr4rqTl7YuY9hXVzzJ855XGR3oYgiWm8Rjyt24/6c5lA JTUCTbWIl7APZZZqXXNB05r99GNaL2vUwk/SupU2K20eXJ/88gDnNddFAhS7XmdFMCQt 2CRU9speVtDifYoEzWB+L41iHUJsugS5HoU17NJ563r/WMhgCIER59ZPHTf5gbH3Ww2o +Cww== X-Gm-Message-State: APjAAAVUWaOeX6RM/wcnsS5RHBh+p0Yy3+DxM5yUHuCIjAtr8umh9f8R HOSg9UUZwsjj4tcwCgwU5m2tUW+kVenJZjN0LS8= X-Google-Smtp-Source: APXvYqyGaKeyeFW4CJ+mNry4sSoLyBJBG6XG67napSO7ii6fRtGtMHBZ22Uqk6Kz7tkBnWCZdn7gXJvY+uDmON78VYg= X-Received: by 2002:a5d:96cb:: with SMTP id r11mr1072135iol.266.1571450112890; Fri, 18 Oct 2019 18:55:12 -0700 (PDT) MIME-Version: 1.0 References: <20191018085559.C6DE2B80119@rfc-editor.org> <01RCQVKQX0I600Z8EC@mauve.mrochek.com> In-Reply-To: <01RCQVKQX0I600Z8EC@mauve.mrochek.com> From: Barry Leiba Date: Fri, 18 Oct 2019 21:55:02 -0400 Message-ID: To: Ned Freed Cc: RFC Errata System , stephan.bosch@open-xchange.com, Alexey Melnikov , Adam Roach , Bron Gondwana , YAO Jiankang , extra@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Extra] [Technical Errata Reported] RFC8579 (5877) X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Oct 2019 01:55:16 -0000 > The issue and fix are both correct, however, there's an error in both > the original and corrected text, noted below. There's no error there: the problem is in the errata system, in that it turns the "dollar-brace-1-brace" into a null string in the email message. The correct string does appear in the errata report. I will mark it Verified now. Barry > > The following errata report has been submitted for RFC8579, > > "Sieve Email Filtering: Delivering to Special-Use Mailboxes". > > > -------------------------------------- > > You may review the report below and at: > > https://www.rfc-editor.org/errata/eid5877 > > > -------------------------------------- > > Type: Technical > > Reported by: Stephan Bosch > > > Section: 6 > > > Original Text > > ------------- > > require "imapsieve"; > > require "special-use"; > > require "environment"; > > require "variables"; > > > if environment :contains "imap.mailbox" "*" { > > set "mailbox" ""; > > This line should read: > > set "mailbox" "${1}"; > > > } > > > if allof( > > environment "imap.cause" "COPY", > > specialuse_exists "${mailbox}" "\Junk") { > > redirect "spam-report@example.org"; > > } > > > > Corrected Text > > -------------- > > require "imapsieve"; > > require "special-use"; > > require "environment"; > > require "variables"; > > > if environment :matches "imap.mailbox" "*" { > > set "mailbox" ""; > > Same thing: > > set "mailbox" "${1}"; > > > } > > > if allof( > > environment "imap.cause" "COPY", > > specialuse_exists "${mailbox}" "\Junk") { > > redirect "spam-report@example.org"; > > } > > > > Notes > > ----- > > The final example is using the ":contains" match type to extract a match variable, which will not work. It should use ":matches" instead. > > > Instructions: > > ------------- > > This erratum is currently posted as "Reported". If necessary, please > > use "Reply All" to discuss whether it should be verified or > > rejected. When a decision is reached, the verifying party > > can log in to change the status and edit the report, if necessary. > > > -------------------------------------- > > RFC8579 (draft-ietf-extra-sieve-special-use-05) > > -------------------------------------- > > Title : Sieve Email Filtering: Delivering to Special-Use Mailboxes > > Publication Date : May 2019 > > Author(s) : S. Bosch > > Category : PROPOSED STANDARD > > Source : Email mailstore and eXtensions To Revise or Amend > > Area : Applications and Real-Time > > Stream : IETF > > Verifying Party : IESG > > > _______________________________________________ > > Extra mailing list > > Extra@ietf.org > > https://www.ietf.org/mailman/listinfo/extra From nobody Fri Oct 18 18:55:42 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A07FD12012E; Fri, 18 Oct 2019 18:55:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 V1bWlJAljljz; Fri, 18 Oct 2019 18:55:39 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F18E3120020; Fri, 18 Oct 2019 18:55:38 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 2F387B80B5E; Fri, 18 Oct 2019 18:55:34 -0700 (PDT) To: stephan.bosch@open-xchange.com, stephan.bosch@open-xchange.com X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: barryleiba@computer.org, iesg@ietf.org, extra@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20191019015534.2F387B80B5E@rfc-editor.org> Date: Fri, 18 Oct 2019 18:55:34 -0700 (PDT) Archived-At: Subject: [Extra] [Errata Verified] RFC8579 (5877) X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Oct 2019 01:55:41 -0000 The following errata report has been verified for RFC8579, "Sieve Email Filtering: Delivering to Special-Use Mailboxes". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid5877 -------------------------------------- Status: Verified Type: Technical Reported by: Stephan Bosch Date Reported: 2019-10-18 Verified by: Barry Leiba (IESG) Section: 6 Original Text ------------- require "imapsieve"; require "special-use"; require "environment"; require "variables"; if environment :contains "imap.mailbox" "*" { set "mailbox" ""; } if allof( environment "imap.cause" "COPY", specialuse_exists "${mailbox}" "\Junk") { redirect "spam-report@example.org"; } Corrected Text -------------- require "imapsieve"; require "special-use"; require "environment"; require "variables"; if environment :matches "imap.mailbox" "*" { set "mailbox" ""; } if allof( environment "imap.cause" "COPY", specialuse_exists "${mailbox}" "\Junk") { redirect "spam-report@example.org"; } Notes ----- The final example is using the ":contains" match type to extract a match variable, which will not work. It should use ":matches" instead. -------------------------------------- RFC8579 (draft-ietf-extra-sieve-special-use-05) -------------------------------------- Title : Sieve Email Filtering: Delivering to Special-Use Mailboxes Publication Date : May 2019 Author(s) : S. Bosch Category : PROPOSED STANDARD Source : Email mailstore and eXtensions To Revise or Amend Area : Applications and Real-Time Stream : IETF Verifying Party : IESG From nobody Sat Oct 19 11:39:26 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E207B1200A1 for ; Sat, 19 Oct 2019 11:39:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mailforce.net header.b=GAq66yDH; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=EEm2rr/4 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 lZhKQ37HuNgK for ; Sat, 19 Oct 2019 11:39:22 -0700 (PDT) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DC38120059 for ; Sat, 19 Oct 2019 11:39:22 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 677B03AB; Sat, 19 Oct 2019 14:39:20 -0400 (EDT) Received: from imap6 ([10.202.2.56]) by compute7.internal (MEProxy); Sat, 19 Oct 2019 14:39:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailforce.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm1; bh=Rq+tq581GU8ylfrTmZpAFfRRcoZt mRGfwy9Hor5LtVU=; b=GAq66yDH0v29FIikTx0ayWooddn0Sg57nZkwKNmXc2Bh XdEGRR+N5w4TKvBULvv0SfwCuzjzM9yj8eu19IQcpIuH/3gx0XbpmO9OBwpyggDL Ca2rtG1P13PPpjV0DMTbT7o2JHNmMWZAFwM1wf2iChbJpPDsEo9DeddFV6kvs09e Y320T1dtwgxx/2YkAWJxyfVtnLaSzfcaIm/RbNGDJz90i17fuxAlxfXc6jPvj1Wf TpzaiUtwNAqcS9DmTVq6USpkxRSlWO2GDXYMeCqTfj9dFldvpgTnUR7QcRUOufrT c0WrmUdUe3CIh5yahq0yONLRItKHRGSGch6eG8XWSA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Rq+tq5 81GU8ylfrTmZpAFfRRcoZtmRGfwy9Hor5LtVU=; b=EEm2rr/4zBQbgD2lygZDIm R72nAxCBl/3bmJw8HpBXBSHZUJqeKp6bE3+tM+jdGZVxWP2MwD7hjwkuel/R8Uyl 6JDR6GG+IlTkgzFbXUt7RvBSiDLrwfIbTiff22Q7zr4iSBNBy46jGxg9SEyQaZ0U lTsSGRy7HzR+yRPDFncNd4tsHxdU4yu6+0y8wpZgo/kdZDPPVxhD8V/+9/7x/U4S sCh7uEGi+adzhvvHuyEE6jhCGWZd9Kher3lp67yZIIwQaOtE8e7QEWrSNP/UqA5k oY5px9TBAh9pRrXOzz/bxkFezSk4YLW1n/H+ZOGpxG/Sqor7up5XlRKsshQvFTXA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrkedugdeivdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfufhtrghn ucfmrghlihhstghhfdcuoehsthgrnhesghhlhihphhgvihhnrdhmrghilhhfohhrtggvrd hnvghtqeenucffohhmrghinheprhhftgdqvgguihhtohhrrdhorhhgpdhivghtfhdrohhr ghenucfrrghrrghmpehmrghilhhfrhhomhepshhtrghnsehglhihphhhvghinhdrmhgrih hlfhhorhgtvgdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id A5CC01400A2; Sat, 19 Oct 2019 14:39:18 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-360-g7dda896-fmstable-20191004v2 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20191018085559.C6DE2B80119@rfc-editor.org> <01RCQVKQX0I600Z8EC@mauve.mrochek.com> Date: Sat, 19 Oct 2019 14:38:50 -0400 From: "Stan Kalisch" To: "Barry Leiba" , "Ned Freed" Cc: "Adam Roach" , "Alexey Melnikov" , extra@ietf.org, "Bron Gondwana" , "YAO Jiankang" , stephan.bosch@open-xchange.com, "RFC Errata System" Content-Type: multipart/alternative; boundary=d55ecd6ecb6b42f8a7b5b7afdb3e516f Archived-At: Subject: Re: [Extra] [Technical Errata Reported] RFC8579 (5877) X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Oct 2019 18:39:25 -0000 --d55ecd6ecb6b42f8a7b5b7afdb3e516f Content-Type: text/plain On Fri, Oct 18, 2019, at 9:55 PM, Barry Leiba wrote: > > The issue and fix are both correct, however, there's an error in both > > the original and corrected text, noted below. > > There's no error there: the problem is in the errata system, in that > it turns the "dollar-brace-1-brace" into a null string in the email > message. The correct string does appear in the errata report. > > I will mark it Verified now. This happened when I reported https://www.rfc-editor.org/errata/eid5015 two years ago: https://mailarchive.ietf.org/arch/msg/sieve/kyeol9Rd_d7bWSkenIrrJgQX8nM At the time, I searched the archives to see if this had impacted messages about any other errata but couldn't uncover any. Thanks, Stan > > Barry > > > > The following errata report has been submitted for RFC8579, > > > "Sieve Email Filtering: Delivering to Special-Use Mailboxes". > > > > > -------------------------------------- > > > You may review the report below and at: > > > https://www.rfc-editor.org/errata/eid5877 > > > > > -------------------------------------- > > > Type: Technical > > > Reported by: Stephan Bosch > > > > > Section: 6 > > > > > Original Text > > > ------------- > > > require "imapsieve"; > > > require "special-use"; > > > require "environment"; > > > require "variables"; > > > > > if environment :contains "imap.mailbox" "*" { > > > set "mailbox" ""; > > > > This line should read: > > > > set "mailbox" "${1}"; > > > > > } > > > > > if allof( > > > environment "imap.cause" "COPY", > > > specialuse_exists "${mailbox}" "\Junk") { > > > redirect "spam-report@example.org"; > > > } > > > > > > > Corrected Text > > > -------------- > > > require "imapsieve"; > > > require "special-use"; > > > require "environment"; > > > require "variables"; > > > > > if environment :matches "imap.mailbox" "*" { > > > set "mailbox" ""; > > > > Same thing: > > > > set "mailbox" "${1}"; > > > > > } > > > > > if allof( > > > environment "imap.cause" "COPY", > > > specialuse_exists "${mailbox}" "\Junk") { > > > redirect "spam-report@example.org"; > > > } > > > > > > > Notes > > > ----- > > > The final example is using the ":contains" match type to extract a match variable, which will not work. It should use ":matches" instead. > > > > > Instructions: > > > ------------- > > > This erratum is currently posted as "Reported". If necessary, please > > > use "Reply All" to discuss whether it should be verified or > > > rejected. When a decision is reached, the verifying party > > > can log in to change the status and edit the report, if necessary. > > > > > -------------------------------------- > > > RFC8579 (draft-ietf-extra-sieve-special-use-05) > > > -------------------------------------- > > > Title : Sieve Email Filtering: Delivering to Special-Use Mailboxes > > > Publication Date : May 2019 > > > Author(s) : S. Bosch > > > Category : PROPOSED STANDARD > > > Source : Email mailstore and eXtensions To Revise or Amend > > > Area : Applications and Real-Time > > > Stream : IETF > > > Verifying Party : IESG > > > > > _______________________________________________ > > > Extra mailing list > > > Extra@ietf.org > > > https://www.ietf.org/mailman/listinfo/extra > > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra > --d55ecd6ecb6b42f8a7b5b7afdb3e516f Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Fri, Oct 18, 2019, at 9:55 PM, Barry Leiba wrote:<= br>
> The issue and fix are both correct, however, there's an erro= r in both
> the original a= nd corrected text, noted below.

There's no error there: t= he problem is in the errata system, in that
it turns the "dollar-brace-1-brace" into a null string in= the email
message.  The= correct string does appear in the errata report.

I will = mark it Verified now.

This happened when I r= eported https://www.rfc-editor.org/errata/eid5015 two years ago:
<= div style=3D"font-family:Arial;">

At the time, I searched the archives= to see if this had impacted messages about any other errata but couldn'= t uncover any.


Thanks,
Stan


Barry

> > The following errata report has = been submitted for RFC8579,
&= gt; > "Sieve Email Filtering: Delivering to Special-Use Mailboxes".
>
> > --------------------------------------
> > You may review the repor= t below and at:
> > htt= ps://www.rfc-editor.org/errata/eid5877
>
> > ----= ----------------------------------
> > Type: Technical
> > Reported by: Stephan Bosch <stephan.bosch@open-xchange.c= om>
>
> > Section: 6
>
> &= gt; Original Text
> > -= ------------
> > requir= e "imapsieve";
> > requ= ire "special-use";
> > = require "environment";
> &= gt; require "variables";
>=
> > if environment :co= ntains "imap.mailbox" "*" {
&= gt; >     set "mailbox" "";
>
>= ; This line should read:
>=
>    =   set "mailbox" "${1}";
= >
> > }
>
> > if allof(
&g= t; >     environment "imap.cause" "COPY",
> >     sp= ecialuse_exists "${mailbox}" "\Junk") {
> >     redirect "spam-report@examp= le.org";
> > }
>
>
> > Cor= rected Text
> > -------= -------
> > require "im= apsieve";
> > require "= special-use";
> > requi= re "environment";
> > r= equire "variables";
>
<= /div>
> > if environment :matches= "imap.mailbox" "*" {
> &g= t;     set "mailbox" "";
>
> Sam= e thing:
>
>      set "mail= box" "${1}";
>
> > }
>
> >= if allof(
> > &nb= sp;   environment "imap.cause" "COPY",
> >     specialuse_exists = "${mailbox}" "\Junk") {
> = >     redirect "spam-report@example.org";
> > }
>
><= br>
> > Notes
> > -----
> > The final example is using the ":contains" ma= tch type to extract a match variable, which will not work. It should use= ":matches" instead.
>
=
> > Instructions:
> > -------------
> > This erratum is currently posted= as "Reported". If necessary, please
> > use "Reply All" to discuss whether it should be verifi= ed or
> > rejected. Whe= n a decision is reached, the verifying party
> > can log in to change the status and edit the r= eport, if necessary.
>
=
> > ----------------------= ----------------
> > RF= C8579 (draft-ietf-extra-sieve-special-use-05)
> > --------------------------------------
> > Title   &n= bsp;           : Sieve= Email Filtering: Delivering to Special-Use Mailboxes
> > Publication Date    : = May 2019
> > Author(s)&= nbsp;          : S. Bosch
> > Category  =           : PROPOSED STANDA= RD
> > Source &nbs= p;            : E= mail mailstore and eXtensions To Revise or Amend
> > Area      &n= bsp;         : Applications and = Real-Time
> > Stream&nb= sp;           &nb= sp; : IETF
> > Verifyin= g Party     : IESG
>
> > ____= ___________________________________________
> > Extra mailing list
> > Extra@ietf.org
> > https://www.ietf.org/mailman/listinfo/extra

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


--d55ecd6ecb6b42f8a7b5b7afdb3e516f-- From nobody Fri Oct 25 14:14:33 2019 Return-Path: X-Original-To: extra@ietf.org Delivered-To: extra@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9AB1208D1; Fri, 25 Oct 2019 14:12:07 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: extra@ietf.org, barryleiba@computer.org X-Test-IDTracker: no X-IETF-IDTracker: 6.108.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <157203792711.2724.4529988883991179320.idtracker@ietfa.amsl.com> Date: Fri, 25 Oct 2019 14:12:07 -0700 Archived-At: Subject: [Extra] extra - Requested session has been scheduled for IETF 106 X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Oct 2019 21:12:12 -0000 Dear Bron Gondwana, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. extra Session 1 (1:00 requested) Monday, 18 November 2019, Afternoon Session I 1330-1530 Room Name: Orchard size: 50 --------------------------------------------- Special Note: 1430 - 1530 iCalendar: https://datatracker.ietf.org/meeting/106/sessions/extra.ics Request Information: --------------------------------------------------------- Working Group Name: Email mailstore and eXtensions To Revise or Amend Area Name: Applications and Real-Time Area Session Requester: Bron Gondwana Number of Sessions: 1 Length of Session(s): 1 Hour Number of Attendees: 15 Conflicts to Avoid: Chair Conflict: jmap calext dispatch People who must be present: Barry Leiba Alexey Melnikov Jiankang Yao Bron Gondwana Resources Requested: Special Requests: --------------------------------------------------------- From nobody Mon Oct 28 03:35:57 2019 Return-Path: X-Original-To: extra@ietf.org Delivered-To: extra@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F3F4B12023E; Mon, 28 Oct 2019 03:35:44 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: extra@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.108.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: extra@ietf.org Message-ID: <157225894489.19962.14593569108839173464@ietfa.amsl.com> Date: Mon, 28 Oct 2019 03:35:44 -0700 Archived-At: Subject: [Extra] I-D Action: draft-ietf-extra-imap4rev2-06.txt X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 10:35:50 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Email mailstore and eXtensions To Revise or Amend WG of the IETF. Title : INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev2 Authors : Alexey Melnikov Barry Leiba Filename : draft-ietf-extra-imap4rev2-06.txt Pages : 146 Date : 2019-10-28 Abstract: The Internet Message Access Protocol, Version 4rev2 (IMAP4rev2) allows a client to access and manipulate electronic mail messages on a server. IMAP4rev2 permits manipulation of mailboxes (remote message folders) in a way that is functionally equivalent to local folders. IMAP4rev2 also provides the capability for an offline client to resynchronize with the server. IMAP4rev2 includes operations for creating, deleting, and renaming mailboxes, checking for new messages, permanently removing messages, setting and clearing flags, RFC 5322, RFC 2045 and RFC 2231 parsing, searching, and selective fetching of message attributes, texts, and portions thereof. Messages in IMAP4rev2 are accessed by the use of numbers. These numbers are either message sequence numbers or unique identifiers. IMAP4rev2 does not specify a means of posting mail; this function is handled by a mail submission protocol such as RFC 6409. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-extra-imap4rev2-06 https://datatracker.ietf.org/doc/html/draft-ietf-extra-imap4rev2-06 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-extra-imap4rev2-06 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/ From nobody Mon Oct 28 05:45:32 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C627912004C for ; Mon, 28 Oct 2019 05:45:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 GvkB24w9MxwT for ; Mon, 28 Oct 2019 05:45:28 -0700 (PDT) Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [144.76.73.169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 954CD12000F for ; Mon, 28 Oct 2019 05:45:28 -0700 (PDT) Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 65EF5C0214; Mon, 28 Oct 2019 12:49:06 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1572266946; bh=bChgZnVHSNf9gfxKnHN/CvcCpE8brD08EVJzw+DPRrc=; h=From:To:Subject:Date:From; b=gCqjVgNnnKqLFqov69exIgBFctRxbFOld0eoYBYcJc5yEvHms2fpiJmA0eZWdO/RW F9IAbJbTNLAqdPn3OzORjtA4EZuBGiKYuontWIKDSiUYoWIWfPniDXa4UnMrdWP74T vuiamRPPh05yNBM7ktBq4YQL5sXkhYh5x4emuqTg= Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1572266945-27258-27256/9/65; Mon, 28 Oct 2019 12:49:05 +0000 From: Arnt Gulbrandsen To: extra@ietf.org Date: Mon, 28 Oct 2019 13:45:24 +0100 Mime-Version: 1.0 Message-Id: User-Agent: Trojita/0.7; Qt/5.7.1; xcb; Linux; Devuan GNU/Linux 2.0 (ascii) Content-Type: text/plain; charset=utf-8; format=flowed Archived-At: Subject: [Extra] IMAP4rev2 , \recent and search new X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 12:45:31 -0000 I had a look at the draft recently and will be sending a number of messages, each pointing out a single issue, mostly simple. I'll space them out and send one every few days. First up: search new and \recent. I suggest that deprecating \recent be given a rationale. I suggest the following additional paragraph in 2.3.2: "Many modern IMAP clients automatically reconnect. For example, mobile email clients may dis- and reconnect whenever they enter or leave an area with WLAN coverage. Because of this, messages can lose their \recent status apparently at random, and using \recent (e.g. via the NEW search key) has become unreliable. For this reason (among others), \recent is now deprecated." The NEW search key needs to be changed, either to deprecate it or to make it an alias for UNSEEN. I think the best course of action is the one that permits the smallest client diff. Suggested wording for section 6.4.4: "Since \recent is now deprecated, the NEW search key may now be an alias for the UNSEEN. Servers that also advertise IMAP4rev1 may implement NEW either as an alias for UNSEEN or as specified in IMAP4rev1. Clients that implement IMAP4rev2 should not rely on either NEW being equal to UNSEEN or NEW returning a subset of UNSEEN." Section 6.3.2 contains an example that doesn't include RECENT. I suggest an additional paragraph: "Note that IMAP4rev1 compliant servers also send e.g. "* 0 RECENT", which IMAP4rev2 clients are advised to ignore." Arnt From nobody Mon Oct 28 13:34:15 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5692E120096 for ; Mon, 28 Oct 2019 13:34:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.5 X-Spam-Level: X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com 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 pNN8DAEMfI38 for ; Mon, 28 Oct 2019 13:34:11 -0700 (PDT) Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CD9512008A for ; Mon, 28 Oct 2019 13:34:11 -0700 (PDT) Received: by mail-vs1-xe2a.google.com with SMTP id j85so7234904vsd.11 for ; Mon, 28 Oct 2019 13:34:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mx5dzF/EKBLth/bTG9ApCU5gXaj21vgmynf+YC6dXC8=; b=stEfZuVCpDwnJAXsF0LKWdAjduI/f2g/xcKr2NeQL1mslOGSu9ejmS5uDvBSSTUjgf Eq8eSa4tfJ7V2ebc8z6vqKAfZO6NeTp0o27B7+EKoyGuY30t3CPS0zlECU1si3ZmaMe5 4BCfBeue4WFd4swU9DcmP1peVhwObK+1H7MSBELdhnNH24nHhqGI1EEzMIGQjzceaLXK CQSzJLafz943JrCE/1ijeE+RclWtyEviwHbAeKHe0pkqu4vyOBJz86COegUdvl5ejaLf UHCrYoCYfB//BqEkOFfJFjkZVtM4b7cAllQMCC/A+cjmCmTmo2IMzl0t8CaUXMdsCZ11 vx3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mx5dzF/EKBLth/bTG9ApCU5gXaj21vgmynf+YC6dXC8=; b=XnwSLA8DBO5mE6pIdx1plzy4Oy5gJAyjUj5vznw6WEJqOfVpoub/o0Qq5CDjEJtyx5 zrONTEqHvLc/0IO/IDJl0TGxbnQ2t90HIl7M2ySxm2pHfvicbgnLvXgNdLogBQ6fd275 RME7UYuRrZh78FY3o12iZoy0nIzIcDZQb7qTYMlqQzDKWcGGtvXNeyqLOh015PBDatOW UNLj5pUyC8qo4s5xDZIA+Vd4h6IbI+XANiB1wwUZjj8rYpXdJsFzHGLMDF1iqZY0tjEL UeuCjj4zGQkLBSKuAjdub2oRQ0//ZXBLRlYSQUcaX5CIaShP7BbiexvqHd1hzCP1GCIc P7KQ== X-Gm-Message-State: APjAAAU0nA8OEnzKJEOtAK//IQVShalQh7gibLNwyXMXMTELTjlESBrD 8WyY/P4oiGgS2hBO7oXIFf+veI6YHEKfYOVhz5UDrMU= X-Google-Smtp-Source: APXvYqzyiNLz+FAvc5gC4XX0KOHm7ix7ZZfzSxK36mD+9AIh6O9bADPN5BtZJdJV446xV2YyylC4vIrkf6iDAUGAU9A= X-Received: by 2002:a67:304a:: with SMTP id w71mr9676426vsw.92.1572294849577; Mon, 28 Oct 2019 13:34:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Brandon Long Date: Mon, 28 Oct 2019 13:33:57 -0700 Message-ID: To: Arnt Gulbrandsen Cc: extra@ietf.org Content-Type: multipart/alternative; boundary="000000000000fe65560595fe6b7e" Archived-At: Subject: Re: [Extra] IMAP4rev2 , \recent and search new X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 20:34:13 -0000 --000000000000fe65560595fe6b7e Content-Type: text/plain; charset="UTF-8" Pretty sure we implement it as "nothing is \Recent", which is also valid in the sense that it's always possible a different client saw them as new first. Using UNSEEN seems like a different type of lie, it is closer to what \Recent means... but since they both existed, one would think the difference between them may be what people consider useful. Brandon On Mon, Oct 28, 2019 at 5:45 AM Arnt Gulbrandsen wrote: > I had a look at the draft recently and will be sending a number of > messages, each pointing out a single issue, mostly simple. I'll space them > out and send one every few days. First up: search new and \recent. > > I suggest that deprecating \recent be given a rationale. I suggest the > following additional paragraph in 2.3.2: > > "Many modern IMAP clients automatically reconnect. For example, mobile > email clients may dis- and reconnect whenever they enter or leave an area > with WLAN coverage. Because of this, messages can lose their \recent > status > apparently at random, and using \recent (e.g. via the NEW search key) has > become unreliable. For this reason (among others), \recent is now > deprecated." > > The NEW search key needs to be changed, either to deprecate it or to make > it an alias for UNSEEN. I think the best course of action is the one that > permits the smallest client diff. Suggested wording for section 6.4.4: > > "Since \recent is now deprecated, the NEW search key may now be an alias > for the UNSEEN. Servers that also advertise IMAP4rev1 may implement NEW > either as an alias for UNSEEN or as specified in IMAP4rev1. Clients that > implement IMAP4rev2 should not rely on either NEW being equal to UNSEEN or > NEW returning a subset of UNSEEN." > > Section 6.3.2 contains an example that doesn't include RECENT. I suggest > an > additional paragraph: > > "Note that IMAP4rev1 compliant servers also send e.g. "* 0 RECENT", which > IMAP4rev2 clients are advised to ignore." > > Arnt > > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://www.ietf.org/mailman/listinfo/extra > --000000000000fe65560595fe6b7e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Pretty sure we implement it as "nothing is \Recent&qu= ot;, which is also valid in the sense that it's always possible a diffe= rent client saw them as new first.

Using UNSEEN seems li= ke a different type of lie, it is closer to what \Recent means... but since= they both existed, one would think the difference between them may be what= people consider useful.

Brandon

On Mon, Oct = 28, 2019 at 5:45 AM Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> wrote:
I had a look at the draft recently and wi= ll be sending a number of
messages, each pointing out a single issue, mostly simple. I'll space t= hem
out and send one every few days. First up: search new and \recent.

I suggest that deprecating \recent be given a rationale. I suggest the
following additional paragraph in 2.3.2:

"Many modern IMAP clients automatically reconnect. For example, mobile=
email clients may dis- and reconnect whenever they enter or leave an area <= br> with WLAN coverage. Because of this, messages can lose their \recent status=
apparently at random, and using \recent (e.g. via the NEW search key) has <= br> become unreliable. For this reason (among others), \recent is now
deprecated."

The NEW search key needs to be changed, either to deprecate it or to make <= br> it an alias for UNSEEN. I think the best course of action is the one that <= br> permits the smallest client diff. Suggested wording for section 6.4.4:

"Since \recent is now deprecated, the NEW search key may now be an ali= as
for the UNSEEN. Servers that also advertise IMAP4rev1 may implement NEW either as an alias for UNSEEN or as specified in IMAP4rev1. Clients that implement IMAP4rev2 should not rely on either NEW being equal to UNSEEN or =
NEW returning a subset of UNSEEN."

Section 6.3.2 contains an example that doesn't include RECENT. I sugges= t an
additional paragraph:

"Note that IMAP4rev1 compliant servers also send e.g. "* 0 RECENT= ", which
IMAP4rev2 clients are advised to ignore."

Arnt

_______________________________________________
Extra mailing list
Extra@ietf.org
https://www.ietf.org/mailman/listinfo/extra
--000000000000fe65560595fe6b7e-- From nobody Mon Oct 28 13:54:20 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4DB7120072 for ; Mon, 28 Oct 2019 13:54:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 0-QTjvdiZn37 for ; Mon, 28 Oct 2019 13:54:17 -0700 (PDT) Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7025E120024 for ; Mon, 28 Oct 2019 13:54:17 -0700 (PDT) Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 3D0A0C0050; Mon, 28 Oct 2019 20:57:56 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1572296276; bh=DUy3iPQ69LO5h4altfH3IUYbNKX2R+q/6A0gX2rY6n8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=H35B4GTHgwhE/7ATF2LkW0n+MYlO80EpO2XVPT2aCVh29veq3RAWVBz2uXlRNwJ17 UyRkRksFX5FpmMHP8TOAMEyR5ZvhO5Vj3oYI40joUOj+tV4lY8nqHMaoCpGjPwwoQe KZ2vZJqcm+vbA5KL74woKsin9yjql8fW2+QlnFIk= Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1572296275-27258-27256/9/66; Mon, 28 Oct 2019 20:57:55 +0000 From: Arnt Gulbrandsen To: extra@ietf.org Date: Mon, 28 Oct 2019 21:54:13 +0100 Mime-Version: 1.0 Message-Id: In-Reply-To: References: User-Agent: Trojita/0.7; Qt/5.7.1; xcb; Linux; Devuan GNU/Linux 2.0 (ascii) Content-Type: text/plain; charset=utf-8; format=flowed Archived-At: Subject: Re: [Extra] IMAP4rev2 , \recent and search new X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 20:54:19 -0000 On Monday 28 October 2019 21:33:57 CET, Brandon Long wrote: > Using UNSEEN seems like a different type of lie, it is closer > to what \Recent means... but since they both existed, one would > think the difference between them may be what people consider > useful. I suggested (optionally) aliasing it to UNSEEN since it seemed to me that any client that issues SEARCH NEW would want the search resunt to sometimes be nonempty. Arnt From nobody Mon Oct 28 19:53:50 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18EC01200EB for ; Mon, 28 Oct 2019 19:53:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=j9OCM8/+; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JHatUocr 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 LDYSDXO0ejAS for ; Mon, 28 Oct 2019 19:53:47 -0700 (PDT) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D02D01200B1 for ; Mon, 28 Oct 2019 19:53:47 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 4065840E for ; Mon, 28 Oct 2019 22:53:46 -0400 (EDT) Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Mon, 28 Oct 2019 22:53:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=beqV81B FFE1uPwKobOiRhhJZTPr0LlgNqSY4J40P1rM=; b=j9OCM8/+r0oAld1ohHNsBPS 5asKJcbYfegnmkjuuwumgdR/oeczcLe8KcU2EGrqDVRCHrkSZDNFxke7sVTzTzJh tGGuqytjHeHyOYHJX7b9NT5NFbo6OS/SrkvhqLJW8x+s4CywR3IwwQBE5e3d7lpD JaJBbVDIjLPK9Vner2hgj7C76QHEclkGeFH4LPzLyTyyg6tRXT0KFFOpI0gRXG8p MDzY1aoMtR99Ni/NVhm8BqZfmk/QX2l/TH6yyqtet5KRcXc2pZJ4T7QVtQkIWqb6 oDAYWDjptEeEkQ7pY7wf9lytaRWM0t6aT+rUqhBDXQWusa/H1W23hfvRE8BWXCg= = DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=beqV81 BFFE1uPwKobOiRhhJZTPr0LlgNqSY4J40P1rM=; b=JHatUocruqOSmh5hY0IVfY uiJIR1PxVwIpDLTIL43ZgdYfdXxY2PcgDEXDpz/Q3sa8Iy31NkGO+m4NthNIFhFO ewYag74zQGVv3JU8bzFr6iVLSsDlWgoKV756u9wWSPEYuWLKimQWxkIEkhPoVD4v knmsIzrHnfhD2YlfJyQaTLnndwyStmyQTZlGLDoherxCR91ykaik42dyVOiX88fK QFS00hN0MCaXWgEl6zWVv6Wz3TJPF6D/C/ZmogSOaegSerFXl5UDLOjVdjURZx17 FuZ85r/A61hXAhYzchl11z7VlNE3T12Am4C49jaEG40z9NWCwTIRa3t6dRzvIBjQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddttddgheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucfrrghrrghmpehmrghilhhfrhhomhepsg hrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmnecuvehluhhsthgvrhfuihiivgep td X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 83F1940693F; Mon, 28 Oct 2019 22:53:45 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-512-g193a140-fmstable-20191028v1 Mime-Version: 1.0 Message-Id: <9a7518f3-e89b-4e29-99cb-4a7dc5b17f2d@beta.fastmail.com> In-Reply-To: References: Date: Tue, 29 Oct 2019 13:53:24 +1100 From: "Bron Gondwana" To: extra@ietf.org Content-Type: multipart/alternative; boundary=05796777ebb14410aeeb4a5312cd3003 Archived-At: Subject: Re: [Extra] IMAP4rev2 , \recent and search new X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 02:53:49 -0000 --05796777ebb14410aeeb4a5312cd3003 Content-Type: text/plain On Tue, Oct 29, 2019, at 07:54, Arnt Gulbrandsen wrote: > On Monday 28 October 2019 21:33:57 CET, Brandon Long wrote: > > Using UNSEEN seems like a different type of lie, it is closer > > to what \Recent means... but since they both existed, one would > > think the difference between them may be what people consider > > useful. > > I suggested (optionally) aliasing it to UNSEEN since it seemed to me that > any client that issues SEARCH NEW would want the search resunt to sometimes > be nonempty. I think I'd prefer for it to just return the empty set, easy to implement and won't confuse anything. UNSEEN can have messages appear and disappear from the set, whereas a message can never go from un\Recent to \Recent. Bron. -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com --05796777ebb14410aeeb4a5312cd3003 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Tue, Oct 29, 2019, at 07:54, Arnt Gulbrandsen wrote:
On Monday 28 October 2019 21:33:57 CET, Brandon Long wrote:
> Using UNSEEN seems like a diffe= rent type of lie, it is closer 
> to what \Recent means... but since they both existed, one w= ould 
> think the dif= ference between them may be what people consider 
> useful.

I suggested (optio= nally) aliasing it to UNSEEN since it seemed to me that 
<= div style=3D"font-family:Arial;">any client that issues SEARCH NEW would= want the search resunt to sometimes 
be nonempty.

I think I'd prefe= r for it to just return the empty set, easy to implement and won't confu= se anything.

UNSEEN can have messages appear and disappea= r from the set, whereas a message can never go from un\Recent to \Recent= .

Bron.

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
<= div class=3D"signature">  brong@fastmailteam.com


--05796777ebb14410aeeb4a5312cd3003-- From nobody Tue Oct 29 04:12:49 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 626B6120169 for ; Tue, 29 Oct 2019 04:12:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.101 X-Spam-Level: X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com 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 5vRI3u3l1Atd for ; Tue, 29 Oct 2019 04:12:46 -0700 (PDT) Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 0733A120154 for ; Tue, 29 Oct 2019 04:12:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1572347565; d=isode.com; s=june2016; i=@isode.com; bh=1Dz7ABz9mKj36aox/5gF4266tee+Oh3nmHZLfR6ae9M=; 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=FMHXN9hSyLWCQj2ZXT+CC0Yo7L8PXm+gZYNMvLUp5/ehv0tdlp+H2dKqw9l4WEbhbJ8KHr JV+tWah4Zd62oWF/mV0umHSnCPmx6JC6Kqc4KyEes9mCUAsEI4WLzSPpAjjnj5SuA1EaWY VA5tyUGgoabY4M5Mr9xgK1NZgpnnYAc=; 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 ; Tue, 29 Oct 2019 11:12:45 +0000 To: Arnt Gulbrandsen , Bron Gondwana References: Cc: extra From: Alexey Melnikov Message-ID: <978c88aa-f211-8e74-ae49-6fd6543cbd0d@isode.com> Date: Tue, 29 Oct 2019 11:12:07 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB Archived-At: Subject: Re: [Extra] IMAP4rev2 , \recent and search new X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 11:12:48 -0000 On 28/10/2019 20:54, Arnt Gulbrandsen wrote: > On Monday 28 October 2019 21:33:57 CET, Brandon Long wrote: >> Using UNSEEN seems like a different type of lie, it is closer to what >> \Recent means... but since they both existed, one would think the >> difference between them may be what people consider useful. > > I suggested (optionally) aliasing it to UNSEEN since it seemed to me > that any client that issues SEARCH NEW would want the search resunt to > sometimes be nonempty. Maybe we should just deprecate NEW and add some explanatory text? From nobody Tue Oct 29 04:14:16 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07EB2120110 for ; Tue, 29 Oct 2019 04:14:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=HKisYNm8; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=jkv3zKId 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 qJbrbX82RWwj for ; Tue, 29 Oct 2019 04:14:12 -0700 (PDT) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 826CB120041 for ; Tue, 29 Oct 2019 04:14:12 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0107521E6A for ; Tue, 29 Oct 2019 07:14:11 -0400 (EDT) Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Tue, 29 Oct 2019 07:14:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=XCPTkEC BqX6Q3u2h+aIdUoyblfd+V9KOlchx396+EoA=; b=HKisYNm8w3HRmUmGNV3foaN ISOrZJPHtBy75Pt4gpEX2m4eew5fYD2k7ZM1RrNzsoleI1jrL4LZYLU5TneGFN8g x7LPOh6OEYYKGG/S7M9ni/cZn3WIa6dpGLOaweIft/1qjmldEwBl+WEvA7CPXPpv b4vQ5+G9e8lPgF4HdZgfTJvC92lEVC/QkAn17EZvUG0pegkpR3G4aoggKwYfVTCm w6Gsta+kM82gHPe7UtNHmIUjanCdnH1sSiDWCiruzT6/yDjJl1fegOCnB7sh/vx8 Yqvzwb2MTeHnDNhouo+3X9DpI2E5nGTegK9J+VRFI9nncsEYnmKmvBv+Koxj1Tg= = DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=XCPTkE CBqX6Q3u2h+aIdUoyblfd+V9KOlchx396+EoA=; b=jkv3zKIdyzWlXFGcqMxIsz 8hL0wb+kb9bVDvm8ibfhD34hTAKz/YkmYrkgNyDH2eLy8AYXh35DwE3Tf5fkTK3u TvDO38M3LR/zLzYBfFmCKD/py2kDiNRFYsuUwU8uB2tWz+LIkdAcO76WPp6wNaIw E/HTpKe3A+Z+vDzzHtIEJ0qU4CDv2pi6wkqFFMn0+hOBSBIPI3JG89jPtQbzZeBz TMKL35oflozYi/EK8Un8ZTZw3DOL26AM+rIboDGthBVUCoPFQ5dJj0BDVJ3Ioyl0 eCqRpH3dubkIslUfi05BrXmjZR0rqvUszHppJFzKjyXtRHfVTVHIuStgkN8RAMgA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddtuddgvdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucfrrghrrghmpehmrghilhhfrhhomhepsg hrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmnecuvehluhhsthgvrhfuihiivgep td X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 8D2FB300096; Tue, 29 Oct 2019 07:14:10 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-512-g193a140-fmstable-20191028v1 Mime-Version: 1.0 Message-Id: <25e64401-0b91-4387-ba35-1f353aff1bbe@www.fastmail.com> In-Reply-To: <978c88aa-f211-8e74-ae49-6fd6543cbd0d@isode.com> References: <978c88aa-f211-8e74-ae49-6fd6543cbd0d@isode.com> Date: Tue, 29 Oct 2019 22:13:50 +1100 From: "Bron Gondwana" To: extra@ietf.org Content-Type: multipart/alternative; boundary=4cd6c299edf44e63a790c180b77c4bfb Archived-At: Subject: Re: [Extra] IMAP4rev2 , \recent and search new X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 11:14:14 -0000 --4cd6c299edf44e63a790c180b77c4bfb Content-Type: text/plain On Tue, Oct 29, 2019, at 22:12, Alexey Melnikov wrote: > On 28/10/2019 20:54, Arnt Gulbrandsen wrote: > > > On Monday 28 October 2019 21:33:57 CET, Brandon Long wrote: > >> Using UNSEEN seems like a different type of lie, it is closer to what > >> \Recent means... but since they both existed, one would think the > >> difference between them may be what people consider useful. > > > > I suggested (optionally) aliasing it to UNSEEN since it seemed to me > > that any client that issues SEARCH NEW would want the search resunt to > > sometimes be nonempty. > > Maybe we should just deprecate NEW and add some explanatory text? I think deprecate NEW and allow it to always return empty is right (with the text of course). Bron. -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com --4cd6c299edf44e63a790c180b77c4bfb Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Tue, Oct 29, 2019, at 22:12, Alexey Melnikov wrote:
=
On 28/10/2019 20:54, Arnt Gulbrandsen wrote:

> On = Monday 28 October 2019 21:33:57 CET, Brandon Long wrote:
>> Using UNSEEN seems like a different= type of lie, it is closer to what 
>> \Recent means... but since they both existed, one w= ould think the 
>>= difference between them may be what people consider useful.
>
> I suggested (optionally) aliasing it to UNSEEN since it see= med to me 
> that any= client that issues SEARCH NEW would want the search resunt to 
=
> sometimes be nonempty.
<= /div>

Maybe we should just deprecate NEW and add some explanatory t= ext?

<= div style=3D"font-family:Arial;">I think deprecate NEW and allow it to a= lways return empty is right (with the text of course).

Bron.

--
=
  Bron Gondwana, CEO, Fastmail Pty L= td
  brong@fastmailteam.com


--4cd6c299edf44e63a790c180b77c4bfb-- From nobody Tue Oct 29 05:14:50 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5E0D120154 for ; Tue, 29 Oct 2019 05:14:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 eg4iLlUoX5Lk for ; Tue, 29 Oct 2019 05:14:47 -0700 (PDT) Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 554A8120106 for ; Tue, 29 Oct 2019 05:14:47 -0700 (PDT) Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 55975C0074; Tue, 29 Oct 2019 12:18:25 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1572351505; bh=vbFh1cYg07JLwnZY/WiDH5VHT0mqvwrDBTFcfe2ucnc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lkzsEJPl6lCAUOis8k0HMV2f8r085IUjihUTPixXXriz7HglAh+QvUm3vtSHPZkgz qpCRO3M52EwppZ4PMXBbvDooFcueJkdOG/ShgEL3KFMvrZ6M6Xm8tNk1JOrueu0MEG SpWL3G2t4AIcB47FW4xm99NG9L2AwRIbw5BH+qgg= Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1572351504-27259-27256/9/38; Tue, 29 Oct 2019 12:18:24 +0000 From: Arnt Gulbrandsen To: extra@ietf.org Date: Tue, 29 Oct 2019 13:14:42 +0100 Mime-Version: 1.0 Message-Id: <6f213c47-03d0-4cea-8cbf-f81156130bcb@gulbrandsen.priv.no> In-Reply-To: <25e64401-0b91-4387-ba35-1f353aff1bbe@www.fastmail.com> References: <978c88aa-f211-8e74-ae49-6fd6543cbd0d@isode.com> <25e64401-0b91-4387-ba35-1f353aff1bbe@www.fastmail.com> User-Agent: Trojita/0.7; Qt/5.7.1; xcb; Linux; Devuan GNU/Linux 2.0 (ascii) Content-Type: text/plain; charset=utf-8; format=flowed Archived-At: Subject: Re: [Extra] IMAP4rev2 , \recent and search new X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 12:14:49 -0000 On Tuesday 29 October 2019 12:13:50 CET, Bron Gondwana wrote: > I think deprecate NEW and allow it to always return empty is > right (with the text of course). Since gmail has done that for a while I think it's a perfectly acceptable course of action... and NEW/\recent isn't worth much heartache, so anything good is better than a search for best. Suggested text: "Since \recent is now deprecated, the NEW search key is also deprecated. IMAP4rev2-capable servers MAY match no messages (ie. make NEW an alias for NONE), servers that also implement IMAP4rev1 MAY alternatively choose to implement NEW as specified in RFC3501, and clients that implement IMAP4rev2 MUST NOT rely on any particular behaviour." Arnt From nobody Tue Oct 29 12:54:51 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C15551208DE for ; Tue, 29 Oct 2019 12:54:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=jdFq/q88; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=pB4ZvgEx 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 kTjhA4Sz6jax for ; Tue, 29 Oct 2019 12:54:48 -0700 (PDT) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F331120119 for ; Tue, 29 Oct 2019 12:54:48 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id A25AB4B5 for ; Tue, 29 Oct 2019 15:54:47 -0400 (EDT) Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Tue, 29 Oct 2019 15:54:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=lvqBTz3 o5qZFHcPKAMOhdv6sEXJlxmRbBXbcl72N9D0=; b=jdFq/q88J4aQF+eFaFULGqE verv1B5GNPCdcArcdKPACs5pUkR5jlVFowErDqAOGocwmGNbT7ED5PpZuCPc3PZ+ lTiP2ciTid6PP8vfkm5lusui/bWO1Va3mT24dBW5eR4zr9HVtLcZT5Uq43OsSNT6 nMMP10aBul4MescaI1oRBYoZv9E9szDPmcJeUeiyUhZq6TAseGUMYXA9FmqnOX5E cT6cvn6AOjVb1iAsMlY/LYpMLKT7cHDfPYWhH7eNTz7KewA8IBul4DM8/F0OmcFK Qzb6rOL11rmquwRzcQhadjZP+dFBN+mN/oxJBdAte7g6MVaQqCb1MNW5rnQTO1A= = DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=lvqBTz 3o5qZFHcPKAMOhdv6sEXJlxmRbBXbcl72N9D0=; b=pB4ZvgExFpsqJmsMbVRByK bkv/rAImDiPMR8tGkg6Sz0FV7F6Kzs6OObg0I97CFw1CvGa7jXh5Rk6jjcE2G0Lv bskcBPe0ntfpyKZBkkAFDYthz3MbkQ1c+jcW4Q+5EsljDu19cS/8LVAzEch8HAN7 dd708+Lgz1XHMO76kZv9q9466uUnhzMoqVNu/4V2xwOYis7q33E6YZZ5ArYWHffK uJ7CSbzrhdzFwXwL07vM7FI66BxKY3CFV8VM/nZdtuKDv+U/K51epzkcPfCYShAB 6wc31uw5inIv4WE67wcBu0GQqu4GFbg5f81+cONEGAxcQGmzp7yVHOgTRzcXBMzQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddtuddguddvlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrg dtreerreertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhg sehfrghsthhmrghilhhtvggrmhdrtghomheqnecurfgrrhgrmhepmhgrihhlfhhrohhmpe gsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomhenucevlhhushhtvghrufhiiigv pedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id F2E63300096; Tue, 29 Oct 2019 15:54:46 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-512-g193a140-fmstable-20191028v1 Mime-Version: 1.0 Message-Id: <8f54941c-ad32-4221-9acf-dd55387b35cd@www.fastmail.com> In-Reply-To: <6f213c47-03d0-4cea-8cbf-f81156130bcb@gulbrandsen.priv.no> References: <978c88aa-f211-8e74-ae49-6fd6543cbd0d@isode.com> <25e64401-0b91-4387-ba35-1f353aff1bbe@www.fastmail.com> <6f213c47-03d0-4cea-8cbf-f81156130bcb@gulbrandsen.priv.no> Date: Wed, 30 Oct 2019 06:54:26 +1100 From: "Bron Gondwana" To: extra@ietf.org Content-Type: multipart/alternative; boundary=32a9172c68e347a1a43ab8b437e043d0 Archived-At: Subject: Re: [Extra] IMAP4rev2 , \recent and search new X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 19:54:50 -0000 --32a9172c68e347a1a43ab8b437e043d0 Content-Type: text/plain On Tue, Oct 29, 2019, at 23:14, Arnt Gulbrandsen wrote: > On Tuesday 29 October 2019 12:13:50 CET, Bron Gondwana wrote: > > I think deprecate NEW and allow it to always return empty is > > right (with the text of course). > > Since gmail has done that for a while I think it's a perfectly acceptable > course of action... and NEW/\recent isn't worth much heartache, so anything > good is better than a search for best. > > Suggested text: "Since \recent is now deprecated, the NEW search key is > also deprecated. IMAP4rev2-capable servers MAY match no messages (ie. make > NEW an alias for NONE), servers that also implement IMAP4rev1 MAY > alternatively choose to implement NEW as specified in RFC3501, and clients > that implement IMAP4rev2 MUST NOT rely on any particular behaviour." Looks great to me. Bron. -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com --32a9172c68e347a1a43ab8b437e043d0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable


On Tue, Oct 29, 2019, at 23:14, Arnt Gulbrandsen wrote:
On Tuesd= ay 29 October 2019 12:13:50 CET, Bron Gondwana wrote:
> I think deprecate NEW and allow it to alwa= ys return empty is 
>= right (with the text of course).

Since gmail has done th= at for a while I think it's a perfectly acceptable 
course of action... and NEW/\recent isn't wo= rth much heartache, so anything 
good is better than a search for best.

Suggested= text: "Since \recent is now deprecated, the NEW search key is 
=
also deprecated. IMAP4rev2-capab= le servers MAY match no messages (ie. make 
NEW an alias for NONE), servers that also implement = IMAP4rev1 MAY 
alternati= vely choose to implement NEW as specified in RFC3501, and clients <= br>
that implement IMAP4rev2 MUST= NOT rely on any particular behaviour."

Look= s great to me.

Bron.
--
  Bron G= ondwana, CEO, Fastmail Pty Ltd
  = brong@fastmailteam.com


--32a9172c68e347a1a43ab8b437e043d0-- From nobody Wed Oct 30 03:58:14 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5AC120104 for ; Wed, 30 Oct 2019 03:58:13 -0700 (PDT) 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_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com 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 Vx_uasJN-uvC for ; Wed, 30 Oct 2019 03:58:11 -0700 (PDT) Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id B83C81200CE for ; Wed, 30 Oct 2019 03:58:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1572433091; d=isode.com; s=june2016; i=@isode.com; bh=WPByXJlXAsxumXfKylRykhoGz2+Suhm7tJbUvEyv+ao=; 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=YnCuikumZrtEpHmCj5H7s/H25qdnIDDSYqgTFMRwLuJZPofED/8cFmmX8W8vFEEUaT/vOm YmJfUb07GOZponSfkpFAfBbSGKQBSxLXGEM0TswpEYHXlOwv0mIV9xHwdYhEj0jhfHpdJW MbXbwSS9vQzAn4F8/TCt8km6abxAe4M=; Received: from [192.168.0.7] (cpc121086-nmal24-2-0-cust54.19-2.cable.virginm.net [77.97.145.55]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id ; Wed, 30 Oct 2019 10:58:10 +0000 To: Chris Newman , Ned Freed Cc: extra@ietf.org, Timo Sirainen References: <44234C00-7A5D-4B41-9E85-4CF839B48214@iki.fi> <01R4QZ1O8F8G000051@mauve.mrochek.com> <3ACD6BFE-2936-4F12-8159-BCEEFC965CBE@oracle.com> From: Alexey Melnikov Message-ID: Date: Wed, 30 Oct 2019 10:58:11 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0 In-Reply-To: <3ACD6BFE-2936-4F12-8159-BCEEFC965CBE@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-transfer-encoding: quoted-printable Archived-At: Subject: Re: [Extra] draft-ietf-extra-imap4rev2-04 review X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2019 10:58:13 -0000 On 26/03/2019 15:42, Chris Newman wrote: > On 26 Mar 2019, at 15:13, Ned Freed wrote: >>> On 25 Mar 2019, at 13:04, Timo Sirainen wrote: >>> >> 3.4.=C2=A0 Logout State >>> >> >>> > >>> >>=C2=A0=C2=A0=C2=A0 A server MUST NOT unilaterally close the connection= without >>> >> sending >>> >>=C2=A0=C2=A0=C2=A0 an untagged BYE response that contains the reason f= or having done >>> >> so. >>> > >>> > Also already in RFC 3501, but this MUST NOT has to be violated >>> > sometimes. For example otherwise it would allow client to FETCH a >>> > large message and keep reading it very very slowly over days, and >>> > server wouldn't be allowed to disconnect it, because it can't send=20 >>> BYE >>> > in the middle of the large mail literal. >> >>> Another example is if a client gets hung up (or goes silently offline) >>> during a TLS negotiation. The server has to eventually timeout the >>> connection but it would be semantically wrong to send a "* BYE" since >>> there's no data channel. One case where this happened was when our SSL >>> stack dropped support for an SSLv2-compatible hello (allowed by RFC >>> 6176), but some very old client kept sending such a hello=20 >>> (prohibited by >>> RFC 6176). Incidentally, SSLv2 is completely incompatible with SSLv3 so >>> the client sends something that's not sufficient to complete an SSLv3 >>> packet so both ends get stuck waiting until one side hangs up. >> >> There was a suggestion (I think) during the meeting that this should=20 >> be handled >> by sending the TLS equivalent of "* BYE". Which sounds fine in=20 >> theory, but as >> said at the time, I'm skeptical that many/most TLS implementations=20 >> provide >> implementors with the means to conveniently do that. > > I didn't hear such a suggestion. I made the observation that a wedged=20 > TLS negotiation is a scenario where sending "* BYE" shouldn't be done.=20 > It was suggested that example be mentioned in the document. I did not=20 > mention the fact that TLS has it's own alert syntax that could be used=20 > instead of "* BYE" -- I agree discussing that would be a bad idea. To followup on this: I've changed "MUST NOT unilaterally close the=20 connection without sending BYE" to "SHOULD NOT ...". Do people think=20 this is sufficient? Best Regards, Alexey From nobody Wed Oct 30 08:03:08 2019 Return-Path: X-Original-To: extra@ietfa.amsl.com Delivered-To: extra@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66BBD120CAB for ; Wed, 30 Oct 2019 08:03:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.302 X-Spam-Level: X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.com 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 jFr3f9M2r3Jl for ; Wed, 30 Oct 2019 08:03:01 -0700 (PDT) Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) (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 29C7F120C52 for ; Wed, 30 Oct 2019 08:02:57 -0700 (PDT) Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x9UF1pH5018674; Wed, 30 Oct 2019 15:02:56 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type : content-transfer-encoding; s=corp-2019-08-05; bh=NHS+szRlMrinwF4yjktfJL8mHUfhHwVt0b8ySETLz/E=; b=WUvu2yJ9KobT7c30ugb5lWEzvHUW520NNZDAKV2Kvu/drtRAsotbTv0ZNh/QdMs9Zj2a 2PR8Rv0vA5uOei3TejzVlLFrbzi8upj+CUBxcr5jyrLGiRtm0830n5BZMBPzjwIl5Z9H sErhpdI+V1RsfZRwk6OQ79rnmvQudohK5mhklDWprTxOwiTJJVI7enO1RVG3O65fXVNj BPN4MONy1vZwan9KpbYWQz0xTrmqsiKo/yGFX474oobkrlGEYwRqUK8hv92xYVg9trlE oyFrNs9almRhoMGje38/GKL0FF5p2jFWOckli281gyabvCS9nTgh8Is3Ru5sB/siQL/A 4A== Received: from userp3020.oracle.com (userp3020.oracle.com [156.151.31.79]) by userp2130.oracle.com with ESMTP id 2vxwhfmvsp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 30 Oct 2019 15:02:56 +0000 Received: from pps.filterd (userp3020.oracle.com [127.0.0.1]) by userp3020.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x9UF0TVf134932; Wed, 30 Oct 2019 15:00:55 GMT Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userp3020.oracle.com with ESMTP id 2vxwj9eqbx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 30 Oct 2019 15:00:53 +0000 Received: from abhmp0023.oracle.com (abhmp0023.oracle.com [141.146.116.29]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id x9UExFYr027038; Wed, 30 Oct 2019 14:59:15 GMT Received: from [10.159.251.45] (/10.159.251.45) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 30 Oct 2019 14:59:15 +0000 From: "Chris Newman" To: "Alexey Melnikov" Cc: "Ned Freed" , extra@ietf.org, "Timo Sirainen" Date: Wed, 30 Oct 2019 07:59:14 -0700 X-Mailer: MailMate (1.13r5655) Message-ID: <92BA4444-11D2-4DE7-B938-F1E72F509705@oracle.com> In-Reply-To: References: <44234C00-7A5D-4B41-9E85-4CF839B48214@iki.fi> <01R4QZ1O8F8G000051@mauve.mrochek.com> <3ACD6BFE-2936-4F12-8159-BCEEFC965CBE@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9425 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=903 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1910300141 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9425 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=981 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1910300141 Archived-At: Subject: Re: [Extra] draft-ietf-extra-imap4rev2-04 review X-BeenThere: extra@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Email mailstore and eXtensions To Revise or Amend List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2019 15:03:07 -0000 On 30 Oct 2019, at 3:58, Alexey Melnikov wrote: > On 26/03/2019 15:42, Chris Newman wrote: > >> On 26 Mar 2019, at 15:13, Ned Freed wrote: >>>> On 25 Mar 2019, at 13:04, Timo Sirainen wrote: >>>> >> 3.4.  Logout State >>>> >> >>>> > >>>> >>    A server MUST NOT unilaterally close the connection >>>> without >>>> >> sending >>>> >>    an untagged BYE response that contains the reason for >>>> having done >>>> >> so. >>>> > >>>> > Also already in RFC 3501, but this MUST NOT has to be violated >>>> > sometimes. For example otherwise it would allow client to FETCH a >>>> > large message and keep reading it very very slowly over days, and >>>> > server wouldn't be allowed to disconnect it, because it can't >>>> send BYE >>>> > in the middle of the large mail literal. >>> >>>> Another example is if a client gets hung up (or goes silently >>>> offline) >>>> during a TLS negotiation. The server has to eventually timeout the >>>> connection but it would be semantically wrong to send a "* BYE" >>>> since >>>> there's no data channel. One case where this happened was when our >>>> SSL >>>> stack dropped support for an SSLv2-compatible hello (allowed by RFC >>>> 6176), but some very old client kept sending such a hello >>>> (prohibited by >>>> RFC 6176). Incidentally, SSLv2 is completely incompatible with >>>> SSLv3 so >>>> the client sends something that's not sufficient to complete an >>>> SSLv3 >>>> packet so both ends get stuck waiting until one side hangs up. >>> >>> There was a suggestion (I think) during the meeting that this should >>> be handled >>> by sending the TLS equivalent of "* BYE". Which sounds fine in >>> theory, but as >>> said at the time, I'm skeptical that many/most TLS implementations >>> provide >>> implementors with the means to conveniently do that. >> >> I didn't hear such a suggestion. I made the observation that a wedged >> TLS negotiation is a scenario where sending "* BYE" shouldn't be >> done. It was suggested that example be mentioned in the document. I >> did not mention the fact that TLS has it's own alert syntax that >> could be used instead of "* BYE" -- I agree discussing that would be >> a bad idea. > > To followup on this: I've changed "MUST NOT unilaterally close the > connection without sending BYE" to "SHOULD NOT ...". Do people think > this is sufficient? Works for me. - Chris