<h1><img src="postfix-logo.jpg" width="203" height="98" ALT="">Postfix
Replacements for Deprecated Features</h1>
<hr>
<h2>Purpose of this document </h2>
<p> This document describes Postfix features that are deprecated
(will be removed) or that have already been removed. It also has
tips for making an existing Postfix configuration more future-proof.
</p>
<p> Overview: </p>
<ul>
<li> <a href="#why"> Why deprecate? </a>
<li> <a href="#process"> Deprecation process </a>
<li> <a href="#features"> Deprecated features </a>
</ul>
<h2> <a name="why"> Why deprecate? </a> </h2>
<p> Sometimes, a Postfix feature needs to be replaced with a different
one. To give an example: </p>
<ul>
<li> <p> The initial Postfix TLS implementation used multiple boolean
parameters: one parameter to enable opportunistic TLS (for example, "<a href="postconf.5.html#smtp_enforce_tls">smtp_enforce_tls</a> = yes") and one parameter to enable mandatory TLS
(for example, "smtp_require_tls = yes"). </p>
<li> <p> As we added support more features such as fingerprint,
dane, and so on, we decided not to add more boolean parameters.
Instead we introduced one configuration parameter to select from
multiple deployment models (for example, <a href="postconf.5.html#smtp_tls_security_level">smtp_tls_security_level</a> =
may | encrypt | dane, etc...). </p>
<p> Having both the "old" and "new" way to configure Postfix is
convenient for existing Postfix installations, because their
configuration does not break after an upgrade to a new version.
Unfortunately, there are also disadvantages. Having multiple ways
to do similar things is not only confusing for newcomers, it also
makes Postfix harder to change. </p>
<h2> <a name="process"> Deprecation process </a> </h2>
<p> The basic process steps are: </p>
<ol>
<li> <p> Inform humans that a feature will be removed, and suggest
replacements, in logging and documentation. </p>
<li> <p> Remove the feature, and update logging and documentation. </p>
</ol>
<p> Disclaimer: it has taken 20 years for some features to be
removed. This past is not a guarantee for the future. </p>
<h2> <a name="features"> Deprecated features </a> </h2>
<p> The table summarizes removed or deprecated features and
replacements. Click on the "obsolete feature" name for a more
detailed description. </p>
<blockquote>
<table border="1">
<tr> <th> Obsolete feature name </th> <th> Warning as <br> of version
</th> <th> Removed <br> in version </th> <th> Replacement </th>
</tr>
<h3> <a name="renamed"> Parameters that have been renamed for
consistency </a> </h3>
<p> The <a href="postconf.1.html">postconf(1)</a> command logs one or more of the following: </p>
<ul>
<li> support for parameter "<a href="postconf.5.html#authorized_verp_clients">authorized_verp_clients</a>" will be removed;
instead, specify "<a href="postconf.5.html#smtpd_authorized_verp_clients">smtpd_authorized_verp_clients</a>" </li>
<li> support for parameter "<a href="postconf.5.html#fallback_relay">fallback_relay</a>" will be removed; instead,
specify "<a href="postconf.5.html#smtp_fallback_relay">smtp_fallback_relay</a>" </li>
<li> support for parameter "<a href="postconf.5.html#lmtp_per_record_deadline">lmtp_per_record_deadline</a>" will be
removed; instead, specify "<a href="postconf.5.html#lmtp_per_request_deadline">lmtp_per_request_deadline</a>" </li>
<li> support for parameter "<a href="postconf.5.html#postscreen_blacklist_action">postscreen_blacklist_action</a>" will be
removed; instead, specify "<a href="postconf.5.html#postscreen_denylist_action">postscreen_denylist_action</a>" </li>
<li> support for parameter "<a href="postconf.5.html#postscreen_dnsbl_ttl">postscreen_dnsbl_ttl</a>" will be removed;
instead, specify "<a href="postconf.5.html#postscreen_dnsbl_max_ttl">postscreen_dnsbl_max_ttl</a>" </li>
<li> support for parameter "<a href="postconf.5.html#postscreen_dnsbl_whitelist_threshold">postscreen_dnsbl_whitelist_threshold</a>"
will be removed; instead, specify "<a href="postconf.5.html#postscreen_dnsbl_allowlist_threshold">postscreen_dnsbl_allowlist_threshold</a>"
</li>
<li> support for parameter "<a href="postconf.5.html#postscreen_whitelist_interfaces">postscreen_whitelist_interfaces</a>" will
be removed; instead, specify "<a href="postconf.5.html#postscreen_allowlist_interfaces">postscreen_allowlist_interfaces</a>" </li>
<li> support for parameter "<a href="postconf.5.html#smtpd_client_connection_limit_exceptions">smtpd_client_connection_limit_exceptions</a>"
will be removed; instead, specify "<a href="postconf.5.html#smtpd_client_event_limit_exceptions">smtpd_client_event_limit_exceptions</a>"
</li>
<li> support for parameter "<a href="postconf.5.html#smtp_per_record_deadline">smtp_per_record_deadline</a>" will be
removed; instead, specify "<a href="postconf.5.html#smtp_per_request_deadline">smtp_per_request_deadline</a>" </li>
<li> support for parameter "<a href="postconf.5.html#tlsproxy_client_level">tlsproxy_client_level</a>" will be removed;
instead, specify "<a href="postconf.5.html#tlsproxy_client_security_level">tlsproxy_client_security_level</a>" </li>
<li> support for parameter "<a href="postconf.5.html#tlsproxy_client_policy">tlsproxy_client_policy</a>" will be removed;
instead, specify "<a href="postconf.5.html#tlsproxy_client_policy_maps">tlsproxy_client_policy_maps</a>" </li>
<li> support for parameter "<a href="postconf.5.html#virtual_maps">virtual_maps</a>" will be removed; instead,
specify "<a href="postconf.5.html#virtual_alias_maps">virtual_alias_maps</a>" </li>
</ul>
<p> The above parameters have been renamed for consistency with other
parameters. For backwards compatibility, the old parameter values are
used as the default value for the new parameters, but they will
eventually be removed to eliminate clutter and confusion </p>
<p> To silence these warning messages, edit <a href="postconf.5.html">main.cf</a> or <a href="master.5.html">master.cf</a>,
and replace each obsolete parameter name with its replacement. </p>
<h3> <a name="cname_overrides_servername"> Obsolete CNAME override
for peer name configuration </a> </h3>
<p> The <a href="postconf.1.html">postconf(1)</a> command logs one of the following: </p>
<ul>
<li> support for parameter "<a href="postconf.5.html#smtp_cname_overrides_servername">smtp_cname_overrides_servername</a>" will be
removed; instead, do not specify
<li> support for parameter "<a href="postconf.5.html#lmtp_cname_overrides_servername">lmtp_cname_overrides_servername</a>" will be
removed; instead, do not specify
</ul>
<p> These features control whether a DNS CNAME record can override
the server peer name that Postfix will use for policy lookup or for
certificate verification. This behavior is disabled by default as of
Postfix 2.11, because it no longer solves a real problem. </p>
<h3> <a name="xxx_tls_enforce_peername"> Obsolete TLS peer name
match configuration </a> </h3>
<p> The <a href="postconf.1.html">postconf(1)</a> command logs one of the following: </p>
<ul>
<li> support for parameter "<a href="postconf.5.html#lmtp_tls_enforce_peername">lmtp_tls_enforce_peername</a>" will be
removed; instead, specify "<a href="postconf.5.html#lmtp_tls_security_level">lmtp_tls_security_level</a>"
<li> support for parameter "<a href="postconf.5.html#smtp_tls_enforce_peername">smtp_tls_enforce_peername</a>" will be
removed; instead, specify "<a href="postconf.5.html#smtp_tls_security_level">smtp_tls_security_level</a>"
</ul>
<p> There are similarly-named parameters and warnings for <a href="postscreen.8.html">postscreen(8)</a>
and <a href="tlsproxy.8.html">tlsproxy(8)</a>, but those parameters should rarely be specified
by hand. </p>
<p> Replace obsolete configuration with its replacement: </p>
<tr> <td> Enforce peer name match with server certificate </td>
<td> <i>xxx</i>_enforce_peername = yes </td> <td> <i>xxx</i>_security_level
= verify <br> <i>xxx</i>_security_level = secure </td> </tr>
<tr> <td> Disable peer name match with server certificate </td>
<td> <i>xxx</i>_enforce_peername = no </td> <td> <i>xxx</i>_security_level
= may <br> <i>xxx</i>_security_level = encrypt </td> </tr>
</table>
</blockquote>
<h3> <a name="disable_dns_lookups"> Obsolete DNS on/off configuration
</a> </h3>
<p> The <a href="postconf.1.html">postconf(1)</a> command logs the following: </p>
<ul>
<li> support for parameter "<a href="postconf.5.html#disable_dns_lookups">disable_dns_lookups</a>" will be removed; instead, specify "<a href="postconf.5.html#smtp_dns_support_level">smtp_dns_support_level</a>"
</ul>
<p> Replace obsolete configuration with its replacement: </p>
<tr> <td> To disable DNS lookups in the Postfix SMTP/LMTP client
</td> <td> <a href="postconf.5.html#disable_dns_lookups">disable_dns_lookups</a> = yes </td> <td> <a href="postconf.5.html#smtp_dns_support_level">smtp_dns_support_level</a>
= disabled </td> </tr>
<tr> <td> To enable DNS lookups in the Postfix SMTP/LMTP client </td> <td>
<a href="postconf.5.html#disable_dns_lookups">disable_dns_lookups</a> = no </td> <td>
Leave <a href="postconf.5.html#smtp_dns_support_level">smtp_dns_support_level</a> at the implicit default which is empty, unless
you need a higher support level such as DNSSEC. </td> </tr>
<p> The <a href="postconf.1.html">postconf(1)</a> command logs one of the following: </p>
<ul>
<li> support for parameter "<a href="postconf.5.html#lmtp_use_tls">lmtp_use_tls</a>" will be removed; instead, specify "<a href="postconf.5.html#lmtp_tls_security_level">lmtp_tls_security_level</a>"
<li> support for parameter "<a href="postconf.5.html#smtp_use_tls">smtp_use_tls</a>" will be removed; instead, specify "<a href="postconf.5.html#smtp_tls_security_level">smtp_tls_security_level</a>"
<li> support for parameter "<a href="postconf.5.html#smtpd_use_tls">smtpd_use_tls</a>" will be removed; instead, specify "<a href="postconf.5.html#smtpd_tls_security_level">smtpd_tls_security_level</a>"
</ul>
<p> There are similarly-named parameters and warnings for <a href="postscreen.8.html">postscreen(8)</a>
and <a href="tlsproxy.8.html">tlsproxy(8)</a>, but those parameters should rarely be specified
by hand. </p>
<p> Replace obsolete configuration with its replacement: </p>
<p> The <a href="postconf.1.html">postconf(1)</a> command logs one of the following: </p>
<ul>
<li> support for parameter "<a href="postconf.5.html#lmtp_enforce_tls">lmtp_enforce_tls</a>" will be removed; instead, specify "<a href="postconf.5.html#lmtp_tls_security_level">lmtp_tls_security_level</a>"
<li> support for parameter "<a href="postconf.5.html#smtp_enforce_tls">smtp_enforce_tls</a>" will be removed; instead, specify "<a href="postconf.5.html#smtp_tls_security_level">smtp_tls_security_level</a>"
<li> support for parameter "<a href="postconf.5.html#smtpd_enforce_tls">smtpd_enforce_tls</a>" will be removed; instead, specify "<a href="postconf.5.html#smtpd_tls_security_level">smtpd_tls_security_level</a>"
</ul>
<p> There are similarly-named parameters and warnings for <a href="postscreen.8.html">postscreen(8)</a>
and <a href="tlsproxy.8.html">tlsproxy(8)</a>, but those parameters should rarely be specified
by hand. </p>
<p> Replace obsolete configuration with its replacement: </p>
<p> The <a href="postconf.1.html">postconf(1)</a> command logs one of the following: </p>
<ul>
<li> support for parameter "<a href="postconf.5.html#lmtp_tls_per_site">lmtp_tls_per_site</a>" will be removed;
instead, specify "<a href="postconf.5.html#lmtp_tls_policy_maps">lmtp_tls_policy_maps</a>"
<li> support for parameter "<a href="postconf.5.html#smtp_tls_per_site">smtp_tls_per_site</a>" will be removed;
instead, specify "<a href="postconf.5.html#smtp_tls_policy_maps">smtp_tls_policy_maps</a>"
</ul>
<p> There is similarly-named parameter and warning for <a href="tlsproxy.8.html">tlsproxy(8)</a>,
but that parameter should rarely be specified by hand. </p>
<p> Unfortunately, this is more than a name change: the table format
has changed too, as has the table search process. There is no simple
conversion of the obsolete form to its replacement. </p>
<p> Depending on the Postfix version, the Postfix SMTP daemon logs
following warning: </p>
<ul>
<li> support for restriction "check_relay_domains" has been removed
in Postfix 3.9"; instead, specify "<a href="postconf.5.html#reject_unauth_destination">reject_unauth_destination</a>"
<li> support for restriction "check_relay_domains" will be removed
from Postfix; use "<a href="postconf.5.html#reject_unauth_destination">reject_unauth_destination</a>" instead
</ul>
<p> This feature was removed because it would relay based on the
client domain name, which is not robust. </p>
<p> Recommended configuration to prevent an "open relay" problem
with the SMTP service on port 25:
</p>
<p> The Postfix version 3.9 and later SMTP daemon logs the following
warning: </p>
<ul>
<li> support for restriction "<a href="postconf.5.html#permit_mx_backup">permit_mx_backup</a>" will be removed
from Postfix; instead, specify "<a href="postconf.5.html#relay_domains">relay_domains</a>"
</ul>
<p> This feature will be removed because it is too difficult to
configure recipient address validation, making Postfix a source of
backscatter bounces. </p>
<p> To specify the domains that Postfix will provide MX backup
service for, see <a href="STANDARD_CONFIGURATION_README.html#backup">
Configuring Postfix as primary or backup MX host for a remote
site</a>. </p>
<p> Depending on the Postfix version, the SMTP daemon logs one of
the following warnings: </p>
<ul>
<li> support for restriction "reject_maps_rbl" has been removed in
Postfix 3.9"; instead, specify "<a href="postconf.5.html#reject_rbl_client">reject_rbl_client</a> domain-name"
<li> support for restriction "reject_maps_rbl" will be removed from
Postfix; use "<a href="postconf.5.html#reject_rbl_client">reject_rbl_client</a> domain-name" instead
</ul>
<p> This feature was replaced because "MAPS RBL" is the name of a
specific reputation service. The <a href="postconf.5.html#reject_rbl_client">reject_rbl_client</a> feature provides
a superset of the reject_maps_rbl functionality. </p>
<p> Depending on the Postfix version, the SMTP daemon logs one of
the following warnings: </p>
<ul>
<li> support for restriction "permit_naked_ip_address" has been
removed in Postfix 3.9"; instead, specify "<a href="postconf.5.html#permit_mynetworks">permit_mynetworks</a>" or "<a href="postconf.5.html#permit_sasl_authenticated">permit_sasl_authenticated</a>"
<li> restriction permit_naked_ip_address is deprecated. Use
<a href="postconf.5.html#permit_mynetworks">permit_mynetworks</a> or <a href="postconf.5.html#permit_sasl_authenticated">permit_sasl_authenticated</a> instead
</ul>
<p> This feature was removed because it was easy to get a false
match when <a href="postconf.5.html#smtpd_recipient_restrictions">smtpd_recipient_restrictions</a> was intended to match a
remote SMTP client IP address. </p>
<p> That is, no restriction on HELO or EHLO syntax. Such restrictions
ar rarely useful nowadays.
</body>
</html>
Messung V0.5 in Prozent
¤ Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.0.17Bemerkung:
(vorverarbeitet am 2026-08-08)
¤
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.
