Manual browser: canonical(5)
|CANONICAL(5)||File Formats Manual||CANONICAL(5)|
NAMEcanonical - Postfix canonical table format
postmap -q "string" /etc/postfix/canonical
postmap -q - /etc/postfix/canonical <inputfile
The optional canonical(5) table specifies an address mapping for local and non-local addresses. The mapping is used by the cleanup(8) daemon, before mail is stored into the queue. The address mapping is recursive.
The search string is folded to lowercase before database lookup. As of Postfix 2.3, the search string is not case folded with database types such as regexp: or pcre: whose lookup fields can match both upper and lower case.
The input format for the postmap(1) command is as follows:
- pattern address
- When pattern matches a mail address, replace it by the corresponding address.
- blank lines and comments
- Empty lines and whitespace-only lines are ignored, as are lines whose first non-whitespace character is a `#'.
- multi-line text
- A logical line starts with non-whitespace text. A line that starts with whitespace continues a logical line.
TABLE SEARCH ORDER
With lookups from indexed files such as DB or DBM, or from networked tables such as NIS, LDAP or SQL, patterns are tried in the order as listed below:
- user@domain address
Replace user@domain by address. This form has the highest precedence.
- user address
Replace user@site by address when site is equal to $ myorigin, when site is listed in $ mydestination, or when it is listed in $inet_interfaces or $ proxy_interfaces.
- @domain address
Replace other addresses in domain by address. This form has the lowest precedence.
RESULT ADDRESS REWRITING
The lookup result is subject to address rewriting:
- When the result has the form @otherdomain, the result becomes the same user in otherdomain.
- When "append_at_myorigin=yes", append "@$myorigin" to addresses without "@domain".
- When "append_dot_mydomain=yes", append " .$mydomain" to addresses without ".domain".
When a mail address localpart contains the optional recipient delimiter (e.g., user+foo@domain), the lookup order becomes: user+foo@domain, user@domain, user+foo, user, and @domain.
REGULAR EXPRESSION TABLES
This section describes how the table lookups change when the table is given in the form of regular expressions. For a description of regular expression lookup table syntax, see regexp_table(5) or pcre_table(5).
This section describes how the table lookups change when lookups are directed to a TCP-based server. For a description of the TCP client/server lookup protocol, see tcp_table(5). This feature is not available up to and including Postfix version 2.4.
The table format does not understand quoting conventions.
The following main.cf parameters are especially relevant. The text below provides only a parameter summary. See postconf(5) for more details including examples.
- What addresses are subject to canonical address mapping.
- List of canonical mapping tables.
- Address mapping lookup table for envelope and header recipient addresses.
- Address mapping lookup table for envelope and header sender addresses.
- A list of address rewriting or forwarding mechanisms that propagate an address extension from the original address to the result. Specify zero or more of canonical, virtual, alias, forward, include, or generic.
Other parameters of interest:
- The network interface addresses that this system receives mail on. You need to stop and start Postfix when this parameter changes.
- 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.
- Other interfaces that this machine receives mail on by way of a proxy agent or network address translator.
- List of address classes subject to masquerading: zero or more of envelope_sender, envelope_recipient, header_sender, header_recipient.
- List of domains that hide their subdomain structure.
- List of user names that are not subject to address masquerading.
- List of domains that this mail system considers local.
- The domain that is appended to locally-posted mail.
- Give special treatment to owner-xxx and xxx-request addresses.
- 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.
cleanup(8), canonicalize and enqueue mail
postmap(1), Postfix lookup table manager
postconf(5), configuration parameters
virtual(5), virtual aliasing
Use "postconf readme_directory" or " postconf html_directory" to locate this information.
DATABASE_README, Postfix lookup table overview
ADDRESS_REWRITING_README, address rewriting guide
The Secure Mailer license must be distributed with this software.
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA