Differences
This shows you the differences between two versions of the page.
|
documents [2006/07/25 22:12] avel add managesieve draft |
documents [2020/02/08 22:15] (current) avel2 Add RFC 8580 |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Standards Track Documents (RFCs) ===== | ===== Standards Track Documents (RFCs) ===== | ||
| + | ==== Sieve Base Spec ==== | ||
| + | * [[http://www.ietf.org/rfc/rfc5228.txt|RFC 5228: Sieve: A Mail Filtering Language]] | ||
| + | This document describes a language for filtering email messages at time of final delivery. It is designed to be implementable on either a mail client or mail server. It is meant to be extensible, simple, and independent of access protocol, mail architecture, and operating system. It is suitable for running on a mail server where users may not be allowed to execute arbitrary programs, such as on black box Internet Message Access Protocol (IMAP) servers, as the base language has no variables, loops, or ability to shell out to external programs. | ||
| - | ==== Sieve Base Spec ==== | ||
| - | * [[http://www.ietf.org/rfc/rfc3028.txt|RFC 3028: Sieve: A Mail Filtering Language]] | + | ==== ManageSieve Protocol ==== |
| - | This document describes a language for filtering e-mail messages at time of final delivery. It is designed to be implementable on either a mail client or mail server. It is meant to be extensible, simple, and independent of access protocol, mail architecture, and operating system. It is suitable for running on a mail server where users may not be allowed to execute arbitrary programs, such as on black box Internet Message Access Protocol (IMAP) servers, as it has no variables, loops, or ability to shell out to external programs. | + | |
| - | ==== Sieve Extensions ==== | + | * [[http://www.ietf.org/rfc/rfc5804.txt|RFC 5804: ManageSieve: A Protocol for Remotely Managing Sieve Scripts]] |
| + | 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. | ||
| - | * [[http://www.ietf.org/rfc/rfc3431.txt|RFC 3431: Sieve Extension: Relational Tests]] | ||
| - | This document describes the RELATIONAL extension to the Sieve mail filtering language defined in RFC 3028. This extension extends existing conditional tests in Sieve to allow relational operators. In addition to testing their content, it also allows for testing of the number of entities in header and envelope fields. | ||
| - | * [[http://www.ietf.org/rfc/rfc3598.txt|RFC 3598: Sieve Email Filtering -- Subaddress Extension]] | + | ==== Alternative Representations ==== |
| - | 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. | + | |
| - | * [[http://www.ietf.org/rfc/rfc3685.txt|RFC 3685: SIEVE Email Filtering: Spamtest and VirusTest Extensions]] | + | * [[http://www.ietf.org/rfc/rfc5784.txt|RFC 5784: Sieves and Display Directives in XML]] |
| - | The SIEVE mail filtering language "spamtest" and "virustest" extensions permit users to use simple, portable commands for spam and virus tests on email messages. Each extension provides a new test using matches against numeric 'scores'. It is the responsibility of the underlying SIEVE implementation to do the actual checks that result in values returned by the tests. | + | This document describes a way to represent Sieve email filtering language scripts in XML. Representing Sieves in XML is intended not as an alternate storage format for Sieve but rather as a means to facilitate manipulation of scripts using XML tools. |
| - | ===== Internet Drafts ===== | + | ==== Sieve Language Extensions ==== |
| - | Note that the following links refer to the [[http://ietfreport.isoc.org|IETFreport site]] by ISOC. The linked page will always show the latest version of the I-D in question, and provide diffs to previous versions. | + | * [[http://www.ietf.org/rfc/rfc5173.txt|RFC 5173: Body Extension]] |
| + | This document defines a new command that tests for the occurrence of one or more strings in the body of an email message. | ||
| + | * [[http://www.ietf.org/rfc/rfc5229.txt|RFC 5229: Variables Extension]] | ||
| + | In advanced mail filtering rule sets, it is useful to keep state or configuration details across rules. This document updates the Sieve filtering language (RFC 5228) with an extension to support variables. The extension changes the interpretation of strings, adds an action to store data in variables, and supplies a new test so that the value of a string can be examined. | ||
| - | ==== Revision of base spec RFC ==== | + | * [[http://www.ietf.org/rfc/rfc5230.txt|RFC 5230: Vacation Extension]] |
| + | This document describes an extension to the Sieve email filtering language for an autoresponder similar to that of the Unix "vacation" command for replying to messages. Various safety features are included to prevent problems such as message loops. | ||
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-3028bis|Sieve: An Email Filtering Language]] | + | * [[http://www.ietf.org/rfc/rfc5231.txt|RFC 5231: Relational Extension]] |
| - | * [[draft-3028bis|Current list issues]] | + | This extension extends existing conditional tests in Sieve to allow relational operators. In addition to testing their content, it also allows for testing of the number of entities in header and envelope fields. |
| - | ==== Revision of extensions RFCs ==== | + | * [[http://www.ietf.org/rfc/rfc5232.txt|RFC 5232: Imap4flags Extension]] |
| + | This document describes an extension to the Sieve mail filtering language for setting IMAP flags. The extension allows setting of both IMAP system flags and IMAP keywords. | ||
| - | These Internet Drafts, if approved, are to make the above RFCs obsolete: | + | * [[http://www.ietf.org/rfc/rfc5233.txt|RFC 5233: Subaddress Extension]] |
| + | 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 Email Filtering Language that allows users to compare against the user and detail sub-parts of an address. | ||
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-spamtestbis|SIEVE Email Filtering: Spamtest and Virustest Extensions]] | + | * [[http://www.ietf.org/rfc/rfc5235.txt|RFC 5235: Spamtest and Virustest Extensions]] |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-rfc3598bis|Subaddress Extension]] | + | The Sieve email filtering language "spamtest", "spamtestplus", and |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-3431bis|Sieve Extension: Relational Tests]] | + | "virustest" extensions permit users to use simple, portable commands |
| + | for spam and virus tests on email messages. Each extension provides | ||
| + | a new test using matches against numeric "scores". It is the | ||
| + | responsibility of the underlying Sieve implementation to do the | ||
| + | actual checks that result in proper input to the tests. | ||
| + | * [[http://www.ietf.org/rfc/rfc3894.txt|RFC 3894: Copying Without Side Effects]] | ||
| + | By default, an e-mail message that is processed by a Sieve script is saved in the owner's "inbox". | ||
| + | Actions such as "fileinto" and "redirect" cancel this default behavior. This document defines a new keyword parameter, ":copy", to be used with the Sieve "fileinto" and "redirect" actions. Adding ":copy" to an action suppresses cancellation of the default "inbox" save. | ||
| + | * [[http://www.ietf.org/rfc/rfc5183.txt|RFC 5183: Environment Extension]] | ||
| + | The "environment" extension gives a Sieve script access to information about the Sieve interpreter itself, where it is running, and about any transport connection currently involved in transferring the message. | ||
| + | * [[http://www.ietf.org/rfc/rfc5260.txt|RFC 5260: Date and Index Extensions]] | ||
| + | The "date" extension gives Sieve the ability to test date and time values in various ways. The "index" extension provides a means to limit header and address tests to specific instances of header fields when header fields are repeated. | ||
| + | * [[http://www.ietf.org/rfc/rfc5293.txt|RFC 5293: Editheader Extension]] | ||
| + | Email header fields are a flexible and easy-to-understand means of communication between email processors. This extension enables Sieve scripts to interact with other components that consume or produce header fields by allowing the script to delete and add header fields. | ||
| - | ==== Other Sieve Extensions Drafts ==== | + | * [[http://www.ietf.org/rfc/rfc5429.txt|RFC 5429: Reject and Extended Reject Extensions]] |
| + | The "reject" and "ereject" actions shall discard a message by refusing delivery during the SMTP transaction, if possible, or by sending a Message Disposition Notification [MDN] to the envelope sender along with an explanatory message. | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc5463.txt|RFC 5463: Ihave Extension]] | ||
| + | The "ihave" extension provides a means to write scripts that can take advantage of optional Sieve features but can still run when those optional features are not available. The extension also defines a new error control command intended to be used to report situations where no combination of available extensions satisfies the needs of the script. | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc5490.txt|RFC 5490: Extensions for Checking Mailbox Status and Accessing Mailbox Metadata]] | ||
| + | This is an extension for accessing mailbox and server annotations, checking for mailbox existence, and controlling mailbox creation on "fileinto" action. | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc5703.txt|RFC 5703: MIME Part Tests, Iteration, Extraction, Replacement, and Enclosure]] | ||
| + | Extensions to the Sieve email filtering language to permit analysis and manipulation of the MIME body parts of an email message. | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc6609.txt|RFC 6609: Sieve Email Filtering: Include Extension]] | ||
| + | This 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. | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc6558.txt|RFC 6558 Sieve Extension for Converting Messages before Delivery]] | ||
| + | This document describes how the "CONVERT" IMAP extension can be used within the Sieve mail filtering language to transform messages before final delivery. | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc6785.txt|RFC 6785 Support for Internet Message Access Protocol (IMAP) Events in Sieve]] | ||
| + | Sieve defines an email filtering language that can, in principle, plug into any point in the processing of an email message. As defined in the base specification, it plugs into mail delivery. This document defines how Sieve can plug into points in IMAP where messages are created or changed, adding the option of user-defined or installation-defined filtering (or, with Sieve extensions, features such as notifications). | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc8580.txt|RFC 8580: Sieve Extension: File Carbon Copy (FCC)]] | ||
| + | The Sieve email filtering language provides a number of action commands, some of which can generate additional messages on behalf of the user. This document defines an extension to such commands to allow a copy of any generated message to be filed into a target mailbox. | ||
| + | |||
| + | |||
| + | ==== Sieve Extension for Notifications and Notification Mechanisms ==== | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc5435.txt|RFC 5435: Extension for Notifications]] | ||
| + | This document describes an extension to the Sieve mail filtering language that allows users to give specific rules for how and when notifications should be sent. | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc5436.txt|RFC 5436: Sieve Notification Mechanism: mailto]] | ||
| + | This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent by electronic mail. | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc5437.txt|RFC 5437: Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)]] | ||
| + | This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent over the Extensible Messaging and Presence Protocol (XMPP), also known as Jabber. | ||
| + | |||
| + | * [[http://www.ietf.org/rfc/rfc6468.txt|RFC 6468: Sieve Notification Mechanism: SIP Message]] | ||
| + | This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent over SIP MESSAGE. | ||
| + | |||
| + | |||
| + | ===== Internet Drafts ===== | ||
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-variables|Variables Extension]] (Approved as RFC) | + | * [[http://tools.ietf.org/html/draft-ietf-sieve-regex|Regular Expression Extension]] |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-3431bis|Relational Tests]] (Approved as RFC) | + | The Sieve base specification defines so-called match types for tests: is, contains, and matches. An "is" test requires an exact match, a "contains" test provides a substring match, and "matches" provides glob-style wildcards. This document describes an extension to the Sieve language that provides a new match type for regular expression comparisons. |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-vacation|Vacation Extension]] (Approved as RFC) | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-imapflags|IMAP flag Extension]] (Approved as RFC) | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-rfc3598bis|Subaddress Extension]] (Approved as RFC) | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-spamtestbis|Spamtest and Virustest Extensions]] | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-body|Body Extension]] | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-editheader|Editheader Extension]] | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-refuse-reject|Reject Extension]] | + | |
| - | * [[draft-reject|Current list issues]] | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-regex|Regular Expression Extension]] | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-mime-loop|Sieve Extensions: MIME Tests, MIME Bodypart Iteration, Replacement and Enclosure]] | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-freed-sieve-date-index/|Date and Index Extensions]] (individual submission) | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-daboo-sieve-include/|Include Extension]] (individual submission) | + | |
| - | ==== Sieve Management Protocol: ManageSieve ==== | + | * [[http://tools.ietf.org/html/draft-melnikov-sieve-external-lists|Externally Stored Lists]] |
| + | 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. | ||
| - | * [[http://ietfreport.isoc.org/idref/draft-martin-managesieve/|ManageSieve, A Protocol for Remotely Managing Sieve Scripts]] | ||
| - | ==== Sieve Notification Extension and Related Notification Mechanisms ==== | + | ===== Additional Links ==== |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-notify|Sieve Extension: Notifications]] | + | Obsoleted RFCs: |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-notify-mailto|Sieve Notification Mechanism: mailto]] | + | |
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-sieve-notify-xmpp|Sieve Notification Mechanism: xmpp ]] | + | |
| - | ==== Other Drafts related to Sieve ==== | + | * [[http://www.ietf.org/rfc/rfc3028.txt|RFC 3028: Sieve: A Mail Filtering Language]], obsoleted by RFC 5228 |
| + | * [[http://www.ietf.org/rfc/rfc3431.txt|RFC 3431: Relational Extension]], obsoleted by RFC 5231 | ||
| + | * [[http://www.ietf.org/rfc/rfc3598.txt|RFC 3598: Subaddress Extension]], obsoleted by RFC 5233 | ||
| + | * [[http://www.ietf.org/rfc/rfc3685.txt|RFC 3685: Spamtest and VirusTest Extensions]], obsoleted by RFC 5235 | ||
| - | * [[http://ietfreport.isoc.org/idref/draft-ietf-lemonade-imap-sieve|Support for Sieve in Internet Message Access Protocol (IMAP4)]] (Lemonade WG) | + | Other related pages and documents: |
| - | * [[http://ietfreport.isoc.org/idref/draft-newman-i18n-comparator/|Internet Application Protocol Collation Registry]] | + | |
| + | * [[http://tools.ietf.org/wg/sieve/|Sieve WG Status Pages]] | ||
| + | * [[http://tools.ietf.org/id/draft-*-sieve-|All drafts related to Sieve]] | ||
| + | * [[http://ietfreport.isoc.org/idref/rfc4790/|RFC 4790: Internet Application Protocol Collation Registry]] | ||
| + | and | ||