RFC 5232: Sieve Email Filtering: Imap4flags Extension
In plain English — editorial summary, not part of the RFC
Recent discussions have shown that it is desirable to set different IMAP (RFC 3501) flags on message delivery. This can be done, for example, by a Sieve interpreter that works as a part of a Mail Delivery Agent. This document describes an extension to the Sieve mail filtering language for setting IMAP flags. The extension allows setting of both IMAP system flags and IMAP keywords. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5232
- Published
- January 2008
- Authors
- A. Melnikov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5255Internet Message Access Protocol InternationalizationCurrent
June 2008
- RFC 5257Internet Message Access Protocol - ANNOTATE ExtensionCurrent
June 2008
- RFC 5259Internet Message Access Protocol - CONVERT ExtensionCurrent
July 2008
- RFC 5423Internet Message Store EventsCurrent
March 2009
- RFC 5524Extended URLFETCH for Binary and Converted PartsCurrent
May 2009
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 4468Message Submission BURL ExtensionUpdated
May 2006
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?