Re: [Extra] IMAP4rev2: how to signal canonical mailbox name after CREATE

Bron Gondwana <brong@fastmailteam.com> Wed, 17 June 2020 12:27 UTC

Return-Path: <brong@fastmailteam.com>
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 0A5B23A0365 for <extra@ietfa.amsl.com>; Wed, 17 Jun 2020 05:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=h/pcewfI; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ePyDQKmi
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 oANGHkhRF9lA for <extra@ietfa.amsl.com>; Wed, 17 Jun 2020 05:27:30 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B331D3A0112 for <extra@ietf.org>; Wed, 17 Jun 2020 05:27:30 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0C0BE5C0185; Wed, 17 Jun 2020 08:27:30 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Wed, 17 Jun 2020 08:27:30 -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:cc:subject:content-type; s=fm3; bh=FWGm kkwC+Df2oSN1TT/4wmPTNwej3wJ1C3nV5GbYcPw=; b=h/pcewfIuu/9LvTC9GCP Zv2T0jBotaDzzKShIcN+tM2vhh20IB4JhQC/cMvoYFn3/l5slyGTxqOzn1Xjy905 YbXtzVaZIUnfEBoEv6l+23DdsWA5UTGxL2BRX142BqHtUPp7wGg5ARqs9L8tv54W 3VDWQi7ywfAQqMNZjnj8Kpzo3MTSHInwHbYVvoJMh+7gFT6A6Ng/Gl9QaQxQp2Ag LnMXOQ+zmYA9LY5sBMbJo3sIMGu8xqMGFNwEqI3jeF1nvaXAAFvGAeMGV1R5X3jh uz+eCUaujfJb1gqvQWw9CphUK7Rjv3sHzmutZ68e1kvjgwsfqwdEWT81eEKZwnIq tQ==
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=fm3; bh=FWGmkk wC+Df2oSN1TT/4wmPTNwej3wJ1C3nV5GbYcPw=; b=ePyDQKmilvD7HEy+ISSfl2 sSWjgq2F3A7BlCOOqITkDqLqP9Co+mn46vyiqWlTSFODhwONQ8Z+Rc5ck/NQYf1f ZuQBOitj2kdkoVkpwOCC+BkHeIFtajSkgncPP2Tr8FQfnl6l1B1kR87jl7obuN1t ySyb9w9I9d3kDczdgjzSgUT6fxA/dqi+Djs8qJf2FdZ08PaWjaK2IxiadMS54ciz DM2VSBg4+sGVv8Pib0TGbQHZT8WTDUZYwUrBXUvORS+JUCpCMcJJ3Dk3TAypxKyE VihobBs231tTo7AS9WrpF0nwVgkU5ksxS8vQJ+g3llFxr+DF6v8+SJLcVuClt7hQ ==
X-ME-Sender: <xms:MQzqXonMikn3RXzA0tpdLggpd-pWa5Uq0K8_7sNKa6M-mIdTQWndWg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudejvddghedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdeurhho nhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh eqnecuggftrfgrthhtvghrnheptdehteegfeevteduffevteehfffghefhvdevkeeuhfeh ueetudehgfegieekjeetnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:MQzqXn1IHqiJjsr0EWxImvn8qJVujrdrKgB78vMnl1dyLTZhzeifyg> <xmx:MQzqXmqDofpitGbvkS4ZGNPpi3DdCru4_xL6OxTjc3cvlLzxU_2pkw> <xmx:MQzqXkmccSkoarnAoUFrT21gwwP3FZ7F_ED5CxfYGB80g6WegCS_Fg> <xmx:MgzqXvgtwgc7CSiM9UWd6aTuQTWxOI02zTRfSE4FxoKMQiDatXiubA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 975DC180091; Wed, 17 Jun 2020 08:27:29 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-534-g18b7ee1-fm-20200616.002-g18b7ee12
Mime-Version: 1.0
Message-Id: <2fe5352f-f2c5-4e50-b9c4-6da38fbcc4d0@dogfood.fastmail.com>
In-Reply-To: <1BC59434-C16C-4A32-AB3C-D2783092CF9B@sirainen.com>
References: <9fdfa8e8-147d-4248-a0c1-48de171ac675@dogfood.fastmail.com> <872422BE-C8FA-4AA0-8EF1-2ECA79F64926@sirainen.com> <96BAB7A5-420A-49AF-977F-1F722746E5DD@isode.com> <5FAA4D04-F1A8-4E23-B9F2-817EBAFF8021@sirainen.com> <5fe122d9-5313-8be1-199e-075a61d1bb2a@isode.com> <0fd3e8e2-1865-4021-b80c-11c4987b7d64@dogfood.fastmail.com> <9c674fad-dabe-cc9d-649d-30cb40f5c506@isode.com> <1BC59434-C16C-4A32-AB3C-D2783092CF9B@sirainen.com>
Date: Wed, 17 Jun 2020 22:27:09 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: Timo Sirainen <timo@sirainen.com>, Alexey Melnikov <alexey.melnikov@isode.com>
Cc: extra@ietf.org
Content-Type: multipart/alternative; boundary="99a0b2c05ce94b8b9dedec5f3cb5df36"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/bHJzVV-O3g5zlsx7Z39pEFdCVoc>
Subject: Re: [Extra] IMAP4rev2: how to signal canonical mailbox name after CREATE
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2020 12:27:32 -0000

On Wed, Jun 17, 2020, at 22:15, Timo Sirainen wrote:
>> 1) abandon use of this response code (and use a new response instead), e.g.

>> * CREATED "a123" "Denormalized name" MAILBOXID "123456"

>>  This would require clients to ignore an extra response, if they don't recognize it.

> 
> Somehow I've a feeling that there are going to be clients that will break if they see these kind of unknown untagged replies. But that's just a guess, so maybe not. We could of course send it only when client has used ENABLE IMAP4REV2 and then there wouldn't be any problems.

I like this. Only send if IMAP4REV2 is enabled and all[tm] your problems go away.

Bron.

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