{"id":21896,"date":"2026-11-01T14:20:00","date_gmt":"2026-11-01T13:20:00","guid":{"rendered":"https:\/\/webhosting.de\/?p=21896"},"modified":"2026-10-30T12:49:30","modified_gmt":"2026-10-30T11:49:30","slug":"dovecot-update-ce-24-new-features-in-dovecot-3","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/dovecot-update-ce-24-neuerungen-dovecot-3\/","title":{"rendered":"Dovecot Update: What's New in CE 2.4 and the Status of Dovecot 3"},"content":{"rendered":"<div class=\"wh-article\" data-wh-layout=\"2.1.2\" style=\"width:100%;max-width:820px;margin:0 auto;color:#263b4b;font-family:inherit;font-size:18px;line-height:1.8;text-align:start;overflow-wrap:break-word;box-sizing:border-box\"><p class=\"wh-lead\" style=\"font-size:20px;line-height:1.7;color:#233746;margin:0 0 1.1em\">For a <strong style=\"font-weight:700;color:inherit\">Dovecot Update<\/strong> CE 2.4.5 is the reliable, stable reference point, not an announced Dovecot 3 roadmap. Anyone migrating from 2.3 must separately verify the configuration, removed components, storage formats, and additional services such as Sieve or full-text search. It is particularly important to activate configuration and storage versions in stages and to conduct tests using representative mailboxes. Statements from the development branch do not replace either a published release or a robust migration plan.  <\/p>\n<nav class=\"wh-toc\" aria-label=\"Contents of this article\" style=\"display:block;margin:28px 0 38px;padding:22px;border:1px solid #d9e4e8;border-radius:14px;background:#f4f8f8\"><p class=\"wh-toc-title\" style=\"font-size:13px;font-weight:700;letter-spacing:.08em;color:#49656b;margin:0 0 14px\">Go directly to the section<\/p><div class=\"wh-toc-grid\" style=\"display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,280px),1fr));gap:10px\"><div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#versionsstand-und-roadmap\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Dovecot 3: Understanding the Version Status and Roadmap<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#dovecot-24-versionsmodell\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">What Has Changed in the Dovecot 2.4 Versioning Model<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#neuerungen-mit-vorbehalt\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">New Features and Their Maturity Level<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#upgrade-bestandsaufnahme\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Systematically Prepare for the Upgrade to 2.4<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#migrationsmatrix-23-zu-24\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Planning the Migration from 2.3 to 2.4<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#fts-und-storage-abwaegen\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Carefully weigh the pros and cons of search and storage formats<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#sieve-proxy-und-sicherheit\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Check Sieves, Proxies, and Security Limits<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#betrieb-und-fehlersuche\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Operate Safely After the Update<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#update-entscheidung-treffen\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">When It's Worth Updating Dovecot<\/a><\/div>\n<\/div><\/nav><section class=\"wh-section\" aria-labelledby=\"versionsstand-und-roadmap\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"versionsstand-und-roadmap\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Dovecot 3: Understanding the Version Status and Roadmap<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Anyone planning a Dovecot update should not interpret version numbers as a promise of an upcoming major release. As of October 21, 2026, Dovecot CE 2.4.5 is the published stable release in the official Core repository. However, there is no record of a published Dovecot CE version 3.0 or an official CE 3.0 roadmap there.  <\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"Documented version status and statements that do not follow from it\" style=\"width:100%;max-width:100%;overflow-x:auto;margin:28px 0;border:1px solid #dce5e9;border-radius:14px;background:#fff;box-shadow:0 10px 28px -16px rgba(24,47,60,.32);box-sizing:border-box\"><table style=\"width:100%;min-width:580px;border-collapse:separate;border-spacing:0;border:0;margin:0;font-size:15px;line-height:1.6;background:#fff\"><caption style=\"padding:20px;text-align:start;font-size:17px;line-height:1.5;font-weight:700;color:#173246;background:#fff\">Documented version status and statements that do not follow from it<\/caption><thead><tr><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Statement<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Classification as of the reporting date<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Practical Implications<\/th><\/tr><\/thead><tbody><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Dovecot CE 2.4.5<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Stable release published in the official repository.<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Upgrade planning can be based on the documented 2.4 line.<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Documentation on Subsequent Changes to Version 2.4<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Can describe development changes without requiring a new stable release.<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Do not treat this as a target release version or a promised release date.<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Dovecot 3<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">No confirmed CE 3.0 roadmap was found in the reviewed material.<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Do not plan for either the scope of functionality or the migration date.<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">main<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Development branch; not a substitute for a stable product release.<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Suitable for observation and preliminary evaluation, but not for binding product commitments.<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In particular, a heading such as \u201ev2.4.5 to v2.4.6\u201c in the documentation does not indicate that a version 2.4.6 has been released. Such content can help identify changes in the development branch early on. However, it does not indicate when, if, or in what form these changes will be included in a stable package. This is especially true for versions derived from Dovecot 3.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For decisions regarding <strong style=\"font-weight:700;color:inherit\">Email hosting<\/strong> In addition, the product lines must remain separate. Dovecot CE refers to the Community Edition, while Dovecot Pro is a separate commercial offering. Therefore, a feature, operating model, or documentation statement cannot automatically be transferred between the two. Content from the \u201cmain\u201d branch must also be distinguished from published CE releases; the version and documentation that are actually intended for use are the determining factors for an upgrade.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"dovecot-24-versionsmodell\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"dovecot-24-versionsmodell\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">What Has Changed in the Dovecot 2.4 Versioning Model<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Dovecot 2.4 distinguishes between three levels that are often mistakenly conflated during an update: the installed version of the program, <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dovecot_config_version<\/code> and <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dovecot_storage_version<\/code>. The installed package determines which code the IMAP server can execute. The two settings, on the other hand, are specifically designed to control the point at which modified default values or new storage formats are used.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The <strong style=\"font-weight:700;color:inherit\">Configuration Version<\/strong> This prevents a package update from silently activating all new defaults. Administrators can first update Dovecot to version 2.4 and then selectively upgrade the configuration semantics after reviewing authentication, TLS, plugins, and the existing settings. This reduces surprises caused by changed default values, but does not replace the necessary migration of a 2.3 configuration. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The <strong style=\"font-weight:700;color:inherit\">Cache version<\/strong> In contrast, this setting affects the data formats that Dovecot uses in its indexes or other storage areas. A higher value may enable formats that older versions of Dovecot do not support. Therefore, it should only be set once rolling back to an older version is no longer part of the recovery plan. A package rollback alone does not automatically restore previously used index formats.  <\/p>\n<figure class=\"wp-block-image size-large wh-figure\" aria-describedby=\"wh-caption-detail1\" style=\"display:block;float:none;clear:both;width:100%;max-width:760px;margin:34px auto 40px;border:1px solid #dae5e9;border-radius:14px;overflow:hidden;background:#f5f8fa;box-shadow:0 10px 28px -17px rgba(24,47,60,.28);box-sizing:border-box\"><div class=\"wh-figure-media\" style=\"display:block;background:#eef3f5;line-height:0\"><img loading=\"lazy\" width=\"800\" height=\"534\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-speicherversion-server-e0f80596-detail1-fbee140b68-1024x683.webp\" class=\"wp-image-21902\" alt=\"Compact mail server with external storage on a used workbench.\" decoding=\"async\" srcset=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-speicherversion-server-e0f80596-detail1-fbee140b68-1024x683.webp 1024w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-speicherversion-server-e0f80596-detail1-fbee140b68-300x200.webp 300w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-speicherversion-server-e0f80596-detail1-fbee140b68-768x512.webp 768w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-speicherversion-server-e0f80596-detail1-fbee140b68-18x12.webp 18w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-speicherversion-server-e0f80596-detail1-fbee140b68.webp 1536w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" ><\/div><figcaption class=\"wh-caption\" id=\"wh-caption-detail1\" style=\"display:block;margin:0;padding:12px 18px 15px;border-top:1px solid #dce5e9;color:#506575;background:#f5f8fa;font-size:14px;line-height:1.55;text-align:start\">AI-generated stock image: The program version and storage formats should be planned separately during the update.<\/figcaption><\/figure><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For a 2.3-to-2.4 migration, both settings must be present in the main configuration; <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dovecot_config_version<\/code> The first setting must be <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dovecot.conf<\/code> . Set the configuration version to the intended target level only after you have adapted and verified the 2.4 syntax. The storage version initially remains at the compatible level previously required and is not automatically updated to the package level.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The explicit second step is the <strong style=\"font-weight:700;color:inherit\">rollback-critical release<\/strong> new storage formats. Only when all instances are using the new version, a rollback to older Dovecot versions is no longer planned, and a scheduled maintenance window is available, can <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dovecot_storage_version<\/code> be increased to the selected target level, for example to <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">2.4.5<\/code> for the thread index format documented there. Older versions can reconstruct this index in their own format; however, this involves additional work and a switch between index formats that are not mutually compatible. Therefore, this information is not a ready-to-copy standard configuration: the source and target values depend on the version being used and the fallback plan.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">This step-by-step approach is similar to the principle of evaluating the program status and implemented behavioral changes separately. Even for other server components, a high version number alone is not sufficient proof of compatibility; the article on <a href=\"https:\/\/webhosting.de\/en\/redis-8-new-features-hosting-providers\/\">Upgrade Decisions for Redis 8<\/a> explains this distinction for another service. With Dovecot, mailbox formats, index data, and the fallback strategy are also relevant.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"neuerungen-mit-vorbehalt\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"neuerungen-mit-vorbehalt\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">New Features and Their Maturity Level<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A notable new feature in Dovecot 2.4 is <strong style=\"font-weight:700;color:inherit\">fts-flatcurve<\/strong> as a local full-text search backend based on Xapian. The driver stores search data for each mailbox in the Dovecot index path and requires Xapian version 1.4 or later. It supports relevance scoring and can also enable substring searches, but does not offer fuzzy search. Without a full-text index, Dovecot must search through message data sequentially to perform such searches.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Substring search is not automatically enabled in Flatcurve: The documented default setting for <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">fts_flatcurve_substring_search<\/code> is <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">no<\/code>. If it is intentionally enabled for relevant IMAP search queries, additional storage space must be allocated for the index. Flatcurve thus remains an option for IMAP servers with frequently used message search functionality, but it is not a mandatory upgrade without conditions. Index growth, monitoring, and reindexing are part of operational planning.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">SMTPUTF8 and IMAP should be classified differently <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">UTF8=ACCEPT<\/code> and IMAP4rev2. The release notes label these features as experimental. SMTPUTF8 and <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">UTF8=ACCEPT<\/code> Create a build using <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">--enable-experimental-mail-utf8<\/code> and then <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">mail_utf8_extensions = yes<\/code> in the configuration. IMAP4rev2 uses separate switches for this: During the build, <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">--enable-experimental-imap4rev2<\/code> required; after that, you must <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">imap4rev2_enabled = yes<\/code> can be configured.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">\"Experimental\" does not mean here that the feature is generally unsuitable. Rather, it is not a universal standard for every hosting service. Before enabling this feature, operators should verify whether the mail clients in use, the entire delivery chain, and connected systems actually require and are capable of handling the desired UTF-8 processing or IMAP4rev2. Tests should be conducted in an environment that adequately simulates real-world authentication, mailbox names, and client profiles.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">SCRAM mechanisms, TLS channel binding, and advanced TLS SNI and ALPN processing also warrant a separate evaluation. They affect not only the Dovecot process but also its interaction with clients, certificates, proxies, and authentication sources. The appropriate criterion is a clear need with verifiable compatibility, not merely the availability of a new option in a Dovecot release.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"upgrade-bestandsaufnahme\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"upgrade-bestandsaufnahme\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Systematically Prepare for the Upgrade to 2.4<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Upgrading from Dovecot 2.3 to 2.4 begins with an inventory check, not with the package manager. Record the installed version, the current configuration, and the mailbox format, such as Maildir or mdbox. Also document authentication sources, Sieve rules, quotas, full-text search, replication, and upstream proxies. This is the only way to determine which services and data paths are actually affected by the migration. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The following commands are suitable for a read-only inventory. They do not change the configuration or mail data; however, their output should be displayed in a secure workspace because it may reveal information about the server environment. <\/p>\n<div class=\"wh-code-window\" data-wh-code style=\"margin:28px 0 34px;border:1px solid #2c4656;border-radius:12px;overflow:hidden;background:#132a3b;box-shadow:0 9px 25px -13px rgba(15,35,55,.2)\"><div class=\"wh-code-toolbar\" style=\"display:flex;flex-wrap:wrap;align-items:center;justify-content:space-between;gap:10px;padding:11px 16px;background:#223e50;color:#edf5fa;font-size:13px;line-height:1.5;font-weight:600\"><span>Terminal<\/span><button type=\"button\" class=\"wh-code-copy\" data-wh-copy hidden style=\"padding:6px 11px;border:1px solid #7893a1;border-radius:6px;background:transparent;color:#fff;font-size:12px;line-height:1.5;font-weight:600;cursor:pointer\">Copy code<\/button><span class=\"wh-copy-status\" aria-live=\"polite\"><\/span><span data-wh-copy-success hidden>Copied<\/span><span data-wh-copy-fallback hidden>Code highlighted\u2014please copy<\/span><\/div><pre class=\"wh-code\" data-no-translation translate=\"no\" style=\"display:block;margin:0;padding:20px;max-width:100%;overflow-x:auto;color:#edf5fa;background:#132a3b;font:14px\/1.75 ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;white-space:pre;direction:ltr;text-align:left\"><code class=\"language-bash\" style=\"font:inherit;color:inherit;background:transparent;padding:0;border:0;white-space:inherit\">dovecot --version\ndoveconf -n<\/code><\/pre><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dovecot --version<\/code> shows the program status. With <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">doveconf -n<\/code> you check the effective configuration that differs from the default settings. The option <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">-v<\/code> from <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">doveadm<\/code> In contrast, this is not a version query, but rather enables more detailed output\u2014including a progress indicator\u2014and is only associated with a corresponding subcommand. Treat the configuration output as confidential: it may contain hostnames, directory structures, backend addresses, or other infrastructure details. For error analysis, the Dovecot documentation recommends using a minimized configuration rather than an unabridged public dump.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Also check whether the current version is already the latest available 2.3 release. The documented migration path first leads to this version and only then to 2.4. Do not transfer the configuration directly to a production system; instead, transfer it to a test system with representative accounts, permissions, and mailbox sizes. As with a <a href=\"https:\/\/webhosting.de\/en\/linux-kernel-6-new-features-for-hosting-servers\/\">Kernel Update for Hosting Servers<\/a> Here, too, the version number alone is not enough: packaging, enabled modules, and architecture determine the practical impact. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"migrationsmatrix-23-zu-24\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"migrationsmatrix-23-zu-24\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Planning the Migration from 2.3 to 2.4<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Migrating to 2.4 is a separate configuration step. Dovecot 2.4 requires a modified syntax as well as <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dovecot_config_version<\/code> and <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dovecot_storage_version<\/code>; the configuration version must be the first setting in <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dovecot.conf<\/code> Therefore, do not simply copy old files as-is. Compare each setting you use with the version-specific migration documentation and validate it in the test system before scheduling a maintenance window. <\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"Migration Points from Dovecot 2.3 to Dovecot 2.4\" style=\"width:100%;max-width:100%;overflow-x:auto;margin:28px 0;border:1px solid #dce5e9;border-radius:14px;background:#fff;box-shadow:0 10px 28px -16px rgba(24,47,60,.32);box-sizing:border-box\"><table style=\"width:100%;min-width:580px;border-collapse:separate;border-spacing:0;border:0;margin:0;font-size:15px;line-height:1.6;background:#fff\"><caption style=\"padding:20px;text-align:start;font-size:17px;line-height:1.5;font-weight:700;color:#173246;background:#fff\">Migration Points from Dovecot 2.3 to Dovecot 2.4<\/caption><thead><tr><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Range<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Change in 2.4<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Possible Approach<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Test Before the Switch<\/th><\/tr><\/thead><tbody><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Basic configuration<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Version information and syntax changes required<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Revise the configuration for 2.4<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Parser Check and Test Start<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Director<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">The Dovecot Director architecture has been removed<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">For small environments, Lua Director can be tested; the documentation notes that it is not supported. The former Director role is replaced by Palomar in Dovecot Pro.<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Evaluate routing, failure scenarios, and operational responsibility separately<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Replicator<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Component removed<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Consider NFS or another shared file system as an architectural approach<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Testing Storage Accesses, Failover, and Consistency Processes<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">dsync command<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">The dsync symlink has been removed<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Customize scheduled synchronization or migration processes using `doveadm sync` or `doveadm backup`<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Check Command Calls and Return Values During the Test Run<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">quota-dict and quota-dirsize<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Quota backends removed<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Evaluate \"quota-count\" as a possible alternative<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Calculate Quotas and Review Borderline Cases<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">fts-lucene and fts-squat<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Search backends removed<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Rate fts-flatcurve or Solr<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Testing Search, Indexing, and Storage Requirements<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The table does not list any alternative solutions. The removed Director and the removed Replicator serve different purposes: According to the documentation, Lua Director is merely an unsupported solution for small deployments, whereas Replicator is described as an approach based on a shared file system. <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">doveadm sync<\/code> is, on the other hand, the successor to the removed <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dsync<\/code>-Symlinks and can be used for intentionally planned synchronization or migration processes; however, this does not constitute a documented \"drop-in\" replacement for Director or Replicator.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The existing data set is also a determining factor when it comes to quotas and searches. <strong style=\"font-weight:700;color:inherit\">Compatibility<\/strong> This doesn't just mean that Dovecot starts up: quota warnings, Sieve actions, IMAP searches, and access from multiple clients must work with realistic test accounts. For each component being removed, document where it is configured, what data it uses, and what the fallback plan is. Only then can the package migration be scheduled appropriately. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"fts-und-storage-abwaegen\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"fts-und-storage-abwaegen\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Carefully weigh the pros and cons of search and storage formats<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In Dovecot 2.4, the program state, configuration state, and storage state can be developed separately by design. Increase <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">dovecot_storage_version<\/code> only when a rollback to an older version of Dovecot is no longer planned. With Storage Level 2.4.5, the thread index for the IMAP command <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">THREAD<\/code> A new v2 format. Existing thread indexes will be rebuilt during the next threading operation; this can result in additional overhead, especially for large mailboxes, during the initial query. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">An older version of Dovecot does not understand this thread index format and generates the index in the old format again. The <strong style=\"font-weight:700;color:inherit\">Storage Level<\/strong> It is therefore a company-wide policy, not merely a cosmetic change. Schedule any potential index rebuilds within a monitored time window, and do not perform them simultaneously with other changes to search, storage, or proxy topology that are difficult to reverse. <\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"Search Approaches in the Dovecot Environment by Operational Model\" style=\"width:100%;max-width:100%;overflow-x:auto;margin:28px 0;border:1px solid #dce5e9;border-radius:14px;background:#fff;box-shadow:0 10px 28px -16px rgba(24,47,60,.32);box-sizing:border-box\"><table style=\"width:100%;min-width:580px;border-collapse:separate;border-spacing:0;border:0;margin:0;font-size:15px;line-height:1.6;background:#fff\"><caption style=\"padding:20px;text-align:start;font-size:17px;line-height:1.5;font-weight:700;color:#173246;background:#fff\">Search Approaches in the Dovecot Environment by Operational Model<\/caption><thead><tr><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Approach<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Index Location<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Additional infrastructure<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Operating Limit<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Product Line<\/th><\/tr><\/thead><tbody><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">No AGV<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">No search index<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">None<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Text and body searches are performed sequentially<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Dovecot CE<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">fts-flatcurve<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Per mailbox in the Dovecot index path<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Xapian, version 1.4 or later<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Schedule local index storage, monitoring, and reindexing; substring search is disabled by default<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Dovecot CE<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Solr<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Separate Search Service<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Solr Operation<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Manage Additional Services and Their Availability<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Dovecot CE<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Dovecot Pro FTS<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Designed for Object Storage<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Pro-Environment<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Do not equate with CE-Flatcurve<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Dovecot Pro<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For local search indexes, <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">fts-flatcurve<\/code> An option if the environment provides Xapian 1.4 or later. The driver stores index data for each mailbox in the Dovecot index path and supports relevance scoring. Substring searches can be enabled using <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">fts_flatcurve_substring_search = no<\/code> However, they are disabled by default and require significantly more index memory when enabled. Flatcurve does not support fuzzy search.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">So please rate the <strong style=\"font-weight:700;color:inherit\">Search Architecture<\/strong> based on mailbox sizes, storage type, and operating model, rather than a blanket ranking. <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">doveadm fts flatcurve stats<\/code> provides stored status data for the Flatcurve indices. This should be distinguished from <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">doveadm fts flatcurve check<\/code>: This command checks Xapian databases and attempts to fix basic errors, so it may alter their state. Rotating and removing indexes are also targeted maintenance tasks. Before performing such operations, plan for the scope of the work, the mailboxes affected, and the possible need to rebuild the indexes.  <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"sieve-proxy-und-sicherheit\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"sieve-proxy-und-sicherheit\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Check Sieves, Proxies, and Security Limits<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Sieve filters are a separate checkpoint during the Dovecot update because the extension is not part of the Dovecot core: Sieve and ManageSieve are provided by the separate Pigeonhole project. For installations built from source, Pigeonhole must be recompiled along with the new Dovecot version. Otherwise, the interpreter plugin will fail to load due to a version conflict.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For distribution-based installations, it is crucial that the Dovecot and Pigeonhole packages come from compatible package sources. Before the maintenance window, check which active user scripts, global scripts, and ManageSieve accounts are present. After the update, delivery, forwarding, vacation replies, and changes made via ManageSieve should be verified using a test account designated for this purpose; production filters are not a substitute for this test.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In proxy architectures, the <strong style=\"font-weight:700;color:inherit\">IMAP Compression<\/strong> special attention. When the configuration version is updated to 2.4.5, the default for <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">imap_compress_on_proxy<\/code> <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">yes<\/code>. This shifts the handling of compression to the proxy; according to the documentation, this setting belongs on the backend. This requires correctly defined <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">login_trusted_networks<\/code> as well as transparent trust boundaries between the proxy and the backend.  <\/p>\n<figure class=\"wp-block-image size-large wh-figure\" aria-describedby=\"wh-caption-detail2\" style=\"display:block;float:none;clear:both;width:100%;max-width:760px;margin:34px auto 40px;border:1px solid #dae5e9;border-radius:14px;overflow:hidden;background:#f5f8fa;box-shadow:0 10px 28px -17px rgba(24,47,60,.28);box-sizing:border-box\"><div class=\"wh-figure-media\" style=\"display:block;background:#eef3f5;line-height:0\"><img loading=\"lazy\" width=\"800\" height=\"534\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-proxy-vertrauensgrenzen-e0f80596-detail2-f9be61d862-1024x683.webp\" class=\"wp-image-21903\" alt=\"A technician checks server connections in a compact proxy and mail server environment.\" decoding=\"async\" srcset=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-proxy-vertrauensgrenzen-e0f80596-detail2-f9be61d862-1024x683.webp 1024w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-proxy-vertrauensgrenzen-e0f80596-detail2-f9be61d862-300x200.webp 300w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-proxy-vertrauensgrenzen-e0f80596-detail2-f9be61d862-768x512.webp 768w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-proxy-vertrauensgrenzen-e0f80596-detail2-f9be61d862-18x12.webp 18w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/dovecot-proxy-vertrauensgrenzen-e0f80596-detail2-f9be61d862.webp 1536w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" ><\/div><figcaption class=\"wh-caption\" id=\"wh-caption-detail2\" style=\"display:block;margin:0;padding:12px 18px 15px;border-top:1px solid #dce5e9;color:#506575;background:#f5f8fa;font-size:14px;line-height:1.55;text-align:start\">AI-generated stock image: Proxy paths and trust boundaries are part of the update verification process.<\/figcaption><\/figure><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Therefore, before adopting the new default, clarify the following: Which connections terminate at the proxy, which IP addresses should the backend treat as trustworthy, and on which system should the CPU load and data traffic resulting from compression occur? A change can only be properly evaluated if it aligns with the actual network architecture. It does not replace either TLS verification or robust access control between the involved systems.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">New authentication and experimental protocol features should not be enabled by default either. The release notes mention SCRAM mechanisms, including TLS channel binding, as well as SMTPUTF8, IMAP <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">UTF8=ACCEPT<\/code> and IMAP4rev2. SMTPUTF8 and UTF8=ACCEPT are required during the build <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">--enable-experimental-mail-utf8<\/code> and in the configuration <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">mail_utf8_extensions = yes<\/code>. Separately, IMAP4rev2 sets the build switch <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">--enable-experimental-imap4rev2<\/code> and <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">imap4rev2_enabled = yes<\/code> First, check client support, the delivery chain, and fallback behavior for each function individually before you implement it in the <strong style=\"font-weight:700;color:inherit\">Email hosting<\/strong> offer.  <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"betrieb-und-fehlersuche\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"betrieb-und-fehlersuche\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Operate Safely After the Update<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">An update is not complete until it has passed technical tests; it is not complete simply because the package installation was successful. During the maintenance window, first check whether the service starts and whether the logs show any configuration, plugin, or permission errors. Next, log in and access the mailbox using a test account. Be sure to check at least the folder list, message selection, reading, and a controlled delivery to ensure that the IMAP server is not only accessible but also functional.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Validate Sieve and Quota as separate functions. A successful IMAP login does not prove that Pigeonhole has been loaded, nor that quota limits are being determined correctly. Therefore, test a harmless filter rule and a delivery that comes close to a specified quota limit in an isolated test mailbox. This allows you to identify errors in plugins, permissions, and the connection to the respective quota backend without intentionally overloading customer mailboxes.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">When full-text search is enabled, monitoring the index status and search queries is part of the post-processing. To get a quick overview of existing Flatcurve index data, use <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">doveadm fts flatcurve stats<\/code>. The subcommand <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">check<\/code> This must be clearly distinguished from the following: It checks Xapian databases and attempts to correct basic errors; therefore, it is not a guaranteed read-only diagnostic tool. Just like rotation or removing indexes, use it only as a scheduled maintenance task for specific mailboxes, and take into account possible changes in status as well as the need to rebuild the index.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">With upstream proxies, you also control the entire <strong style=\"font-weight:700;color:inherit\">Traffic route<\/strong>: Does the login request reach the expected backend, are the client IP and trusted network handled correctly, and do no unexpected compression or TLS issues arise? To verify this, compare the logs of the involved components over time. A few successful logins are not sufficient if multiple backends, different client networks, or separate TLS termination are involved.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For troubleshooting, the Dovecot documentation recommends using a minimal configuration. To do this, work step by step in a secure environment to narrow down the components that reproduce the error, rather than exposing the entire production configuration. <strong style=\"font-weight:700;color:inherit\">Warning:<\/strong> Information such as effective configurations may contain infrastructure details or sensitive information. Therefore, do not share it in its entirety in tickets, forums, or public documents; instead, redact it as needed.  <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"update-entscheidung-treffen\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"update-entscheidung-treffen\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">When It's Worth Updating Dovecot<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Updating Dovecot to CE 2.4.5 is not just a matter of functionality and architecture. The release notes list numerous <strong style=\"font-weight:700;color:inherit\">Critical security fixes<\/strong> including, among other things, IMAP commands, submission, OAuth checks, dsync, authentication, and compression. Administrators should therefore check as soon as possible whether their installation is affected and determine which package or backport version their distribution uses to provide the fixes. The upstream version alone does not indicate that a distribution package is unpatched, nor does it mean that a generic immediate upgrade without a migration check would be safe.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In addition to this security assessment, an update is justifiable if it is driven by a necessary compatibility requirement, a specific operational need, or a modernization that can be verifiably tested. This may include controllable version switches for configuration and storage. However, the package version alone is not a sufficient basis for a decision: mailbox format, authentication, quota, Sieve, search, and proxy topology determine how significant the migration effort actually is.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Prioritizing an upgrade to 2.3 is particularly advisable when the security situation and the available distribution version suggest an update, and the migration can be tested on a test system. However, the storage level remains deliberately conservative: New storage formats should only be enabled once a rollback to older Dovecot versions is no longer planned. This applies, among other things, to the thread index, which was changed in version 2.4.5 and is rebuilt during the next threading query.   <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Additional features are separate architectural decisions. <strong style=\"font-weight:700;color:inherit\">Flatcurve<\/strong> It makes sense to consider this option if news search is used regularly and local index storage, Xapian dependency, monitoring, and reindexing fit the operational model. The documentation classifies the driver as a local, Xapian-based full-text search index; this does not imply a blanket recommendation over Solr or against using FTS.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Experimental UTF-8 and IMAP4rev2 options are justified only if there is a proven need throughout the entire chain\u2014from the mail client, through submission or delivery, to IMAP access. Without this prerequisite, enabling these options primarily increases the verification effort. The same applies to new authentication mechanisms: An existing feature in the release does not replace the need to verify the clients in use, the TLS configuration, and the authentication source.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Based on the published CE information, it is not possible to provide a release date, a list of features, or a migration path for Dovecot 3. The current stable release is CE 2.4.5; references in the development documentation or in the branch <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">main<\/code> are not a published product status or roadmap. Therefore, plan based on the 2.4 line that is actually available, keep it separate from Dovecot Pro, and evaluate future announcements only once they have been officially released.   <\/p>\n<\/section><section class=\"wh-sources\" style=\"margin:40px 0 0;padding:24px 0 0;border-top:1px solid #dce5e9;color:#596b7b;font-size:14px;line-height:1.65\"><h2 style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Sources and Current State of Knowledge<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Status of the research: <time datetime=\"2026-10-21\">2026-10-21<\/time><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Status of the research: October 21, 2026. Dovecot CE 2.4.5 is the stable release documented in the available official sources. No published CE 3.0 roadmap has been documented.<\/p><div class=\"wh-source-urls\"><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/github.com\/dovecot\/core\/releases<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/doc.dovecot.org\/2.4.2\/installation\/upgrade\/2.3-to-2.4.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/doc.dovecot.org\/2.4.5\/installation\/upgrade\/2.4-to-2.4.x.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/doc.dovecot.org\/2.4.2\/installation\/upgrade\/overview.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/doc.dovecot.org\/2.4.0\/core\/plugins\/fts_flatcurve.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/doc.dovecot.org\/2.4.5\/issues.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/doc.dovecot.org\/2.4.5\/core\/man\/doveadm-fts.1.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/doc.dovecot.org\/2.4.0\/core\/plugins\/fts.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/doc.dovecot.org\/2.4.5\/installation\/sieve.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/doc.dovecot.org\/2.4.5\/core\/summaries\/settings.html<\/span><\/p><\/div><\/section><\/div>","protected":false},"excerpt":{"rendered":"<p>Dovecot CE 2.4.5 is the current stable release. This article explains the migration from 2.3, version and storage switches, Flatcurve, and the limitations of unconfirmed statements regarding Dovecot 3.<\/p>","protected":false},"author":1,"featured_media":22060,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[791],"tags":[],"class_list":["post-21896","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-emailserver-administration-anleitungen"],"acf":[],"_links":{"self":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21896","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/comments?post=21896"}],"version-history":[{"count":5,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21896\/revisions"}],"predecessor-version":[{"id":21904,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21896\/revisions\/21904"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media\/22060"}],"wp:attachment":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media?parent=21896"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/categories?post=21896"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/tags?post=21896"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}