This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 40 and 42 (spanning 2 versions)
Revision 40 as of 2010-08-12 18:23:16
Size: 1594
Editor: TimoSirainen
Comment:
Revision 42 as of 2010-09-07 12:36:41
Size: 1482
Editor: TimoSirainen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from ManageSieve
Line 8: Line 9:
Dovecot's ManageSieve support is distributed in a separate package. Currently it also requires patching Dovecot sources, but this won't be necessary anymore in Dovecot v2.0. Dovecot's ManageSieve implementation is part of the [[http://pigeonhole.dovecot.org/|Pigeonhole project]]. There exists also an alternative [[http://gitorious.org/pysieved/pages/Home|pysieved]] ManageSieve server that works with Dovecot. Dovecot's ManageSieve support is distributed in a separate package from the [[http://pigeonhole.dovecot.org/|Pigeonhole project]]. There exists also an alternative [[http://gitorious.org/pysieved/pages/Home|pysieved]] ManageSieve server that works with Dovecot.

Dovecot ManageSieve Server

ManageSieve service is used to manage a user's Sieve script collection. It has the following advantages over doing it directly via filesystem:

  • No need to let users log in via FTP/SFTP/etc, which could be difficult especially with virtual users.
  • ManageSieve is a standard protocol, so users can manage their scripts using (hopefully) user-friendly ManageSieve clients. Many webmails already include a ManageSieve client.

  • Scripts are compiled before they are installed, which guarantees that the uploaded script is valid. This prevents a user from inadvertently installing a broken Sieve script.

Dovecot's ManageSieve support is distributed in a separate package from the Pigeonhole project. There exists also an alternative pysieved ManageSieve server that works with Dovecot.

Contact Info

None: Pigeonhole/ManageSieve (last edited 2019-09-12 08:43:59 by MichaelSlusarz)