Thanks for taking the time to respond Patrick.
Previously (in v1.0) we did not need the plugin section: sieve = mailfilter.sieve
Is this now required even when just wanting to use a global sieve script? We have ~100 users so manually adding a mailfilter.sieve file to each users directory will be very time consuming. Are we able to input the full path name to our global script instead, i.e. /etc/dovecot-sieve/global?
I tried using sieve_global_path = /etc/dovecot-sieve/global in the 'lda protocol' section but, as stated, the script seems to be ignored. The local delivery agent is working but everything gets delivered to the users inbox instead of being filtered.
Gavin
On Tue, 2008-07-08 at 10:36 +0800, Patrick Nagel wrote:
Hi Gavin,
On Tuesday 08 July 2008, you wrote:
We have been using dovecot v1:1.0.15-1_72 and dovecot-sieve v1.0.3-7 very successfully for many months but I've been unable to get dovecot-sieve to work with the latest 1.1 release. The new release seems to completely ignore our global sieve script no matter what we do.
Is anyone else using the atrpms-stable rpms packages and able to get dovecot-sieve to work correctly?
Any help would be greatly appreciated.
Gavin
yes, we're using the following
dovecot Version: 1.1.1 Release: 2_76.el5
and
dovecot-sieve Version: 1.1.5 Release: 8.el5
from atrpms, and sieve works as it did before.
Sieve relevant configuration looks as follows:
in section 'protocol lda': mail_plugins = cmusieve sieve_global_dir = /storage/sieve
in section 'plugin': sieve = mailfilter.sieve
In each user's home directory who should have sieve filtering activated, we place a mailfilter.sieve and in there we include one or more global and/or personal sieve scripts.
For example:
- /home/john.doe/mailfilter.sieve: require "include"; include :personal "vacation.sieve"; include :global "spam.sieve";
spam.sieve resides in the /storage/sieve directory.
Hope this helps. Patrick.