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@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