On Mon Jul 14, 2025 at 1:38 AM CEST, Steve Litt via dovecot wrote:
[.. snip ..]
There was no one place I got stuck. On July 7 my email stopped working, griping about P12 certs in the .pem (don't remember the exact message). It quickly became obvious the problem was in Dovecot, and dovecot -F gave a "bad config file" error with a config that had worked for years.
More research showed that the Void distribution had upgraded from Dovecot 2.3.21 to 2.4.1 around July 3, and I had subsequently done a distro upgrade on July 7.
Perhaps if I had been paying more attention to the Dovecot mailing list I would have seen this coming and would have been more ready for it. But my bad, I just lightly skimmed the Dovecot mailing list because up until now, Dovecot *never* had problems or drama.
So I came upon the following:
https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html
https://willem.com/blog/2025-06-04_breaking-changes/
Neither told the complete story, and my email was down so I couldn't email this list.
As far as being a show-stopper, yeah, I'll let the community decide. But for me it was an absolute show-stopper. Time will tell whether I'm just some dummy who can't admin, or whether I'm the canary in the coal mine with most distros still on 2.3.x.
SteveT
[.. snip ..]
Steve
I'm also on Void, which is great, but that's what you get with a rolling release distro. All the upgrade trouble you have with other distros when switching from one major release to the next, with Void it just happens bit by bit over time. Things break, like out of the blue, and that's to be expected.
That's why I run all the sensitive stuff in LXC containers, with Alpine. Like my LDAP/Postfix/Dovecot (still, maybe Cyrus soon) server. Having the stuff you really depend on isolated means that you can deal with upgrades when you yourself choose to do so, not when somebody else says you should, potentially hitting you totally unprepared.
Greets, B