Dovecot 2.4
Summary
Update the Dovecot email server in Fedora from Dovecot 2.3.x to Dovecot 2.4.x, the newest major release.
Owner
- Name: Michal Hlavinka
- Email: mhlavink[at]redhat[dot]com
Current status
- Targeted release: Fedora Linux 43
- Last updated: 2025-07-03
- Announced
- Discussion thread
- FESCo issue: #3422
- Tracker bug: #2376116
- Release notes tracker: #238
Detailed Description
Update the Dovecot email server in Fedora from Dovecot 2.3.x to Dovecot 2.4.x. This is the latest major release that upstream released after 7 years. Dovecot 2.3 and 2.4 configuration is not mutually compatible. Configuration upgrade process is documented at details see https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html
Feedback
Benefit to Fedora
With Dovecot 2.4 release, upstream shifted its support from 2.3.x to 2.4. Updating Dovecot in Fedora will allow to continue providing mail server that is secure, actively developed and maintained. List of changes and improvements at https://github.com/dovecot/core/releases/tag/2.4.0
Scope
- Proposal owners:
- update dovecot rpm to 2.4, port downstream patches, testing
- Other developers: N/A
- Release engineering: N/A #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with the Fedora Strategy:
Upgrade/compatibility impact
Dovecot 2.4.x configuration is not compatible with 2.3.x configuration. Configuration changes and upgrade procedure is documented at https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html
Early Testing (Optional)
Do you require 'QA Blueprint' support? N
How To Test
- if you already have dovecot installed
1. backup
2. update dovecot rpm
3. update dovecot configuration as described https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html
4. test that everything still works
User Experience
Updated Dovecot 2.4.x provides more currently relevant security features and protocols. Easier configuration and deployment.
Dependencies
NONE
Contingency Plan
Worst case scenario, we can easily revert the change and delay for next Fedora release.
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)
