Public bug reported:
Ubuntu 26.04
Summary
The default configuration shipped in
/etc/dovecot/conf.d/20-managesieve.conf includes:
protocols {
sieve = yes
}
This is misleading in modern Dovecot/Pigeonhole setups and can lead to
misconfiguration when combined with current recommended Sieve storage
methods (sieve_script personal { driver = file }).
Expected behavior
The default configuration should:
Only use modern Sieve enablement via:
mail_plugins = sieve
Enable ManageSieve using service managesieve configuration only
Avoid legacy or ambiguous “protocol-style” Sieve enablement snippets
Actual behavior
The shipped configuration includes:
protocols {
sieve = yes
}
When combined with modern file-based Sieve configuration, this can lead
to:
Incorrect assumption of legacy Sieve directory-based storage
Conflicts with file-based Sieve setup (sieve_script personal)
Errors such as:
stat /.dovecot.sieve/tmp failed: Not a directory
Steps to reproduce
Install Dovecot + ManageSieve:
apt install dovecot-core dovecot-managesieved dovecot-pigeonhole
Configure modern file-based Sieve:
sieve_script personal {
driver = file
path = ~/sieve
active_path = ~/.dovecot.sieve
}
Use Roundcube ManageSieve plugin to create a rule
Observe errors in mail logs:
.dovecot.sieve/tmp is not a directory
** Affects: dovecot (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2153479
Title:
Misleading default Dovecot config includes protocols { sieve = yes },
causing ManageSieve + file-based Sieve misconfiguration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/2153479/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
