Hello, I'm using dovecot 2.2.10 and roundcube (with managesieve enabled). Sieve filtering works well, as long the rule is written into ~/.dovecot.sieve (which is a link to ~/sieve/managesieve.sieve) When adding a new filter set (in roundcube) the script is written to ~/sieve/newfilterset.sieve. This script will not be executed. How can I solve this? I set sieve_dir = ~/sieve This should work, except I misunderstand the doc. # ls -l ./sieve total 6 -rw------- 1 vmail mail 105 Feb 5 09:24 managesieve.sieve -rw------- 1 vmail mail 113 Feb 4 16:30 test.sieve drwx------ 2 vmail mail 512 Feb 5 09:24 tmp Regards, Thomas.
In the meantime I found, that the .dovecot.svbin is not generated, when I add or modify a filter. I can only force building of .dovecot.svbin by deleting of .dovecot.svbin. Is that a bug? Regards, Thomas.> Hello, > I'm using dovecot 2.2.10 and roundcube (with managesieve enabled). > Sieve filtering works well, as long the rule is written > into ~/.dovecot.sieve (which is a link to ~/sieve/managesieve.sieve) > When adding a new filter set (in roundcube) the script is > written to ~/sieve/newfilterset.sieve. This script will not be > executed. How can I solve this? > > I set > sieve_dir = ~/sieve > This should work, except I misunderstand the doc. > > # ls -l ./sieve > total 6 > -rw------- 1 vmail mail 105 Feb 5 09:24 managesieve.sieve > -rw------- 1 vmail mail 113 Feb 4 16:30 test.sieve > drwx------ 2 vmail mail 512 Feb 5 09:24 tmp > > Regards, > Thomas. > >
On 2/5/2014 9:59 AM, Thomas Krause wrote:> Hello, > I'm using dovecot 2.2.10 and roundcube (with managesieve enabled). > Sieve filtering works well, as long the rule is written > into ~/.dovecot.sieve (which is a link to ~/sieve/managesieve.sieve) > When adding a new filter set (in roundcube) the script is > written to ~/sieve/newfilterset.sieve. This script will not be > executed. How can I solve this? > > I set > sieve_dir = ~/sieve > This should work, except I misunderstand the doc.I see no obvious problems in your configuration. Do the logs say anything interesting (set mail_debug=yes)? Your symptoms suggest that Roundcube is not activating the uploaded script for some reason. That is when the symbolic link is updated. You could sniff the protocol exchange between Roundcube and Dovecot on port 4190 (without TLS obviously). Roundcube should issue the SETACTIVE command. Regards, Stephan.
Reasonably Related Threads
- Exposing global (default) sieve script through Managesieve
- sieve problem email silently discard
- dovecot-pigeonhole problems after upgrade to v2.3.0
- Global sieve doesn't run and I don't know why
- Dovecot dsync not replicating ".dovecot.sieve -> .sieve/managesieve.sieve" / setactive