sieve_after seems to ignored ?
sieve and managesieve are both working fine, have been for years. Now I want to add a sieve_after script:
/etc/dovecot/conf.d/90-sieve.conf :
plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_before = sieve_after = ~/sieve/personal.sieve sieve_subaddress_sep = + }
I have compiled ~/sieve/personal.sieve to ~/sieve/personal.svbin, but it doesn't seem to be read. Any hints?
thanks Per Jessen
-- Per Jessen, Zürich (17.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
Hi Per,
On 25.08.2015 11:40, Per Jessen wrote:
sieve and managesieve are both working fine, have been for years. Now I want to add a sieve_after script:
/etc/dovecot/conf.d/90-sieve.conf :
plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_before = sieve_after = ~/sieve/personal.sieve sieve_subaddress_sep = + }
I have compiled ~/sieve/personal.sieve to ~/sieve/personal.svbin, but it doesn't seem to be read. Any hints?
sieve_after is only executed if no rule matched in other sieve-scripts before.
Michael
Michael Kliewe wrote:
Hi Per,
On 25.08.2015 11:40, Per Jessen wrote:
sieve and managesieve are both working fine, have been for years. Now I want to add a sieve_after script:
/etc/dovecot/conf.d/90-sieve.conf :
plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_before = sieve_after = ~/sieve/personal.sieve sieve_subaddress_sep = + }
I have compiled ~/sieve/personal.sieve to ~/sieve/personal.svbin, but it doesn't seem to be read. Any hints?
sieve_after is only executed if no rule matched in other sieve-scripts before.
Michael
Thanks Michael - in this case I have no other scripts, not even a ~/.dovecot.sieve. Also, I thought sieve_after was run as long as the previous script doesn't say "keep"?
http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#multiscript
-- Per Jessen, Zürich (20.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
Per Jessen wrote:
Michael Kliewe wrote:
Hi Per,
On 25.08.2015 11:40, Per Jessen wrote:
sieve and managesieve are both working fine, have been for years. Now I want to add a sieve_after script:
/etc/dovecot/conf.d/90-sieve.conf :
plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_before = sieve_after = ~/sieve/personal.sieve sieve_subaddress_sep = + }
I have compiled ~/sieve/personal.sieve to ~/sieve/personal.svbin, but it doesn't seem to be read. Any hints?
sieve_after is only executed if no rule matched in other sieve-scripts before.
Michael
Thanks Michael - in this case I have no other scripts, not even a ~/.dovecot.sieve. Also, I thought sieve_after was run as long as the previous script doesn't say "keep"?
I have also tried it for a user that does have a ~/.dovecot.sieve - no rules are hit, but sieve_after still isn't executed.
-- Per Jessen, Zürich (20.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
Per Jessen wrote:
Per Jessen wrote:
Michael Kliewe wrote:
Hi Per,
On 25.08.2015 11:40, Per Jessen wrote:
sieve and managesieve are both working fine, have been for years. Now I want to add a sieve_after script:
/etc/dovecot/conf.d/90-sieve.conf :
plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_before = sieve_after = ~/sieve/personal.sieve sieve_subaddress_sep = + }
I have compiled ~/sieve/personal.sieve to ~/sieve/personal.svbin, but it doesn't seem to be read. Any hints?
sieve_after is only executed if no rule matched in other sieve-scripts before.
Michael
Thanks Michael - in this case I have no other scripts, not even a ~/.dovecot.sieve. Also, I thought sieve_after was run as long as the previous script doesn't say "keep"?
I have also tried it for a user that does have a ~/.dovecot.sieve - no rules are hit, but sieve_after still isn't executed.
As a test, I tried with an empty ~/.dovecot.sieve (contents moved to ~/sieve/personal.sieve), the sieve_after script still isn't picked up. Any suggestions on how to debug this?
Thanks Per
-- Per Jessen, Zürich (20.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.
Per Jessen skrev den 2015-08-25 15:49:
plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_before = sieve_after = ~/sieve/personal.sieve sieve_subaddress_sep = + }
sieve is the personal, and sieve_after is the global, you have swapped names ?
all that asside does both svbin exists ?, if not make sure dovecot can read them, run sievec on the source file
imho global sieve files must not be in $HOME
Benny Pedersen wrote:
Per Jessen skrev den 2015-08-25 15:49:
plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_before = sieve_after = ~/sieve/personal.sieve sieve_subaddress_sep = + }
sieve is the personal, and sieve_after is the global, you have swapped names ?
all that asside does both svbin exists ?, if not make sure dovecot can read them, run sievec on the source file
Yes, it was compiled.
However, I have found the problem - it was in fact a missing '}' in another config file. :-(
imho global sieve files must not be in $HOME
I agree - I'm not really using a global, just a personal "after" script. I'm setting up SOGo with filters, but some advanced users have long sieve scripts that can't just be converted. So I'm moving their existing sieve scripts so ~/sieve/personal.sieve and I'm letting SOGo manage ~/.dovecot.sieve.
-- Per Jessen, Zürich (20.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
participants (3)
-
Benny Pedersen
-
Michael Kliewe
-
Per Jessen