RFC 5784: Sieve Email Filtering: Sieves and Display Directives in XML
In plain English — editorial summary, not part of the RFC
This document describes a way to represent Sieve email filtering language scripts in XML. Representing Sieves in XML is intended not as an alternate storage format for Sieve but rather as a means to facilitate manipulation of scripts using XML tools. The XML representation also defines additional elements that have no counterparts in the regular Sieve language. These elements are intended for use by graphical user interfaces and provide facilities for labeling or grouping sections of a script so they can be displayed more conveniently. These elements are represented as specially structured comments in regular Sieve format. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5784
- Published
- March 2010
- Authors
- N. Freed; S. Vedam
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6009Sieve Email Filtering: Delivery Status Notifications and Deliver-By ExtensionsCurrent
October 2010
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 5463Sieve Email Filtering: Ihave ExtensionCurrent
March 2009
- RFC 5429Sieve Email Filtering: Reject and Extended Reject ExtensionsCurrent
March 2009
- RFC 5260Sieve Email Filtering: Date and Index ExtensionsCurrent
July 2008
- RFC 9422The LIMITS SMTP Service ExtensionCurrent
February 2024
- RFC 5337Internationalized Delivery Status and Disposition NotificationsObsoleted
September 2008
- RFC 6468Sieve Notification Mechanism: SIP MESSAGECurrent
February 2012
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?