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

Michael Slusarz <michael.slusarz@open-xchange.com> Wed, 20 November 2019 17:58 UTC

Return-Path: <michael.slusarz@open-xchange.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 56E2312013A for <extra@ietfa.amsl.com>; Wed, 20 Nov 2019 09:58:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 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_HTML_ONLY=0.1, RCVD_IN_DNSWL_MED=-2.3, 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 (2048-bit key) header.d=open-xchange.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 3OBo9DdFD2Kc for <extra@ietfa.amsl.com>; Wed, 20 Nov 2019 09:58:44 -0800 (PST)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 B75CD1200E6 for <extra@ietf.org>; Wed, 20 Nov 2019 09:58:43 -0800 (PST)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.open-xchange.com (Postfix) with ESMTPS id 880DC6A27D; Wed, 20 Nov 2019 18:58:41 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1574272721; bh=0OO/ukI1Rx1rlc8zeEr7a15wvcb23Lc53FD183p6vlo=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From; b=Qw9vUw12Zjn40kDOJdUFF6s47vtcKL7Yl4KW/0Ku0foolOJ8Rs7jd05ZTFnnwOofO azQYNVjkLvvtz1sda/ZpPkmEHJT4jgFOXzkadsk2phgk29roau/wnXrbtfxbXY/hVh qBKep3GijOEB0SJUqVYI5y0CA9Xg+n4GvOQAMWMLmgNdjq6WLmIfX94YNm0hBzP0Vo eOl8wSo2/iZlBwycJNXlP44Sld7fvJQKNKEFlRdyh97szRSseB4tjDE+ZI1eUZgeIr RfW6TSZCPNIyk2bBvxOYlrIwiLcHQlssvRXz9mPNNnIFwFYxYptcvj9tddO1Fi1xU4 gPA47viImTVAQ==
Received: from appsuite-gw2.open-xchange.com (appsuite-gw2.open-xchange.com [10.20.28.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 7A92A3C0101; Wed, 20 Nov 2019 18:58:41 +0100 (CET)
Date: Wed, 20 Nov 2019 10:58:41 -0700 (MST)
From: Michael Slusarz <michael.slusarz@open-xchange.com>
Reply-To: Michael Slusarz <michael.slusarz@open-xchange.com>
To: Bron Gondwana <brong@fastmailteam.com>, extra@ietf.org
Message-ID: <779461021.18132.1574272721408@appsuite-gw2.open-xchange.com>
In-Reply-To: <9583d392-d699-486a-9111-b8a0288d2cda@dogfood.fastmail.com>
References: <51568edb-792c-46b7-a2b2-3f0a1ac91997@dogfood.fastmail.com> <9583d392-d699-486a-9111-b8a0288d2cda@dogfood.fastmail.com>
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.2-Rev17
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=michael.slusarz@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFdRf+ABCACjsnzeuEJqUrZHnmyTL0r8JwN0YF6ZS/hgHYx83/dhz2LRgq0bkl5FSYPc6ZY7j7G NqvvPxR4Ri6xfevym91IhdJbQaiJ2B0kWAz+p4H/iXhgZwsYdjFN/c3+MPEjSazCPwASWCDHv2ueCay 0YO2dmw9TnR6rA6GiReQPGumgCZJ4xX8AUBUQftdJOrq/fl1xpYWrsFrTIfBml1x3Q4Mf3+ocH7ZT/u SST2IJTx4a9szQcnrsVHn/Fc2wp4P4FkW87sQFpLND80E5VAwxEdCAtQrhoocUfmh3LyyIncAOIRdw0 aR/1PSgwuj8A2c1W0DRYuzCNaGveugCT6GmbF7qbABEBAAG5AQ0EV1F/4AEIAJ98e4BRvKeJSzSqybD ZzOcphkUy+PlMrhkQkc2m36U01+4E9AtUz3XGNIJE+in9yYKqXbtHJCavOPcFhktVGFvSADKT311ZXq Cx/ibvrWI/DmoBCCIY9iwrutJX08nOoj53wpiNVOuR6vGFJIHO7TNosPcWWsw16LiZIwo9GiU2KseU/ xW0h26ouPbVqVpFX1Tgv+xaCBF8rj4kgoghnvTVG5aEgF+QExOLqx6BmarePKboTFVnMk6NYAwC5TtJ DfpWqa/5vQa8oVAex09elUrN+IQM/tcbMG+tAe5mhjJCke96tdEno29KYjs3Ecl9t1GMcsVAM1k8D8J DJzPCB/cAEQEAAYkBMQQYAQIAGwUCV1F/4AIbDAQLCQgHBhUKCQgLAgUJEswDAAAKCRAH1y6/pl54M6 obB/9AbXRu5SYhYrmTMFGDNqq0BKeoeS1n6cA2rvYRPmmwKSd9/sZG6815X8worSUjPb4r0P/9UoUUy P99BIN0aKc/7baCCV2/00fITrW0sS5Es2xuDuwcRAwwMJX09yMDeCu6M0Y2kn8QjKr1Pu87isoxliQz QDdsYJd9b/iSPFAW+sV7xYlkVcw4XoXYolQTUjNBuWbl6tV6dQN66m6RnCnB1uolFtbZENRiVcHOAdI DmYMjX3UL8cMtqpMyAXe0HTkb1BK2I5m4Kz0thK+beBBLyd6M4bK45zI6L3f5oDOty9o2jAnxlSVdUi ZfBSBypOekOX0bw2w/4XtUoS9emDRk
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/Ohc46DvEYUZ_ZZeKJcC1JWdFtGE>
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: Wed, 20 Nov 2019 17:58:46 -0000

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" rel="nofollow">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