1TRIVIAL-REWRITE(8)          System Manager's Manual         TRIVIAL-REWRITE(8)
2
3
4

NAME

6       trivial-rewrite - Postfix address rewriting and resolving daemon
7

SYNOPSIS

9       trivial-rewrite [generic Postfix daemon options]
10

DESCRIPTION

12       The  trivial-rewrite(8)  daemon processes three types of client service
13       requests:
14
15       rewrite context address
16              Rewrite an address to standard form, according  to  the  address
17              rewriting context:
18
19              local  Append  the domain names specified with $myorigin or $my‐
20                     domain to incomplete addresses; do swap_bangpath and  al‐
21                     low_percent_hack processing as described below, and strip
22                     source  routed  addresses  (@site,@site:user@domain)   to
23                     user@domain form.
24
25              remote Append  the domain name specified with $remote_header_re‐
26                     write_domain to incomplete addresses. Otherwise  the  re‐
27                     sult  is identical to that of the local address rewriting
28                     context. This prevents Postfix from appending  the  local
29                     domain to spam from poorly written remote clients.
30
31       resolve sender address
32              Resolve  the address to a (transport, nexthop, recipient, flags)
33              quadruple. The meaning of the results is as follows:
34
35              transport
36                     The delivery agent to use. This is the first field of  an
37                     entry in the master.cf file.
38
39              nexthop
40                     The host to send to and optional delivery method informa‐
41                     tion.
42
43              recipient
44                     The envelope recipient address that is passed on to  nex‐
45                     thop.
46
47              flags  The address class, whether the address requires relaying,
48                     whether the address has problems, and whether the request
49                     failed.
50
51       verify sender address
52              Resolve the address for address verification purposes.
53

SERVER PROCESS MANAGEMENT

55       The  trivial-rewrite(8)  servers  run under control by the Postfix mas‐
56       ter(8) server.  Each server can handle  multiple  simultaneous  connec‐
57       tions.   When  all servers are busy while a client connects, the master
58       creates a new server process, provided that the trivial-rewrite  server
59       process  limit is not exceeded.  Each trivial-rewrite server terminates
60       after serving at least $max_use clients of after $max_idle  seconds  of
61       idle time.
62

STANDARDS

64       None. The command does not interact with the outside world.
65

SECURITY

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

DIAGNOSTICS

72       Problems and transactions are logged to syslogd(8) or postlogd(8).
73

CONFIGURATION PARAMETERS

75       On  busy  mail systems a long time may pass before a main.cf change af‐
76       fecting trivial-rewrite(8) is  picked  up.  Use  the  command  "postfix
77       reload" to speed up a change.
78
79       The  text  below provides only a parameter summary. See postconf(5) for
80       more details including examples.
81

COMPATIBILITY CONTROLS

83       resolve_dequoted_address (yes)
84              Resolve a recipient address  safely  instead  of  correctly,  by
85              looking inside quotes.
86
87       Available with Postfix version 2.1 and later:
88
89       resolve_null_domain (no)
90              Resolve  an  address  that ends in the "@" null domain as if the
91              local hostname were specified, instead of rejecting the  address
92              as invalid.
93
94       Available with Postfix version 2.3 and later:
95
96       resolve_numeric_domain (no)
97              Resolve  "user@ipaddress"  as "user@[ipaddress]", instead of re‐
98              jecting the address as invalid.
99
100       Available with Postfix version 2.5 and later:
101
102       allow_min_user (no)
103              Allow a sender or recipient address to have  `-'  as  the  first
104              character.
105

ADDRESS REWRITING CONTROLS

107       myorigin ($myhostname)
108              The  domain  name that locally-posted mail appears to come from,
109              and that locally posted mail is delivered to.
110
111       allow_percent_hack (yes)
112              Enable the rewriting of the form "user%domain" to "user@domain".
113
114       append_at_myorigin (yes)
115              With locally submitted mail, append the string  "@$myorigin"  to
116              mail addresses without domain information.
117
118       append_dot_mydomain (Postfix >= 3.0: no, Postfix < 3.0: yes)
119              With  locally  submitted mail, append the string ".$mydomain" to
120              addresses that have no ".domain" information.
121
122       recipient_delimiter (empty)
123              The set of characters that can separate an email address  local‐
124              part, user name, or a .forward file name from its extension.
125
126       swap_bangpath (yes)
127              Enable the rewriting of "site!user" into "user@site".
128
129       Available in Postfix 2.2 and later:
130
131       remote_header_rewrite_domain (empty)
132              Don't  rewrite  message  headers from remote clients at all when
133              this parameter is empty; otherwise, rewrite message headers  and
134              append the specified domain name to incomplete addresses.
135

ROUTING CONTROLS

137       The  following is applicable to Postfix version 2.0 and later.  Earlier
138       versions do not have support for:  virtual_transport,  relay_transport,
139       virtual_alias_domains, virtual_mailbox_domains or proxy_interfaces.
140
141       local_transport (local:$myhostname)
142              The default mail delivery transport and next-hop destination for
143              final delivery to domains listed  with  mydestination,  and  for
144              [ipaddress]   destinations   that   match   $inet_interfaces  or
145              $proxy_interfaces.
146
147       virtual_transport (virtual)
148              The default mail delivery transport and next-hop destination for
149              final delivery to domains listed with $virtual_mailbox_domains.
150
151       relay_transport (relay)
152              The default mail delivery transport and next-hop destination for
153              remote delivery to domains listed with $relay_domains.
154
155       default_transport (smtp)
156              The default mail delivery transport and next-hop destination for
157              destinations that do not match $mydestination, $inet_interfaces,
158              $proxy_interfaces, $virtual_alias_domains,  $virtual_mailbox_do‐
159              mains, or $relay_domains.
160
161       parent_domain_matches_subdomains (see 'postconf -d' output)
162              A  list of Postfix features where the pattern "example.com" also
163              matches subdomains of example.com, instead of requiring  an  ex‐
164              plicit ".example.com" pattern.
165
166       relayhost (empty)
167              The   next-hop  destination(s)  for  non-local  mail;  overrides
168              non-local domains in recipient addresses.
169
170       transport_maps (empty)
171              Optional lookup tables with mappings from recipient  address  to
172              (message delivery transport, next-hop destination).
173
174       Available in Postfix version 2.3 and later:
175
176       sender_dependent_relayhost_maps (empty)
177              A  sender-dependent  override for the global relayhost parameter
178              setting.
179
180       Available in Postfix version 2.5 and later:
181
182       empty_address_relayhost_maps_lookup_key (<>)
183              The sender_dependent_relayhost_maps search string that  will  be
184              used instead of the null sender address.
185
186       Available in Postfix version 2.7 and later:
187
188       empty_address_default_transport_maps_lookup_key (<>)
189              The  sender_dependent_default_transport_maps  search string that
190              will be used instead of the null sender address.
191
192       sender_dependent_default_transport_maps (empty)
193              A sender-dependent override for the global default_transport pa‐
194              rameter setting.
195

ADDRESS VERIFICATION CONTROLS

197       Postfix  version  2.1 introduces sender and recipient address verifica‐
198       tion.  This feature is implemented by sending probe email messages that
199       are  not  actually  delivered.  By default, address verification probes
200       use the same route as regular mail. To  override  specific  aspects  of
201       message routing for address verification probes, specify one or more of
202       the following:
203
204       address_verify_local_transport ($local_transport)
205              Overrides the local_transport parameter setting for address ver‐
206              ification probes.
207
208       address_verify_virtual_transport ($virtual_transport)
209              Overrides  the  virtual_transport  parameter setting for address
210              verification probes.
211
212       address_verify_relay_transport ($relay_transport)
213              Overrides the relay_transport parameter setting for address ver‐
214              ification probes.
215
216       address_verify_default_transport ($default_transport)
217              Overrides  the  default_transport  parameter setting for address
218              verification probes.
219
220       address_verify_relayhost ($relayhost)
221              Overrides the relayhost parameter setting for address  verifica‐
222              tion probes.
223
224       address_verify_transport_maps ($transport_maps)
225              Overrides the transport_maps parameter setting for address veri‐
226              fication probes.
227
228       Available in Postfix version 2.3 and later:
229
230       address_verify_sender_dependent_relayhost_maps   ($sender_dependent_re‐
231       layhost_maps)
232              Overrides  the sender_dependent_relayhost_maps parameter setting
233              for address verification probes.
234
235       Available in Postfix version 2.7 and later:
236
237       address_verify_sender_dependent_default_transport_maps  ($sender_depen‐
238       dent_default_transport_maps)
239              Overrides  the sender_dependent_default_transport_maps parameter
240              setting for address verification probes.
241

MISCELLANEOUS CONTROLS

243       config_directory (see 'postconf -d' output)
244              The default location of the Postfix main.cf and  master.cf  con‐
245              figuration files.
246
247       daemon_timeout (18000s)
248              How  much time a Postfix daemon process may take to handle a re‐
249              quest before it is terminated by a built-in watchdog timer.
250
251       empty_address_recipient (MAILER-DAEMON)
252              The recipient of mail addressed to the null address.
253
254       ipc_timeout (3600s)
255              The time limit for sending or receiving information over an  in‐
256              ternal communication channel.
257
258       max_idle (100s)
259              The  maximum  amount of time that an idle Postfix daemon process
260              waits for an incoming connection before terminating voluntarily.
261
262       max_use (100)
263              The maximal number of incoming connections that a Postfix daemon
264              process will service before terminating voluntarily.
265
266       relocated_maps (empty)
267              Optional lookup tables with new contact information for users or
268              domains that no longer exist.
269
270       process_id (read-only)
271              The process ID of a Postfix command or daemon process.
272
273       process_name (read-only)
274              The process name of a Postfix command or daemon process.
275
276       queue_directory (see 'postconf -d' output)
277              The location of the Postfix top-level queue directory.
278
279       show_user_unknown_table_name (yes)
280              Display the name of the recipient table in  the  "User  unknown"
281              responses.
282
283       syslog_facility (mail)
284              The syslog facility of Postfix logging.
285
286       syslog_name (see 'postconf -d' output)
287              A  prefix  that  is  prepended  to  the  process  name in syslog
288              records, so that, for example, "smtpd" becomes "prefix/smtpd".
289
290       Available in Postfix version 2.0 and later:
291
292       helpful_warnings (yes)
293              Log warnings about problematic configuration settings, and  pro‐
294              vide helpful suggestions.
295
296       Available in Postfix 3.3 and later:
297
298       service_name (read-only)
299              The master.cf service name of a Postfix daemon process.
300

SEE ALSO

302       postconf(5), configuration parameters
303       transport(5), transport table format
304       relocated(5), format of the "user has moved" table
305       master(8), process manager
306       postlogd(8), Postfix logging
307       syslogd(8), system logging
308

README FILES

310       Use  "postconf readme_directory" or "postconf html_directory" to locate
311       this information.
312       ADDRESS_CLASS_README, Postfix address classes howto
313       ADDRESS_VERIFICATION_README, Postfix address verification
314

LICENSE

316       The Secure Mailer license must be distributed with this software.
317

AUTHOR(S)

319       Wietse Venema
320       IBM T.J. Watson Research
321       P.O. Box 704
322       Yorktown Heights, NY 10598, USA
323
324       Wietse Venema
325       Google, Inc.
326       111 8th Avenue
327       New York, NY 10011, USA
328
329
330
331                                                            TRIVIAL-REWRITE(8)
Impressum