|
Size: 1594
Comment:
|
Size: 1482
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
Author: Stephan Bosch, stephan@rename-it.nl
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.