Your IP : 216.73.216.155


Current Path : /usr/share/doc/dovecot-common/
Upload File :
Current File : //usr/share/doc/dovecot-common/managesieve.README

ManageSieve implementation for Dovecot v1.2

For the most up-to-date information you are referred to the Dovecot wiki:

http://wiki.dovecot.org/ManageSieve

Introduction
------------

By writing Sieve scripts, users can customize how messages are delivered, e.g.
whether they are forwarded or stored in special folders. The Sieve language is
meant to be simple, extensible and system independent. And, unlike most other
mail filtering script languages, it does not allow users to execute arbitrary
programs. This is particularly useful to prevent virtual users from having
full access to the mail store. The intention of the language is to make it
impossible for users to do anything more complex (and dangerous) than write
simple mail filters.

The 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 (although still a draft), 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.

For Dovecot, ManageSieve support is provided in this separate package. This
implementation is part of the Pigeonhole project
(http://pigeonhole.dovecot.org).

Compiling and Configuring
-------------------------

Refer to INSTALL file.

Known Issues
------------

* Although this ManageSieve server should comply with the draft specification of
  the ManageSieve protocol, quite a few clients don't. This is particularly true
  for the TLS support. However, now that Cyrus' Timsieved has changed its
  behavior towards protocol compliance, all those clients will follow
  eventually.

  Clients known to have TLS issues:
	- Thunderbird Sieve add-on: fixed as per version 0.1.5
	- AvelSieve: patch on the wiki:	http://wiki.dovecot.org/ManageSieve
	- KMail + kio_sieve: TLS broken for old versions. This issue is fixed at
	  least in kmail 1.9.9 / kde 3.5.9.

  Unfortunately, there is no reliable way to provide a workaround for this
  problem. We will have to wait for the authors of these clients to make the
  proper adjustments.

* Other client issues:

	- SmartSieve, WebSieve:
	  These clients are specifically written for Cyrus timsieved and fail on
	  multiple stages of the protocol when connected to Dovecot ManageSieve.

* The ANONYMOUS authentication mechanism is currently not supported and
  explicitly denied.

Contact Info
------------

Stephan Bosch <stephan at rename-it dot nl>
IRC: Freenode, #dovecot, S[r]us
Web: http://pigeonhole.dovecot.org

Please use the Dovecot mailing list <dovecot at dovecot.org> for questions about
this package. You can post to the list without subscribing, the mail then waits
in a moderator queue for a while. See http://dovecot.org/mailinglists.html