RFC 9698: The JMAPACCESS Extension for IMAP
In plain English — editorial summary, not part of the RFC
This document defines an IMAP extension to let clients know that the messages in this IMAP server are also available via the JSON Meta Application Protocol (JMAP), and how. It is intended for clients that want to migrate gradually to JMAP or use JMAP extensions within an IMAP client.
Document record
- Document ID
- RFC9698
- Published
- January 2025
- Authors
- A. Gulbrandsen; B. Gondwana
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9979Registration of Further IMAP/JMAP Keywords and Mailbox Name AttributesCurrent
May 2026
- RFC 9670JSON Meta Application Protocol (JMAP) SharingCurrent
November 2024
- RFC 9661The JSON Meta Application Protocol (JMAP) for Sieve ScriptsCurrent
September 2024
- RFC 9755IMAP Support for UTF-8Current
March 2025
- RFC 9610JSON Meta Application Protocol (JMAP) for ContactsCurrent
December 2024
- RFC 9586IMAP Extension for Using and Returning Unique Identifiers (UIDs) OnlyCurrent
May 2024
- RFC 9585IMAP Response Code for Command Progress NotificationsCurrent
May 2024
- RFC 9425JSON Meta Application Protocol (JMAP) for QuotasCurrent
June 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?