Re: [Extra] AD review of draft-ietf-extra-sieve-mailboxid-03

Bron Gondwana <brong@fastmailteam.com> Mon, 02 November 2020 05:00 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 8E2893A0D95; Sun, 1 Nov 2020 21:00:35 -0800 (PST)
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=pj6Z8KYA; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=SuuQgcGT
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 Wl0EmfCC6Oqk; Sun, 1 Nov 2020 21:00:33 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33D073A0D8B; Sun, 1 Nov 2020 21:00:29 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 809735C009C; Mon, 2 Nov 2020 00:00:28 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Mon, 02 Nov 2020 00:00:28 -0500
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=fm1; bh=ffyC lxxqi1F3mDbjDQgkyrKqlYhI0FvZrC9VY07qlLA=; b=pj6Z8KYASCnazRVl/C7v QuA7UyNBQHb+mGMKVrypuhDtpgi6dIo4nMj6rrb7YT2zguKmaPZ1RHJWybO8Tddq Wu5C7v5OObrlYvhGuv0t6PTlUVEdNCYp+x6JqimjPEfnJatMGGn6QchTMlwTbZum fzaLqu55K9ycEBqahqsSx6fvDY/RiQJwC1mYZcRdmTt3MJ5AjmziO1TuKXsmm3Ob cH4pBd+rgFdr/siqNXRhp66fp8Css/9Uv56mm4NVeLGRyGneB6M41mKFeQTpHhgB M//UodhWrLA3g2xdwFTji42YNa0l/KYX067T70yUDRyUkCa9NpQrlSyd1meL28IX iw==
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=ffyClx xqi1F3mDbjDQgkyrKqlYhI0FvZrC9VY07qlLA=; b=SuuQgcGTaqcFD8aJJiuM0w AMD6pUXz45uvO1CaTYhk+o/tObAY1EKcl7x1q4mOgagMGsaYxJs62mC0uRVUKIL5 PdERs3lYIKEWCBNMb0PRkbPHzkeYC/6r5qtvvLOCy4YMt9djxcf1Sa2Uk3dQ+YE6 D6Uwz4C4HY/d+8R6/ZN28uS6SD3d0kj1PV6Y5vuu4jcXjcZvGw8NQRagg5WpB2vl QiydiSQxL/fB9yOyKqV1hash/skZUV1x0TWQKOvfy052XxAN9lAOtHjjDuuHz3GO cUP9wHMrrrmRD0e2gmVUYDqwltyc+z5H06/y0cA01bzRBPGgUUpLdNVgy79lY+Kw ==
X-ME-Sender: <xms:bJKfX5cYMRJk_RzU-we7Gj1bxXscWkA0PjR3nfp7ENC8sMNxnPVVPg> <xme:bJKfX3M-KcCtJFioAxuDiz0Qa_su3mtpzN6fPSvfgjghGstdLpApeIP5Fk6Svhvif W82WB8nTMM>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedruddttddgjeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdeurhho nhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh eqnecuggftrfgrthhtvghrnheptdehteegfeevteduffevteehfffghefhvdevkeeuhfeh ueetudehgfegieekjeetnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:bJKfXyhBDyNm0eTh3xil5dF5VoaMJz15p2Q-t6b27woXyMzEAc-CJw> <xmx:bJKfXy8azKfVeT5u3whtx8RJVtWHEMWmbPPYakFV41Oh-7uym1ThmQ> <xmx:bJKfX1skBfODNIoKPDMmgYWodiIHoWbWJZBVIgPGUoMIvyt59qRHCw> <xmx:bJKfXz1bhGmT1B2Qhiu9mrLTy1_ZPOj64UzFacPnqdKT3hFKQAVpHQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 0921C180093; Mon, 2 Nov 2020 00:00:28 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-530-g8da6958-fm-20201021.003-g69105b13-v35
Mime-Version: 1.0
Message-Id: <d606f42d-ce13-4eb7-90e8-10727e7ca2d4@dogfood.fastmail.com>
In-Reply-To: <bff22cc7-aa9e-4c4a-ab29-df0dd5e08cce@www.fastmail.com>
References: <CALaySJ+zuKm=eK=KxfyFNecZPXN_F0TxQAERxapmnHNYLdj_hg@mail.gmail.com> <bff22cc7-aa9e-4c4a-ab29-df0dd5e08cce@www.fastmail.com>
Date: Mon, 02 Nov 2020 16:00:06 +1100
From: Bron Gondwana <brong@fastmailteam.com>
To: Barry Leiba <barryleiba@computer.org>, draft-ietf-extra-sieve-mailboxid.all@ietf.org
Cc: extra@ietf.org
Content-Type: multipart/alternative; boundary="476301d9189a49a8bd7b9193e11c07c4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/VqAdhH1zcGyJiKxRHHJTw2x6FIQ>
Subject: Re: [Extra] AD review of draft-ietf-extra-sieve-mailboxid-03
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, 02 Nov 2020 05:00:41 -0000

On Mon, Sep 7, 2020, at 11:01, Bron Gondwana wrote:
> 
> 
> On Sat, Sep 5, 2020, at 03:23, Barry Leiba wrote:
>> Here's my AD review of the subject document.  I have some issues to
>> discuss about the specification, so please read my comments and let's
>> have the discussion.  I'll set the substrate to "AD Followup".

[...]

>> — Section 4.2 —
>> 
>> What’s the use case for prioritising the mailboxid over the special
>> use?  That also seems an odd choice, given the context of special use
>> mailboxes.  The combination just seems strange — I would normally
>> specify *either* the special use of the mailbox *or* the name, but not
>> both.  Adding mailboxid to that just adds more weirdness.
> 
> That's fair - I would be willing to change the order there.  I expect that nobody will do it, but I don't want to forbid it either, and I want to define a fixed order that works the same across servers.
> 
> I will write an email to the list about this particular issue, so it doesn't get lost in this.

I ran into too much complexity with this in the end.  It means we can't just say "follow the process in the other doc" and instead have to create a big messy state machine that replicates it - for no real benefit.

If you don't want delivery to stick with the mailboxid, then in this case you would indeed create a rule that is just "fileinto by specialuse" and not specify a mailboxid - so the only reason to specify the ID is if you wanted to stick with the mailbox even if the specialuse was moved.  Maybe it doesn't make sense to allow both, but I also don't think it hurts to allow both, and having the ID bind more tightly is clean, because the ID can never be moved to another mailbox.

Bron.

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