Thx, I did try this right away: Compiled my script with sievec and: autocreate_sieve_script_compiled: /etc/cyrus/spam.bc autocreate_sieve_script: /etc/cyrus/spam.sieveTried that without a autocreate_sieve_script option as well and neither one does create a sieve script for a new mailbox.
A mailbox 'user.$uid.#sieve' is created, adding a script with sieve-connect also works.. so it's not sieve in general that has a problem.
On 4/4/24 12:24, Robert Stepanek via Info wrote:
It shows there is both a typo in the description of the autocreate_sieve_script_compile option and itsdocumentation hasn't been updated either.The typo is "autocreate_sieve_compiledscript" where it means "autocreate_sieve_compiled_script".And: the "autocreate_sieve_compiled_script" option has been deprecated in favor of "autocreate_sieve_script_compiled".https://github.com/cyrusimap/cyrus-imapd/blob/master/lib/imapoptions#L385 <https://github.com/cyrusimap/cyrus-imapd/blob/master/lib/imapoptions#L385> Using the autocreate_sieve_script_compiled option should work.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/T433432d9dd58c6b3-M5823c59e214d9b0be84c9d2a Delivery options: https://cyrus.topicbox.com/groups/info/subscription
