IETF Logo Mail Archive

Re: [Extra] In favour of OBJECTID being inculded in IMAP4REV2 - please reply by Friday!

"Bron Gondwana" <brong@fastmailteam.com> Fri, 22 November 2019 03:10 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 E5668120836 for <extra@ietfa.amsl.com>; Thu, 21 Nov 2019 19:10:38 -0800 (PST)
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=Bp/4kv3e; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=i7A3+yJp
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 rv-6AJm9zBV6 for <extra@ietfa.amsl.com>; Thu, 21 Nov 2019 19:10:36 -0800 (PST)
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 B4E1312018B for <extra@ietf.org>; Thu, 21 Nov 2019 19:10:36 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id F2091D92; Thu, 21 Nov 2019 22:10:35 -0500 (EST)
Received: from imap99 ([10.202.2.99]) by compute6.internal (MEProxy); Thu, 21 Nov 2019 22:10:36 -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:subject:content-type; s=fm1; bh=l3V48O+ JN9KX3aEcGGU06pF7fphz8Q92SnzMsb5oa6o=; b=Bp/4kv3eOe+o9dbaIbtK1TA KJdhyq2JIfHrUMTj0FU6IYyj/hfx69yZyMJ/gKbsZ/sDa3oqhTsY3Ea5Zy59w+3m GirZF8T8CSnelKwY2zvgTuXEk4eVHoezFOBKaRqQ7gcIXHh1NpnMFNiq9Fx11kA1 kIXkk7sZNfEM4sR2ZyDR2PUKdoeuQETf/qTwF6OkiCNrPndhvgf1EieGhaPDf818 qrFAsaFKR8U+VHtwDFYFcUB/BXZE4ZcLKjx3tWiljRaCz/HTxaXQ7ubjvr7nNRPk LAM9IC5HSGMWSR4foKB/uouztyY5Hmi1jEvp1qFNEQSShAD7DLu2j/FI58yTydg= =
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=l3V48O +JN9KX3aEcGGU06pF7fphz8Q92SnzMsb5oa6o=; b=i7A3+yJp2KWHoOKHq6pU3X 457JBwT8yRDjfgXFo+NxEQJhXf4uEeuRd8Y2PA61d7JaIuhubiYgYr5Hj5k5CTfO +4bgKqtF1qL16AyL5n6clqJDaKjP6YUH4nsDe38/0OwRP7gMO8U9Lsl86PYO0QOb LABi4tIaclrqIpTCL+m8T1mgOUdrezwDiY7a4qFJ28sGr7c+o40BXqTGOGYvWH3t rmvONkheua7FopDOJR5uxAoJ/8AWCiamH20FFW9sJlDP1fFJvawtgzEW1Tfi57MS D/OfYyn6SO6+VFu1LkDPs94smzv7FuLrj/mmqApyHLYiTeL+MXCEcp2jbiSr6FUA ==
X-ME-Sender: <xms:q1HXXbXA1uzjjjcobW82Y8tTLeb4AYMQ3aO0AvgNG_eLy2PRCijCjg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudehfedgheefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdeurhho nhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh eqnecuffhomhgrihhnpehivghtfhdrohhrghenucfrrghrrghmpehmrghilhhfrhhomhep sghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmnecuvehluhhsthgvrhfuihiivg eptd
X-ME-Proxy: <xmx:q1HXXfSBuwDFm3VpquMARFlgbzKwjuiQnBRL78xVGbolTdqWtBsofg> <xmx:q1HXXeSE-ffNH3rQWUq7HZgSQdIh_vjbW85DruF9upzhZa0PA8X3mA> <xmx:q1HXXbItv0oXxS8ZGIt619OKTi6MyI5saO4I5Cx8XASPYLkXS51gGA> <xmx:q1HXXacjCGaI86DGy6FNs9DxyX__VcoeW4FrRFEv_P_yuRR40zV09w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6A28B300DAA; Thu, 21 Nov 2019 22:10:35 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-578-g826f590-fmstable-20191119v1
Mime-Version: 1.0
Message-Id: <7397ac9a-b2cf-49a1-a620-9c2ae1b18d0a@dogfood.fastmail.com>
In-Reply-To: <779461021.18132.1574272721408@appsuite-gw2.open-xchange.com>
References: <51568edb-792c-46b7-a2b2-3f0a1ac91997@dogfood.fastmail.com> <9583d392-d699-486a-9111-b8a0288d2cda@dogfood.fastmail.com> <779461021.18132.1574272721408@appsuite-gw2.open-xchange.com>
Date: Fri, 22 Nov 2019 14:10:32 +1100
From: Bron Gondwana <brong@fastmailteam.com>
To: Michael Slusarz <michael.slusarz@open-xchange.com>, extra@ietf.org
Content-Type: multipart/alternative; boundary="75206f3d15de432bb7df15bcdb77961d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/b3MHW_OGNbFo08yDi98m0XuduJo>
Subject: Re: [Extra] In favour of OBJECTID being inculded in IMAP4REV2 - please reply by Friday!
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: Fri, 22 Nov 2019 03:10:39 -0000

Thanks Michael,

I've discussed this with Alexey and Barry today, and we've decided not to *require* OBJECTID in the base spec, but to add a section of "recommended other extensions" to the base spec which mentions the benefits of implementing OBJECTID.

Bron.

On Thu, Nov 21, 2019, at 04:58, Michael Slusarz wrote:
>> On November 20, 2019 12:49 AM Bron Gondwana <brong@fastmailteam.com> wrote:
>> 
>> 
>> On Mon, Nov 18, 2019, at 20:50, Bron Gondwana wrote: 
>>> Also - if your server doesn't store a value and doesn't have anywhere to cache it, it can fall back to this algorithm: 
>>> 
>>>  - MAILBOXID: digest(mboxname,uidvalidity)
 - EMAILID: digest(mboxname,uidvalidity,uid)
 - THREADID: NIL
>> 
>> I was reminded off list that the final text in RFC8474 made it MUST be the same value, so it's not as easy as all that to have the objectid change on MOVE or RENAME and be totally compliant. 
>> 
>> Some options: 
>> 1) insist on remaining exactly compliant. 
>> 2) include RFC8474 naming and behaviour in IMAP4REV2 but weaken the MUSTs around keeping IDs the same. 
>> 3) OK, leave OBJECTID as optional and don't include it in IMAP4REV2.
> Dovecot response:
>  * Our previous thoughts: https://mailarchive.ietf.org/arch/msg/extra/9-hEpNOrcJryfMgMYkhrgqSPs8Q
>  * New thoughts: MAILBOXID/EMAILID is ok for rev2
>  * Dovecot already tracks this internally, so we have work-in-progress code to expose this already
>  * Agree that MAILBOXID/EMAILID should not be "fake", but should be persistent - a server should do this right, rather than trying to fake it with on-demand digest generation. So I think this is a vote for #1 of Bron's options. This requirement (assigning a non-ephemeral uniqueid per message/mailbox) doesn't seem any more onerous than keeping a UID associated with a specific message.
>  * THREADID comment from Timo (so he can expand on this, if needed): "I wonder if it would be ok to have MAILBOXID and EMAILID in the base spec, while THREADID would exist only if OBJECTID capability exists. Slightly nicer than just returning NILs as THREADIDs."
> michael 
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra
> 

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

v2.23.0 | Report a Bug | By Email