IETF Logo Mail Archive

[mailmaint] Re: WGLC on draft-ietf-mailmaint-imap-objectid-partial-00

Matt Diephouse <diephouse@apple.com> Thu, 06 November 2025 15:55 UTC

Return-Path: <diephouse@apple.com>
X-Original-To: mailmaint@mail2.ietf.org
Delivered-To: mailmaint@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id C664484749C2 for <mailmaint@mail2.ietf.org>; Thu, 6 Nov 2025 07:55:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IV-m51GfLXgl for <mailmaint@mail2.ietf.org>; Thu, 6 Nov 2025 07:55:46 -0800 (PST)
Received: from ma-mx04.apple.com (ma-mx04.apple.com [17.23.4.22]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 312F184749B6 for <mailmaint@ietf.org>; Thu, 6 Nov 2025 07:55:46 -0800 (PST)
Received: from st47p01nt-mtap05.apple.com (st47p01nt-mtap05.ise.apple.com [10.170.123.88]) by st47p01nt-mxp04.apple.com (Oracle Communications Messaging Server 8.1.0.28.20250821 64bit (built Aug 21 2025)) with ESMTPS id <0T5B16FOVAWSJF00@st47p01nt-mxp04.apple.com> for mailmaint@ietf.org; Thu, 06 Nov 2025 15:55:40 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.100.49 definitions=2025-11-06_03,2025-11-06_01,2025-10-01_01
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=content-type : date : from : in-reply-to : message-id : mime-version : references : subject : to; s=20180706; bh=0+YijtNIWcx12hpe6+WOMCFz7DIEFoCJb9Cxxjnc7DY=; b=bC4mdGqQCZwFEKrkLK5HX//3GQaku3+PlzkpcSriEgDCyLNEtpan17UmxjFlwJf14HPX YUR/rP2qmw+3TF3Kkorka+2GLBFy8st5FzaYjgxe2rgZWGjl5maEPIor/h5cR8rKO9/e 4AlBF8zxBhaHeV5kw5oH4GMyEWThlixz5SE1c38u98+g+O/Ea6afvRwruZmcevOqqj3q Ox7RpN5vW7132Opcd/z0F5AREMTtio7lC3RWCN3NPpidmuQjTfNtNxvcxT5gMvUDDTWG x8Wi1T1dw1JWS5XxhziJdj2D25kGDoTIY3KFgLoyMJJ0EwQqFF8GLkAExkaaCFSCGOiZ 9Q==
Received: from st47p01nt-mmpp06.apple.com (st47p01nt-mmpp06.ise.apple.com [10.170.123.80]) by st47p01nt-mtap05.apple.com (Oracle Communications Messaging Server 8.1.0.28.20250821 64bit (built Aug 21 2025)) with ESMTPS id <0T5B0R8BVAWSDP50@st47p01nt-mtap05.apple.com> for mailmaint@ietf.org; Thu, 06 Nov 2025 15:55:40 +0000 (GMT)
Received: from process_milters-daemon.st47p01nt-mmpp06.apple.com by st47p01nt-mmpp06.apple.com (Oracle Communications Messaging Server 8.1.0.28.20250821 64bit (built Aug 21 2025)) id <0T5B1X600AUMBS00@st47p01nt-mmpp06.apple.com> for mailmaint@ietf.org; Thu, 06 Nov 2025 15:55:40 +0000 (GMT)
X-Va-A:
X-Va-T-CD: d929b57b965f8371e7eeacb9eb4d4b30
X-Va-E-CD: 134b983b37d81c58afb8cf70ac605d89
X-Va-R-CD: 084bf22e5caa93a2866db6c104955d29
X-Va-ID: 3f1c68ea-5698-49d3-a629-2b5f6175b9d3
X-Va-CD: 0
X-V-A:
X-V-T-CD: d929b57b965f8371e7eeacb9eb4d4b30
X-V-E-CD: 134b983b37d81c58afb8cf70ac605d89
X-V-R-CD: 084bf22e5caa93a2866db6c104955d29
X-V-ID: 99dfad2b-6f1c-4a1d-b6a0-bbb0498b8213
X-V-CD: 0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.100.49 definitions=2025-11-06_03,2025-11-06_01,2025-10-01_01
Received: from smtpclient.apple (unknown [17.10.12.9]) by st47p01nt-mmpp06.apple.com (Oracle Communications Messaging Server 8.1.0.28.20250821 64bit (built Aug 21 2025)) with ESMTPSA id <0T5B1WGLEAWRHK00@st47p01nt-mmpp06.apple.com> for mailmaint@ietf.org; Thu, 06 Nov 2025 15:55:40 +0000 (GMT)
From: Matt Diephouse <diephouse@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_61084DB4-CAF0-4057-9E49-B8537C722AA1"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3864.300.2\))
Date: Thu, 06 Nov 2025 10:55:29 -0500
References: <b4403ff0-204a-435d-ba62-7ed3ddac4f22@fastmail.com>
To: "mailmaint@ietf.org" <mailmaint@ietf.org>
In-reply-to: <b4403ff0-204a-435d-ba62-7ed3ddac4f22@fastmail.com>
Message-id: <C5610B7E-A3DF-4D14-BA27-982A2A6B2808@apple.com>
X-Mailer: Apple Mail (2.3864.300.2)
Message-ID-Hash: M3WVKQ5XXBXMRV4HYCKZS2AGEYIZN2U4
X-Message-ID-Hash: M3WVKQ5XXBXMRV4HYCKZS2AGEYIZN2U4
X-MailFrom: diephouse@apple.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [mailmaint] Re: WGLC on draft-ietf-mailmaint-imap-objectid-partial-00
List-Id: Mail Maintenance <mailmaint.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mailmaint/-XXZYfdI-E3URDSR_wXpF4Mo7VI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mailmaint>
List-Help: <mailto:mailmaint-request@ietf.org?subject=help>
List-Owner: <mailto:mailmaint-owner@ietf.org>
List-Post: <mailto:mailmaint@ietf.org>
List-Subscribe: <mailto:mailmaint-join@ietf.org>
List-Unsubscribe: <mailto:mailmaint-leave@ietf.org>

I’m very interested in how OBJECTID=MAILBOXID + JMAPACCESS + jmap-email-push can be used together to register for JMAP push notifications for an IMAP mailbox. (Full adoption of OBJECTID requires user-facing product decisions about how to treat emails that are in multiple mailboxes.)

However, Mauro’s ACCOUNTID draft has alerted me to a hole in this solution:

• jmap-email-push does not return the account ID during registration
• There’s no way to get the account ID over IMAP
• Clients need the account ID to map the push payload to an IMAP account (mailbox IDs are not guaranteed to be unique across accounts)

This could be solved by returning the account ID during the jmap-email-push push registration, by adding account IDs to mailboxes over IMAP as Mauro has suggested, or probably in other ways.

That isn’t strictly related to this proposal, but it may be worth considering these problems together.

Matt

> On Oct 6, 2025, at 10:03 AM, Ken Murchison <murch@fastmail.com> wrote:
> 
> Dear WG Participants,
> 
> This email starts a WG Last Call on the "IMAP OBJECTID Partial" document (draft-ietf-mailmaint-imap-objectid-partial) <https://datatracker.ietf.org/doc/draft-ietf-mailmaint-imap-objectid-partial/>.
> 
> This is a very simple document that allows a server to implement just half of the existing OBJECTID capability.
> 
> Please review this document and reply on the mailing list if you support progression of the document to IESG or have any comments or concerns, by Fri, Oct 24, 2025.
> 
> 
> -- 
> Kenneth Murchison
> Staff Software Developer
> Fastmail US LLC
> IETF MailMaint Co-Chair
> -- 
> mailmaint mailing list -- mailmaint@ietf.org
> To unsubscribe send an email to mailmaint-leave@ietf.org

v2.46.0 | Report a Bug | By Email | System Status