RFC 9661: The JSON Meta Application Protocol (JMAP) for Sieve Scripts
In plain English — editorial summary, not part of the RFC
This document specifies a data model for managing Sieve scripts on a server using the JSON Meta Application Protocol (JMAP). Clients can use this protocol to efficiently search, access, organize, and validate Sieve scripts.
Document record
- Document ID
- RFC9661
- Published
- September 2024
- Authors
- K. Murchison
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9670JSON Meta Application Protocol (JMAP) SharingCurrent
November 2024
- RFC 9610JSON Meta Application Protocol (JMAP) for ContactsCurrent
December 2024
- RFC 9425JSON Meta Application Protocol (JMAP) for QuotasCurrent
June 2023
- RFC 9007Handling Message Disposition Notification with the JSON Meta Application Protocol (JMAP)Current
March 2021
- RFC 8621The JSON Meta Application Protocol (JMAP) for MailCurrent
August 2019
- RFC 8620The JSON Meta Application Protocol (JMAP)Updated
July 2019
- RFC 9671Sieve Email Filtering: Extension for Processing Calendar AttachmentsCurrent
October 2024
- RFC 9698The JMAPACCESS Extension for IMAPCurrent
January 2025
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?