Sieve default script configuration
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... 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-de...
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
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... 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-de...
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 -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
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?
Here they are: Debug: sieve: Pigeonhole version 2.4.1-4 (0a86619f) initializing Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 2.4.1-4 (0a86619f) loaded Debug: sieve: storage: file: Performing auto-detection Debug: sieve: storage: file: Use home (/var/mail/vhosts/<domain>/<user>) Debug: sieve: storage: file: Checking storage path /var/mail/vhosts/<domain>/<user>/sieve Debug: sieve: storage: file: Storage path '/var/mail/vhosts/<domain>/<user>/sieve' not found Debug: sieve: storage: file: Checking storage path ~/.dovecot.sieve Debug: sieve: storage: file: Storage path '/var/mail/vhosts/<domain>/<user>/.dovecot.sieve' not found Debug: sieve: storage: Autodetection failed Debug: sieve: storage: No matching Sieve storage configured (type=personal and cause=delivery) Debug: sieve: storage default: file: Using script storage path: /etc/sieve/ 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-15 01:47:58] (temporary failure)
It confirms the fallback to the default sieve_script… without explaining what is wrong with it and/or its location.
Bernard Rosset
Hi Stephan,
Have you got any lead on this?
There seems to be something wrong handling the default script storage.
I tried to compile the code to try & reproduce the bug in a controlled environment, failing to do this: pigeonhole fails to build with some ldap linking failure, even though core & pigeonhole codebase were compiled without LDAP support, per default options. I requested help on the IRC channel without any answer.
If you were available, I would very much like to dig into this with you, to the best my (limited) abilities.
Bernard Rosset
On 18/11/2025 21:09 EET Bernard via dovecot <dovecot@dovecot.org> wrote:
Hi Stephan,
Have you got any lead on this?
There seems to be something wrong handling the default script storage.
I tried to compile the code to try & reproduce the bug in a controlled environment, failing to do this: pigeonhole fails to build with some ldap linking failure, even though core & pigeonhole codebase were compiled without LDAP support, per default options. I requested help on the IRC channel without any answer.
If you were available, I would very much like to dig into this with you, to the best my (limited) abilities.
Bernard Rosset
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
Are you trying to build with 2.4.2 or some other version?
Unfortunately you asked your question in IRC during middle of the night in europe, which is not very optimal time for getting answers.
Aki
Can you please be sure? There has been some LDAP compilation fixes with 2.4.2
Aki
On 18/11/2025 22:23 EET Bernard via dovecot <dovecot@dovecot.org> wrote:
Are you trying to build with 2.4.2 or some other version?
It was probably main/main. 2.4.1 would not compile.
Bernard Rosset
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
Can you please be sure? There has been some LDAP compilation fixes with 2.4.2
I sent another message yesterday evening, in French - brain fart.
I checked the problem arises by compiling 2.4.2 tag on pigeonhole project against the 2.4.2 tag on the core one. I tried 2.4.2 after being unable to build 2.4.1, which is the version I am involved with.
My problem is, the instance I am trying to solve the problem on is running the Debian stable package, still on 2.4.1. The facts that 2.4.1 contains such a bug, and that *both* 2.4.1 & 2.4.2 tags are not buildable in their current state are serious obstacles.
What I am seeking for is a fix, backportable to v2.4.1, which could end up in an update to said package. At the moment I am getting emails ending up being rejected on accounts impacted by this bug, as a consequence to their processing constantly failing.
I tried cherry-picking some commits, without having reached a buildable state.
After many attempts on different directions, and overall a lot of time spent into this, I am still facing dead ends.
Here are the questions I am left with:
- Would it be possible to fix 2.4.1 so it is buildable?
- Is a 2.4.1 fix regarding default sieve storage envisioned?
Bernard Rosset
Sorry, still need to work on this..
Op 19-11-2025 om 13:41 schreef Bernard via dovecot:
Can you please be sure? There has been some LDAP compilation fixes with 2.4.2
I sent another message yesterday evening, in French - brain fart.
I checked the problem arises by compiling 2.4.2 tag on pigeonhole project against the 2.4.2 tag on the core one. I tried 2.4.2 after being unable to build 2.4.1, which is the version I am involved with.
My problem is, the instance I am trying to solve the problem on is running the Debian stable package, still on 2.4.1. The facts that 2.4.1 contains such a bug, and that *both* 2.4.1 & 2.4.2 tags are not buildable in their current state are serious obstacles.
What I am seeking for is a fix, backportable to v2.4.1, which could end up in an update to said package. At the moment I am getting emails ending up being rejected on accounts impacted by this bug, as a consequence to their processing constantly failing.
I tried cherry-picking some commits, without having reached a buildable state.
After many attempts on different directions, and overall a lot of time spent into this, I am still facing dead ends.
Here are the questions I am left with:
- Would it be possible to fix 2.4.1 so it is buildable?
- Is a 2.4.1 fix regarding default sieve storage envisioned?
Bernard Rosset
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
Are you trying to build with 2.4.2 or some other version?
Verification faite, c'est en compilant l'étiquette 2.4.2 des projets core & pigeonhole : l'erreur intervient sur le projet pigeonhole après avoir compilé & installé celui core: CCLD libdovecot-sieve.la /usr/bin/ld: cannot find -ldovecot-ldap: No such file or directory
Bernard Rosset
Op 15-11-2025 om 01:56 schreef Bernard via dovecot:
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?
Here they are: Debug: sieve: Pigeonhole version 2.4.1-4 (0a86619f) initializing Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 2.4.1-4 (0a86619f) loaded Debug: sieve: storage: file: Performing auto-detection Debug: sieve: storage: file: Use home (/var/mail/vhosts/<domain>/<user>) Debug: sieve: storage: file: Checking storage path /var/mail/vhosts/<domain>/<user>/sieve Debug: sieve: storage: file: Storage path '/var/mail/vhosts/<domain>/<user>/sieve' not found Debug: sieve: storage: file: Checking storage path ~/.dovecot.sieve Debug: sieve: storage: file: Storage path '/var/mail/vhosts/<domain>/<user>/.dovecot.sieve' not found Debug: sieve: storage: Autodetection failed Debug: sieve: storage: No matching Sieve storage configured (type=personal and cause=delivery) Debug: sieve: storage default: file: Using script storage path: /etc/sieve/ 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-15 01:47:58] (temporary failure)
It confirms the fallback to the default sieve_script… without explaining what is wrong with it and/or its location.
I can finally reproduce it:
Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: Pigeonhole version 2.4.1 (0a86619f1) initializing Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Performing auto-detection Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Use home (/home/stephan) Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Checking storage path /home/stephan/sieve Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Storage path '/home/stephan/sieve' not found Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Checking storage path ~/.dovecot.sieve Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Storage path '/home/stephan/.dovecot.sieve' not found Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: Autodetection failed Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: No matching Sieve storage configured (type=personal and cause=delivery) Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage default: file: Using script storage path: /etc/sieve/ Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Error: sieve: file storage: Performing t_readlink() on active sieve symlink '(null)' failed: readlink() failed: Bad address Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Error: sieve: Failed to access active Sieve script in parsonal storage 'default': Internal error occurred. Refer to server log for more information. [2025-11-25 03:41:57] (temporary failure)
Now to figure out what is going on...
Bernard Rosset
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
Workaround: use explicit path to script
sieve_script default { type = default name = default driver = file path = /etc/sieve/default.sieve }
Op 25-11-2025 om 03:45 schreef Stephan Bosch via dovecot:
Op 15-11-2025 om 01:56 schreef Bernard via dovecot:
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?
Here they are: Debug: sieve: Pigeonhole version 2.4.1-4 (0a86619f) initializing Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 2.4.1-4 (0a86619f) loaded Debug: sieve: storage: file: Performing auto-detection Debug: sieve: storage: file: Use home (/var/mail/vhosts/<domain>/<user>) Debug: sieve: storage: file: Checking storage path /var/mail/vhosts/<domain>/<user>/sieve Debug: sieve: storage: file: Storage path '/var/mail/vhosts/<domain>/<user>/sieve' not found Debug: sieve: storage: file: Checking storage path ~/.dovecot.sieve Debug: sieve: storage: file: Storage path '/var/mail/vhosts/<domain>/<user>/.dovecot.sieve' not found Debug: sieve: storage: Autodetection failed Debug: sieve: storage: No matching Sieve storage configured (type=personal and cause=delivery) Debug: sieve: storage default: file: Using script storage path: /etc/sieve/ 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-15 01:47:58] (temporary failure)
It confirms the fallback to the default sieve_script… without explaining what is wrong with it and/or its location.
I can finally reproduce it:
Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: Pigeonhole version 2.4.1 (0a86619f1) initializing Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Performing auto-detection Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Use home (/home/stephan) Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Checking storage path /home/stephan/sieve Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Storage path '/home/stephan/sieve' not found Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Checking storage path ~/.dovecot.sieve Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Storage path '/home/stephan/.dovecot.sieve' not found Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: Autodetection failed Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: No matching Sieve storage configured (type=personal and cause=delivery) Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage default: file: Using script storage path: /etc/sieve/ Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Error: sieve: file storage: Performing t_readlink() on active sieve symlink '(null)' failed: readlink() failed: Bad address Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Error: sieve: Failed to access active Sieve script in parsonal storage 'default': Internal error occurred. Refer to server log for more information. [2025-11-25 03:41:57] (temporary failure)
Now to figure out what is going on...
Bernard Rosset
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
Fix is in the pipeline (DOV-8469)
Op 25-11-2025 om 03:49 schreef Stephan Bosch via dovecot:
Workaround: use explicit path to script
sieve_script default { type = default name = default driver = file path = /etc/sieve/default.sieve }
Op 25-11-2025 om 03:45 schreef Stephan Bosch via dovecot:
Op 15-11-2025 om 01:56 schreef Bernard via dovecot:
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?
Here they are: Debug: sieve: Pigeonhole version 2.4.1-4 (0a86619f) initializing Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 2.4.1-4 (0a86619f) loaded Debug: sieve: storage: file: Performing auto-detection Debug: sieve: storage: file: Use home (/var/mail/vhosts/<domain>/<user>) Debug: sieve: storage: file: Checking storage path /var/mail/vhosts/<domain>/<user>/sieve Debug: sieve: storage: file: Storage path '/var/mail/vhosts/<domain>/<user>/sieve' not found Debug: sieve: storage: file: Checking storage path ~/.dovecot.sieve Debug: sieve: storage: file: Storage path '/var/mail/vhosts/<domain>/<user>/.dovecot.sieve' not found Debug: sieve: storage: Autodetection failed Debug: sieve: storage: No matching Sieve storage configured (type=personal and cause=delivery) Debug: sieve: storage default: file: Using script storage path: /etc/sieve/ 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-15 01:47:58] (temporary failure)
It confirms the fallback to the default sieve_script… without explaining what is wrong with it and/or its location.
I can finally reproduce it:
Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: Pigeonhole version 2.4.1 (0a86619f1) initializing Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Performing auto-detection Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Use home (/home/stephan) Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Checking storage path /home/stephan/sieve Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Storage path '/home/stephan/sieve' not found Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Checking storage path ~/.dovecot.sieve Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Storage path '/home/stephan/.dovecot.sieve' not found Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: Autodetection failed Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: No matching Sieve storage configured (type=personal and cause=delivery) Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage default: file: Using script storage path: /etc/sieve/ Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Error: sieve: file storage: Performing t_readlink() on active sieve symlink '(null)' failed: readlink() failed: Bad address Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Error: sieve: Failed to access active Sieve script in parsonal storage 'default': Internal error occurred. Refer to server log for more information. [2025-11-25 03:41:57] (temporary failure)
Now to figure out what is going on...
Bernard Rosset
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
Fix is now in main (two commits): https://github.com/dovecot/pigeonhole/commit/89f44ed0cb17e6564bdd1a1835a71e9...
Op 25-11-2025 om 13:01 schreef Stephan Bosch via dovecot:
Fix is in the pipeline (DOV-8469)
Op 25-11-2025 om 03:49 schreef Stephan Bosch via dovecot:
Workaround: use explicit path to script
sieve_script default { type = default name = default driver = file path = /etc/sieve/default.sieve }
Op 25-11-2025 om 03:45 schreef Stephan Bosch via dovecot:
Op 15-11-2025 om 01:56 schreef Bernard via dovecot:
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?
Here they are: Debug: sieve: Pigeonhole version 2.4.1-4 (0a86619f) initializing Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 2.4.1-4 (0a86619f) loaded Debug: sieve: storage: file: Performing auto-detection Debug: sieve: storage: file: Use home (/var/mail/vhosts/<domain>/<user>) Debug: sieve: storage: file: Checking storage path /var/mail/vhosts/<domain>/<user>/sieve Debug: sieve: storage: file: Storage path '/var/mail/vhosts/<domain>/<user>/sieve' not found Debug: sieve: storage: file: Checking storage path ~/.dovecot.sieve Debug: sieve: storage: file: Storage path '/var/mail/vhosts/<domain>/<user>/.dovecot.sieve' not found Debug: sieve: storage: Autodetection failed Debug: sieve: storage: No matching Sieve storage configured (type=personal and cause=delivery) Debug: sieve: storage default: file: Using script storage path: /etc/sieve/ 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-15 01:47:58] (temporary failure)
It confirms the fallback to the default sieve_script… without explaining what is wrong with it and/or its location.
I can finally reproduce it:
Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: Pigeonhole version 2.4.1 (0a86619f1) initializing Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Performing auto-detection Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Use home (/home/stephan) Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Checking storage path /home/stephan/sieve Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Storage path '/home/stephan/sieve' not found Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Checking storage path ~/.dovecot.sieve Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: file: Storage path '/home/stephan/.dovecot.sieve' not found Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: Autodetection failed Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage: No matching Sieve storage configured (type=personal and cause=delivery) Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Debug: sieve: storage default: file: Using script storage path: /etc/sieve/ Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Error: sieve: file storage: Performing t_readlink() on active sieve symlink '(null)' failed: readlink() failed: Bad address Nov 25 03:41:57 lda(stephan)<3385477><0ZkxB3UXJWmFqDMAmoV78g>: Error: sieve: Failed to access active Sieve script in parsonal storage 'default': Internal error occurred. Refer to server log for more information. [2025-11-25 03:41:57] (temporary failure)
Now to figure out what is going on...
Bernard Rosset
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
participants (3)
-
Aki Tuomi
-
Bernard
-
Stephan Bosch