Avelsieve Logo

Supported Servers

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 Backend

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:

It is also possible to connect to many more servers, by using a standalone ManageSieve daemon.

File Backend

For simple storage of scripts in the filesystem.

Server implementations that can be used with this backend:

LDAP 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.

Implemented Capabilities

Capability Name:Defined in Document:Notes:Since Avelsieve Version:
fileintoRFC 5228: Sieve Base spec
envelopeRFC 5228: Sieve Base spec
imapflags draft-melnikov-sieve-imapflags-03Just a checkbox "mark as deleted", no real implementation of IMAP Flags
imap4flagsRFC 5232: IMAP4Flags Sieve ExtensionSee also: RFC 3501 Section
rejectSieve Base spec (RFC 3028)Implementation based on RFC 3028, but is compatible with newer RFC 5429: Reject and Extended Reject Extensions
bodyRFC 5173: Body Extension
vacationRFC 5230: Vacation Extension
relationalRFC 5231: Relational ExtensionUI exists for Match Type "VALUE"; see also #70
date RFC 5260: Date and Index Extensions1.9.9
index RFC 5260: Date and Index Extensions1.9.9