This looks like a bug. But I cannot reproduce this here immediately. Can
you enable sieve debugging (log_debug = category=sieve) and show what it
logs?
Op 13-11-2025 om 19:20 schreef Bernard via dovecot:
Hello,
Using Dovecot v2.4.1 (Devuan stable), I am facing difficulties
debugging what is wrong with my configuration.
Here is the error:
Error: sieve: file storage: Performing t_readlink() on active sieve
symlink '(null)' failed: readlink() failed: Bad address
Error: sieve: Failed to access active Sieve script in parsonal storage
'default': Internal error occurred. Refer to server log for more
information. [2025-11-13 19:08:48] (temporary failure)
This happens on the mailbox which has no personal Sieve file in its
personal directory, hence falling back to the default sieve configured
that way:
sieve_script default {
type = default
name = default
driver = file
path = /etc/sieve/
}
/etc/sieve contains:
drwxr-xr-x 2 root root 4096 Nov 13 18:57 /etc/sieve/
-rw-r--r-- 1 root root 2209 Aug 19 2021 default.sieve
-rw-r--r-- 1 root root 2276 Nov 13 18:57 default.svbin
I read:
-
https://doc.dovecot.org/2.4.2/installation/upgrade/2.3-to-2.4.html#converted-settings
converting sieve_default to a sieve_script block with type = default
-
https://doc.dovecot.org/2.4.2/core/plugins/sieve.html#script-storage-type-default
doveadm sieve list -A returns:
vmail default ACTIVE
doveadm sieve get -A default returns the sieve file contents
/etc/sieve was previously belonging to vmail:vmail. Switching to
root:root did not yield any change.
Moreover, running sievec on the default.sieve file with vmail:vmail
permissions yielded default.svbin with root:root ownership.
The error message is cryptic to me: what is this symlink problem?
Cheers,
Bernard Rosset
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
