RFC 5233: Sieve Email Filtering: Subaddress Extension
In plain English — editorial summary, not part of the RFC
On email systems that allow for 'subaddressing' or 'detailed addressing' (e.g., "ken+sieve@example.org"), it is sometimes desirable to make comparisons against these sub-parts of addresses. This document defines an extension to the Sieve Email Filtering Language that allows users to compare against the user and detail sub-parts of an address. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5233
- Published
- January 2008
- Authors
- K. Murchison
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 7
- Also known as
- —
- Obsoletes:
- RFC 3598
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5232Sieve Email Filtering: Imap4flags ExtensionCurrent
January 2008
- RFC 5235Sieve Email Filtering: Spamtest and Virustest ExtensionsCurrent
January 2008
- RFC 5231Sieve Email Filtering: Relational ExtensionCurrent
January 2008
- RFC 5230Sieve Email Filtering: Vacation ExtensionUpdated
January 2008
- RFC 5229Sieve Email Filtering: Variables ExtensionUpdated
January 2008
- RFC 5228Sieve: An Email Filtering LanguageUpdated
January 2008
- RFC 5255Internet Message Access Protocol InternationalizationCurrent
June 2008
- RFC 5256Internet Message Access Protocol - SORT and THREAD ExtensionsUpdated
June 2008
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?