Manual Pages for UNIX Darwin command on man transport

TRANSPORT(5) TRANSPORT(5)

NAME

transport - format of Postfix transport table

SYNOPSIS

ppoossttmmaapp //eettcc//ppoossttffiixx//ttrraannssppoorrtt

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

ppoossttmmaapp -qq - //eettcc//ppoossttffiixx//ttrraannssppoorrtt <

DESCRIPTION

The optional ttrraannssppoorrtt table specifies a mapping from email addresses

to message delivery transports and/or relay hosts. The mapping is used

by the ttrriivviiaall-rreewwrriittee(8) daemon.

This mapping overrides the default routing that is built into Postfix: mmyyddeessttiinnaattiioonn

A list of domains that is by default delivered via $$llooccaallttrraannss-

ppoorrtt. This also includes domains that match $$iinneettiinntteerrffaacceess or

$$pprrooxxyyiinntteerrffaacceess.

vviirrttuuaallmmaaiillbbooxxddoommaaiinnss

A list of domains that is by default delivered via $$vviirr-

ttuuaallttrraannssppoorrtt. rreellaayyddoommaaiinnss

A list of domains that is by default delivered via $$rreellaayyttrraannss-

ppoorrtt. any other destination Mail for any other destination is by default delivered via

$$ddeeffaauullttttrraannssppoorrtt.

Normally, the ttrraannssppoorrtt 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//ttrraannssppoorrtt in order to rebuild the

indexed file after changing the transport table.

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 that case, the lookups are done in a

slightly different way as described below under "REGULAR EXPRESSION

TABLES" and "TCP-BASED TABLES".

TTAABBLLEE FFOORRMMAATT The input format for the ppoossttmmaapp(1) command is as follows: pattern result When pattern matches the recipient address or domain, use the corresponding 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. The pattern specifies an email address, a domain name, or a domain name hierarchy, as described in section "TABLE LOOKUP".

The result is of the form transport:nexthop and specifies how or where

to deliver mail. This is described in section "RESULT FORMAT". TTAABBLLEE LLOOOOKKUUPP 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+extension@domain transport:nexthop

Mail for user+extension@domain is delivered through transport to

nexthop.

user@domain transport:nexthop

Mail for user@domain is delivered through transport to nexthop.

domain transport:nexthop

Mail for domain is delivered through transport to nexthop.

.domain transport:nexthop

Mail for any subdomain of domain is delivered through transport

to nexthop. This applies only when the string ttrraannssppoorrttmmaappss is not listed in the ppaarreennttddoommaaiinnmmaattcchheessssuubbddoommaaiinnss configuration

setting. Otherwise, a domain name matches itself and its subdo-

mains. Note 1: the special pattern ** represents any address (i.e. it functions

as the wild-card pattern).

Note 2: the null recipient address is looked up as

$$eemmppttyyaaddddrreessssrreecciippiieenntt@$$mmyyhhoossttnnaammee (default: mailer-daemon@hostname).

RREESSUULLTT FFOORRMMAATT

The lookup result is of the form transport::nexthop. The transport

field specifies a mail delivery transport such as ssmmttpp or llooccaall. The

nexthop field specifies where and how to deliver mail.

The transport field specifies the name of a mail delivery transport

(the first name of a mail delivery service entry in the Postfix mmaass-

tteerr..ccff file).

The interpretation of the nexthop field is transport dependent. In the

case of SMTP, specify a service on a non-default port as host:service,

and disable MX (mail exchanger) DNS lookups with [host] or [host]:port. The [] form is required when you specify an IP address instead of a hostname.

A null transport and null nexthop result means "do not change": use the

delivery transport and nexthop information that would be used when the

entire transport table did not exist.

A non-null transport field with a null nexthop field resets the nexthop

information to the recipient domain.

A null transport field with non-null nexthop field does not modify the

transport information.

EEXXAAMMPPLLEESS In order to deliver internal mail directly, while using a mail relay for all other mail, specify a null entry for internal destinations (do

not change the delivery transport or the nexthop information) and spec-

ify a wildcard for all other destinations. mmyy..ddoommaaiinn :: ..mmyy..ddoommaaiinn ::

** ssmmttpp::oouuttbboouunndd-rreellaayy..mmyy..ddoommaaiinn

In order to send mail for eexxaammppllee..ccoomm and its subdomains via the uuuuccpp

transport to the UUCP host named eexxaammppllee:

eexxaammppllee..ccoomm uuuuccpp::eexxaammppllee ..eexxaammppllee..ccoomm uuuuccpp::eexxaammppllee When no nexthop host name is specified, the destination domain name is

used instead. For example, the following directs mail for user@eexxaamm-

ppllee..ccoomm via the ssllooww transport to a mail exchanger for eexxaammppllee..ccoomm.

The ssllooww transport could be configured to run at most one delivery

process at a time: eexxaammppllee..ccoomm ssllooww::

When no transport is specified, Postfix uses the transport that matches

the address domain class (see DESCRIPTION above). The following sends

all mail for eexxaammppllee..ccoomm and its subdomains to host ggaatteewwaayy..eexxaamm-

ppllee..ccoomm: eexxaammppllee..ccoomm ::[[ggaatteewwaayy..eexxaammppllee..ccoomm]] ..eexxaammppllee..ccoomm ::[[ggaatteewwaayy..eexxaammppllee..ccoomm]] In the above example, the [] suppress MX lookups. This prevents mail routing loops when your machine is primary MX host for eexxaammppllee..ccoomm. In the case of delivery via SMTP, one may specify hostname:service instead of just a host: eexxaammppllee..ccoomm ssmmttpp::bbaarr..eexxaammppllee::22002255 This directs mail for user@eexxaammppllee..ccoomm to host bbaarr..eexxaammppllee port 22002255. Instead of a numerical port a symbolic name may be used. Specify [] around the hostname if MX lookups must be disabled. The error mailer can be used to bounce mail: ..eexxaammppllee..ccoomm eerrrroorr::mmaaiill ffoorr **..eexxaammppllee..ccoomm iiss nnoott ddeelliivveerraabbllee This causes all mail for user@anything..eexxaammppllee..ccoomm to be bounced. 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, some.domain.hierarchy is not looked up via its parent domains, nor is user+foo@domain looked up as user@domain. 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 in Postfix version 2.1. Each lookup operation uses the entire recipient address once. Thus, some.domain.hierarchy is not looked up via its parent domains, nor is user+foo@domain looked up as user@domain. Results are the same as with indexed file lookups. CCOONNFFIIGGUURRAATTIIOONN PPAARRAAMMEETTEERRSS The following mmaaiinn..ccff parameters are especially relevant. The text below provides only a parameter summary. See postconf(5) for more details including examples. eemmppttyyaaddddrreessssrreecciippiieenntt The address that is looked up instead of the null sender address. ppaarreennttddoommaaiinnmmaattcchheessssuubbddoommaaiinnss List of Postfix features that use domain.tld patterns to match sub.domain.tld (as opposed to requiring .domain.tld patterns). ttrraannssppoorrttmmaappss