[Dovecot] Sieve problem with 1.1.2
Hello,
I am new here, so excuse me if i am asking something already asked. I am
using dovecot 1.1.2 along with postfix 2.6 and a pgsql backend. So far
everything is great, until i wanted to try out the sieve implementation.
I am using dovecot for deliver and i have set
global_script_path = /home/vmail/globalsieverc
The script IS working until a given user defines his own sieve script (
for example ) :
require [fileinto];
# Move mail from my gmail account to gmail folder
if header :contains From [[EMAIL PROTECTED]] {
fileinto gmail;
}
This ( or any other script for all i know ) breaks up the global one,
and it stops working. The global script looks like this :
require [fileinto];
# Move spam to spam folder
if header :contains X-Spam-Flag [YES] {
fileinto spam;
stop;
}
Am i missing something, or this is the desired behaviour ?
Re: [Dovecot] Sieve problem with 1.1.2
[EMAIL PROTECTED] escreveu:
Hello,
I am new here, so excuse me if i am asking something already asked. I am
using dovecot 1.1.2 along with postfix 2.6 and a pgsql backend. So far
everything is great, until i wanted to try out the sieve implementation.
I am using dovecot for deliver and i have set
global_script_path = /home/vmail/globalsieverc
The script IS working until a given user defines his own sieve script (
for example ) :
This ( or any other script for all i know ) breaks up the global one,
and it stops working. The global script looks like this :
Am i missing something, or this is the desired behaviour ?
It is the documented behavior. (If this is desirable or not, that is
another question.) From http://wiki.dovecot.org/LDA/Sieve :
protocol lda {
..
# If there is no user-specific Sieve-script, global Sieve script is
# executed if set. (v1.0.1 and older used global_script_path)
#sieve_global_path =
...
--
Eduardo M Kalinowski
[EMAIL PROTECTED]
Re: [Dovecot] Sieve problem with 1.1.2
Any suggestions on how to disable this ? I'd like to be able to filter
all spam by default with sieve, and still allow users to have their own
rules.
Eduardo M KALINOWSKI wrote:
[EMAIL PROTECTED] escreveu:
Hello,
I am new here, so excuse me if i am asking something already asked. I am
using dovecot 1.1.2 along with postfix 2.6 and a pgsql backend. So far
everything is great, until i wanted to try out the sieve implementation.
I am using dovecot for deliver and i have set
global_script_path = /home/vmail/globalsieverc
The script IS working until a given user defines his own sieve script (
for example ) :
This ( or any other script for all i know ) breaks up the global one,
and it stops working. The global script looks like this :
Am i missing something, or this is the desired behaviour ?
It is the documented behavior. (If this is desirable or not, that is
another question.) From http://wiki.dovecot.org/LDA/Sieve :
protocol lda {
..
# If there is no user-specific Sieve-script, global Sieve script is
# executed if set. (v1.0.1 and older used global_script_path)
#sieve_global_path =
...
Re: [Dovecot] Sieve problem with 1.1.2
On Thu, 04 Sep 2008 16:07:35 +0300, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Any suggestions on how to disable this ? I'd like to be able to filter all spam by default with sieve, and still allow users to have their own rules. We autocreate a 'mailfilter.sieve' in each new user's homedir, in which a global 'spam.sieve' is being included. The user can then add rules as desired after that inclusion. Patrick. -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone:+86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key: E883A005 https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005
