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

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 06 July 2020 17:38 UTC

Return-Path: <alexey.melnikov@isode.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 17A0F3A005F for <extra@ietfa.amsl.com>; Mon, 6 Jul 2020 10:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 mKnQA5px8g2E for <extra@ietfa.amsl.com>; Mon, 6 Jul 2020 10:38:08 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 9D9F73A005B for <extra@ietf.org>; Mon, 6 Jul 2020 10:38:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1594057087; d=isode.com; s=june2016; i=@isode.com; bh=M4C50GX/w/OcHlotdFBq5cbvfUMcmV4Z6tnRavSklO0=; 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=ckg82nAHKKV5nBvrYxLIkio9VaVT6eG0CniMXxJVHgXK8Atu6I9flMz6H2zlTPlikJwt1g 4FqGk9HoZP2PbRrXyF3TRhVNHooCY7E/Nu3SrkzeC6BhBdRhTA6ca26zyCuDc5n7YKef6H 0HAHIFZPnxFkeqWM1VJa38c+ES2yq9E=;
Received: from [172.27.253.179] (connect.isode.net [172.20.0.72]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <XwNhfwAkBhH8@waldorf.isode.com>; Mon, 6 Jul 2020 18:38:07 +0100
To: Bron Gondwana <brong@fastmailteam.com>, Timo Sirainen <timo@sirainen.com>
Cc: extra@ietf.org
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> <2fe5352f-f2c5-4e50-b9c4-6da38fbcc4d0@dogfood.fastmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <93c5effc-bf6c-b36b-282f-c334883c2966@isode.com>
Date: Mon, 6 Jul 2020 18:38:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
In-Reply-To: <2fe5352f-f2c5-4e50-b9c4-6da38fbcc4d0@dogfood.fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------5D37FA9A6870CB100AC4823C"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/yY-HCzHH2ZRd243Zh9jHR44hrDE>
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: Mon, 06 Jul 2020 17:38:10 -0000

On 17/06/2020 13:27, Bron Gondwana wrote:

> 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.

Following on the suggestion to use LIST extended data items for this

       C: C04 create NonCannonicalName
       S: * LIST () "/" "CannonicalName" ("TAG" ("C04"))
       S: C04 OK done

In the example above imagine that "CannonicalName" is the canonical 
(normalized) version of "NonCannonicalName"

And the corresponding ABNF:

tag-extended-item = "TAG" SP "(" tag-string ")"
    ; Complies with &lt;mbox-list-extended-item&gt;
    ; The value complies with &lt;tagged-ext-val&gt;
    ; The value is the tag of the corresponding
    ; CREATE command.

And a similar extended data item can be used to return MAILBOXID (when 
supported).

Does this work for people?

Best Regards,

Alexey