On Mon, Apr 19, 2021 at 06:19:35PM +0200, Felix Zielcke wrote: > > I have upgraded a buster system to bullseye. > > Even though dovecot starts up fine with the old config, systemd fails > > to notify that. And kills it again: > > > > # systemctl start dovecot > > > > Job for dovecot.service failed because a timeout was exceeded. > > > > I have brought this up on upstream's mailing list: > > > > https://dovecot.org/pipermail/dovecot/2021-April/121921.html > > > > Solution was to change the dovecot.service file to not use > > Type=notify but Type=simple > > > > Upstreams' fixes, which will be released with 2.3.15, are here: > > https://github.com/dovecot/core/compare/19e05adc3657d2133412635f1345b53cc210ba5b%5E..576d40df2ca38e16c2c9dad798d9b74721568fb0 > > I'm not sure if this actually should be RC. Anyone who uses systemd > can't start dovecot without manual changes. So this really should be > fixed before bullseye will be released.
This is definitely RC if it results in the service not starting as expected after an upgrade. However, I haven't been able to reproduce problems you've described. Starting with a clean installation of dovecot-imapd on a buster system, I have upgraded the system to bullseye and rebooted. The dovecot.service systemd service is started as expected at boot. I can authenticate as usual and the service is stable. I assume I'm missing something, but I'm not sure what. noah
signature.asc
Description: PGP signature
