Tolbert, Joshua P
2016-Mar-17 19:04 UTC
Trouble getting vnd.dovecot.filter and filter visible/usable...
Hello, I?m trying to make vnd.dovecot.filter available both globally and for users through sieve, but I haven?t had much luck getting things to work right. Sieve scripts won?t validate and vnd.dovecot.filter never shows up in the managesieve capability list. I?ve spent lots of time looking for where problems could be, but I?m out of ideas?So I?m asking you guys. In the protocol lmtp section, I?m defining mail_plugins = $mail_plugins sieve, however I?ve tried it without $mail_plugins too?No luck that way either. Any help/advice would be much appreciated. Thanks! Cheers, Josh -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: doveconf.txt URL: <http://dovecot.org/pipermail/dovecot/attachments/20160317/8947236f/attachment.txt>
Stephan Bosch
2016-Mar-17 20:59 UTC
Trouble getting vnd.dovecot.filter and filter visible/usable...
Op 3/17/2016 om 8:04 PM schreef Tolbert, Joshua P:> Hello, > > I?m trying to make vnd.dovecot.filter available both globally and for users through sieve, but I haven?t had much luck getting things to work right. Sieve scripts won?t validate and vnd.dovecot.filter never shows up in the managesieve capability list. I?ve spent lots of time looking for where problems could be, but I?m out of ideas?So I?m asking you guys. > > In the protocol lmtp section, I?m defining mail_plugins = $mail_plugins sieve, however I?ve tried it without $mail_plugins too?No luck that way either. > > Any help/advice would be much appreciated. Thanks!Then don't put it in sieve_global_extensions. That setting overrides the sieve_extensions setting and restricts all listed extensions to global context only; this way these extensions are only available from sieve_before, sieve_after, and sieve_global Sieve scripts. User scripts will not accept it in that case. Regards, Stephan
Tolbert, Joshua P
2016-Mar-17 21:04 UTC
Trouble getting vnd.dovecot.filter and filter visible/usable...
Hi Stephan, I?ll be damned, that was it. I figured it was something simple I was overlooking. Reading the description of sieve_global_extensions again, it makes sense now. Thanks again. Cheers, Josh On 3/17/16, 3:59 PM, "Stephan Bosch" <stephan at rename-it.nl> wrote:>Op 3/17/2016 om 8:04 PM schreef Tolbert, Joshua P: >> Hello, >> >> I?m trying to make vnd.dovecot.filter available both globally and for >>users through sieve, but I haven?t had much luck getting things to work >>right. Sieve scripts won?t validate and vnd.dovecot.filter never shows >>up in the managesieve capability list. I?ve spent lots of time looking >>for where problems could be, but I?m out of ideas?So I?m asking you guys. >> >> In the protocol lmtp section, I?m defining mail_plugins = $mail_plugins >>sieve, however I?ve tried it without $mail_plugins too?No luck that way >>either. >> >> Any help/advice would be much appreciated. Thanks! > >Then don't put it in sieve_global_extensions. That setting overrides the >sieve_extensions setting and restricts all listed extensions to global >context only; this way these extensions are only available from >sieve_before, sieve_after, and sieve_global Sieve scripts. User scripts >will not accept it in that case. > >Regards, > >Stephan