RFC 6134: Sieve Extension: Externally Stored Lists
In plain English — editorial summary, not part of the RFC
The Sieve email filtering language can be used to implement email whitelisting, blacklisting, personal distribution lists, and other sorts of list matching. Currently, this requires that all members of such lists be hard-coded in the script itself. Whenever a member of a list is added or deleted, the script needs to be updated and possibly uploaded to a mail server. This document defines a Sieve extension for accessing externally stored lists -- lists whose members are stored externally to the script, such as using the Lightweight Directory Access Protocol (LDAP), the Application Configuration Access Protocol (ACAP), vCard Extensions to WebDAV (CardDAV), or relational databases. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6134
- Published
- July 2011
- Authors
- A. Melnikov; B. Leiba
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 18
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6133Sieve Email Filtering: Use of Presence Information with Auto-Responder FunctionalityCurrent
July 2011
- RFC 6132Sieve Notification Using Presence InformationCurrent
July 2011
- RFC 6131Sieve Vacation Extension: "Seconds" ParameterCurrent
July 2011
- RFC 6152SMTP Service Extension for 8-bit MIME TransportCurrent
March 2011
- RFC 6154IMAP LIST Extension for Special-Use MailboxesCurrent
March 2011
- RFC 6065Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group MappingsCurrent
December 2010
- RFC 6203IMAP4 Extension for Fuzzy SearchCurrent
March 2011
- RFC 6047iCalendar Message-Based Interoperability Protocol (iMIP)Current
December 2010
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?