Manual Pages for UNIX Darwin command on man generic

GENERIC(5) GENERIC(5)

NAME

generic - Postfix generic table format

SYNOPSIS

ppoossttmmaapp //eettcc//ppoossttffiixx//ggeenneerriicc

ppoossttmmaapp -qq ""string"" //eettcc//ppoossttffiixx//ggeenneerriicc

ppoossttmmaapp -qq - //eettcc//ppoossttffiixx//ggeenneerriicc <

DESCRIPTION

The optional ggeenneerriicc(5) table specifies an address mapping that applies when mail is delivered. This is the opposite of ccaannoonniiccaall(5) mapping, which applies when mail is received. Typically, one would use the ggeenneerriicc(5) table on a system that does not

have a valid Internet domain name and that uses something like localdo-

main.local instead. The ggeenneerriicc(5) table is then used by the ssmmttpp(8) client to transform local mail addresses into valid Internet mail

addresses when mail has to be sent across the Internet. See the EXAM-

PLE section at the end of this document. The ggeenneerriicc(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). Normally, the ggeenneerriicc(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//ggeenneerriicc" 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 case, the lookups are done in a

slightly different way as described below under "REGULAR EXPRESSION

TABLES" or "TCP-BASED TABLES".

CCAASSEE FFOOLLDDIINNGG 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. TTAABBLLEE FFOORRMMAATT The input format for the ppoossttmmaapp(1) command is as follows: pattern result

When pattern matches a mail address, replace it by the corre-

sponding result. 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. TTAABBLLEE SSEEAARRCCHH OORRDDEERR 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 prece-

dence. user address

Replace user@site by address when site is equal to $mmyyoorriiggiinn,

when site is listed in $mmyyddeessttiinnaattiioonn, or when it is listed in

$iinneettiinntteerrffaacceess or $pprrooxxyyiinntteerrffaacceess.

@domain address Replace other addresses in domain by address. This form has the lowest precedence. RREESSUULLTT AADDDDRREESSSS RREEWWRRIITTIINNGG The lookup result is subject to address rewriting: +o When the result has the form @otherdomain, the result becomes the same user in otherdomain.

+o When "aappppeennddaattmmyyoorriiggiinn==yyeess", append "@@$$mmyyoorriiggiinn" to addresses

without "@domain".

+o When "aappppeennddddoottmmyyddoommaaiinn==yyeess", append "..$$mmyyddoommaaiinn" to addresses

without ".domain". AADDDDRREESSSS EEXXTTEENNSSIIOONN 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. The pprrooppaaggaatteeuunnmmaattcchheeddeexxtteennssiioonnss parameter controls whether an unmatched address extension (+foo) is propagated to the result of table lookup. RREEGGUULLAARR EEXXPPRREESSSSIIOONN TTAABBLLEESS 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 rreeggeexxppttaabbllee(5) or ppccrreettaabbllee(5). Each pattern is a regular expression that is applied to the entire

address being looked up. Thus, user@domain mail addresses are not bro-

ken up into their user and @domain 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 string. Results are the same as with indexed file lookups, with the additional

feature that parenthesized substrings from the pattern can be interpo-

lated as $$11, $$22 and so on.

TTCCPP-BBAASSEEDD TTAABBLLEESS

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 ttccppttaabbllee(5). This feature is not available up to and including Postfix version 2.4. Each lookup operation uses the entire address once. Thus, user@domain

mail addresses are not broken up into their user and @domain con-

stituent parts, nor is user+foo broken up into user and foo. Results are the same as with indexed file lookups. EEXXAAMMPPLLEE

The following shows a generic mapping with an indexed file. When mail

is sent to a remote host via SMTP, this replaces his@localdomain.local by his ISP mail address, replaces her@localdomain.local by her ISP mail address, and replaces other local addresses by his ISP account, with an address extension of +local (this example assumes that the ISP supports "+" style address extensions). /etc/postfix/main.cf:

smtpgenericmaps = hash:/etc/postfix/generic

/etc/postfix/generic:

his@localdomain.local hisaccount@hisisp.example her@localdomain.local heraccount@herisp.example @localdomain.local hisaccount+local@hisisp.example Execute the command "ppoossttmmaapp //eettcc//ppoossttffiixx//ggeenneerriicc" whenever the table is changed. Instead of hhaasshh, some systems use ddbbmm database files. To find out what tables your system supports use the command "ppoossttccoonnff

-mm".

BUGS

The table format does not understand quoting conventions. CCOONNFFIIGGUURRAATTIIOONN PPAARRAAMMEETTEERRSS The following mmaaiinn..ccff parameters are especially relevant. The text below provides only a parameter summary. See ppoossttccoonnff(5) for more details including examples. ssmmttppggeenneerriiccmmaappss Address mapping lookup table for envelope and header sender and recipient addresses while delivering mail via SMTP. pprrooppaaggaatteeuunnmmaattcchheeddeexxtteennssiioonnss

A list of address rewriting or forwarding mechanisms that propa-

gate an address extension from the original address to the

result. Specify zero or more of ccaannoonniiccaall, vviirrttuuaall, aalliiaass, ffoorr-

wwaarrdd, iinncclluuddee, or ggeenneerriicc. Other parameters of interest: iinneettiinntteerrffaacceess The network interface addresses that this system receives mail on. You need to stop and start Postfix when this parameter changes. pprrooxxyyiinntteerrffaacceess Other interfaces that this machine receives mail on by way of a proxy agent or network address translator. mmyyddeessttiinnaattiioonn List of domains that this mail system considers local. mmyyoorriiggiinn

The domain that is appended to locally-posted mail.

oowwnneerrrreeqquueessttssppeecciiaall

Give special treatment to oowwnneerr-xxx and xxx-rreeqquueesstt addresses.

A genericstable feature appears in the Sendmail MTA.

This feature is available in Postfix 2.2 and later. AUTHOR(S) Wietse Venema IBM T.J. Watson Research P.O. Box 704 Yorktown Heights, NY 10598, USA GENERIC(5)