Today, Dovecot package has been upgraded to 1:2.2.21-1. During the upgrade, the following message was displayed. Could someone from the yuno staff tell us if we need to re-enable dovecot.socket, as suggested?
Thanks!
dovecot (1:2.2.21-1) unstable; urgency=medium
This release disables the dovecot.socket systemd unit by default. The unit is
disabled only if the dovecot.service unit is already enabled, making sure
that dovecot will start on system boot. If you are upgrading dovecot and
previously relied on dovecot.socket and dovecot.service being both enabled,
please re-enable dovecot.socket manually using
systemctl enable dovecot.socket
Future package updates will not disable the socket unit again. For details
regarding this decision, please see Debian bugs #803915 and #814999.
-- Apollon Oikonomopoulos <[apoikos@debian.org](mailto:apoikos@debian.org)> Fri, 19 Feb 2016 16:54:27 +0200
Meh that doesnât make sense to me ⌠you message is talking about version 2.2.21, but stretch ships 2.2.27 so thereâs something pretty weird with your apt source config âŚ
Can you run and show the output of grep -nr 'deb' /etc/apt/sources.list*
Hmokay, so that looks like itâs a pretty old server. Which is nice in fact But you might want to clean some of those files. So I think you should run :
I cleaned up the sources, update / upgrade but when running the last commandâŚ
# apt install dovecot-core=2.2.27-3+deb9u3
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '2.2.27-3+deb9u3' for 'dovecot-core' was not found
# apt install dovecot-core=1:2.2.27-3+deb9u3
Reading package lists... Done
Building dependency tree        
Reading state information... Done
dovecot-core is already the newest version (1:2.2.27-3+deb9u3).
dovecot-core set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# /usr/sbin/dovecot --version
2.2.27 (c0f36b0)