36
36
# Mail for any other destination is by default deliv-
37
37
# ered via $default_transport.
39
# Normally, the transport table is specified as a text file
40
# that serves as input to the postmap(1) command. The
39
# Normally, the transport(5) table is specified as a text
40
# file that serves as input to the postmap(1) command. The
41
41
# result, an indexed file in dbm or db format, is used for
42
42
# fast searching by the mail system. Execute the command
43
# postmap /etc/postfix/transport in order to rebuild the
43
# "postmap /etc/postfix/transport" in order to rebuild the
44
44
# indexed file after changing the transport table.
46
46
# When the table is provided via other means such as NIS,
79
79
# how or where to deliver mail. This is described in section
83
83
# With lookups from indexed files such as DB or DBM, or from
84
84
# networked tables such as NIS, LDAP or SQL, patterns are
85
85
# tried in the order as listed below:
87
87
# user+extension@domain transport:nexthop
88
# Mail for user+extension@domain is delivered through
88
# Deliver mail for user+extension@domain through
89
89
# transport to nexthop.
91
91
# user@domain transport:nexthop
92
# Mail for user@domain is delivered through transport
92
# Deliver mail for user@domain through transport to
95
95
# domain transport:nexthop
96
# Mail for domain is delivered through transport to
96
# Deliver mail for domain through transport to nex-
99
99
# .domain transport:nexthop
100
# Mail for any subdomain of domain is delivered
101
# through transport to nexthop. This applies only
102
# when the string transport_maps is not listed in the
103
# parent_domain_matches_subdomains configuration set-
100
# Deliver mail for any subdomain of domain through
101
# transport to nexthop. This applies only when the
102
# string transport_maps is not listed in the par-
103
# ent_domain_matches_subdomains configuration set-
104
104
# ting. Otherwise, a domain name matches itself and
105
105
# its subdomains.
111
111
# $empty_address_recipient@$myhostname (default: mailer-dae-
114
# Note 3: user@domain or user+extension@domain lookup is
115
# available in Postfix 2.0 and later.
115
# The lookup result is of the form transport:nexthop. The
116
# transport field specifies a mail delivery transport such
117
# as smtp or local. The nexthop field specifies where and
118
# The lookup result is of the form transport:nexthop. The
119
# transport field specifies a mail delivery transport such
120
# as smtp or local. The nexthop field specifies where and
118
121
# how to deliver mail.
120
# The transport field specifies the name of a mail delivery
123
# The transport field specifies the name of a mail delivery
121
124
# transport (the first name of a mail delivery service entry
122
125
# in the Postfix master.cf file).
124
# The interpretation of the nexthop field is transport
125
# dependent. In the case of SMTP, specify a service on a
126
# non-default port as host:service, and disable MX (mail
127
# exchanger) DNS lookups with [host] or [host]:port. The []
127
# The interpretation of the nexthop field is transport
128
# dependent. In the case of SMTP, specify a service on a
129
# non-default port as host:service, and disable MX (mail
130
# exchanger) DNS lookups with [host] or [host]:port. The []
128
131
# form is required when you specify an IP address instead of
131
# A null transport and null nexthop result means "do not
132
# change": use the delivery transport and nexthop informa-
133
# tion that would be used when the entire transport table
134
# A null transport and null nexthop result means "do not
135
# change": use the delivery transport and nexthop informa-
136
# tion that would be used when the entire transport table
136
# A non-null transport field with a null nexthop field
139
# A non-null transport field with a null nexthop field
137
140
# resets the nexthop information to the recipient domain.
139
# A null transport field with non-null nexthop field does
142
# A null transport field with non-null nexthop field does
140
143
# not modify the transport information.
143
# In order to deliver internal mail directly, while using a
144
# mail relay for all other mail, specify a null entry for
145
# internal destinations (do not change the delivery trans-
146
# port or the nexthop information) and specify a wildcard
146
# In order to deliver internal mail directly, while using a
147
# mail relay for all other mail, specify a null entry for
148
# internal destinations (do not change the delivery trans-
149
# port or the nexthop information) and specify a wildcard
147
150
# for all other destinations.
151
154
# * smtp:outbound-relay.my.domain
153
# In order to send mail for example.com and its subdomains
156
# In order to send mail for example.com and its subdomains
154
157
# via the uucp transport to the UUCP host named example:
156
159
# example.com uucp:example
157
160
# .example.com uucp:example
159
# When no nexthop host name is specified, the destination
160
# domain name is used instead. For example, the following
161
# directs mail for user@example.com via the slow transport
162
# to a mail exchanger for example.com. The slow transport
162
# When no nexthop host name is specified, the destination
163
# domain name is used instead. For example, the following
164
# directs mail for user@example.com via the slow transport
165
# to a mail exchanger for example.com. The slow transport
163
166
# could be configured to run at most one delivery process at
166
169
# example.com slow:
168
171
# When no transport is specified, Postfix uses the transport
169
# that matches the address domain class (see DESCRIPTION
170
# above). The following sends all mail for example.com and
172
# that matches the address domain class (see DESCRIPTION
173
# above). The following sends all mail for example.com and
171
174
# its subdomains to host gateway.example.com:
173
176
# example.com :[gateway.example.com]
174
177
# .example.com :[gateway.example.com]
176
# In the above example, the [] suppress MX lookups. This
177
# prevents mail routing loops when your machine is primary
179
# In the above example, the [] suppress MX lookups. This
180
# prevents mail routing loops when your machine is primary
178
181
# MX host for example.com.
180
# In the case of delivery via SMTP, one may specify host-
183
# In the case of delivery via SMTP, one may specify host-
181
184
# name:service instead of just a host:
183
186
# example.com smtp:bar.example:2025
190
193
# The error mailer can be used to bounce mail:
192
# .example.com error:mail for *.example.com is not
195
# .example.com error:mail for *.example.com is not
195
# This causes all mail for user@anything.example.com to be
198
# This causes all mail for user@anything.example.com to be
198
201
# REGULAR EXPRESSION TABLES
199
# This section describes how the table lookups change when
202
# This section describes how the table lookups change when
200
203
# the table is given in the form of regular expressions. For
201
# a description of regular expression lookup table syntax,
204
# a description of regular expression lookup table syntax,
202
205
# see regexp_table(5) or pcre_table(5).
204
# Each pattern is a regular expression that is applied to
205
# the entire address being looked up. Thus,
206
# some.domain.hierarchy is not looked up via its parent
207
# domains, nor is user+foo@domain looked up as user@domain.
207
# Each pattern is a regular expression that is applied to
208
# the entire address being looked up. Thus,
209
# some.domain.hierarchy is not looked up via its parent
210
# domains, nor is user+foo@domain looked up as user@domain.
209
# Patterns are applied in the order as specified in the
210
# table, until a pattern is found that matches the search
212
# Patterns are applied in the order as specified in the
213
# table, until a pattern is found that matches the search
213
# Results are the same as with indexed file lookups, with
214
# the additional feature that parenthesized substrings from
216
# Results are the same as with indexed file lookups, with
217
# the additional feature that parenthesized substrings from
215
218
# the pattern can be interpolated as $1, $2 and so on.
217
220
# TCP-BASED TABLES
218
# This section describes how the table lookups change when
221
# This section describes how the table lookups change when
219
222
# lookups are directed to a TCP-based server. For a descrip-
220
# tion of the TCP client/server lookup protocol, see
221
# tcp_table(5). This feature is not available in Postfix
223
# tion of the TCP client/server lookup protocol, see
224
# tcp_table(5). This feature is not available up to and
225
# including Postfix version 2.2.
224
# Each lookup operation uses the entire recipient address
225
# once. Thus, some.domain.hierarchy is not looked up via
226
# its parent domains, nor is user+foo@domain looked up as
227
# Each lookup operation uses the entire recipient address
228
# once. Thus, some.domain.hierarchy is not looked up via
229
# its parent domains, nor is user+foo@domain looked up as
229
232
# Results are the same as with indexed file lookups.
231
234
# CONFIGURATION PARAMETERS
232
# The following main.cf parameters are especially relevant.
233
# The text below provides only a parameter summary. See
235
# The following main.cf parameters are especially relevant.
236
# The text below provides only a parameter summary. See
234
237
# postconf(5) for more details including examples.
236
239
# empty_address_recipient
237
# The address that is looked up instead of the null
240
# The address that is looked up instead of the null
238
241
# sender address.
240
243
# parent_domain_matches_subdomains
241
# List of Postfix features that use domain.tld pat-
242
# terns to match sub.domain.tld (as opposed to
244
# List of Postfix features that use domain.tld pat-
245
# terns to match sub.domain.tld (as opposed to
243
246
# requiring .domain.tld patterns).
added
removed
conf/transport
