search for: manually_compiling_sieve_scripts

I recently updated dovecot and my sieve filters stopped working. Checking the logs I see: Dec 9 00:09:59 mailhost dovecot: lda(gessel at domain.com): Error: sieve: binary save: failed to create temporary file: open(/usr/local/etc/dovecot/sieve/10-move-spam.svbin.mailhost.domain.com.114.) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +w perm: /usr/local/etc/dovecot/sieve,

On 10/21/20 2:12 PM, @lbutlr wrote: > Do I HAVE to have a default.sieve, that's the only thing that I can think the has changed in that folder. RE: compile, fyi note @ https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Executing_Multiple_Scripts_Sequentially the conditions under which you need to manually pre-compile the scripts specified by sieve_before and sieve_after > HAVE to have In my config, it's def'd, but I don't explicitly _have...

...ssion to save global Sieve script binaries; global Sieve scripts like `/usr/local/etc/dovecot/sieve/10-move-spam.sieve' need to be pre-compiled using the sievec tool > > As mentioned in the error message from your logs and in the wiki <http://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts>: To mitigate this problem, the administrator must manually pre-compile global scripts using the sievec command line tool. Regards, Pascal -- The trapper recommends today: defaced.1434318 at localdomain.org

...global Sieve script binaries; global Sieve scripts like `/usr/local/etc/dovecot/sieve/10-move-spam.sieve' need to be pre-compiled using the sievec tool >> >> As mentioned in the error message from your logs and in the wiki >> <http://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts>: >> >> To mitigate this problem, the administrator must manually >> pre-compile global scripts using the sievec command line tool. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVIftyXz1H7kL/d9rAQLoLwf/bA1r7DR5AVxBUYT2R54eM8yA...

...t Dev <pgnet.dev at gmail.com> wrote: > > On 10/21/20 2:12 PM, @lbutlr wrote: >> Do I HAVE to have a default.sieve, that's the only thing that I can think the has changed in that folder. > RE: compile, fyi note @ > > https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts > https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Executing_Multiple_Scripts_Sequentially > > the conditions under which you need to manually pre-compile the scripts specified by sieve_before and sieve_after As I said, the scripts compile just fine. 8 -rw-r--r-- 1 root whee...

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 script binaries; global Sieve scripts like `/usr/local/etc/dovecot/sieve/10-move-spam.sieve' need to be pre-compiled using the sievec tool >> >> > > As mentioned in the error message from your logs and in the wiki > <http://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts>: > > To mitigate this problem, the administrator must manually > pre-compile global scripts using the sievec command line tool. > > > Regards, > Pascal >