| Internet-Draft | IMAP OBJECTID Partial | September 2025 |
| Gondwana | Expires 29 March 2026 | [Page] |
This document extends the IMAP OBJECTID specification in RFC8474, which describes persistent identifiers for Mailboxes, Emails, and Threads in email.¶
Some servers may be unable to provide persistent identifiers for some data types, but be able to provide them for others. This extension allows a server to specify that it can provide some objectids, without needing to implement all data types.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 29 March 2026.¶
Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
If a server has the capability OBJECTID=MAILBOX then it supports the objectids for mailboxes described in [OBJECTID] section 4.¶
If a server has the capability OBJECTID=EMAILID then it supports the objectids for emails (and optionally threads) described in [OBJECTID] sections 5 and 6.¶
An implementation which supports both MAILBOXID and EMAILDID SHOULD only issue the capability OBJECTID as defined in [OBJECTID]. Clients are recommended to check for both the specific or general capability when deciding what requests to send.¶
IANA is asked to register the capabilities OBJECTID=MAILBOX and OBJECTID=EMAILID with reference to this document.¶
This document does not introduce any security considerations beyond those described in [OBJECTID].¶
Daniel Eggert, Ken Murchison, Matt Diephouse, the bar at Melia Castilla in Madrid.¶
[[This section to be removed by RFC Editor]]¶
Initial version¶