Re: sieve path issue with dovecot 2.4 on debian 13

2026-07-22T01:31:35Z

b.cherrier wrote:

Is this normal ? did I find a bug ?

You're correct, it's indeed a bug of recent iRedMail releases. Fixed moment ago, will releasae iRedMail-1.8.4 with this fix shortly:
https://github.com/iredmail/iRedMail/co … 3dedd2f347

By the way:
- iRedMail Enterprise Edition ("EE") is not affected.
- If you upgraded Debian from 12 to 13 by following our tutorial[1], it's not affected[2] either.

[1] https://docs.iredmail.org/upgrade.debian.12-13.html
[2] https://github.com/iredmail/docs/blob/m … .conf#L727

sieve path issue with dovecot 2.4 on debian 13

2026-07-21T22:48:36Z

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.8.3
- Deployed with iRedMail Easy or the downloadable installer? installer
- Linux/BSD distribution name and version: Debian 13
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mariadb
- Web server (Apache or Nginx): nginx
- Manage mail accounts with iRedAdmin-Pro? yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

A fresh install on debian 13, then restore config and data

This is the error we get :

dovecot: sieve(name@domaine.tld)<16329>: Error: sieve: file storage: Sieve storage path '/var/vmail/vmail1/domaine.tld/n/a/m/name-
2021.04.15.10.29.46//sieve/dovecot.sieve' is not a directory, but it is to be opened for write access

To solve this problem we had to change dovecot.conf from this :

sieve_script personal {
    type = personal
    driver = file
    path = ~/sieve/dovecot.sieve
}

to this :

sieve_script personal {
    type = personal
    driver = file
    path = ~/sieve
    active_path = ~/sieve/dovecot.sieve
}

It's the second server on debian 13 that has this issue.

Is this normal ? did I find a bug ?

iRedMail — sieve path issue with dovecot 2.4 on debian 13

Re: sieve path issue with dovecot 2.4 on debian 13

sieve path issue with dovecot 2.4 on debian 13