From: "Eray Aslan" <eras@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2025-05-23-dovecot-2_4-upgrade/
Date: Fri, 23 May 2025 05:58:24 +0000 (UTC) [thread overview]
Message-ID: <1747979836.4fa481dc53f0b8a874f52a045a5d8e4e2f8d4271.eras@gentoo> (raw)
commit: 4fa481dc53f0b8a874f52a045a5d8e4e2f8d4271
Author: Eray Aslan <eras <AT> gentoo <DOT> org>
AuthorDate: Fri May 23 05:57:16 2025 +0000
Commit: Eray Aslan <eras <AT> gentoo <DOT> org>
CommitDate: Fri May 23 05:57:16 2025 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=4fa481dc
Add news item for dovecot-2.4 upgrade
Signed-off-by: Eray Aslan <eras <AT> gentoo.org>
.../2025-05-23-dovecot-2_4-upgrade.en.txt | 25 ++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/2025-05-23-dovecot-2_4-upgrade/2025-05-23-dovecot-2_4-upgrade.en.txt b/2025-05-23-dovecot-2_4-upgrade/2025-05-23-dovecot-2_4-upgrade.en.txt
new file mode 100644
index 0000000..0bd7053
--- /dev/null
+++ b/2025-05-23-dovecot-2_4-upgrade/2025-05-23-dovecot-2_4-upgrade.en.txt
@@ -0,0 +1,25 @@
+Title: net-mail/dovecot-2.4.x may break on upgrade
+Author: Eray Aslan <eras@gentoo.org>
+Posted: 2025-05-23
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: net-mail/dovecot
+
+Dovecot-2.4 introduced breaking change to its entire configuration system and
+Dovecot-2.3 configuration files will NOT work after upgrade. Please read
+
+https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html
+
+before upgrading. We strongly recommend finalizing your Dovecot 2.4
+configuration on a test system before upgrading any production systems.
+
+The following steps typically make the upgrade process easier:
+
+1. Make a note of your current configuration by running doveconf -n
+2. Stop the dovecot daemon
+3. Move ALL your configuration files to a temporary location
+4. Upgrade to dovecot-2.4.x
+5. Read the new configuration files and uncomment as necessary
+6. Compare the new doveconf -n output with the old one and add missing
+configuration settings one by one while checking that the system works after
+each change
reply other threads:[~2025-05-23 5:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1747979836.4fa481dc53f0b8a874f52a045a5d8e4e2f8d4271.eras@gentoo \
--to=eras@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox