On 09-12-2022 12:16 pm, hi@zakaria.website wrote:
It seems that dovecot doesn't understand the relative format and requires absolute format, per the documentation example. Perhaps find the code which parses the absolute path, and compile your own dovecot build, which can understand the path format you want?
I did not find that. I want to learn more, can you link me the dovecot documentation you found explaining how absolute paths are required for sieve?
On 2022-08-25 13:32, dovecot@ptld.com wrote:
The first time when the sieve files and folders get created, the active symlink is created as a full absolute path
.active_sieve -> /mnt/email/domain/user/_sieve/filters.sieveAfter that, if you disable and enable the rule set the symlink gets recreated as relative
.active_sieve -> filters.sieveHow can i have the symlink always created as a relative path even on first time creation? Having a full absolute path over a mounted NSF is fragile.
Dovecot 2.3.16 Pigeonhole 2.3.16
mail_home = /mnt/email/%d/%n/_dovecot mail_location = maildir:/mnt/email/%d/%n/_folders:INDEX=/mnt/email/%d/%n/_dovecot:CONTROL=/mnt/email/%d/%n/_dovecot plugin { sieve = file:~/../_sieve;active=~/../_sieve/.active_sieve sieve_max_script_size = 1M sieve_max_actions = 32 sieve_max_redirects = 4 sieve_quota_max_scripts = 20 sieve_quota_max_storage = 5M sieve_vacation_min_period = 1d sieve_vacation_use_original_recipient = no sieve_vacation_dont_check_recipient = no sieve_vacation_send_from_recipient = no sieve_redirect_envelope_from = sender sieve_user_email = %u }