1TRIVIAL-REWRITE(8) System Manager's Manual TRIVIAL-REWRITE(8)
2
6 trivial-rewrite - Postfix address rewriting and resolving daemon
7
9 trivial-rewrite [generic Postfix daemon options]
10
12 The trivial-rewrite(8) daemon processes three types of client service
13 requests:
14 rewrite context address
16 Rewrite an address to standard form, according to the address
17 rewriting context:
18 local Append the domain names specified with $myorigin or
20 $mydomain to incomplete addresses; do swap_bangpath and
21 allow_percent_hack processing as described below, and
22 strip source routed addresses (@site,@site:user@domain)
23 to user@domain form.
24 remote Append the domain name specified with $remote_header_re‐
26 write_domain to incomplete addresses. Otherwise the
27 result is identical to that of the local address rewrit‐
28 ing context. This prevents Postfix from appending the
29 local domain to spam from poorly written remote clients.
30 resolve sender address
32 Resolve the address to a (transport, nexthop, recipient, flags)
33 quadruple. The meaning of the results is as follows:
34 transport
36 The delivery agent to use. This is the first field of an
37 entry in the master.cf file.
38 nexthop
40 The host to send to and optional delivery method informa‐
41 tion.
42 recipient
44 The envelope recipient address that is passed on to nex‐
45 thop.
46 flags The address class, whether the address requires relaying,
48 whether the address has problems, and whether the request
49 failed.
50 verify sender address
52 Resolve the address for address verification purposes.
53
55 The trivial-rewrite(8) servers run under control by the Postfix master
56 server. Each server can handle multiple simultaneous connections.
57 When all servers are busy while a client connects, the master creates a
58 new server process, provided that the trivial-rewrite server process
59 limit is not exceeded. Each trivial-rewrite server terminates after
60 serving at least $max_use clients of after $max_idle seconds of idle
61 time.
62
64 None. The command does not interact with the outside world.
65
67 The trivial-rewrite(8) daemon is not security sensitive. By default,
68 this daemon does not talk to remote or local users. It can run at a
69 fixed low privilege in a chrooted environment.
70
72 Problems and transactions are logged to syslogd(8).
73
75 On busy mail systems a long time may pass before a main.cf change
76 affecting trivial-rewrite(8) is picked up. Use the command "postfix
77 reload" to speed up a change.
78 The text below provides only a parameter summary. See postconf(5) for
80 more details including examples.
81
83 resolve_dequoted_address (yes)
84 Resolve a recipient address safely instead of correctly, by
85 looking inside quotes.
86 resolve_null_domain (no)
88 Resolve an address that ends in the "@" null domain as if the
89 local hostname were specified, instead of rejecting the address
90 as invalid.
91 resolve_numeric_domain (no)
93 Resolve "user@ipaddress" as "user@[ipaddress]", instead of
94 rejecting the address as invalid.
95 Available with Postfix version 2.5 and later:
97 allow_min_user (no)
99 Allow a sender or recipient address to have `-' as the first
100 character.
101
103 myorigin ($myhostname)
104 The domain name that locally-posted mail appears to come from,
105 and that locally posted mail is delivered to.
106 allow_percent_hack (yes)
108 Enable the rewriting of the form "user%domain" to "user@domain".
109 append_at_myorigin (yes)
111 With locally submitted mail, append the string "@$myorigin" to
112 mail addresses without domain information.
113 append_dot_mydomain (yes)
115 With locally submitted mail, append the string ".$mydomain" to
116 addresses that have no ".domain" information.
117 recipient_delimiter (empty)
119 The separator between user names and address extensions
120 (user+foo).
121 swap_bangpath (yes)
123 Enable the rewriting of "site!user" into "user@site".
124 Available in Postfix 2.2 and later:
126 remote_header_rewrite_domain (empty)
128 Don't rewrite message headers from remote clients at all when
129 this parameter is empty; otherwise, rewrite message headers and
130 append the specified domain name to incomplete addresses.
131
133 The following is applicable to Postfix version 2.0 and later. Earlier
134 versions do not have support for: virtual_transport, relay_transport,
135 virtual_alias_domains, virtual_mailbox_domains or proxy_interfaces.
136 local_transport (local:$myhostname)
138 The default mail delivery transport and next-hop destination for
139 final delivery to domains listed with mydestination, and for
140 [ipaddress] destinations that match $inet_interfaces or
141 $proxy_interfaces.
142 virtual_transport (virtual)
144 The default mail delivery transport and next-hop destination for
145 final delivery to domains listed with $virtual_mailbox_domains.
146 relay_transport (relay)
148 The default mail delivery transport and next-hop destination for
149 remote delivery to domains listed with $relay_domains.
150 default_transport (smtp)
152 The default mail delivery transport and next-hop destination for
153 destinations that do not match $mydestination, $inet_interfaces,
154 $proxy_interfaces, $virtual_alias_domains, $virtual_mail‐
155 box_domains, or $relay_domains.
156 parent_domain_matches_subdomains (see 'postconf -d' output)
158 What Postfix features match subdomains of "domain.tld" automati‐
159 cally, instead of requiring an explicit ".domain.tld" pattern.
160 relayhost (empty)
162 The next-hop destination of non-local mail; overrides non-local
163 domains in recipient addresses.
164 transport_maps (empty)
166 Optional lookup tables with mappings from recipient address to
167 (message delivery transport, next-hop destination).
168 Available in Postfix version 2.3 and later:
170 sender_dependent_relayhost_maps (empty)
172 A sender-dependent override for the global relayhost parameter
173 setting.
174 Available in Postfix version 2.5 and later:
176 empty_address_relayhost_maps_lookup_key (<>)
178 The sender_dependent_relayhost_maps search string that will be
179 used instead of the null sender address.
180
182 Postfix version 2.1 introduces sender and recipient address verifica‐
183 tion. This feature is implemented by sending probe email messages that
184 are not actually delivered. By default, address verification probes
185 use the same route as regular mail. To override specific aspects of
186 message routing for address verification probes, specify one or more of
187 the following:
188 address_verify_local_transport ($local_transport)
190 Overrides the local_transport parameter setting for address ver‐
191 ification probes.
192 address_verify_virtual_transport ($virtual_transport)
194 Overrides the virtual_transport parameter setting for address
195 verification probes.
196 address_verify_relay_transport ($relay_transport)
198 Overrides the relay_transport parameter setting for address ver‐
199 ification probes.
200 address_verify_default_transport ($default_transport)
202 Overrides the default_transport parameter setting for address
203 verification probes.
204 address_verify_relayhost ($relayhost)
206 Overrides the relayhost parameter setting for address verifica‐
207 tion probes.
208 address_verify_transport_maps ($transport_maps)
210 Overrides the transport_maps parameter setting for address veri‐
211 fication probes.
212 Available in Postfix version 2.3 and later:
214 address_verify_sender_dependent_relayhost_maps ($sender_depen‐
216 dent_relayhost_maps)
217 Overrides the sender_dependent_relayhost_maps parameter setting
218 for address verification probes.
219
221 config_directory (see 'postconf -d' output)
222 The default location of the Postfix main.cf and master.cf con‐
223 figuration files.
224 daemon_timeout (18000s)
226 How much time a Postfix daemon process may take to handle a
227 request before it is terminated by a built-in watchdog timer.
228 empty_address_recipient (MAILER-DAEMON)
230 The recipient of mail addressed to the null address.
231 ipc_timeout (3600s)
233 The time limit for sending or receiving information over an
234 internal communication channel.
235 max_idle (100s)
237 The maximum amount of time that an idle Postfix daemon process
238 waits for an incoming connection before terminating voluntarily.
239 max_use (100)
241 The maximal number of incoming connections that a Postfix daemon
242 process will service before terminating voluntarily.
243 relocated_maps (empty)
245 Optional lookup tables with new contact information for users or
246 domains that no longer exist.
247 process_id (read-only)
249 The process ID of a Postfix command or daemon process.
250 process_name (read-only)
252 The process name of a Postfix command or daemon process.
253 queue_directory (see 'postconf -d' output)
255 The location of the Postfix top-level queue directory.
256 show_user_unknown_table_name (yes)
258 Display the name of the recipient table in the "User unknown"
259 responses.
260 syslog_facility (mail)
262 The syslog facility of Postfix logging.
263 syslog_name (see 'postconf -d' output)
265 The mail system name that is prepended to the process name in
266 syslog records, so that "smtpd" becomes, for example, "post‐
267 fix/smtpd".
268 Available in Postfix version 2.0 and later:
270 helpful_warnings (yes)
272 Log warnings about problematic configuration settings, and pro‐
273 vide helpful suggestions.
274
276 postconf(5), configuration parameters
277 transport(5), transport table format
278 relocated(5), format of the "user has moved" table
279 master(8), process manager
280 syslogd(8), system logging
281
283 Use "postconf readme_directory" or "postconf html_directory" to locate
284 this information.
285 ADDRESS_CLASS_README, Postfix address classes howto
286 ADDRESS_VERIFICATION_README, Postfix address verification
287
289 The Secure Mailer license must be distributed with this software.
290
292 Wietse Venema
293 IBM T.J. Watson Research
294 P.O. Box 704
295 Yorktown Heights, NY 10598, USA
296 TRIVIAL-REWRITE(8)