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:

• ​Cyrus IMAP (running timsieved)
• ​Isode M-Box
• ​DBMail
• ​Dovecot, either via a ​ManageSieve patch or through a standalone ManageSieve server.
• Apple MacOS X Server Mail Services, ​see this forum thread for a rough HOWTO, probably substituting the stable version for a more recent one.

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:

• ​Exim MTA

LDAP Backend

This is a specialized, contributed backend for users of Sun Java System Messaging Server.

• ​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