from remote SMTP clients at all, or to label incomplete addresses in such
message headers as invalid. Here is how it works:
- * Postfix always rewrites message header addresses from local SMTP clients,
- and from the Postfix sendmail command. The local_header_rewrite_clients
- parameter controls what SMTP clients Postfix considers local (by default,
- only local network interface addresses).
+ * Postfix always rewrites message headers from local SMTP clients and from
+ the Postfix sendmail command, and appends its own domain to incomplete
+ addresses. The local_header_rewrite_clients parameter controls what SMTP
+ clients Postfix considers local (by default, only local network interface
+ addresses).
* Postfix never rewrites message header addresses from remote SMTP clients
when the remote_header_rewrite_domain parameter value is empty (the default
setting).
- * Otherwise, Postfix appends the remote_header_rewrite_domain value to
- incomplete message header addresses from remote SMTP clients. This feature
- can be used to append a reserved domain such as "domain.invalid", so that
- incomplete addresses cannot be mistaken for local addresses.
+ * Otherwise, Postfix rewrites message headers from remote SMTP clients, and
+ appends the remote_header_rewrite_domain value to incomplete addresses.
+ This feature can be used to append a reserved domain such as
+ "domain.invalid", so that incomplete addresses cannot be mistaken for local
+ addresses.
P\bPo\bos\bst\btf\bfi\bix\bx a\bad\bdd\bdr\bre\bes\bss\bs r\bre\bew\bwr\bri\bit\bti\bin\bng\bg o\bov\bve\ber\brv\bvi\bie\bew\bw
rewrite(8) daemon. The purpose of rewriting to standard form is to reduce the
number of entries needed in lookup tables.
-NOTE: Postfix versions 2.2 and later rewrite message headers from remote SMTP
-clients only if the client matches the local_header_rewrite_clients parameter,
-or if the remote_header_rewrite_domain configuration parameter specifies a non-
-empty value. To get the behavior before Postfix 2.2, specify
-"local_header_rewrite_clients = static:all".
-
The Postfix trivial-rewrite(8) daemon implements the following hard-coded
address manipulations:
time. Postfix has no ability to handle route addresses, other than to
strip off the route part.
+ NOTE: Postfix versions 2.2 and later rewrite message headers from
+ remote SMTP clients only if the client matches the
+ local_header_rewrite_clients parameter, or if the
+ remote_header_rewrite_domain configuration parameter specifies a non-
+ empty value. To get the behavior before Postfix 2.2, specify
+ "local_header_rewrite_clients = static:all".
+
Rewrite "site!user" to "user@site"
This feature is controlled by the boolean swap_bangpath parameter
(default: yes). The purpose is to rewrite UUCP-style addresses to
domain style. This is useful only when you receive mail via UUCP, but
it probably does not hurt otherwise.
+ NOTE: Postfix versions 2.2 and later rewrite message headers from
+ remote SMTP clients only if the client matches the
+ local_header_rewrite_clients parameter, or if the
+ remote_header_rewrite_domain configuration parameter specifies a non-
+ empty value. To get the behavior before Postfix 2.2, specify
+ "local_header_rewrite_clients = static:all".
+
Rewrite "user%domain" to "user@domain"
This feature is controlled by the boolean allow_percent_hack parameter
(default: yes). Typically, this is used in order to deal with
monstrosities such as "user%domain@otherdomain".
+ NOTE: Postfix versions 2.2 and later rewrite message headers from
+ remote SMTP clients only if the client matches the
+ local_header_rewrite_clients parameter, or if the
+ remote_header_rewrite_domain configuration parameter specifies a non-
+ empty value. To get the behavior before Postfix 2.2, specify
+ "local_header_rewrite_clients = static:all".
+
Rewrite "user" to "user@$myorigin"
This feature is controlled by the boolean append_at_myorigin parameter
(default: yes). You should never turn off this feature, because a lot
A single trailing dot is silently removed. However, an address that
ends in multiple dots will be rejected as an invalid address.
+ NOTE: Postfix versions 2.2 and later rewrite message headers from
+ remote SMTP clients only if the client matches the
+ local_header_rewrite_clients parameter, or if the
+ remote_header_rewrite_domain configuration parameter specifies a non-
+ empty value. To get the behavior before Postfix 2.2, specify
+ "local_header_rewrite_clients = static:all".
+
C\bCa\ban\bno\bon\bni\bic\bca\bal\bl a\bad\bdd\bdr\bre\bes\bss\bs m\bma\bap\bpp\bpi\bin\bng\bg
The cleanup(8) daemon uses the canonical(5) tables to rewrite addresses in
$inet_interfaces in each instance with just the corresponding interface
address.
-In most cases using inet_interaces in this way will not work, because as
+In most cases, using inet_interfaces in this way will not work, because as
documented in the $inet_interfaces reference manual, the smtp(8) delivery agent
will also use the specified interface address as the source address for
outbound connections and will be unable to reach hosts on "the other side" of
up deliveries to high-volume destinations that have some servers
that respond, and some non-responding mail servers.
-- By default, message header address rewriting is now disabled for
-SMTP mail from other systems (including masquerading and canonical
-mapping). Thus, spam from poorly written software no longer looks
-like it came from a local user.
+- By default, Postfix no longer rewrites message headers in mail
+from remote clients. This includes masquerading, canonical mapping,
+replacing "!" and "%" by "@", and appending the local domain to
+incomplete addresses. Thus, spam from poorly written software no
+longer looks like it came from a local user.
- When your machine does not have its own domain name, Postfix can
now replace your "home network" email address by your ISP account
example is in the STANDARD_CONFIGURATION_README document, the section
titled "Postfix on hosts without a real Internet hostname".
-[Feature 20041023] By default, Postfix no longer appends its own
-domain to addresses in message headers from remote clients. Thus,
-spam from poorly written software no longer looks like it came from
-a local user.
+[Feature 20041023] By default, Postfix no longer rewrites message
+headers in mail from remote clients. This includes masquerading,
+canonical mapping, replacing "!" and "%" by "@", and appending the
+local domain to incomplete addresses. Thus, spam from poorly written
+software no longer looks like it came from a local user.
-Postfix either does not rewrite remote message headers at all, or
-it rewrites headers and appends the domain name that is specified
-with the remote_header_rewrite_domain parameter (like "domain.invalid").
+By default, Postfix rewrites message header addresses only when the
+client IP address matches the local machine's interface addresses,
+or when mail is submitted with the Postfix sendmail(1) command.
-To get the behavior of earlier Postfix versions (always append
-Postfix's own domain to incomplete addresses in message headers)
-specify:
+Postfix rewrites message headers in mail from other clients only
+when the remote_header_rewrite_domain parameter specifies a domain
+name (such as "domain.invalid"); this domain is appended to incomplete
+addresses. Rewriting also includes masquerading, canonical mapping,
+and replacing "!" and "%" by "@".
+
+To get the behavior before Postfix 2.2 (always append Postfix's own
+domain to incomplete addresses in message headers, always subject
+message headers to canonical mapping, address masquerading, and
+always replace "!" and "%" by "@") specify:
/etc/postfix/main.cf:
local_header_rewrite_clients = static:all
-Postfix always appends its own domain information to addresses in
-message headers from Postfix sendmail and from local SMTP clients.
-
-By default, Postfix considers an SMTP client local (and thus updates
-message header addresses with the Postfix's own domain) when the
-client IP address matches the local machine's interface addresses,
-or when mail is submitted with the Postfix sendmail(1) command.
-
-If you must rewrite headers from other clients then you can specify,
-for example,
+If you must rewrite headers in mail from specific clients then you
+can specify, for example,
/etc/postfix/main.cf:
local_header_rewrite_clients = permit_mynetworks,
un-parse a header so that there may be subtle changes in formatting,
such as the amount of whitespace between tokens.
-[Incompat 20050227] When header address rewriting is enabled, Postfix
-no longer changes header label capitalization, i.e. FROM: or CC:
-are no longer replaced by From: or Cc:.
+[Incompat 20050227] Postfix no longer changes message header labels.
+Thus, FROM: or CC: are no longer replaced by From: or Cc:.
[Feature 20040827] Finer control over canonical mapping with
canonical_classes, sender_canonical_classes and
-# CANONICAL(5) CANONICAL(5)
+# CANONICAL(5) CANONICAL(5)
#
# NAME
# canonical - Postfix canonical table format
# Sendmail rule set S3, if you like. This is controlled
# with the canonical_classes parameter.
#
+# NOTE: Postfix versions 2.2 and later rewrite message head-
+# ers from remote SMTP clients only if the client matches
+# the local_header_rewrite_clients parameter, or if the
+# remote_header_rewrite_domain configuration parameter spec-
+# ifies a non-empty value. To get the behavior before Post-
+# fix 2.2, specify "local_header_rewrite_clients =
+# static:all".
+#
# Typically, one would use the canonical(5) table to replace
# login names by Firstname.Lastname, or to clean up
# addresses produced by legacy mail systems.
# constituent parts, nor is user+foo broken up into user and
# foo.
#
-# Patterns are applied in the order as specified in the
-# table, until a pattern is found that matches the search
+# Patterns are applied in the order as specified in the ta-
+# ble, until a pattern is found that matches the search
# string.
#
# Results are the same as with indexed file lookups, with
# TCP-BASED TABLES
# This section describes how the table lookups change when
# lookups are directed to a TCP-based server. For a descrip-
-# tion of the TCP client/server lookup protocol, see
-# tcp_table(5). This feature is not available up to and
-# including Postfix version 2.2.
+# tion of the TCP client/server lookup protocol, see tcp_ta-
+# ble(5). This feature is not available up to and including
+# Postfix version 2.2.
#
# Each lookup operation uses the entire address once. Thus,
# user@domain mail addresses are not broken up into their
# receives mail on. You need to stop and start Post-
# fix when this parameter changes.
#
+# local_header_rewrite_clients
+# Rewrite message header addresses in mail from these
+# clients and update incomplete addresses with the
+# domain name in $myorigin or $mydomain; either don't
+# rewrite message headers from other clients at all,
+# or rewrite message headers and update incomplete
+# addresses with the domain specified in the
+# remote_header_rewrite_domain parameter.
+#
# proxy_interfaces
# Other interfaces that this machine receives mail on
# by way of a proxy agent or network address transla-
# Give special treatment to owner-xxx and xxx-request
# addresses.
#
+# remote_header_rewrite_domain
+# Don't rewrite message headers from remote clients
+# at all when this parameter is empty; otherwise, re-
+# write message headers and append the specified
+# domain name to incomplete addresses.
+#
# SEE ALSO
# cleanup(8), canonicalize and enqueue mail
# postmap(1), Postfix lookup table manager
# virtual(5), virtual aliasing
#
# README FILES
-# Use "postconf readme_directory" or "postconf html_direc-
+# Use "postconf readme_directory" or "postconf html_direc-
# tory" to locate this information.
# DATABASE_README, Postfix lookup table overview
# ADDRESS_REWRITING_README, address rewriting guide
#
# LICENSE
-# The Secure Mailer license must be distributed with this
+# The Secure Mailer license must be distributed with this
# software.
#
# AUTHOR(S)
# P.O. Box 704
# Yorktown Heights, NY 10598, USA
#
-# CANONICAL(5)
+# CANONICAL(5)
<ul>
-<li> Postfix always rewrites message header addresses from local
-SMTP clients, and from the Postfix sendmail command. The
-<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> parameter controls what SMTP clients
-Postfix considers local (by default, only local network interface
-addresses).
+<li> Postfix always rewrites message headers from local SMTP clients
+and from the Postfix sendmail command, and appends its own domain
+to incomplete addresses. The <a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> parameter
+controls what SMTP clients Postfix considers local (by default,
+only local network interface addresses).
<li> Postfix never rewrites message header addresses from remote
SMTP clients when the <a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> parameter value
is empty (the default setting).
-<li> Otherwise, Postfix appends the <a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a>
-value to incomplete message header addresses from remote SMTP
-clients. This feature can be used to append a reserved domain such
-as "domain.invalid", so that incomplete addresses cannot be mistaken
-for local addresses.
+<li> Otherwise, Postfix rewrites message headers from remote SMTP
+clients, and appends the <a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> value to
+incomplete addresses. This feature can be used to append a reserved
+domain such as "domain.invalid", so that incomplete addresses cannot
+be mistaken for local addresses.
</ul>
form is to reduce the number of entries needed in lookup tables.
</p>
-<p> NOTE: Postfix versions 2.2 and later rewrite message headers
-from remote SMTP clients only if the client matches the
-<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> parameter, or if the
-<a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> configuration parameter specifies a
-non-empty value. To get the behavior before Postfix 2.2, specify
-"<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> = static:all". </p>
-
<p> The Postfix <a href="trivial-rewrite.8.html">trivial-rewrite(8)</a> daemon implements the following
hard-coded address manipulations: </p>
is called a route address, and specifies that mail for "user@site"
be delivered via "hosta" and "hostb". Usage of this form has been
deprecated for a long time. Postfix has no ability to handle route
-addresses, other than to strip off the route part. </p> </dd>
+addresses, other than to strip off the route part. </p>
+
+<p> NOTE: Postfix versions 2.2 and later rewrite message headers
+from remote SMTP clients only if the client matches the
+<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> parameter, or if the
+<a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> configuration parameter specifies a
+non-empty value. To get the behavior before Postfix 2.2, specify
+"<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> = static:all". </p> </dd>
<dt>Rewrite "site!user" to "user@site" </dt>
<dd> <p> This feature is controlled by the boolean <a href="postconf.5.html#swap_bangpath">swap_bangpath</a>
parameter (default: yes). The purpose is to rewrite UUCP-style
addresses to domain style. This is useful only when you receive
-mail via UUCP, but it probably does not hurt otherwise. </p> </dd>
+mail via UUCP, but it probably does not hurt otherwise. </p>
+
+<p> NOTE: Postfix versions 2.2 and later rewrite message headers
+from remote SMTP clients only if the client matches the
+<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> parameter, or if the
+<a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> configuration parameter specifies a
+non-empty value. To get the behavior before Postfix 2.2, specify
+"<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> = static:all". </p> </dd>
<dt>Rewrite "user%domain" to "user@domain"</dt>
<dd> <p> This feature is controlled by the boolean <a href="postconf.5.html#allow_percent_hack">allow_percent_hack</a>
parameter (default: yes). Typically, this is used in order to deal
with monstrosities such as "user%domain@otherdomain". </p>
-</dd>
+
+<p> NOTE: Postfix versions 2.2 and later rewrite message headers
+from remote SMTP clients only if the client matches the
+<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> parameter, or if the
+<a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> configuration parameter specifies a
+non-empty value. To get the behavior before Postfix 2.2, specify
+"<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> = static:all". </p> </dd>
<dt>
<dd> <p> A single trailing dot is silently removed. However, an
address that ends in multiple dots will be rejected as an invalid
-address. </p> </dd>
+address. </p>
+
+<p> NOTE: Postfix versions 2.2 and later rewrite message headers
+from remote SMTP clients only if the client matches the
+<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> parameter, or if the
+<a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> configuration parameter specifies a
+non-empty value. To get the behavior before Postfix 2.2, specify
+"<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> = static:all". </p> </dd>
</dl>
tempting to configure $<a href="postconf.5.html#inet_interfaces">inet_interfaces</a> in each instance with just the
corresponding interface address. </p>
-<p> In most cases using inet_interaces in this way will not work,
+<p> In most cases, using <a href="postconf.5.html#inet_interfaces">inet_interfaces</a> in this way will not work,
because as documented in the $<a href="postconf.5.html#inet_interfaces">inet_interfaces</a> reference manual, the
<a href="smtp.8.html">smtp(8)</a> delivery agent will also use the specified interface address
as the source address for outbound connections and will be unable to
Sendmail rule set <b>S3</b>, if you like. This is controlled
with the <b><a href="postconf.5.html#canonical_classes">canonical_classes</a></b> parameter.
+ NOTE: Postfix versions 2.2 and later rewrite message head-
+ ers from remote SMTP clients only if the client matches
+ the <a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> parameter, or if the
+ <a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> configuration parameter spec-
+ ifies a non-empty value. To get the behavior before Post-
+ fix 2.2, specify "<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> =
+ static:all".
+
Typically, one would use the <a href="canonical.5.html"><b>canonical</b>(5)</a> table to replace
login names by <i>Firstname.Lastname</i>, or to clean up
addresses produced by legacy mail systems.
receives mail on. You need to stop and start Post-
fix when this parameter changes.
+ <b><a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a></b>
+ Rewrite message header addresses in mail from these
+ clients and update incomplete addresses with the
+ domain name in $<a href="postconf.5.html#myorigin">myorigin</a> or $<a href="postconf.5.html#mydomain">mydomain</a>; either don't
+ rewrite message headers from other clients at all,
+ or rewrite message headers and update incomplete
+ addresses with the domain specified in the
+ <a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> parameter.
+
<b><a href="postconf.5.html#proxy_interfaces">proxy_interfaces</a></b>
Other interfaces that this machine receives mail on
by way of a proxy agent or network address transla-
Give special treatment to <b>owner-</b><i>xxx</i> and <i>xxx</i><b>-request</b>
addresses.
+ <b><a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a></b>
+ Don't rewrite message headers from remote clients
+ at all when this parameter is empty; otherwise, re-
+ write message headers and append the specified
+ domain name to incomplete addresses.
+
<b>SEE ALSO</b>
<a href="cleanup.8.html">cleanup(8)</a>, canonicalize and enqueue mail
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
<a href="ADDRESS_REWRITING_README.html">ADDRESS_REWRITING_README</a>, address rewriting guide
<b>LICENSE</b>
- The Secure Mailer license must be distributed with this
+ The Secure Mailer license must be distributed with this
software.
<b>AUTHOR(S)</b>
<b><a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> (empty)</b>
Don't rewrite message headers from remote clients
at all when this parameter is empty; otherwise, re-
- write remote message headers and append the speci-
- fied domain name to incomplete addresses.
+ write message headers and append the specified
+ domain name to incomplete addresses.
<b>RESOURCE AND RATE CONTROLS</b>
<b><a href="postconf.5.html#duplicate_filter_limit">duplicate_filter_limit</a> (1000)</b>
<b>%[SUD1-9]</b>
The upper-case and decimal digit expansions
interpolate the parts of the input key
- rather than the result. Their behaviour is
+ rather than the result. Their behavior is
identical to that described with <b>query_fil-</b>
<b>ter</b>, and in fact because the input key is
known in advance, lookups whose key does not
<b>FILES</b>
The following are examples; details differ between systems.
$HOME/.forward, per-user aliasing
- /etc/aliases, sytem-wide alias database
+ /etc/aliases, system-wide alias database
/var/spool/mail, system mailboxes
<b>SEE ALSO</b>
<b>%[SUD1-9]</b>
The upper-case and decimal digit expansions
interpolate the parts of the input key
- rather than the result. Their behaviour is
+ rather than the result. Their behavior is
identical to that described with <b>query</b>, and
in fact because the input key is known in
advance, queries whose key does not contain
<b>query</b> = SELECT <i>select</i><b>_</b><i>function</i>('%s')
- or in the absense of <b>selection_function</b>, the lower prece-
+ or in the absence of <b>selection_function</b>, the lower prece-
dence:
<b>query</b> = SELECT <i>select</i><b>_</b><i>field</i>
<b>%[SUD1-9]</b>
The upper-case and decimal digit expansions
interpolate the parts of the input key
- rather than the result. Their behaviour is
+ rather than the result. Their behavior is
identical to that described with <b>query</b>, and
in fact because the input key is known in
advance, queries whose key does not contain
This is enabled by default.
</p>
-<p> Note: With Postfix version 2.2, message header address rewriting
+<p> Note: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true: </p>
<ul>
</p>
<p>
-NOTE: if mail to the BCC address bounces it will be returned to
+Note: if mail to the BCC address bounces it will be returned to
the sender.
</p>
-<p> NOTE: automatic BCC recipients are produced only for new mail.
+<p> Note: automatic BCC recipients are produced only for new mail.
To avoid mailer loops, automatic BCC recipients are not generated
for mail that Postfix forwards internally, nor for mail that Postfix
generates itself. </p>
</p>
<p>
-Note 1: This feature is enabled by default and must not be turned off.
+Note 1: this feature is enabled by default and must not be turned off.
Postfix does not support domain-less addresses.
</p>
-<p> Note 2: With Postfix version 2.2, message header address rewriting
+<p> Note 2: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true: </p>
<ul>
</p>
<p>
-Note 1: This feature is enabled by default. If disabled, users will not be
+Note 1: this feature is enabled by default. If disabled, users will not be
able to send mail to "user@partialdomainname" but will have to
specify full domain names instead.
</p>
-<p> Note 2: With Postfix version 2.2, message header address rewriting
+<p> Note 2: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true: </p>
<ul>
[host] turns off MX lookups. If you specify multiple SMTP
destinations, Postfix will try them in the specified order. </p>
-<p> N
OTE: Do not use the <a href="postconf.5.html#fallback_relay">fallback_relay</a> feature when relaying mail
+<p> N
ote: do not use the <a href="postconf.5.html#fallback_relay">fallback_relay</a> feature when relaying mail
for a backup or primary MX domain. Mail would loop between the
Postfix MX host and the <a href="postconf.5.html#fallback_relay">fallback_relay</a> host when the final destination
is unavailable. </p>
<DT><b><a name="local_header_rewrite_clients">local_header_rewrite_clients</a>
(default: <a href="postconf.5.html#permit_inet_interfaces">permit_inet_interfaces</a>)</b></DT><DD>
-<p> Append the domain name in $<a href="postconf.5.html#myorigin">myorigin</a> or $<a href="postconf.5.html#mydomain">mydomain</a> to message
-header addresses from these clients only; either don't rewrite
-message headers from other clients at all, or append the domain
-specified with the <a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> parameter. </p>
+<p> Rewrite message header addresses in mail from these clients and
+update incomplete addresses with the domain name in $<a href="postconf.5.html#myorigin">myorigin</a> or
+$<a href="postconf.5.html#mydomain">mydomain</a>; either don't rewrite message headers from other clients
+at all, or rewrite message headers and update incomplete addresses
+with the domain specified in the <a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a>
+parameter. </p>
<p> See the <a href="postconf.5.html#append_at_myorigin">append_at_myorigin</a> and <a href="postconf.5.html#append_dot_mydomain">append_dot_mydomain</a> parameters
for details of how domain names are appended to incomplete addresses.
$<a href="postconf.5.html#myorigin">myorigin</a> or $<a href="postconf.5.html#mydomain">mydomain</a> information only with mail from Postfix
sendmail, from local clients, or from authorized SMTP clients. </p>
-<p> NOTE: This setting will not prevent remote mail header address
+<p> Note: this setting will not prevent remote mail header address
rewriting when mail from a remote client is forwarded by a neighboring
system. </p>
</p>
<p>
-NOTE: if you use this feature for accounts not in the UNIX password
+Note: if you use this feature for accounts not in the UNIX password
file, then you must specify "<a href="postconf.5.html#local_recipient_maps">local_recipient_maps</a> =" (i.e. empty)
in the main.cf file, otherwise the Postfix SMTP server will reject mail
for non-UNIX accounts with "User unknown in local recipient table".
</p>
<p>
-NOTE: if mail to the BCC address bounces it will be returned to
+Note: if mail to the BCC address bounces it will be returned to
the sender.
</p>
-<p> NOTE: automatic BCC recipients are produced only for new mail.
+<p> Note: automatic BCC recipients are produced only for new mail.
To avoid mailer loops, automatic BCC recipients are not generated
for mail that Postfix forwards internally, nor for mail that Postfix
generates itself. </p>
recipients. See also the <a href="ADDRESS_CLASS_README.html#relay_domain_class">relay domains</a> address class in the
<a href="ADDRESS_CLASS_README.html">ADDRESS_CLASS_README</a> file. </p>
-<p> NOTE: Postfix will not automatically forward mail for domains
+<p> Note: Postfix will not automatically forward mail for domains
that list this system as their primary or backup MX host. See the
<a href="postconf.5.html#permit_mx_backup">permit_mx_backup</a> restriction in the <a href="postconf.5.html">postconf(5)</a> manual page. </p>
(default: empty)</b></DT><DD>
<p> Don't rewrite message headers from remote clients at all when
-this parameter is empty; otherwise, rewrite remote message headers
-and append the specified domain name to incomplete addresses. The
+this parameter is empty; otherwise, rewrite message headers and
+append the specified domain name to incomplete addresses. The
<a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> parameter controls what clients Postfix
considers local. </p>
</p>
<p>
-NOTE: if mail to the BCC address bounces it will be returned to
+Note: if mail to the BCC address bounces it will be returned to
the sender.
</p>
-<p> NOTE: automatic BCC recipients are produced only for new mail.
+<p> Note: automatic BCC recipients are produced only for new mail.
To avoid mailer loops, automatic BCC recipients are not generated
for mail that Postfix forwards internally, nor for mail that Postfix
generates itself. </p>
such as <b>btree</b> or <b>sdbm</b>; there is no need to support
concurrent access. The file is created if it does not exist. </p>
-<p> NOTE: <b>dbm</b> databases are not suitable. TLS
+<p> Note: <b>dbm</b> databases are not suitable. TLS
session objects are too large. </p>
<p> Example: </p>
<dd>Reject the request when the envelope sender is the null address,
and the message has multiple envelope recipients. Although this
usage is technically allowed, it seems to have no legitimate
-application. <br> NOTE: this restriction can only work reliably
+application. <br> Note: this restriction can only work reliably
when used in <a href="postconf.5.html#smtpd_data_restrictions">smtpd_data_restrictions</a> or
<a href="postconf.5.html#smtpd_end_of_data_restrictions">smtpd_end_of_data_restrictions</a>, because the total number of
recipients is not known at an earlier stage of the SMTP conversation.
commands ahead of time without knowing that Postfix actually supports
ESMTP command pipelining. This stops mail from bulk mail software
that improperly uses ESMTP command pipelining in order to speed up
-deliveries. <br> N
OTE: <a href="postconf.5.html#reject_unauth_pipelining">reject_unauth_pipelining</a> is not useful
+deliveries. <br> N
ote: <a href="postconf.5.html#reject_unauth_pipelining">reject_unauth_pipelining</a> is not useful
outside <a href="postconf.5.html#smtpd_data_restrictions">smtpd_data_restrictions</a> when 1) the client uses ESMTP (EHLO
instead of HELO) and 2) with "<a href="postconf.5.html#smtpd_delay_reject">smtpd_delay_reject</a> = yes" (the
default). The use of <a href="postconf.5.html#reject_unauth_pipelining">reject_unauth_pipelining</a> in the other
forward mail with addresses that have sender-specified routing
information (example: user@elsewhere@domain). Use the optional
<a href="postconf.5.html#permit_mx_backup_networks">permit_mx_backup_networks</a> parameter to require that the primary
-MX hosts match a list of network blocks. <br> NOTE: prior to
+MX hosts match a list of network blocks. <br> Note: prior to
Postfix version 2.0, use of <a href="postconf.5.html#permit_mx_backup">permit_mx_backup</a> is not recommended;
mail may be rejected in case of a temporary DNS lookup problem. </dd>
such as <b>btree</b> or <b>sdbm</b>; there is no need to support
concurrent access. The file is created if it does not exist. </p>
-<p> NOTE: <b>dbm</b> databases are not suitable. TLS
+<p> Note: <b>dbm</b> databases are not suitable. TLS
session objects are too large. </p>
<p> Example: </p>
enabled by default.
</p>
-<p> Note: With Postfix version 2.2, message header address rewriting
+<p> Note: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true: </p>
<ul>
</p>
<p>
-Note 1: The <b>dotlock</b> method requires that the recipient UID
+Note 1: the <b>dotlock</b> method requires that the recipient UID
or GID has write access to the parent directory of the recipient's
mailbox file.
</p>
Available in Postfix version 2.2 and later:
<b><a href="postconf.5.html#local_header_rewrite_clients">local_header_rewrite_clients</a> (<a href="postconf.5.html#permit_inet_interfaces">permit_inet_interfaces</a>)</b>
- Append the domain name in $<a href="postconf.5.html#myorigin">myorigin</a> or $<a href="postconf.5.html#mydomain">mydomain</a> to
- message header addresses from these clients only;
- either don't rewrite message headers from other
- clients at all, or append the domain specified with
- the <a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> parameter.
+ Rewrite message header addresses in mail from these
+ clients and update incomplete addresses with the
+ domain name in $<a href="postconf.5.html#myorigin">myorigin</a> or $<a href="postconf.5.html#mydomain">mydomain</a>; either don't
+ rewrite message headers from other clients at all,
+ or rewrite message headers and update incomplete
+ addresses with the domain specified in the
+ <a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> parameter.
<b>AFTER QUEUE EXTERNAL CONTENT INSPECTION CONTROLS</b>
As of version 1.0, Postfix can be configured to send new
rule set \fBS3\fR, if you like. This is controlled with
the \fBcanonical_classes\fR parameter.
+NOTE: Postfix versions 2.2 and later rewrite message headers
+from remote SMTP clients only if the client matches the
+local_header_rewrite_clients parameter, or if the
+remote_header_rewrite_domain configuration parameter specifies
+a non-empty value. To get the behavior before Postfix 2.2,
+specify "local_header_rewrite_clients = static:all".
+
Typically, one would use the \fBcanonical\fR(5) table to replace login
names by \fIFirstname.Lastname\fR, or to clean up addresses produced
by legacy mail systems.
.IP \fBinet_interfaces\fR
The network interface addresses that this system receives mail on.
You need to stop and start Postfix when this parameter changes.
+.IP \fBlocal_header_rewrite_clients\fR
+Rewrite message header addresses in mail from these clients
+and update incomplete addresses with the domain name in
+$myorigin or $mydomain; either don't rewrite message headers
+from other clients at all, or rewrite message headers and
+update incomplete addresses with the domain specified in
+the remote_header_rewrite_domain parameter.
.IP \fBproxy_interfaces\fR
Other interfaces that this machine receives mail on by way of a
proxy agent or network address translator.
.IP \fBowner_request_special\fR
Give special treatment to \fBowner-\fIxxx\fR and \fIxxx\fB-request\fR
addresses.
+.IP \fBremote_header_rewrite_domain\fR
+Don't rewrite message headers from remote clients at all
+when this parameter is empty; otherwise, rewrite message
+headers and append the specified domain name to incomplete
+addresses.
.SH "SEE ALSO"
.na
.nf
.IP "\fB\fB%[SUD1-9]\fR\fB"
The upper-case and decimal digit expansions interpolate
the parts of the input key rather than the result. Their
-behaviour is identical to that described with \fBquery_filter\fR,
+behavior is identical to that described with \fBquery_filter\fR,
and in fact because the input key is known in advance, lookups
whose key does not contain all the information specified in
the result template are suppressed and return no results.
.IP "\fB\fB%[SUD1-9]\fR\fB"
The upper-case and decimal digit expansions interpolate
the parts of the input key rather than the result. Their
-behaviour is identical to that described with \fBquery\fR,
+behavior is identical to that described with \fBquery\fR,
and in fact because the input key is known in advance, queries
whose key does not contain all the information specified in
the result template are suppressed and return no results.
.ti +4
\fBquery\fR = SELECT \fIselect_function\fR('%s')
-or in the absense of \fBselection_function\fR, the lower precedence:
+or in the absence of \fBselection_function\fR, the lower precedence:
.ti +4
\fBquery\fR = SELECT \fIselect_field\fR
.IP "\fB\fB%[SUD1-9]\fR\fB"
The upper-case and decimal digit expansions interpolate
the parts of the input key rather than the result. Their
-behaviour is identical to that described with \fBquery\fR,
+behavior is identical to that described with \fBquery\fR,
and in fact because the input key is known in advance, queries
whose key does not contain all the information specified in
the result template are suppressed and return no results.
Enable the rewriting of the form "user%domain" to "user@domain".
This is enabled by default.
.PP
-Note: With Postfix version 2.2, message header address rewriting
+Note: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true:
.IP \(bu
The message is received with the Postfix \fBsendmail\fR(1) command,
Optional address that receives a "blind carbon copy" of each message
that is received by the Postfix mail system.
.PP
-NOTE: if mail to the BCC address bounces it will be returned to
+Note: if mail to the BCC address bounces it will be returned to
the sender.
.PP
-NOTE: automatic BCC recipients are produced only for new mail.
+Note: automatic BCC recipients are produced only for new mail.
To avoid mailer loops, automatic BCC recipients are not generated
for mail that Postfix forwards internally, nor for mail that Postfix
generates itself.
addresses without domain information. With remotely submitted mail,
append the string "@$remote_header_rewrite_domain" instead.
.PP
-Note 1: This feature is enabled by default and must not be turned off.
+Note 1: this feature is enabled by default and must not be turned off.
Postfix does not support domain-less addresses.
.PP
-Note 2: With Postfix version 2.2, message header address rewriting
+Note 2: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true:
.IP \(bu
The message is received with the Postfix \fBsendmail\fR(1) command,
mail, append the string ".$remote_header_rewrite_domain"
instead.
.PP
-Note 1: This feature is enabled by default. If disabled, users will not be
+Note 1: this feature is enabled by default. If disabled, users will not be
able to send mail to "user@partialdomainname" but will have to
specify full domain names instead.
.PP
-Note 2: With Postfix version 2.2, message header address rewriting
+Note 2: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true:
.IP \(bu
The message is received with the Postfix \fBsendmail\fR(1) command,
[host] turns off MX lookups. If you specify multiple SMTP
destinations, Postfix will try them in the specified order.
.PP
-NOTE: Do not use the fallback_relay feature when relaying mail
+Note: do not use the fallback_relay feature when relaying mail
for a backup or primary MX domain. Mail would loop between the
Postfix MX host and the fallback_relay host when the final destination
is unavailable.
local_destination_concurrency_limit from concurrency per recipient
into concurrency per domain.
.SH local_header_rewrite_clients (default: permit_inet_interfaces)
-Append the domain name in $myorigin or $mydomain to message
-header addresses from these clients only; either don't rewrite
-message headers from other clients at all, or append the domain
-specified with the remote_header_rewrite_domain parameter.
+Rewrite message header addresses in mail from these clients and
+update incomplete addresses with the domain name in $myorigin or
+$mydomain; either don't rewrite message headers from other clients
+at all, or rewrite message headers and update incomplete addresses
+with the domain specified in the remote_header_rewrite_domain
+parameter.
.PP
See the append_at_myorigin and append_dot_mydomain parameters
for details of how domain names are appended to incomplete addresses.
$myorigin or $mydomain information only with mail from Postfix
sendmail, from local clients, or from authorized SMTP clients.
.PP
-NOTE: This setting will not prevent remote mail header address
+Note: this setting will not prevent remote mail header address
rewriting when mail from a remote client is forwarded by a neighboring
system.
.PP
.PP
Note: luser_relay works only for the Postfix \fBlocal\fR(8) delivery agent.
.PP
-NOTE: if you use this feature for accounts not in the UNIX password
+Note: if you use this feature for accounts not in the UNIX password
file, then you must specify "local_recipient_maps =" (i.e. empty)
in the main.cf file, otherwise the Postfix SMTP server will reject mail
for non-UNIX accounts with "User unknown in local recipient table".
Specify the types and names of databases to use. After change,
run "\fBpostmap /etc/postfix/recipient_bcc\fR".
.PP
-NOTE: if mail to the BCC address bounces it will be returned to
+Note: if mail to the BCC address bounces it will be returned to
the sender.
.PP
-NOTE: automatic BCC recipients are produced only for new mail.
+Note: automatic BCC recipients are produced only for new mail.
To avoid mailer loops, automatic BCC recipients are not generated
for mail that Postfix forwards internally, nor for mail that Postfix
generates itself.
recipients. See also the relay domains address class in the
ADDRESS_CLASS_README file.
.PP
-NOTE: Postfix will not automatically forward mail for domains
+Note: Postfix will not automatically forward mail for domains
that list this system as their primary or backup MX host. See the
permit_mx_backup restriction in the \fBpostconf\fR(5) manual page.
.PP
.ft R
.SH remote_header_rewrite_domain (default: empty)
Don't rewrite message headers from remote clients at all when
-this parameter is empty; otherwise, rewrite remote message headers
-and append the specified domain name to incomplete addresses. The
+this parameter is empty; otherwise, rewrite message headers and
+append the specified domain name to incomplete addresses. The
local_header_rewrite_clients parameter controls what clients Postfix
considers local.
.PP
Specify the types and names of databases to use. After change,
run "\fBpostmap /etc/postfix/sender_bcc\fR".
.PP
-NOTE: if mail to the BCC address bounces it will be returned to
+Note: if mail to the BCC address bounces it will be returned to
the sender.
.PP
-NOTE: automatic BCC recipients are produced only for new mail.
+Note: automatic BCC recipients are produced only for new mail.
To avoid mailer loops, automatic BCC recipients are not generated
for mail that Postfix forwards internally, nor for mail that Postfix
generates itself.
such as \fBbtree\fR or \fBsdbm\fR; there is no need to support
concurrent access. The file is created if it does not exist.
.PP
-NOTE: \fBdbm\fR databases are not suitable. TLS
+Note: \fBdbm\fR databases are not suitable. TLS
session objects are too large.
.PP
Example:
usage is technically allowed, it seems to have no legitimate
application.
.br
-NOTE: this restriction can only work reliably
+Note: this restriction can only work reliably
when used in smtpd_data_restrictions or
smtpd_end_of_data_restrictions, because the total number of
recipients is not known at an earlier stage of the SMTP conversation.
that improperly uses ESMTP command pipelining in order to speed up
deliveries.
.br
-NOTE: reject_unauth_pipelining is not useful
+Note: reject_unauth_pipelining is not useful
outside smtpd_data_restrictions when 1) the client uses ESMTP (EHLO
instead of HELO) and 2) with "smtpd_delay_reject = yes" (the
default). The use of reject_unauth_pipelining in the other
permit_mx_backup_networks parameter to require that the primary
MX hosts match a list of network blocks.
.br
-NOTE: prior to
+Note: prior to
Postfix version 2.0, use of permit_mx_backup is not recommended;
mail may be rejected in case of a temporary DNS lookup problem.
.IP "\fBreject_non_fqdn_recipient\fR"
such as \fBbtree\fR or \fBsdbm\fR; there is no need to support
concurrent access. The file is created if it does not exist.
.PP
-NOTE: \fBdbm\fR databases are not suitable. TLS
+Note: \fBdbm\fR databases are not suitable. TLS
session objects are too large.
.PP
Example:
necessary if your machine is connected to UUCP networks. It is
enabled by default.
.PP
-Note: With Postfix version 2.2, message header address rewriting
+Note: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true:
.IP \(bu
The message is received with the Postfix \fBsendmail\fR(1) command,
This setting is ignored with \fBmaildir\fR style delivery, because
such deliveries are safe without application-level locks.
.PP
-Note 1: The \fBdotlock\fR method requires that the recipient UID
+Note 1: the \fBdotlock\fR method requires that the recipient UID
or GID has write access to the parent directory of the recipient's
mailbox file.
.PP
mapping.
.IP "\fBremote_header_rewrite_domain (empty)\fR"
Don't rewrite message headers from remote clients at all when
-this parameter is empty; otherwise, rewrite remote message headers
-and append the specified domain name to incomplete addresses.
+this parameter is empty; otherwise, rewrite message headers and
+append the specified domain name to incomplete addresses.
.SH "RESOURCE AND RATE CONTROLS"
.na
.nf
.nf
The following are examples; details differ between systems.
$HOME/.forward, per-user aliasing
-/etc/aliases, sytem-wide alias database
+/etc/aliases, system-wide alias database
/var/spool/mail, system mailboxes
.SH "SEE ALSO"
.na
.PP
Available in Postfix version 2.2 and later:
.IP "\fBlocal_header_rewrite_clients (permit_inet_interfaces)\fR"
-Append the domain name in $myorigin or $mydomain to message
-header addresses from these clients only; either don't rewrite
-message headers from other clients at all, or append the domain
-specified with the remote_header_rewrite_domain parameter.
+Rewrite message header addresses in mail from these clients and
+update incomplete addresses with the domain name in $myorigin or
+$mydomain; either don't rewrite message headers from other clients
+at all, or rewrite message headers and update incomplete addresses
+with the domain specified in the remote_header_rewrite_domain
+parameter.
.SH "AFTER QUEUE EXTERNAL CONTENT INSPECTION CONTROLS"
.na
.nf
<ul>
-<li> Postfix always rewrites message header addresses from local
-SMTP clients, and from the Postfix sendmail command. The
-local_header_rewrite_clients parameter controls what SMTP clients
-Postfix considers local (by default, only local network interface
-addresses).
+<li> Postfix always rewrites message headers from local SMTP clients
+and from the Postfix sendmail command, and appends its own domain
+to incomplete addresses. The local_header_rewrite_clients parameter
+controls what SMTP clients Postfix considers local (by default,
+only local network interface addresses).
<li> Postfix never rewrites message header addresses from remote
SMTP clients when the remote_header_rewrite_domain parameter value
is empty (the default setting).
-<li> Otherwise, Postfix appends the remote_header_rewrite_domain
-value to incomplete message header addresses from remote SMTP
-clients. This feature can be used to append a reserved domain such
-as "domain.invalid", so that incomplete addresses cannot be mistaken
-for local addresses.
+<li> Otherwise, Postfix rewrites message headers from remote SMTP
+clients, and appends the remote_header_rewrite_domain value to
+incomplete addresses. This feature can be used to append a reserved
+domain such as "domain.invalid", so that incomplete addresses cannot
+be mistaken for local addresses.
</ul>
form is to reduce the number of entries needed in lookup tables.
</p>
-<p> NOTE: Postfix versions 2.2 and later rewrite message headers
-from remote SMTP clients only if the client matches the
-local_header_rewrite_clients parameter, or if the
-remote_header_rewrite_domain configuration parameter specifies a
-non-empty value. To get the behavior before Postfix 2.2, specify
-"local_header_rewrite_clients = static:all". </p>
-
<p> The Postfix trivial-rewrite(8) daemon implements the following
hard-coded address manipulations: </p>
is called a route address, and specifies that mail for "user@site"
be delivered via "hosta" and "hostb". Usage of this form has been
deprecated for a long time. Postfix has no ability to handle route
-addresses, other than to strip off the route part. </p> </dd>
+addresses, other than to strip off the route part. </p>
+
+<p> NOTE: Postfix versions 2.2 and later rewrite message headers
+from remote SMTP clients only if the client matches the
+local_header_rewrite_clients parameter, or if the
+remote_header_rewrite_domain configuration parameter specifies a
+non-empty value. To get the behavior before Postfix 2.2, specify
+"local_header_rewrite_clients = static:all". </p> </dd>
<dt>Rewrite "site!user" to "user@site" </dt>
<dd> <p> This feature is controlled by the boolean swap_bangpath
parameter (default: yes). The purpose is to rewrite UUCP-style
addresses to domain style. This is useful only when you receive
-mail via UUCP, but it probably does not hurt otherwise. </p> </dd>
+mail via UUCP, but it probably does not hurt otherwise. </p>
+
+<p> NOTE: Postfix versions 2.2 and later rewrite message headers
+from remote SMTP clients only if the client matches the
+local_header_rewrite_clients parameter, or if the
+remote_header_rewrite_domain configuration parameter specifies a
+non-empty value. To get the behavior before Postfix 2.2, specify
+"local_header_rewrite_clients = static:all". </p> </dd>
<dt>Rewrite "user%domain" to "user@domain"</dt>
<dd> <p> This feature is controlled by the boolean allow_percent_hack
parameter (default: yes). Typically, this is used in order to deal
with monstrosities such as "user%domain@otherdomain". </p>
-</dd>
+
+<p> NOTE: Postfix versions 2.2 and later rewrite message headers
+from remote SMTP clients only if the client matches the
+local_header_rewrite_clients parameter, or if the
+remote_header_rewrite_domain configuration parameter specifies a
+non-empty value. To get the behavior before Postfix 2.2, specify
+"local_header_rewrite_clients = static:all". </p> </dd>
<dt>
<dd> <p> A single trailing dot is silently removed. However, an
address that ends in multiple dots will be rejected as an invalid
-address. </p> </dd>
+address. </p>
+
+<p> NOTE: Postfix versions 2.2 and later rewrite message headers
+from remote SMTP clients only if the client matches the
+local_header_rewrite_clients parameter, or if the
+remote_header_rewrite_domain configuration parameter specifies a
+non-empty value. To get the behavior before Postfix 2.2, specify
+"local_header_rewrite_clients = static:all". </p> </dd>
</dl>
tempting to configure $inet_interfaces in each instance with just the
corresponding interface address. </p>
-<p> In most cases using inet_interaces in this way will not work,
+<p> In most cases, using inet_interfaces in this way will not work,
because as documented in the $inet_interfaces reference manual, the
smtp(8) delivery agent will also use the specified interface address
as the source address for outbound connections and will be unable to
# rule set \fBS3\fR, if you like. This is controlled with
# the \fBcanonical_classes\fR parameter.
#
+# NOTE: Postfix versions 2.2 and later rewrite message headers
+# from remote SMTP clients only if the client matches the
+# local_header_rewrite_clients parameter, or if the
+# remote_header_rewrite_domain configuration parameter specifies
+# a non-empty value. To get the behavior before Postfix 2.2,
+# specify "local_header_rewrite_clients = static:all".
+#
# Typically, one would use the \fBcanonical\fR(5) table to replace login
# names by \fIFirstname.Lastname\fR, or to clean up addresses produced
# by legacy mail systems.
# .IP \fBinet_interfaces\fR
# The network interface addresses that this system receives mail on.
# You need to stop and start Postfix when this parameter changes.
+# .IP \fBlocal_header_rewrite_clients\fR
+# Rewrite message header addresses in mail from these clients
+# and update incomplete addresses with the domain name in
+# $myorigin or $mydomain; either don't rewrite message headers
+# from other clients at all, or rewrite message headers and
+# update incomplete addresses with the domain specified in
+# the remote_header_rewrite_domain parameter.
# .IP \fBproxy_interfaces\fR
# Other interfaces that this machine receives mail on by way of a
# proxy agent or network address translator.
# .IP \fBowner_request_special\fR
# Give special treatment to \fBowner-\fIxxx\fR and \fIxxx\fB-request\fR
# addresses.
+# .IP \fBremote_header_rewrite_domain\fR
+# Don't rewrite message headers from remote clients at all
+# when this parameter is empty; otherwise, rewrite message
+# headers and append the specified domain name to incomplete
+# addresses.
# SEE ALSO
# cleanup(8), canonicalize and enqueue mail
# postmap(1), Postfix lookup table manager
# .IP "\fB\fB%[SUD1-9]\fR\fB"
# The upper-case and decimal digit expansions interpolate
# the parts of the input key rather than the result. Their
-# behaviour is identical to that described with \fBquery_filter\fR,
+# behavior is identical to that described with \fBquery_filter\fR,
# and in fact because the input key is known in advance, lookups
# whose key does not contain all the information specified in
# the result template are suppressed and return no results.
# .IP "\fB\fB%[SUD1-9]\fR\fB"
# The upper-case and decimal digit expansions interpolate
# the parts of the input key rather than the result. Their
-# behaviour is identical to that described with \fBquery\fR,
+# behavior is identical to that described with \fBquery\fR,
# and in fact because the input key is known in advance, queries
# whose key does not contain all the information specified in
# the result template are suppressed and return no results.
# .ti +4
# \fBquery\fR = SELECT \fIselect_function\fR('%s')
#
-# or in the absense of \fBselection_function\fR, the lower precedence:
+# or in the absence of \fBselection_function\fR, the lower precedence:
#
# .ti +4
# \fBquery\fR = SELECT \fIselect_field\fR
# .IP "\fB\fB%[SUD1-9]\fR\fB"
# The upper-case and decimal digit expansions interpolate
# the parts of the input key rather than the result. Their
-# behaviour is identical to that described with \fBquery\fR,
+# behavior is identical to that described with \fBquery\fR,
# and in fact because the input key is known in advance, queries
# whose key does not contain all the information specified in
# the result template are suppressed and return no results.
This is enabled by default.
</p>
-<p> Note: With Postfix version 2.2, message header address rewriting
+<p> Note: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true: </p>
<ul>
</p>
<p>
-NOTE: if mail to the BCC address bounces it will be returned to
+Note: if mail to the BCC address bounces it will be returned to
the sender.
</p>
-<p> NOTE: automatic BCC recipients are produced only for new mail.
+<p> Note: automatic BCC recipients are produced only for new mail.
To avoid mailer loops, automatic BCC recipients are not generated
for mail that Postfix forwards internally, nor for mail that Postfix
generates itself. </p>
[host] turns off MX lookups. If you specify multiple SMTP
destinations, Postfix will try them in the specified order. </p>
-<p> NOTE: Do not use the fallback_relay feature when relaying mail
+<p> Note: do not use the fallback_relay feature when relaying mail
for a backup or primary MX domain. Mail would loop between the
Postfix MX host and the fallback_relay host when the final destination
is unavailable. </p>
</p>
<p>
-NOTE: if you use this feature for accounts not in the UNIX password
+Note: if you use this feature for accounts not in the UNIX password
file, then you must specify "local_recipient_maps =" (i.e. empty)
in the main.cf file, otherwise the Postfix SMTP server will reject mail
for non-UNIX accounts with "User unknown in local recipient table".
</p>
<p>
-NOTE: if mail to the BCC address bounces it will be returned to
+Note: if mail to the BCC address bounces it will be returned to
the sender.
</p>
-<p> NOTE: automatic BCC recipients are produced only for new mail.
+<p> Note: automatic BCC recipients are produced only for new mail.
To avoid mailer loops, automatic BCC recipients are not generated
for mail that Postfix forwards internally, nor for mail that Postfix
generates itself. </p>
recipients. See also the relay domains address class in the
ADDRESS_CLASS_README file. </p>
-<p> NOTE: Postfix will not automatically forward mail for domains
+<p> Note: Postfix will not automatically forward mail for domains
that list this system as their primary or backup MX host. See the
permit_mx_backup restriction in the postconf(5) manual page. </p>
</p>
<p>
-NOTE: if mail to the BCC address bounces it will be returned to
+Note: if mail to the BCC address bounces it will be returned to
the sender.
</p>
-<p> NOTE: automatic BCC recipients are produced only for new mail.
+<p> Note: automatic BCC recipients are produced only for new mail.
To avoid mailer loops, automatic BCC recipients are not generated
for mail that Postfix forwards internally, nor for mail that Postfix
generates itself. </p>
<dd>Reject the request when the envelope sender is the null address,
and the message has multiple envelope recipients. Although this
usage is technically allowed, it seems to have no legitimate
-application. <br> NOTE: this restriction can only work reliably
+application. <br> Note: this restriction can only work reliably
when used in smtpd_data_restrictions or
smtpd_end_of_data_restrictions, because the total number of
recipients is not known at an earlier stage of the SMTP conversation.
commands ahead of time without knowing that Postfix actually supports
ESMTP command pipelining. This stops mail from bulk mail software
that improperly uses ESMTP command pipelining in order to speed up
-deliveries. <br> NOTE: reject_unauth_pipelining is not useful
+deliveries. <br> Note: reject_unauth_pipelining is not useful
outside smtpd_data_restrictions when 1) the client uses ESMTP (EHLO
instead of HELO) and 2) with "smtpd_delay_reject = yes" (the
default). The use of reject_unauth_pipelining in the other
forward mail with addresses that have sender-specified routing
information (example: user@elsewhere@domain). Use the optional
permit_mx_backup_networks parameter to require that the primary
-MX hosts match a list of network blocks. <br> NOTE: prior to
+MX hosts match a list of network blocks. <br> Note: prior to
Postfix version 2.0, use of permit_mx_backup is not recommended;
mail may be rejected in case of a temporary DNS lookup problem. </dd>
enabled by default.
</p>
-<p> Note: With Postfix version 2.2, message header address rewriting
+<p> Note: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true: </p>
<ul>
</p>
<p>
-Note 1: This feature is enabled by default and must not be turned off.
+Note 1: this feature is enabled by default and must not be turned off.
Postfix does not support domain-less addresses.
</p>
-<p> Note 2: With Postfix version 2.2, message header address rewriting
+<p> Note 2: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true: </p>
<ul>
</p>
<p>
-Note 1: This feature is enabled by default. If disabled, users will not be
+Note 1: this feature is enabled by default. If disabled, users will not be
able to send mail to "user@partialdomainname" but will have to
specify full domain names instead.
</p>
-<p> Note 2: With Postfix version 2.2, message header address rewriting
+<p> Note 2: with Postfix version 2.2, message header address rewriting
happens only when one of the following conditions is true: </p>
<ul>
</p>
<p>
-Note 1: The <b>dotlock</b> method requires that the recipient UID
+Note 1: the <b>dotlock</b> method requires that the recipient UID
or GID has write access to the parent directory of the recipient's
mailbox file.
</p>
%PARAM remote_header_rewrite_domain
<p> Don't rewrite message headers from remote clients at all when
-this parameter is empty; otherwise, rewrite remote message headers
-and append the specified domain name to incomplete addresses. The
+this parameter is empty; otherwise, rewrite message headers and
+append the specified domain name to incomplete addresses. The
local_header_rewrite_clients parameter controls what clients Postfix
considers local. </p>
%PARAM local_header_rewrite_clients permit_inet_interfaces
-<p> Append the domain name in $myorigin or $mydomain to message
-header addresses from these clients only; either don't rewrite
-message headers from other clients at all, or append the domain
-specified with the remote_header_rewrite_domain parameter. </p>
+<p> Rewrite message header addresses in mail from these clients and
+update incomplete addresses with the domain name in $myorigin or
+$mydomain; either don't rewrite message headers from other clients
+at all, or rewrite message headers and update incomplete addresses
+with the domain specified in the remote_header_rewrite_domain
+parameter. </p>
<p> See the append_at_myorigin and append_dot_mydomain parameters
for details of how domain names are appended to incomplete addresses.
$myorigin or $mydomain information only with mail from Postfix
sendmail, from local clients, or from authorized SMTP clients. </p>
-<p> NOTE: This setting will not prevent remote mail header address
+<p> Note: this setting will not prevent remote mail header address
rewriting when mail from a remote client is forwarded by a neighboring
system. </p>
such as <b>btree</b> or <b>sdbm</b>; there is no need to support
concurrent access. The file is created if it does not exist. </p>
-<p> NOTE: <b>dbm</b> databases are not suitable. TLS
+<p> Note: <b>dbm</b> databases are not suitable. TLS
session objects are too large. </p>
<p> Example: </p>
such as <b>btree</b> or <b>sdbm</b>; there is no need to support
concurrent access. The file is created if it does not exist. </p>
-<p> NOTE: <b>dbm</b> databases are not suitable. TLS
+<p> Note: <b>dbm</b> databases are not suitable. TLS
session objects are too large. </p>
<p> Example: </p>
/* mapping.
/* .IP "\fBremote_header_rewrite_domain (empty)\fR"
/* Don't rewrite message headers from remote clients at all when
-/* this parameter is empty; otherwise, rewrite remote message headers
-/* and append the specified domain name to incomplete addresses.
+/* this parameter is empty; otherwise, rewrite message headers and
+/* append the specified domain name to incomplete addresses.
/* RESOURCE AND RATE CONTROLS
/* .ad
/* .fi
* Patches change the patchlevel and the release date. Snapshots change the
* release date only.
*/
-#define MAIL_RELEASE_DATE "20050308"
+#define MAIL_RELEASE_DATE "20050309"
#define MAIL_VERSION_NUMBER "2.3"
#define VAR_MAIL_VERSION "mail_version"
/* FILES
/* The following are examples; details differ between systems.
/* $HOME/.forward, per-user aliasing
-/* /etc/aliases, sytem-wide alias database
+/* /etc/aliases, system-wide alias database
/* /var/spool/mail, system mailboxes
/* SEE ALSO
/* qmgr(8), queue manager
/* .PP
/* Available in Postfix version 2.2 and later:
/* .IP "\fBlocal_header_rewrite_clients (permit_inet_interfaces)\fR"
-/* Append the domain name in $myorigin or $mydomain to message
-/* header addresses from these clients only; either don't rewrite
-/* message headers from other clients at all, or append the domain
-/* specified with the remote_header_rewrite_domain parameter.
+/* Rewrite message header addresses in mail from these clients and
+/* update incomplete addresses with the domain name in $myorigin or
+/* $mydomain; either don't rewrite message headers from other clients
+/* at all, or rewrite message headers and update incomplete addresses
+/* with the domain specified in the remote_header_rewrite_domain
+/* parameter.
/* AFTER QUEUE EXTERNAL CONTENT INSPECTION CONTROLS
/* .ad
/* .fi
projects / thirdparty / postfix.git / commitdiff
