Thank you for reporting this! I can confirm this change happened in 1:2.4.0+dfsg1-1~exp1 when the config files were updated to match the contents of
https://github.com/dovecot/tools/blob/main/dovecot-2.4.0-example- config.tar.gz Likewise, the entry in 20-managesieve.conf from upstream includes # Uncomment to enable managesieve protocol: protocols { sieve = yes } so it may have been mistakenly uncommented. Marking affected releases ** Also affects: dovecot (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: dovecot (Ubuntu Resolute) Importance: Undecided Status: New ** Changed in: dovecot (Ubuntu) Status: New => Triaged ** Changed in: dovecot (Ubuntu Questing) Status: New => Triaged ** Changed in: dovecot (Ubuntu Resolute) Status: New => Triaged ** Tags added: server-triage-discuss -- 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
