RFC 8621: The JSON Meta Application Protocol (JMAP) for Mail
In plain English — editorial summary, not part of the RFC
This document specifies a data model for synchronising email data with a server using the JSON Meta Application Protocol (JMAP). Clients can use this to efficiently search, access, organise, and send messages, and to get push notifications for fast resynchronisation when new messages are delivered or a change is made in another client.
Document record
- Document ID
- RFC8621
- Published
- August 2019
- Authors
- N. Jenkins; C. Newman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 108
- Also known as
- —
- Updates:
- RFC 5788
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9007Handling Message Disposition Notification with the JSON Meta Application Protocol (JMAP)Current
March 2021
- RFC 9425JSON Meta Application Protocol (JMAP) for QuotasCurrent
June 2023
- RFC 8620The JSON Meta Application Protocol (JMAP)Updated
July 2019
- RFC 9610JSON Meta Application Protocol (JMAP) for ContactsCurrent
December 2024
- RFC 9661The JSON Meta Application Protocol (JMAP) for Sieve ScriptsCurrent
September 2024
- RFC 9670JSON Meta Application Protocol (JMAP) SharingCurrent
November 2024
- RFC 8617The Authenticated Received Chain (ARC) ProtocolCurrent
July 2019
- RFC 8616Email Authentication for Internationalized MailCurrent
June 2019
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?