This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 43 and 44
Revision 43 as of 2010-09-07 13:09:55
Size: 1515
Comment: Updated references after Pigeonhole move.
Revision 44 as of 2010-09-07 14:16:30
Size: 1219
Comment: Moved contact information to main page.
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:

== Contact Info ==
 * Author: Stephan Bosch, stephan@rename-it.nl
 * IRC: [[http://freenode.net/|Freenode]], #dovecot, S[r]us
 * Please use the Dovecot [[http://www.dovecot.org/mailinglists.html|mailing list]] for questions about the ManageSieve service. You don't have to subscribe to it.

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.

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