RFC 9042: Sieve Email Filtering: Delivery by MAILBOXID
In plain English — editorial summary, not part of the RFC
The OBJECTID capability of IMAP (RFC 8474) allows clients to identify mailboxes by a unique identifier that survives renaming. This document extends the Sieve email filtering language (RFC 5228) to allow using that same unique identifier as a target for fileinto rules and for testing the existence of mailboxes.
Document record
- Document ID
- RFC9042
- Published
- June 2021
- Authors
- B. Gondwana
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 5228
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 9007Handling Message Disposition Notification with the JSON Meta Application Protocol (JMAP)Current
March 2021
- RFC 9122IANA Registry for Sieve ActionsCurrent
June 2023
- RFC 9425JSON Meta Application Protocol (JMAP) for QuotasCurrent
June 2023
- RFC 8621The JSON Meta Application Protocol (JMAP) for MailCurrent
August 2019
- 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?