Talk:Dovecot
Major config change in 2.4
In 2.4 release notes many config options were changed.
In comments on gitlab it looks like new version is gonna go into repos soon.
Not sure if there is any point of keeping the old config snippets here. Roshless (talk) 21:51, 9 June 2025 (UTC)
Expansion needed for the configuration section
I rewritten the entire configuration section to make it compatible with 2.4.
However, that is at best a replacement for already pretty limited information previously present. I also removed fragments that were marked as making arbitrary assumptions for 2 years, or whose accuracy was disputed since Strykar marked them earlier this year. Which means the current version is even leaner than it was before.
There are two areas that are in need of improvement:
- Mailboxes configuration. In particular the
mail_locationsetting is now gone. - Different deployment scenarios.
--Mpan (talk) 10:56, 30 October 2025 (UTC)
Warn users about difficult migration 2.3 => 2.4
In response to edit Rem. a personal, angry opinion by User:Mpan I would like to emphasize that users should be warned about 'challenges' that might arise during migration from v2.3 to v2.4. After having skimmed the migration guide I light-heartedly jumped into the migration. Just to learn that the migration guide (and generally Dovecot's documentation) are in dire need for improvement. Wolegis (talk) 10:30, 8 November 2025 (UTC)
- I agree with both, can you improve the wording of such note? — Lahwaacz (talk) 13:23, 15 November 2025 (UTC)
dovecot & Postfix : cannot read SSL private key
I made a mistake : I forgot to tell that the dovecot-ssl.conf should be chmoded to 0600.
The error described seemed enough for me but to be clear, when postfix calls for procmail, it is called _as user_. So every run command is _as user_. Dovecot's deliver command (recommanded to be used to enable notifications and alikes) reads the conf and _crashes_ when encounters the SSL keys, since they can only be read by "root".
=> To avoid this error, dovecot mailing list pointed that "include" as a gimmick that is include_try that silently fails when file included is unreadable (and enables deliver to work as user).
- Launch dovecot as root, SSL keys are read, and everything works fine.
- Launching dovecot's deliver as user, file containing keys is << unread >> but deliver works just fine without them.
==> Problem solved.
threads about the issue :
- https://serverfault.com/questions/1197324/permission-issue-after-migrating-dovecot-config-to-2-4
Mansu (talk) 10:51, 23 December 2025 (UTC)
- It would be nice if you added the explanation of the problem and references to the section. Just the error message is not enough. — Lahwaacz (talk) 09:21, 25 December 2025 (UTC)
- I did a version, hoping it's readable :-) Feel free to edit, if I made some grammar/clarity mistakes! (removed the banner, since you seemed to allow it to me) Mansu (talk) 11:27, 28 December 2025 (UTC)
- Thanks. — Lahwaacz (talk) 11:42, 28 December 2025 (UTC)
- I did a version, hoping it's readable :-) Feel free to edit, if I made some grammar/clarity mistakes! (removed the banner, since you seemed to allow it to me) Mansu (talk) 11:27, 28 December 2025 (UTC)