RFC 3598: Sieve Email Filtering -- Subaddress Extension
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5233.
Current version: 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 mail filtering language that allows users to compare against the user and detail parts of an address. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3598
- Published
- September 2003
- Authors
- K. Murchison
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 6
- Also known as
- —
- Obsoleted by:
- RFC 5233
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1971IPv6 Stateless Address AutoconfigurationObsoleted
August 1996
- RFC 5322Internet Message FormatUpdated
October 2008
- RFC 3876Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3)Current
September 2004
- RFC 3138Extended Assignments in 233/8Obsoleted
June 2001
- RFC 3098How to Advertise Responsibly Using E-Mail and Newsgroups or - how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$Current
April 2001
- RFC 3027Protocol Complications with the IP Network Address TranslatorCurrent
January 2001
- RFC 2928Initial IPv6 Sub-TLA ID AssignmentsCurrent
September 2000
- RFC 2779Instant Messaging / Presence Protocol RequirementsCurrent
February 2000
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?