Sieve Extension: Externally Stored Lists
draft-melnikov-sieve-external-lists-02

 
Document Type Replaced Internet-Draft (individual)
Last updated 2009-07-05
Replaced by draft-ietf-sieve-external-lists
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-sieve-external-lists
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-melnikov-sieve-external-lists-02.txt

Abstract

Sieve scripting language can be used for implementing of whitelisting, blacklisting and personal distribution lists. Currently this requires that all members of such lists be hardcoded in the script itself. Whenever a member of such 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 mailing lists, i.e. list whose members are stored externally to the script, for example in LDAP (RFC 4510), ACAP (RFC 2244) or a relational database. ToDo o Need a way to advertise supported URI schemas in ManageSieve and ihave.

Authors

Alexey Melnikov (alexey.melnikov@isode.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)