Sieve Extensions per [RFC3028] Capability names may be registered on a first-come, first-served basis. Extensions designed for interoperable use SHOULD be defined as standards track or IESG approved experimental RFCs. The following template should be used when applying for a new extension: To: iana@iana.org Subject: Registration of new Sieve extension Capability name: Capability keyword: Capability arguments: Standards Track/IESG-approved experimental RFC number: Person and email address to contact for further information: Below is the list of Sieve Extensions. Capability name: fileinto Capability keyword: fileinto Capability arguments: fileinto Standards Track/IESG-approved experimental RFC number: RFC 3028 (Sieve base spec) Person and email address to contact for further information: Tim Showalter tjs@mirapoint.com Capability name: reject Capability keyword: reject Capability arguments: reject Standards Track/IESG-approved experimental RFC number: RFC 3028 (Sieve base spec) Person and email address to contact for further information: Tim Showalter tjs@mirapoint.com Capability name: envelope Capability keyword: envelope Capability arguments: envelope [COMPARATOR] [ADDRESS-PART] [MATCH-TYPE] Standards Track/IESG-approved experimental RFC number: RFC 3028 (Sieve base spec) Person and email address to contact for further information: Tim Showalter tjs@mirapoint.com Capability name: comparator-* Capability keyword: comparator-* (anything starting with "comparator-") Capability arguments: (none) Standards Track/IESG-approved experimental RFC number: RFC 3028, Sieve, by reference of RFC 2244, Application Configuration Access Protocol Person and email address to contact for further information: Tim Showalter tjs@mirapoint.com REFERENCES --------- [RFC2244] C. Newman and J. G. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997. [RFC3028] T. Showalter, "Sieve: A Mail Filtering Language", RFC 3028, January 2001. (created 11/00) []