Avelsieve can hook to an email server (either IMAP mail store or MTA) to manage Sieve scipts, in a variety of ways.
Three ways (backends) are currently offered:
ManageSieve is the transport protocol for uploading, editing, deleting and verifying Sieve scripts on a mail server. A daemon listens to port 2000, where clients such as avelsieve can connect and manage the scripts. The Managesieve protocol is described in Internet draft "A Protocol for Remotely Managing Sieve Scripts".
The use of Managesieve is recommended, since this is the only way that Avelsieve can automatically learn about the capabilities of the server-installed Sieve filtering engine.
Server implementations that make use of Managesieve:
For simple storage of scripts in the filesystem.
Server implementations that can be used with this backend:
This is a specialized, contributed backend for users of Sun Java System Messaging Server.
Note: More server implementations can be found at http://sieve.info/servers . Avelsieve should work with any of them.
|Capability Name:||Defined in Document:||Notes:||Since Avelsieve Version:|
|fileinto||RFC 5228: Sieve Base spec|
|envelope||RFC 5228: Sieve Base spec|
|imapflags||draft-melnikov-sieve-imapflags-03||Just a checkbox "mark as deleted", no real implementation of IMAP Flags|
|imap4flags||RFC 5232: IMAP4Flags Sieve Extension||See also: RFC 3501 Section 2.3.2||1.9.9|
|reject||Sieve Base spec (RFC 3028)||Implementation based on RFC 3028, but is compatible with newer RFC 5429: Reject and Extended Reject Extensions|
|body||RFC 5173: Body Extension|
|vacation||RFC 5230: Vacation Extension|
|relational||RFC 5231: Relational Extension||UI exists for Match Type "VALUE"; see also #70|
|date||RFC 5260: Date and Index Extensions||1.9.9|
|index||RFC 5260: Date and Index Extensions||1.9.9|