This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 41 and 44 (spanning 3 versions)
Revision 41 as of 2010-08-13 06:57:05
Size: 1444
Comment: Removed mention of Dovecot patching.
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 1: Line 1:
## page was renamed from ManageSieve
Line 11: Line 12:
 * [[ManageSieve/Configuration|Configuration]]
 * [[ManageSieve/Troubleshooting|Troubleshooting]]
 * [[ManageSieve/Clients|Client Issues]]

== Contact Info ==
 * Author: Stephan Bosch,
 * IRC: [[|Freenode]], #dovecot, S[r]us
 * Please use the Dovecot [[|mailing list]] for questions about the ManageSieve service. You don't have to subscribe to it.
 * [[Pigeonhole/ManageSieve/Configuration|Configuration]]
 * [[Pigeonhole/ManageSieve/Troubleshooting|Troubleshooting]]
 * [[Pigeonhole/ManageSieve/Clients|Client Issues]]

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)