search for: managesieve_script_name

On 10/21/20 1:10 PM, @lbutlr wrote: > I have trace logs enabled for user scripts, but I think only error get logged for upper level, and only along the lines of "could not compile <name of sieve>". verify that you can compile the scripts manually, even as root then double-check your perms on your sieve/ dir, making sure that the write perms are correct for your dovecot

...= sieve_imapsieve sieve_extprograms } & my Roundcube config (I use RC for user-friendly Sieve UI; so far, seems best of the bunch) includes $config['managesieve_raw_editor'] = true; $config['managesieve_default'] = '/data/sieve/default.sieve'; $config['managesieve_script_name'] = 'managesieve'; and with that^, I do not have a /data/sieve/default.sieve instead, I have, for each user at example.com tree /data/sieve/user at example.com/ /data/sieve/user at example.com/ ??? active.sieve -> managesieve.sieve ??? active.svbin ??? managesieve.siev...

...$config['managesieve_conn_options'] = null; // default contents of filters script (eg. default spam filter) $config['managesieve_default'] = '/var/www/roundcube/config/global.sieve'; // The name of the script which will be used when there's no user script $config['managesieve_script_name'] = 'managesieve'; // Sieve RFC says that we should use UTF-8 endcoding for mailbox names, // but some implementations does not covert UTF-8 to modified UTF-7. // Defaults to UTF7-IMAP $config['managesieve_mbox_encoding'] = 'UTF-8'; // I need this because my dovecot (w...