2.4.0: managesieve: sieve_script_path setting variables: Unknown variable 'user'
Hi,
I have the following (manage)sieve-related parts in my 2.4.0 config:
within the namespace inbox: mailbox Junk { auto = subscribe autoexpunge = 14d sieve_script junk { type = before cause = copy driver = file path = /data/mail/sieve/report-spam.sieve } special_use { "\Junk" = yes }
service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } sieve_script personal { active_path = /data/mail/%{user}/dovecot.sieve driver = file path = /data/mail/%{user}/sieve }
Accessing via managesieve fails:
Error: sieve: file storage: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user'
But the sieve rules in general work.
Regards Bjoern
On 18. Feb 2025, at 14.32, Bjoern Franke via dovecot <dovecot@dovecot.org> wrote:
sieve_script personal { active_path = /data/mail/%{user}/dovecot.sieve driver = file path = /data/mail/%{user}/sieve }
Accessing via managesieve fails:
Error: sieve: file storage: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user'
Looks like managesieve has the same bug as doveadm backup. You could use ~/dovecot.sieve and ~/sieve as the paths if the home directory is set up right. Will be fixed in v2.4.1.
Hi,
Error: sieve: file storage: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user'
Looks like managesieve has the same bug as doveadm backup. You could use ~/dovecot.sieve and ~/sieve as the paths if the home directory is set up right. Will be fixed in v2.4.1.
Thanks for the hint, it worked with ~.
Regards Bjoern
participants (2)
-
Bjoern Franke
-
Timo Sirainen