# SYNOPSIS 概要
# postmap /etc/postfix/transport
#
# postmap -q "string" /etc/postfix/transport
#
# postmap -q - /etc/postfix/transport <inputfile
#
#DESCRIPTION 描述
# The optional transport(5) table specifies a mapping from
# email addresses to message delivery transports and next-
# hop destinations. Message delivery transports such as
# local or smtp are defined in the master.cf file, and next-
# hop destinations are typically hosts or domain names. The
# table is searched by the trivial-rewrite(8) daemon.
可选transport(5)表指定了从电子邮件地址到消息分发传输和nexthop目的地的映射。
消息传递（如local或smtp）在master.cf文件中定义，nexthop目标通常是主机或域名。
这个表由trivial-rewrite(8)守护进程进行搜索
#
# This mapping overrides the default transport:nexthop
# selection that is built into Postfix:
这个映射覆盖了默认的transport:nexthop选择，它内置在Postfix:
#
# local_transport (default: local:$myhostname)
# This is the default for final delivery to domains
# listed with mydestination, and for [ipaddress] des-
# tinations that match $inet_interfaces or
# $proxy_interfaces. The default nexthop destination
# is the MTA hostname.
local_transport（默认值：local：$ myhostname）
这是最终传递使用mydestination列出的域的默认值，
并且匹配$ inet_interfaces或$ proxy_interfaces的[ipaddress]目标
默认的nexthop目标是MTA主机名。
#
# virtual_transport (default: virtual:)
# This is the default for final delivery to domains
# listed with virtual_mailbox_domains. The default
# nexthop destination is the recipient domain.
virtual_transport（默认值：virtual :)
这是最终传递使用virtual_mailbox_domains列出的域的默认值。
默认的nexthop目标是收件人域。
#
# relay_transport (default: relay:)
# This is the default for remote delivery to domains
# listed with relay_domains. In order of decreasing
# precedence, the nexthop destination is taken from
# relay_transport, sender_dependent_relayhost_maps,
# relayhost, or from the recipient domain.
relay_transport（默认：relay :)
这是远程传送到使用relay_domains列出的域的默认值。
以优先级递减的顺序，下一跳目的地取自relay_transport，sender_dependent_relayhost_maps，relayhost或收件人域。
#
# default_transport (default: smtp:)
# This is the default for remote delivery to other
# destinations. In order of decreasing precedence,
# the nexthop destination is taken from sender_depen-
# dent_default_transport_maps, default_transport,
# sender_dependent_relayhost_maps, relayhost, or from
# the recipient domain.
default_transport（默认：smtp :)
这是远程传送到其他目的地的默认值。
按照优先级降低的顺序，nexthop目标取自sender_dependent_default_transport_maps，default_transport，
sender_dependent_relayhost_maps，relayhost或来自收件人域。
#
# Normally, the transport(5) table is specified as a text
# file that serves as input to the postmap(1) command. The
# result, an indexed file in dbm or db format, is used for
# fast searching by the mail system. Execute the command
# "postmap /etc/postfix/transport" to rebuild an indexed
# file after changing the corresponding transport table.
通常，transport（5）表被指定为用作postmap（1）命令的输入的文本文件。
结果是dbm或db格式的索引文件，用于邮件系统的快速搜索。 更改相应的传输表后，
执行命令“postmap / etc / postfix / transport”重建索引文件。
#
# When the table is provided via other means such as NIS,
# LDAP or SQL, the same lookups are done as for ordinary
# indexed files.
当通过其他方式（如NIS，LDAP或SQL）提供表时，对于普通的索引文件，将完成相同的查找
#
# Alternatively, the table can be provided as a regular-
# expression map where patterns are given as regular expres-
# sions, 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".
或者，表可以作为正则表达式映射提供，其中模式作为正则表达式给出，或者查找可以被定向到基于TCP的服务器。
在这种情况下，查找的方式与“REGULAR EXPRESSION TABLES”或“TCP-BASED TABLES”所描述的方式略有不同。
#
# TABLE FORMAT 表格式
# The input format for the postmap(1) command is as follows:
postmap（1）命令的输入格式如下：
#
# 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 logi-
# cal line.
多行文字
逻辑行以非空格文本开始。 以空格开头的行也是是逻辑行
#
# The pattern specifies an email address, a domain name, or
# a domain name hierarchy, as described in section "TABLE
# LOOKUP".
模式指定电子邮件地址，域名或域名层次结构，如“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".
结果格式是transport：nexthop，并指定如何或何处传送邮件。 这在“RESULT FORMAT”一节中描述。
#
# 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:
使用索引文件（如DB或DBM）或从联网表（如NIS，LDAP或SQL）进行查找时，会按照以下顺序尝试模式：
#
# user+extension@domain transport:nexthop
# Deliver mail for user+extension@domain through
# transport to nexthop.
通过传输到nexthop，为user@domain发送邮件。
#
# user@domain transport:nexthop
# Deliver mail for user+extension@domain through tr-
# ansport to nexthop.
通过传输到nexthop，为user@domain发送邮件。
#
# domain transport:nexthop
# Deliver mail for domain through transport to nex-
# thop.
通过传输到nexthop，为domain发送邮件。
#
# .domain transport:nexthop
# Deliver mail for any subdomain of domain through
# transport to nexthop. This applies only when the
# string transport_maps is not listed in the par-
# ent_domain_matches_subdomains configuration set-
# ting. Otherwise, a domain name matches itself and
# its subdomains.
通过传输到nexthop，为域的任何子域传送邮件。
只有当字符串transport_maps没有在parent_domain_matches_subdomains配置设置中列出时才适用。
否则，域名与其子域相匹配。
#
# * transport:nexthop
# The special pattern * represents any address (i.e.
# it functions as the wild-card pattern, and is
# unique to Postfix transport tables).
"*"通配符。表示任意地址。并且是Postfix传输表唯一的。
#
# Note 1: the null recipient address is looked up as
# $empty_address_recipient@$myhostname (default: mailer-dae-
# mon@hostname).
注1：空收件人地址被查找为$empty_address_recipient@$myhostname（默认：mailer-daemon@hostname）。
#
# Note 2: user@domain or user+extension@domain lookup is
# available in Postfix 2.0 and later.
#
# RESULT FORMAT
# The lookup result is of the form transport:nexthop. The
# transport field specifies a mail delivery transport such
# as smtp or local. The nexthop field specifies where and
# how to deliver mail.
查找结果的形式为transport：nexthop。传输的字段指定诸如smtp或本地的邮件传递传输。
nexthop字段指定在何处以及如何传送邮件。
#
# The transport field specifies the name of a mail delivery
# transport (the first name of a mail delivery service entry
# in the Postfix master.cf file).
传输字段指定邮件传递传输的名称（Postfix master.cf文件中邮件传递服务条目的名称）。
#
# 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.
对nexthop字段的解释是传输的依赖。
在SMTP的情况下，将非默认端口上的服务指定为host：service，并使用[host]或[host]：port禁用MX（邮件交换器）DNS查找。
当您指定IP地址而不是主机名时，[]表单是必需的。
#
# A null transport and null nexthop result means "do not
# change": use the delivery transport and nexthop informa-
# tion that would be used when the entire transport table
# did not exist.
空传输和空nexthop结果意味着“不要更改”：在整个传输表不存在时将使用的传递传输和下一跳信息。
#
# A non-null transport field with a null nexthop field
# resets the nexthop information to the recipient domain.
一个非空传输字段包含一个空nexthop字段，重置nexthop信息到收件人的域。
#
# A null transport field with non-null nexthop field does
# not modify the transport information.
一个空的传输字段包含非空的nexthop字段不会修改信息。
#
# EXAMPLES
# 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 trans-
# port or the nexthop information) and specify a wildcard
# for all other destinations.
为了直接发送内部邮件，在为所有其他邮件使用邮件中继时，请为内部目的地指定一个空条目（不要更改传递传输或nexthop信息），并为所有其他目的地指定一个通配符。
#
# my.domain :
# .my.domain :
# * smtp:outbound-relay.my.domain
#
# In order to send mail for example.com and its subdomains
# via the uucp transport to the UUCP host named example:
为了通过uucp传输将example.com及其子域的邮件发送到名为example的UUCP主机：
#
# example.com uucp:example
# .example.com uucp:example
#
# When no nexthop host name is specified, the destination
# domain name is used instead. For example, the following
# directs mail for user@example.com via the slow transport
# to a mail exchanger for example.com. The slow transport
# could be configured to run at most one delivery process at
# a time:
当没有指定nexthop主机名时，将使用目的域名。
例如，以下命令为user@example.com的邮件，通过缓慢的传输到example.com的邮件交换器。
缓慢的传输可以配置为一次运行最多一个交付过程：
#
# example.com slow:
#
# When no transport is specified, Postfix uses the transport
# that matches the address domain class (see DESCRIPTION
# above). The following sends all mail for example.com and
# its subdomains to host gateway.example.com:
当没有指定传输时，Postfix使用与地址域类匹配的传输（参见上面的描述）。
以下将example.com及其子域的所有邮件发送到主机gateway.example.com：
#
# example.com :[gateway.example.com]
# .example.com :[gateway.example.com]
#
# In the above example, the [] suppress MX lookups. This
# prevents mail routing loops when your machine is primary
# MX host for example.com.
在上面的例子中，[]抑制MX查找。当您的计算机是example.com的主MX主机时，可以防止邮件路由循环。
#
# In the case of delivery via SMTP, one may specify host-
# name:service instead of just a host:
在通过SMTP传送的情况下，可以指定主机名：服务而不是主机：
#
# example.com smtp:bar.example:2025
#
# This directs mail for user@example.com to host bar.example
# port 2025. Instead of a numerical port a symbolic name may
# be used. Specify [] around the hostname if MX lookups must
# be disabled.
这会将mail@example.com的邮件指向主机bar.example端口2025.
而不是数字端口，可以使用符号名称。如果必须禁用MX查找，请指定主机名周围的[]。
#
# The error mailer can be used to bounce mail:
错误邮件程序可以用来反弹邮件：
#
# .example.com error:mail for *.example.com is not deliverable
#
# This causes all mail for user@anything.example.com to be
# bounced.
这将导致所有mail@anything.example.com的邮件退回。
#
# 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).
本节介绍当表中的正则表达式的形式给出查表如何变化。
#
# 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.
每个模式都是一个正则表达式，应用于正在查找的整个地址。
因此，some.domain.hierarchy不是通过其父域查找，也不是user+foo@domain查找为user@domain。
#
# Patterns are applied in the order as specified in the ta-
# ble, until a pattern is found that matches the search
# string.
按照表中指定的顺序应用模式，直到找到符合搜索字符串的模式。
#
# The trivial-rewrite(8) server disallows regular expression
# substitution of $1 etc. in regular expression lookup
# tables, because that could open a security hole (Postfix
# version 2.3 and later).
trivial-rewrite（8）服务器不允许正则表达式查找表中正则表达式替换$1等等，因为这可能会打开安全漏洞（Postfix版本2.3及更高版本）。
#
# TCP-BASED TABLES
# This section describes how the table lookups change when
# lookups are directed to a TCP-based server. For a descrip-
# tion of the TCP client/server lookup protocol, see tcp_ta-
# ble(5). This feature is not available up to and including
# Postfix version 2.4.
本节介绍查找被定向到一个基于TCP的服务器查表如何变化。
有关TCP客户端/服务器查找协议的描述，请参见tcp_table（5）。 此功能不适用于Postfix版本2.4。
#
# 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.
每次查找操作都使用整个收件人地址一次。
因此，some.domain.hierarchy不是通过其父域查找，也不是user+foo@domain查找为user@domain。
#
# Results are the same as with indexed file lookups.
结果与索引文件查找相同。
#
# CONFIGURATION PARAMETERS
# The following main.cf parameters are especially relevant.
# The text below provides only a parameter summary. See
# postconf(5) for more details including examples.
以下main.cf参数尤其重要。下面的文本只提供一个参数摘要。有关更多详细信息，请参阅postconf（5）。
#
# empty_address_recipient
# The address that is looked up instead of the null
# sender address.
查找的地址代替空发件人地址。
#
# parent_domain_matches_subdomains
# List of Postfix features that use domain.tld pat-
# terns to match sub.domain.tld (as opposed to
# requiring .domain.tld patterns).
使用domain.tld模式匹配sub.domain.tld（而不是要求.domain.tld模式）的Postfix功能列表。
#
# transport_maps
# List of transport lookup tables.
传输查询表列表
#
# SEE ALSO
# trivial-rewrite(8), rewrite and resolve addresses
# master(5), master.cf file format
# postconf(5), configuration parameters
# postmap(1), Postfix lookup table manager
#
# README FILES
# Use "postconf readme_directory" or "postconf html_direc-
# tory" to locate this information.
# ADDRESS_REWRITING_README, address rewriting guide
# DATABASE_README, Postfix lookup table overview
# FILTER_README, external content filter
#
# LICENSE
# The Secure Mailer license must be distributed with this
# software.
#
# AUTHOR(S)
# Wietse Venema
# IBM T.J. Watson Research
# P.O. Box 704
# Yorktown Heights, NY 10598, USA
#
# TRANSPORT(5)
Postfix邮件路由
最新推荐文章于 2024-04-16 20:25:30 发布
扫一扫
3735
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
