Hi,

I think you must compile them manually first:
# The default Sieve script when the user has none. This is the location of a
# global sieve script file, which gets executed ONLY if user's personal
Sieve
# script doesn't exist. Be sure to pre-compile this script manually using
the
# sievec command line tool if the binary is not stored in a global location.
# --> See sieve_before for executing scripts before the user's personal
#     script.

Only the user's personal Sieve script works without pre-compiling.

Regards,
Anh Do

On Sun, 21 Apr 2024 at 08:25, Joan Moreau via dovecot <dovecot@dovecot.org>
wrote:

> Hi
>
> I have
>
>          sieve = /mails/%d/%n/sieve/roundcube.sieve
>          sieve_after = /mails/sieve/after.sieve
>          sieve_before = /mails/sieve/before.sieve
>          sieve_dir = /mails/%d/%n/sieve/
>          sieve_global_dir = /mails/sieve/
>
> But sieve scripts are not compiled and not executed
>
> It was working until I removed the setting "sieve_global_path"
>
> Something I dont understand ?
>
> Thank you
> _______________________________________________
> dovecot mailing list -- dovecot@dovecot.org
> To unsubscribe send an email to dovecot-le...@dovecot.org
>
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Reply via email to