ppoossttmmaapp //eettcc//ppoossttffiixx//ccaannoonniiccaall
ppoossttmmaapp --qq ""_s_t_r_i_n_g"" //eettcc//ppoossttffiixx//ccaannoonniiccaall
ppoossttmmaapp --qq -- //eettcc//ppoossttffiixx//ccaannoonniiccaall <<_i_n_p_u_t_f_i_l_e
Normally, the ccaannoonniiccaall(5) table is specified as a text file that serves as input to the ppoossttmmaapp(1) command. The result, an indexed file in ddbbmm or ddbb format, is used for fast searching by the mail system. Execute the command "ppoossttmmaapp //eettcc//ppoossttffiixx//ccaannoonniiccaall" to rebuild an indexed file after changing the corresponding text file.
When the table is provided via other means such as NIS, LDAP or SQL, the same lookups are done as for ordinary indexed files.
Alternatively, the table can be provided as a regular-expression map where patterns are given as regular expressions, or lookups can be directed to TCP-based server. In those cases, the lookups are done in a slightly different way as described below under "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
By default the ccaannoonniiccaall(5) mapping affects both message header addresses (i.e. addresses that appear inside messages) and message envelope addresses (for example, the addresses that are used in SMTP protocol commands). This is controlled with the ccaannoonniiccaall__ccllaasssseess 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 ccaannoonniiccaall(5) table to replace login names by _F_i_r_s_t_n_a_m_e_._L_a_s_t_n_a_m_e, or to clean up addresses produced by legacy mail systems.
The ccaannoonniiccaall(5) mapping is not to be confused with _v_i_r_t_u_a_l _a_l_i_a_s support or with local aliasing. To change the destination but not the headers, use the vviirrttuuaall(5) or aalliiaasseess(5) map instead.
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 ppoossttmmaapp(1) command is as follows:
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:
The lookup result is subject to address rewriting:
When a mail address localpart contains the optional recipient delimiter (e.g., _u_s_e_r_+_f_o_o@_d_o_m_a_i_n), the lookup order becomes: _u_s_e_r_+_f_o_o@_d_o_m_a_i_n, _u_s_e_r@_d_o_m_a_i_n, _u_s_e_r_+_f_o_o, _u_s_e_r, and @_d_o_m_a_i_n.
The pprrooppaaggaattee__uunnmmaattcchheedd__eexxtteennssiioonnss parameter controls whether an unmatched address extension (_+_f_o_o) is propagated to the result of table lookup.
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 rreeggeexxpp__ttaabbllee(5) or ppccrree__ttaabbllee(5).
Each pattern is a regular expression that is applied to the entire address being looked up. Thus, _u_s_e_r_@_d_o_m_a_i_n mail addresses are not broken up into their _u_s_e_r and _@_d_o_m_a_i_n constituent parts, nor is _u_s_e_r_+_f_o_o broken up into _u_s_e_r and _f_o_o.
Patterns are applied in the order as specified in the table, until a pattern is found that matches the search string.
Results are the same as with indexed file lookups, with the additional feature that parenthesized substrings from the pattern can be interpolated as $$11, $$22 and so on.
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 ttccpp__ttaabbllee(5). This feature is not available up to and including Postfix version 2.4.
Each lookup operation uses the entire address once. Thus, _u_s_e_r_@_d_o_m_a_i_n mail addresses are not broken up into their _u_s_e_r and _@_d_o_m_a_i_n constituent parts, nor is _u_s_e_r_+_f_o_o broken up into _u_s_e_r and _f_o_o.
Results are the same as with indexed file lookups.
The following mmaaiinn..ccff parameters are especially relevant. The text below provides only a parameter summary. See ppoossttccoonnff(5) for more details including examples.
Other parameters of interest:
cleanup(8), canonicalize and enqueue mail postmap(1), Postfix lookup table manager postconf(5), configuration parameters virtual(5), virtual aliasing
Use "ppoossttccoonnff rreeaaddmmee__ddiirreeccttoorryy" or "ppoossttccoonnff hhttmmll__ddiirreeccttoorryy" 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.
Wietse Venema IBM T.J. Watson Research P.O. Box 704 Yorktown Heights, NY 10598, USA