{"id":21879,"date":"2026-11-01T08:00:00","date_gmt":"2026-11-01T07:00:00","guid":{"rendered":"https:\/\/webhosting.de\/?p=21879"},"modified":"2026-10-30T12:49:29","modified_gmt":"2026-10-30T11:49:29","slug":"postfix-310-update-tlsrpt-mail-server-linux","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/postfix-310-update-tlsrpt-mailserver-linux\/","title":{"rendered":"Postfix 3.10: Updates, TLSRPT, and the Road to 3.11"},"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\">Postfix 3.10 is still supported, but it is no longer the current stable development branch: 3.11 has taken over that role. For existing Linux mail servers, therefore, a controlled <strong style=\"font-weight:700;color:inherit\">Postfix Update<\/strong> with package and changelog checks, configuration validation, and process activation monitoring. TLSRPT can expand visibility into TLS-related delivery errors, provided that the Postfix package being used was built with the necessary support and the separate reporting infrastructure is in place. Whether patch maintenance within version 3.10 is sufficient or whether upgrading to 3.11 makes sense depends on the functional requirements and the operating environment.  <\/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=\"#postfix-310-einordnung\" 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\">Putting Postfix 3.10 in the Right Historical Context<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#mta-rollen-und-ports\" 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\">MTA Role, SMTP Ports, and System 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=\"#tlsrpt-grundlagen\" 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\">TLSRPT Enhances Secure Email Delivery<\/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-ablauf-310\" 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\">Prepare for the Postfix update in the 3.10 branch<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#tlsrpt-konzeption-und-dns\" 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 TLSRPT with DNS and Reporting Infrastructure<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#submission-datenschutz-und-tls\" 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\">Protect Submissions, Carefully Evaluate TLS Options<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#patchstand-und-fehlerbilder\" 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 patch status and known issues<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#tlsrpt-betrieb-und-auswertung\" 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\">Correctly Evaluating TLSRPT Reports During Operation<\/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-oder-legacy-pflege\" 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\">Maintain 3.10 or switch to 3.11<\/a><\/div>\n<\/div><\/nav><section class=\"wh-section\" aria-labelledby=\"postfix-310-einordnung\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"postfix-310-einordnung\" 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\">Putting Postfix 3.10 in the Right Historical Context<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">As of the date of this research, October 20, 2026, Postfix 3.10 is not the current stable release; that role is held by Postfix 3.11. The vendor lists 3.10 as <strong style=\"font-weight:700;color:inherit\">Legacy Branch<\/strong>, but continues to provide bug fixes and security updates for it. In the official announcements, Postfix 3.10.14, released on September 7, 2026, is listed as the most recent patch version available for this branch.   <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">This classification distinguishes between two different types of updates. A maintenance update\u2014such as from 3.10.8 to a newer 3.10 patch\u2014maintains the selected feature branch and incorporates its fixes. An upgrade to 3.11, on the other hand, switches the development branch and must therefore be tested for changes in functionality, configuration compatibility, extensions, and operational workflows. A higher major and minor branch is not automatically the appropriate course of action for every production system.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For Linux packages, in addition to the visible Postfix version, check the package metadata, the changelog, and the security advisories from the operating system vendor. Determine from these sources which fixes this specific package contains and whether the vendor documents backports. The upstream announcement, on the other hand, describes the Postfix release and does not reflect a distribution\u2019s general backport policy.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For maintenance planning, this means: First, document the installed package version, the repository channel, and any local customizations. Then, compare these with the fixes listed by the operating system vendor for this package. Only this comparison will reveal whether there is a pending <strong style=\"font-weight:700;color:inherit\">Postfix Update<\/strong> whether an upgrade to 3.10 is required, or whether a planned upgrade to 3.11 would provide additional technical benefits. Section 3.10.14 serves as an upstream reference point, not as installation instructions for a specific Linux system.  <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"mta-rollen-und-ports\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"mta-rollen-und-ports\" 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\">MTA Role, SMTP Ports, and System Limits<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Postfix is a <strong style=\"font-weight:700;color:inherit\">Mail Transfer Agent<\/strong> (MTA). It accepts emails via SMTP, determines how to process them based on its routing and policy configuration, and forwards messages to other mail servers or local delivery paths. Postfix thus forms the transport layer of a mail server running on Linux. However, its configuration does not automatically determine how users access their mailboxes or how suspicious content is evaluated.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">An IMAP or POP3 server provides mailboxes for email clients and is a separate component from SMTP transport. Similarly, Postfix functions do not replace a complete spam or virus filtering solution: such systems must be properly integrated, maintained, and monitored as needed. This distinction is important in practice because a successful SMTP test does not prove that a mailbox can be retrieved or that content is properly checked.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Port 25 is typically used for SMTP traffic between mail servers and, therefore, for public MX operations. Ports 587 and 465, on the other hand, are intended for mail delivery by email clients, usually with authentication and their own service definition. Postfix does not merely treat these roles differently from an organizational standpoint: some settings should not\u2014or indeed must not\u2014apply across the board to all SMTP services.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Before making any changes, you'll need administrative privileges, a recoverable backup of the Postfix configuration, and a maintenance window that accommodates the queue, delivery deadlines, and connected applications. Also, note whether the server sends outgoing mail, receives mail as a public MX, or offers client delivery. These <strong style=\"font-weight:700;color:inherit\">Termination of Employment<\/strong> Prevents a data protection decision intended for submission from inadvertently changing the publicly accessible port 25.  <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"tlsrpt-grundlagen\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"tlsrpt-grundlagen\" 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\">TLSRPT Enhances Secure Email Delivery<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Postfix 3.10 offers optional TLSRPT support in the SMTP client. Domains can publish a recipient for aggregated TLS reports via DNS; RFC 8460 allows for email addresses and HTTPS endpoints. Postfix reports only the success or failure of TLS handshakes, with at most one final status per SMTP connection. Failed connection attempts and terminations before or after the TLS handshake are not logged.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">However, the version number 3.10 alone does not prove that an installed Postfix package can actually use TLSRPT. The feature requires that Postfix be built with a TLSRPT client library that supports it and the build option <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">USE_TLSRPT<\/code> was created. Before planning the configuration, you must therefore check\u2014using the package documentation, the listed build characteristics, and available add-on packages\u2014whether your distribution includes this support.   <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">TLSRPT complements mechanisms that actually affect the TLS security of a delivery. STARTTLS enables the negotiation of transport encryption. DANE uses TLSA records and relies on DNSSEC for its security assumptions; MTA-STS publishes a policy specifying expected TLS properties. If a mandatory DANE or MTA-STS requirement fails, TLSRPT can provide downstream notifications of such errors. However, it does not itself enable encryption or certificate validation.   <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">There are two distinct roles to consider here. The receiving domain publishes a <strong style=\"font-weight:700;color:inherit\">rua endpoint<\/strong> and operates or commissions the monitored receipt and analysis of incoming reports. A reporting MTA, on the other hand, requires a properly configured and activated Postfix instance, as well as a separate infrastructure that collects, retrieves, aggregates, and sends reports. These two roles can be organizationally separate; a publishing domain owner does not have to generate TLSRPT reports on the same system.   <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A TLS policy plugin is therefore not generally part of every TLSRPT report chain. Postfix supports DANE natively. A suitable plugin becomes particularly relevant when the sending MTA includes MTA-STS policy information via <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">smtp_tls_policy_maps<\/code> integrates. Postfix 3.10 extends the responses from such a plugin to include TLSRPT-related attributes; however, this does not mean that every installation requires a plugin, nor that TLSRPT is included in every 3.10 package.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">TLSRPT is also not a real-time monitoring tool. The Postfix documentation states that it takes an average of about twelve hours for an error message to arrive and therefore explicitly distinguishes these reports from real-time fault monitoring. For ongoing delivery issues, queue checks, log analysis, and alerts remain necessary. TLSRPT primarily helps identify recurring patterns and policy issues across multiple delivery attempts.  <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"update-ablauf-310\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"update-ablauf-310\" 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\">Prepare for the Postfix update in the 3.10 branch<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Updating Postfix 3.10 is a maintenance task with a clear starting point: You update an existing legacy branch to the patch level provided by your distribution. Before proceeding, back up the Postfix configuration and schedule a maintenance window. Also, check whether the server handles outgoing mail, MX traffic, or submission, as monitoring and contingency planning depend on this.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">First, determine the Postfix version that is installed or that is reported by the program you ran, and explicitly document it in <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">main.cf<\/code> specified parameters. The first two commands are used to assess the current status. <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">postfix check<\/code> In contrast, this is an administrative maintenance command: It checks, in particular, the ownership and access permissions of files and directories and can create missing directories. Therefore, run it with the appropriate administrative privileges and do not assume that the file system is guaranteed to be unchanged.<\/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\">postconf mail_version\npostconf -n\npostfix check<\/code><\/pre><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The issue of <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">postconf mail_version<\/code> Specifies the version of the Postfix program base that is being called. <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">postconf -n<\/code> Displays parameters with explicit <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">name=value<\/code>-entries in <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">main.cf<\/code>. This may also include settings whose values match the current built-in default; therefore, the output is not reliable evidence of an actual deviation from the default. Furthermore, default values may change after a version update, while a previously set entry remains in place.<\/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\/postfix-update-konfiguration-sichern-be8cb534-detail1-899d87676d-1024x683.webp\" class=\"wp-image-21887\" alt=\"Close-up of a Linux server with backup media and documentation before maintenance.\" decoding=\"async\" srcset=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/postfix-update-konfiguration-sichern-be8cb534-detail1-899d87676d-1024x683.webp 1024w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/postfix-update-konfiguration-sichern-be8cb534-detail1-899d87676d-300x200.webp 300w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/postfix-update-konfiguration-sichern-be8cb534-detail1-899d87676d-768x512.webp 768w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/postfix-update-konfiguration-sichern-be8cb534-detail1-899d87676d-18x12.webp 18w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/postfix-update-konfiguration-sichern-be8cb534-detail1-899d87676d.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 illustrating the importance of backing up and taking inventory before a Postfix update.<\/figcaption><\/figure><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Also <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">postfix check<\/code> This is not a complete validation of the mail server configuration. The command may report issues with directory or file permissions and create missing directories, but it does not comprehensively assess the technical correctness of all parameters. Certificate chains, external maps, DNS dependencies, filters, authentication, and the integration of connected services must be checked separately.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Use your distribution's supported update method to update the package. Check the package metadata, changelog, and security advisories to see which fixes and any backports the specific package includes. Compare this information with the upstream announcements. Do not assume that a patch is missing based solely on a truncated version string.<\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"Update Checklist for Existing Postfix 3.10 Installations\" 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\">Update Checklist for Existing Postfix 3.10 Installations<\/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\">Test step<\/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\">Purpose<\/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\">Evaluate the result<\/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\">Next step<\/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\">Save 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\">Allow for relapse and reconciliation<\/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\">The fuse is legible and assigned to the maintenance level<\/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\">Release the update only after that<\/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\">Run `postconf mail_version`<\/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\">Record the installed or queried software base<\/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\">Version information documented<\/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\">Compare Package Status and Change Log<\/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\">Run `postconf -n`<\/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\">Document explicit main.cf settings<\/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\">Set parameters and possible version-dependent defaults are recorded<\/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 Local Settings from a Technical Perspective<\/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\">Run a Postfix check in administrative mode<\/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 Permissions and Required Directories<\/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\">Document warnings or created directories<\/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\">Examine the causes and conduct further validation 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\">Read the package metadata and changelog<\/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\">Classify the corrections included<\/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\">Backports or relevant changes are visible<\/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\">Use a Supported Distribution Channel<\/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\">Check Activation Status and Logs<\/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\">Determine whether updated processes are running<\/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 package has reloaded or restarted the service, or old processes are still running<\/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\">If necessary, perform the reload or restart specified by the distribution and package<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The specific requirement for process updates, as documented by Postfix, applies to upgrades from an older development branch to Postfix 3.10.0. Due to a change in the internal delivery agent protocol, at least <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">postfix reload<\/code> or a stop followed by a start is required; otherwise, delivery agents may encounter an unexpected <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">smtputf8<\/code>-Warning attribute. This reasoning cannot be applied across the board to every subsequent patch update within version 3.10.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For maintenance updates within the 3.10 branch, check instead whether the package manager has already reloaded or restarted the service as specified by the distribution, and whether the running processes correspond to the updated state. If that is not the case, use the reload or restart provided by the distribution and the package. Then check the queue and logs in the maintenance window, rather than assuming a specific activation command regardless of the package\u2019s behavior.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"tlsrpt-konzeption-und-dns\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"tlsrpt-konzeption-und-dns\" 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 TLSRPT with DNS and Reporting Infrastructure<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">With TLSRPT, the role of the domain receiving reports and the role of a reporting MTA must be configured separately. A domain that wishes to receive reports about deliveries to its own infrastructure publishes a <strong style=\"font-weight:700;color:inherit\">rua endpoint<\/strong> in the DNS and ensures that its receipt, protection, storage, and analysis are managed in a binding manner. The TXT record thus specifies where other sending MTAs should send their aggregated reports.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">An MTA that is supposed to generate TLSRPT reports on its own requires, regardless of that, a Postfix package that includes a TLSRPT client library and <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">USE_TLSRPT<\/code> was built. The \"Postfix 3.10\" specification only confirms the branch from which the integration is available; it does not indicate the build characteristics of a specific binary package. Therefore, check the package documentation, build information, and available additional packages for your distribution before planning to use this feature.   <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">On each participating Postfix system, a local <strong style=\"font-weight:700;color:inherit\">Collector<\/strong> It receives events passed by the integrated TLSRPT library via a local Unix domain socket. Separately, the fetcher, central aggregation, and report generator can be operated: They retrieve the collected data, generate the specified summaries, and send reports to the destinations published by recipient domains. These downstream components can be centralized on other systems; however, this does not replace the local collector on the respective Postfix system.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A <strong style=\"font-weight:700;color:inherit\">Policy Plugin<\/strong> is only required in certain sender-side scenarios. If the MTA uses MTA-STS policy information via <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">smtp_tls_policy_maps<\/code>, the plugin used for this purpose must support TLSRPT-related attributes. DANE is supported by Postfix itself. Therefore, neither the DNS record of a receiving domain nor the report processing by a properly configured MTA generally requires an MTA-STS plugin. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The following entry explains only the DNS syntax for a report recipient. <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">example.invalid<\/code> is intentionally not a productive domain and must not be copied as-is. The tag <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">v=TLSRPTv1<\/code> characterizes the process; <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">rua<\/code> Specifies a destination for reports here. RFC 8460 allows HTTPS endpoints in addition to email. <\/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>Code<\/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-dns\" style=\"font:inherit;color:inherit;background:transparent;padding:0;border:0;white-space:inherit\">_smtp._tls.example.invalid. IN TXT &quot;v=TLSRPTv1; rua=mailto:tlsrpt@example.invalid&quot;<\/code><\/pre><\/div><div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"Separate components for TLSRPT reception and TLSRPT transmission\" 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\">Separate components for TLSRPT reception and TLSRPT transmission<\/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\">Perspective<\/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\">Component<\/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\">Task<\/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\">Typical gap<\/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\">Destination Domain<\/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\">DNS TXT Record<\/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\">Publishes the report recipient for deliveries to this domain<\/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\">Record does not point to any managed destination<\/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\">Destination Domain<\/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\">rua Reception and Evaluation<\/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\">Accepts reports, safeguards them, and assigns actions<\/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\">No Liability or Retention Policy<\/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\">Reporting MTA<\/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\">Compiled Postfix package and TLSRPT client library<\/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\">Enable the generation and passing of TLSRPT events<\/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 3.10 is considered to have built-in support<\/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\">Each participating Postfix system<\/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\">Local Collector on a Unix domain socket<\/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\">Receives events passed locally by the TLSRPT library<\/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 collector is missing, or its local socket is unreachable<\/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\">Centralized Report Processing<\/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\">Fetcher, Aggregation, and Report Generator<\/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\">Retrieves events from Collectors, summarizes them, and sends reports<\/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\">Key components or their connections to local collectors are missing<\/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\">MTA-STS Special Case<\/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\">Appropriate smtp_tls_policy_maps plugin<\/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\">Provides MTA-STS policy information and TLSRPT attributes<\/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\">Plugin is mistakenly treated as subject to the general TLSRPT requirement<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For TLSRPT reports, Postfix 3.10 defines the header <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">TLS-Required: no<\/code>, so that the report can fall back to the \u201emay\u201c TLS security level during transmission. This strictly limited exception prevents an error report from failing due to strict TLS requirements. It is not a directive to lower TLS requirements for regular business or user emails. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"submission-datenschutz-und-tls\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"submission-datenschutz-und-tls\" 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\">Protect Submissions, Carefully Evaluate TLS Options<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The setting <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">smtpd_hide_client_session<\/code> Applies to authenticated mail client submissions. When enabled, the SMTP server generates \"Received:\" headers without including information from the client session. Depending on the session, this can hide information such as the client hostname and IP address, TLS session data, SASL login information, and SMTP log details from the header. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Sort these <strong style=\"font-weight:700;color:inherit\">Privacy feature<\/strong> a dedicated submission service definition for port 587 or 465, rather than applying it globally across the board in <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">main.cf<\/code> to enable it. The public Port 25 MTA plays a different role in server-to-server transport. The Postfix documentation specifies the default value there to ensure compliance with RFC 5321. <\/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\/postfix-submission-datenschutz-be8cb534-detail2-92e2625488-1024x683.webp\" class=\"wp-image-21888\" alt=\"A person sets up an email client connection on a laptop for the submission.\" decoding=\"async\" srcset=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/postfix-submission-datenschutz-be8cb534-detail2-92e2625488-1024x683.webp 1024w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/postfix-submission-datenschutz-be8cb534-detail2-92e2625488-300x200.webp 300w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/postfix-submission-datenschutz-be8cb534-detail2-92e2625488-768x512.webp 768w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/postfix-submission-datenschutz-be8cb534-detail2-92e2625488-18x12.webp 18w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/postfix-submission-datenschutz-be8cb534-detail2-92e2625488.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 illustrative image depicting the separate handling of mail client delivery and public SMTP.<\/figcaption><\/figure><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The decision therefore concerns not only privacy, but also traceability and service boundaries. For authenticated clients, reducing unnecessary metadata may be appropriate. On a public MX server, however, the same setting would violate the documented expectation regarding \u201cReceived:\u201d information. Therefore, consider using separate services, listeners, and their respective parameters instead of a single global rule. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Postfix 3.10.0 also includes an adaptation for OpenSSL 3.5 and its group syntax for post-quantum cryptography. If you want to delegate the selection of groups entirely to the centrally managed OpenSSL configuration, 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\">tls_eecdh_auto_curves<\/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\">tls_ffdhe_auto_groups<\/code> Both must be set to empty. Only this combined setting allows OpenSSL to make the selection; Postfix does not implement the new OpenSSL syntax on its own. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Clearing both automatic parameters is a <strong style=\"font-weight:700;color:inherit\">Special Case<\/strong> For centrally managed cryptographic settings; this is not a general hardening recommendation. This approach is only suitable if the actual OpenSSL configuration is known, versioned, and tested. Without this control, shifting the selection may mask misconfigurations or produce unexpected TLS behavior; in such cases, the explicit Postfix settings remain more traceable. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"patchstand-und-fehlerbilder\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"patchstand-und-fehlerbilder\" 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 patch status and known issues<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The version number 3.10 alone does not describe a uniform technical state. What matters are the specific patch version, the changelog information for the distribution package, and, if applicable, backported fixes. Postfix 3.10.14 was announced on September 7, 2026, as a legacy release along with other maintained branches. This does not mean that every Linux package already includes this upstream version. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A specific example is Postfix 3.10.6: This release fixed an issue related to <strong style=\"font-weight:700;color:inherit\">TLS Required: no<\/strong> and client-side TLS wrapper mode. The previous implementation could have compromised such connections; the fix treats them with the \u201eencrypt\u201c security level. Users of SMTPS wrapper mode should therefore check their patch status and the actual transmission path used, rather than assuming the same behavior based on \u201c3.10.\u201d. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The release notes for 3.10.14 mention, among other things, fixes and hardening measures for an SMTP smuggling scenario involving smtpd_proxy_filter. This is not a blanket statement that every mail server is affected: The parameter is disabled by default, and its relevance depends on the local configuration as well as the upstream or connected filtering architecture. Therefore, first check whether this feature is actually in use. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">If delivery appears abnormal, there is a logical order for troubleshooting: First, check for significant deviations and verify the configuration; then, verify that the system reloaded successfully after an upgrade. Next, examine the queue and logs for recurring TLS, connection, or deferred messages. A systematic guide to <a href=\"https:\/\/webhosting.de\/en\/postfix-logs-analysis-mailserver-analysis-logfiles-guide-optimization\/\">Analysis of Postfix Logs<\/a> helps map individual events to a queue ID and its delivery attempt.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><strong style=\"font-weight:700;color:inherit\">Warning:<\/strong> A version update is no substitute for a root cause analysis. A reload does not resolve invalid certificate chains, DNS errors, or incorrect routing rules. Conversely, failing to perform a reload after an upgrade can mask changes to processes or configurations that have taken effect during operation. Therefore, document the patch status, package source, time of activation, and observed log messages together.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"tlsrpt-betrieb-und-auswertung\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"tlsrpt-betrieb-und-auswertung\" 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\">Correctly Evaluating TLSRPT Reports During Operation<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">TLSRPT reports are delayed and are not a substitute for real-time monitoring. The Postfix documentation states that it takes an average of about twelve hours for an error report to arrive. In Postfix, the recorded results pertain to TLS handshakes; connection establishment errors and terminations occurring before or after the handshake are not included. For urgent incidents, queue monitoring, log analysis, and alerting remain necessary. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Reuse also limits the count: A reused SMTP connection does not trigger another TLS handshake. For resumed TLS sessions, Postfix 3.10 skips logging by default; the `smtp_tlsrpt_skip_reused_handshakes` setting determines this behavior. Report aggregates are therefore neither a complete count of all SMTP connections nor a message or delivery rate. Evaluate error types, recipient domains, time periods, and recurring patterns in conjunction with the server logs. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Simply delivering a report technically does not provide any benefit. Determine in advance who is responsible for the RUA recipient, who receives and stores the reports, and how long the data will be retained. Since reports may contain information about TLS sessions, access rights, data protection requirements, and a deletion procedure must be included in the operational concept. An escalation policy for recurring errors should also be in place.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The analysis therefore combines two levels: TLSRPT shows aggregated trends over a period of time, while mail server logs provide details on the specific course of individual delivery attempts. For ongoing monitoring, the <a href=\"https:\/\/webhosting.de\/en\/postfix-logs-analysis-guide-mailserver-logfile-optimization\/\">Practical Guide to Postfix Log Monitoring<\/a> Reports on methods for classifying error messages and queues. Automatic alerts should respond to real-time operational data, not wait until TLSRPT aggregates have been received.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">If there is no designated recipient, no secure storage location, and no regular review in place, the TLSRPT publication should be planned first rather than activated hastily. <strong style=\"font-weight:700;color:inherit\">Reporting Responsibilities<\/strong> is part of the security function: Only by assigning an error to the appropriate department can a traceable response be ensured\u2014for example, to an expired MTA-STS policy or problems with TLSA data.  <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"upgrade-oder-legacy-pflege\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"upgrade-oder-legacy-pflege\" 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\">Maintain 3.10 or switch to 3.11<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The choice between continuing to apply patches and switching branches depends on the initial situation and operational goals. As of this writing, Postfix 3.10 remains a supported legacy branch, while 3.11 is the stable development branch. Regular fixes within the 3.10 branch are therefore advisable for existing installations; however, they are not equivalent to a feature upgrade to 3.11.  <\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"Decision Matrix for Postfix 3.10 and 3.11\" 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\">Decision Matrix for Postfix 3.10 and 3.11<\/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\">Background<\/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\">Measure<\/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\">Benefit<\/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\">Dependencies and Risk<\/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\">Checkpoint<\/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\">A Well-Maintained Postfix 3.10 System<\/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\">Apply the patch status provided by the operating system<\/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\">Bug fixes and security patches with limited functional changes<\/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\">The package may contain backports; be sure to enable updated processes and account for local customizations<\/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\">Compare the distribution changelog and package behavior with the upstream announcement<\/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\">New Mail Server or System Upgrade<\/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\">Evaluating Postfix 3.11<\/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\">Access to features explicitly documented there<\/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\">Migration and compatibility testing 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:#f4f7f9;color:#294252\">Create a testing and rollback plan for configuration and integrations<\/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\">The domain should receive TLSRPT reports<\/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\">Plan the rua target and its operation first<\/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\">Reports from other MTAs can be accepted in an organized manner<\/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\">A DNS record alone does not replace either reception or evaluation<\/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\">Define responsibilities for receiving, safeguarding, and evaluating<\/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\">In-house MTA to send TLSRPT reports<\/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 the build characteristics of the Postfix package as well as the collector, fetcher, and reporter infrastructure<\/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\">Aggregated results of the recorded TLS handshakes<\/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\">Postfix 3.10 does not include built-in TLSRPT support on its own; a suitable policy plugin may also be required for MTA-STS<\/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 the package documentation, TLSRPT library, event collection, and report distribution<\/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\">Less client metadata upon submission<\/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 `smtpd_hide_client_session` on a per-service basis<\/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\">Abbreviated session information for MUA submission<\/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 generalize this to the public Port 25 MTA<\/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\">Check the service definition and port mapping<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Upgrading to 3.11 is objectively justified primarily when its features or long-term target state are required. REQUIRETLS and JSON output from certain management tools are documented as features of the newer branch and should not be planned for as Postfix 3.10 features. Before switching branches, configuration parameters, connected filters, authentication, and automation must be checked for compatibility. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For a stable 3.10 system that doesn't require new features, <strong style=\"font-weight:700;color:inherit\">ongoing patch maintenance<\/strong> the most appropriate immediate action. It nevertheless requires a controlled process involving backups, package verification, validation, verification of process activation, and monitoring. Switching branches, on the other hand, requires a technical justification and a scheduled maintenance window; a higher version number alone is not a sufficient criterion for making this decision.  <\/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-20\">2026-10-20<\/time><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Research and version status: October 20, 2026. Postfix 3.11 is the stable development branch; Postfix 3.10 is maintained as a legacy branch. The most recent 3.10 patch version mentioned in the official announcements is 3.10.14, released on September 7, 2026.<\/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:\/\/www.postfix.org\/announcements.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:\/\/www.postfix.org\/TLSRPT_README.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:\/\/www.postfix.org\/announcements\/postfix-3.11.7.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:\/\/www.postfix.org\/postconf.5.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:\/\/www.rfc-editor.org\/info\/rfc8460\/<\/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:\/\/www.postfix.org\/announcements\/postfix-3.10.0.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:\/\/www.postfix.org\/announcements\/postfix-3.10.6.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:\/\/www.postfix.org\/features.html<\/span><\/p><\/div><\/section><\/div>","protected":false},"excerpt":{"rendered":"<p>Postfix 3.10 is still being maintained, but it is a legacy branch. This article explains TLSRPT, secure update procedures, submission privacy, and the decision between continuing to apply patches and upgrading to Postfix 3.11.<\/p>","protected":false},"author":1,"featured_media":22054,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[792],"tags":[],"class_list":["post-21879","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-postfix-emailserver-administration-anleitungen"],"acf":[],"_links":{"self":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21879","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=21879"}],"version-history":[{"count":7,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21879\/revisions"}],"predecessor-version":[{"id":21889,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21879\/revisions\/21889"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media\/22054"}],"wp:attachment":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media?parent=21879"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/categories?post=21879"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/tags?post=21879"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}