Sieve Extensions per [RFCXXXX]

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 <folder: string>
Standards Track/IESG-approved experimental RFC number:
	RFC XXXX (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 <reason: string>
Standards Track/IESG-approved experimental RFC number:
	RFC XXXX (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]
<envelope-part: string-list> <key-list:string-list>
Standards Track/IESG-approved experimental RFC number:
	RFC XXXX (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 XXXX, 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
--------- 

[RFCXXXX]

(created 11/00)

[]