Am 27.08.25 um 16:52 schrieb Rory Campbell-Lange:
On 27/08/25, Stefan G. Weichinger via dovecot (dovecot@dovecot.org) wrote: I've often used apt-pinning in this way. (https://douglasrumbaugh.com/post/apt-pinning/)
The issue may be that 2.3.x series may not receive security updates, I guess?
That's why I asked ;-)
here it was mentioned that 2.3 gets security patches:
https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/3P45L7...
I don't know if the 2.3 repositories for Debian will be maintained also, but I assume so.
The upgrade to 2.4 is planned here, but the config changes are quite drastic as far as I see. Until I figured out how to convert all the sieve- and imapsieve-parameters I will stay on 2.3. Yes, I read the docs, sure, but without some kind of secondary test-clone this looks too risky for me right now. I prepare the new config in a test VM and work my way through it until dovecot doesn't complain anymore.
I assume the 2.3 repos will live for a few months from now, I will be ready to upgrade sooner ;-)