Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

A. Melnikov
B. Leiba

Stream:

IETF

Source:

sieve (app)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6134

Discuss this RFC: Send questions or comments to the mailing listsieve@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6134

Abstract

The Sieve email filtering language can be used to implement emailwhitelisting, blacklisting, personal distribution lists, and othersorts of list matching. Currently, this requires that all members ofsuch lists be hard-coded in the script itself. Whenever a member ofa list is added or deleted, the script needs to be updated andpossibly uploaded to a mail server.

This document defines a Sieve extension for accessing externallystored lists -- lists whose members are stored externally to thescript, such as using the Lightweight Directory Access Protocol(LDAP), the Application Configuration Access Protocol (ACAP), vCardExtensions to WebDAV (CardDAV), or relational databases. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.