
Sieve Extensions 

(last updated 2008-01-29)

Registries included below:
- Sieve Extensions


Registry Name: Sieve Extensions
Reference: [RFC5228]
Registration Procedures: Standards track or IESG approved experimental RFC

Note:
Vendor-controlled capability names may be registered on a 
first-come, first-served basis by applying to IANA with 
the template below. Registration of capability prefixes that 
do not begin with "vnd." REQUIRES a standards track or 
IESG-approved experimental RFC.

The following template should be used when applying for a 
new extension:

To: iana&iana.org
Subject: Registration of new Sieve extension

Capability name: [the string for use in the 'require' statement]
Description:     [a brief description of what the extension adds
                  or changes]
RFC number:      [for extensions published as RFCs]
Contact address: [email and/or physical address to contact for
                  additional information]

Registry:
Capability name: comparator-* (anything starting with "comparator-")
Description:     adds the indicated comparator for use with the
                 :comparator argument
RFC number:      [RFC4790][RFC5228] (Sieve base spec)
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: copy
Description:
RFC number:      [RFC3894]
Contact address: Jutta Degener
                 Sendmail, Inc.
                 6425 Christie Ave, 4th Floor
                 Emeryville, CA 94608
                 <jutta&sendmail.com>

Capability name: encoded-character
Description:     changes the interpretation of strings to allow
                 arbitrary octets and Unicode characters to be
                 represented using US-ASCII
RFC number:      [RFC5228] (Sieve base spec)
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: enotify
Description:     adds the 'notify' action for notifying user about the
                 received message. It also provides two new tests: 
                 valid_notify_method checks notification URIs for 
                 validity; notify_method_capability can check recipients 
                 capabilities.
RFC number:      [RFC-ietf-sieve-notify-12.txt]
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: envelope
Description:     adds the 'envelope' test for testing the message
                 transport sender and recipient address
RFC number:      [RFC5228] (Sieve base spec)
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: fileinto
Description:     adds the 'fileinto' action for delivering to a
                 mailbox other than the default
RFC number:      [RFC5228] (Sieve base spec)
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: imap4flags
Description:     Adds actions and tests for manipulating IMAP flags
RFC number:      [RFC5232]
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: refuse
Description:
RFC number:      [draft-elvey-refuse-sieve-01.txt]
Contact address: Matthew Elvey
                 The Elvey Partnership, LLC
                 3042 Sacramento-ietf St Ste 04
                 San Francisco, CA
                 U.S.A.
                 <sieve3&matthew.elvey.com>

Capability name: regex
Description:
RFC number:      [draft-murchison-sieve-regex-07.txt]
Contact address: Kenneth Murchison
                 <ken&oceana.com>

Capability name: reject
Description:
RFC number:      [RFC3028]
Contact address: Tim Showalter
                 <tjs&psaux.com>

Capability name: relational
Description:     Extends existing conditional tests in Sieve language
                 to allow relational operators
RFC number:      [RFC5231]
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: spamtest
Description:     Provides a test to check for varying likelihood of
                 an email message being spam.
RFC number:      [RFC5235]
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: spamtestplus
Description:     Provides a test to check for varying likelihood of
                 an email message being spam, possibly using a percentage 
                 range.
RFC number:      [RFC5235]
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: subaddress
Description:     adds the ':user' and ':detail' address parts
                 for use with the address and envelope tests
RFC number:      [RFC5233]
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: vacation
Description:     adds an action for generating an auto-reply saying
                 that the original message will not be read or
                 answered immediately
RFC number:      [RFC5230]
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: variables
Description:     Adds support for variables to the Sieve filtering language.
RFC number:      [RFC5229]
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>

Capability name: virustest
Description:     Provides a test to check for varying likelihood of
                 there being malicious content in an email message.
RFC number:      [RFC5235]
Contact address: The Sieve discussion list <ietf-mta-filters&imc.org>


References
---------- 
[RFC3028]  T. Showalter, "Sieve: A Mail Filtering Language",
           RFC 3028, January 2001.

[RFC3431]  W. Segmuller, "Sieve Extension: Relational Tests", RFC 3431,
           November 2002.

[RFC3598]  K. Murchison, "Sieve -- Subaddress Extension", RFC 3598, 
           September 2003.

[RFC3685]  C. Daboo, "SIEVE Spamtest and Virustest Extensions", RFC 3685,
           February 2004.

[RFC3894]  J. Degener, "Sieve Extension: Copying Without Side 
           Effects", RFC 3894, October 2004.

[RFC4790]  C. Newman, M. Duerst, A. Gulbrandsen, "Internet Application 
           Protocol Collation Registry", RFC 4790, March 2007.

[draft-elvey-refuse-sieve-01.txt] work in progress, June 2004.

[draft-murchison-sieve-regex-07.txt] work in progress, June 2004.  

[RFC5228]  P. Guenther and T. Showalter, Editors, "Sieve: An Email Filtering 
           Language", RFC 5228, January 2008.

[RFC5229]  K. T. Homme, "Sieve Extension: Variables", RFC 5229, January 2008.

[RFC5230]  T. Showalter and N. Freed, "Sieve Email Filtering: Vacation 
           Extension", RFC 5230, January 2008.

[RFC5231]  W. Segmuller and B. Leiba, "Sieve Extension: Relational Tests",
           RFC 5231, January 2008.

[RFC5232]  A. Melnikov, "SIEVE Email Filtering: IMAP flag Extension", RFC 5232,
           January 2008.

[RFC5233]  K. Murchison, "Sieve Email Filtering -- Subaddress Extension", 
           RFC 5233, January 2008.

[RFC5235]  C. Daboo, "SIEVE Email Filtering: Spamtest and Virustest Extensions",
           RFC 5235, January 2008.
           
[RFC-ietf-sieve-notify-12.txt]
           A. Melnikov, Ed., B. Leiba, Ed., W. Segmuller, T. Martin, "SIEVE 
           Email Filtering: Extension for Notifications", RFC XXXX, Month Year.

(created 2000-11)

[]
