Re: [Dovecot] Using global und per-user sieve scripts at the same time
Hi list, I'm still trying to get global and per-user sieve scripts to work. With no success yet. This is what I've got for the moment: dovecot.conf --- protocol lda { postmaster_address = [EMAIL PROTECTED] fsync_disable = no mail_plugins = cmusieve quota mail_plugin_dir = /usr/local/lib/dovecot/lda sieve_global_path = /usr/local/etc/sieve/spam sendmail_path = /usr/sbin/sendmail auth_socket_path = /var/run/dovecot/auth-master } plugin { sieve = /usr/mail/%Lu/sieve } --- /usr/local/etc/sieve/spam: --- require fileinto; if header :contains [Subject] [***Spam***] { fileinto Spam; stop; } --- If I enable sieve_global_path and sieve in plugin section only the user sieve script is working. If I enable only the sieve_global_path setting this one is working. Both at the same time won't work. Dovecot version is 1.0.7. Is there really a way to get this to work under Dovecot 1.0.7? Matthias
[Dovecot] Using global und per-user sieve scripts at the same time
Hi list, I'm trying to get a global sieve mailfilter with per-user sieve scripts to work. At the lda-section in the dovecot.conf file I have: global_script_path = /usr/local/etc/sieve/spam /usr/local/etc/sieve/spam: require fileinto; if header :contains [Subject] [***Spam***] { fileinto Spam; stop; } which will work fine delivering Spam Mails in a Spam dir for every user. If a user creates his own .dovecot.sieve file the global script will not work anymore. How can I enable global and local per-user sieve scripts at once? Is this possible? Do you know any workaround so all users will have the same (Spam-)sieve filters beside there own (global templates or so)? Matthias
Re: [Dovecot] Using global und per-user sieve scripts at the same time
Nikolay Shopik schrieb: You forgot to insert this one, where users sieve files stored. plugin { sieve = /var/mail/store/%u/sieve } Thanks for your answer Nikolay. But I think this won't do the trick. This setting will override the global setting as well. At the moment I'm using the default location for the sieve scripts in the user's home dir. Matthias
Re: [Dovecot] Using global und per-user sieve scripts at the same time
Nikolay Shopik schrieb: On 26.11.2007 18:57, Matthias Kellermann wrote: Nikolay Shopik schrieb: You forgot to insert this one, where users sieve files stored. plugin { sieve = /var/mail/store/%u/sieve } Thanks for your answer Nikolay. But I think this won't do the trick. This setting will override the global setting as well. At the moment I'm using the default location for the sieve scripts in the user's home dir. Matthias Very strange but in my case global rules still works even if user have their own sieve rules. So spam still moved to junk folder ;). Hmm, so you have an entry like this in your LDA section: global_script_path = /usr/local/etc/sieve/spam Where spam is the file with the global sieve rules. Then you have the following entry in the plugin section: sieve = /var/mail/store/%u/sieve Where sieve ist the per-user sieve file, right? Is /var/mail/store the same location where you save the user's email? Matthias
[Dovecot] sieve parse error
Hello everyone, I'm using Dovecot (v1.0.beta3-3ubuntu5.4 under Ubuntu) with postfix and LDA with virtual users. Everything is working fine. To filter mails I use the Dovecot Sieve feature. But I get some strange error for one simple Sieve script: require fileinto; if header :contains [to, Cc, Bcc] [[EMAIL PROTECTED]] { fileinto Mailinglists.FreeWRT; stop; } elseif header :contains [to, Cc, Bcc] [[EMAIL PROTECTED]] { fileinto Mailinglists.getmail; stop; } This is the error I get in mail.log: May 6 15:47:08 gehirnschnecke deliver: sieve parse error for [EMAIL PROTECTED]: line 8: syntax error, unexpected IF, expecting '{' After studying sieve.info my sieve script should be correct. What could be wrong here? Thanks best regards Matthias
Re: [Dovecot] sieve parse error
Mark E. Mallett schrieb: On Sun, May 06, 2007 at 03:52:14PM +0200, Matthias Kellermann wrote: Hello everyone, } elseif header :contains [to, Cc, Bcc] sieve has elsif .. not elseif Dunno if that is the problem, but: May 6 15:47:08 gehirnschnecke deliver: sieve parse error for [EMAIL PROTECTED]: line 8: syntax error, unexpected IF, expecting '{' it seems to be the right line number. mm That was the problem. Just one letter - mea culpa .. Thanks Matthias