"Sieve Email Filtering: MIME part Tests, Iteration, Extraction, Replacement and Enclosure", Tony Hansen, Cyrus Daboo, 13-Jul-09. ( bytes)

This document defines extensions to the Sieve email filtering language to permit analysis and manipulation of the MIME body parts of an email message. Note This document is being discussed on the MTA-FILTERS mailing list, ietf-mta-filters@imc.org.

"Sieve Email Filtering: Delivery Status Notifications and Deliver-By Extensions", Ned Freed, 23-Mar-09. ( bytes)

This document describes the "envelope-dsn", "redirect-dsn", "envelope-deliverby", and "redirect-deliverby" extensions to the Sieve email filtering language. The "envelope-dsn" and "envelope- deliverby" extensions provide access to additional envelope information provided by the delivery status notification and deliver-by SMTP extensions. The "redirect-dsn" and "redirect- deliverby" extensions extend Sieve's redirect action to provide control over delivery status notification and deliver-by parameters, respectively.

"A Protocol for Remotely Managing Sieve Scripts", Alexey Melnikov, Tim Martin, 17-Jan-09. ( bytes)

Sieve scripts allow users to filter incoming email. Message stores are commonly sealed servers so users cannot log into them, yet users must be able to update their scripts on them. This document describes a protocol "ManageSieve" for securely managing Sieve scripts on a remote server. This protocol allows a user to have multiple scripts, and also alerts a user to syntactically flawed scripts.

"Sieve Notification Mechanism: SIP MESSAGE", Alexey Melnikov, Henning Schulzrinne, Qian Sun, 7-Mar-09. ( bytes)

This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent over the SIP MESSAGE.

"Sieve Email Filtering: Include Extension", Cyrus Daboo, Aaron Stone, 29-Jul-09. ( bytes)

The Sieve Email Filtering "include" extension permits users to include one Sieve script inside another. This can make managing large scripts or multiple sets of scripts much easier, and allows a site and its users to build up libraries of scripts. Users are able to include their own personal scripts or site-wide scripts. Change History (to be removed prior to publication as an RFC) Changes from ietf-02 to ietf-03: a. Setting a variable then calling global on it is an error (something like 'use strict'). b. Specify that the 'global' keyword is only available when 'variables' has also been required. c. Uploading a script that includes a nonexistent script is not an error at upload time. Changes from ietf-01 to ietf-02: a. Require that script names must be constant strings, not subject to variable expansion. b. Try the phrase immediate script instead of current script. c. Clarify that "global 'varname'" and "global.varname" refer to the same variable. d. Drop the requirement the global keywords come after require and before anything else. Changes from ietf-00 to ietf-01: a. Replaced import/export with global. b. Added :once modifier to include. c. Added global namespace to see if it holds water. Changes from daboo-06 to ietf-00: a. None Changes from -05 to -06: a. Aaron Stone joins as author. b. Removed | characters from the script examples. c. Updated draft references to published RFCs. Changes from -04 to -05: a. Fixed examples. b. Relaxed requirement that imported/exported variables be set before being used. Changes from -03 to -04: a. Fixed missing 2119 definitions. b. Defined interaction with variables through use of import and export commands. Changes from -02 to -03: a. Refreshing expired draft (updated for nits). b. Syntax -> Usage. c. Updated to 3028bis reference. Changes from -01 to -02: a. Minor formatting changes only - refreshing expired draft. Changes from -00 to -01: a. Added IPR boiler plate. b. Re-ordered sections at start to conform to RFC style. c. Moved recursion comment into General Considerations section. d. Switched to using optional parameter to indicate personal vs global. e. Explicitly state that an error occurs when a missing script is included.

"Sieve Extension: Externally Stored Lists", Alexey Melnikov, 5-Jul-09. ( bytes)

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.

Return to Internet-Draft directory.

Return to IETF home page.