xref: /netbsd-src/external/ibm-public/postfix/dist/html/postconf.1.html (revision e6c7e151de239c49d2e38720a061ed9d1fa99309)
1<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"
2        "http://www.w3.org/TR/html4/loose.dtd">
3<html> <head>
4<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
5<title> Postfix manual - postconf(1) </title>
6</head> <body> <pre>
7POSTCONF(1)                                                        POSTCONF(1)
8
9<b>NAME</b>
10       postconf - Postfix configuration utility
11
12<b>SYNOPSIS</b>
13   <b>Managing <a href="postconf.5.html">main.cf</a>:</b>
14
15       <b>postconf</b> [<b>-dfhHnopvx</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<b>-C</b> <i>class,...</i>] [<i>parameter ...</i>]
16
17       <b>postconf</b> [<b>-epv</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <i>parameter</i><b>=</b><i>value ...</i>
18
19       <b>postconf -#</b> [<b>-pv</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <i>parameter ...</i>
20
21       <b>postconf -X</b> [<b>-pv</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <i>parameter ...</i>
22
23   <b>Managing <a href="master.5.html">master.cf</a> service entries:</b>
24
25       <b>postconf -M</b> [<b>-fovx</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<i>service</i>[<b>/</b><i>type</i>] <i>...</i>]
26
27       <b>postconf -M</b> [<b>-ev</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <i>service</i><b>/</b><i>type</i><b>=</b><i>value ...</i>
28
29       <b>postconf -M#</b> [<b>-v</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <i>service</i><b>/</b><i>type ...</i>
30
31       <b>postconf -MX</b> [<b>-v</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <i>service</i><b>/</b><i>type ...</i>
32
33   <b>Managing <a href="master.5.html">master.cf</a> service fields:</b>
34
35       <b>postconf -F</b> [<b>-fhHovx</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<i>service</i>[<b>/</b><i>type</i>[<b>/</b><i>field</i>]] <i>...</i>]
36
37       <b>postconf -F</b> [<b>-ev</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <i>service</i><b>/</b><i>type</i><b>/</b><i>field</i><b>=</b><i>value ...</i>
38
39   <b>Managing <a href="master.5.html">master.cf</a> service parameters:</b>
40
41       <b>postconf -P</b> [<b>-fhHovx</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<i>service</i>[<b>/</b><i>type</i>[<b>/</b><i>parameter</i>]] <i>...</i>]
42
43       <b>postconf -P</b> [<b>-ev</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <i>service</i><b>/</b><i>type</i><b>/</b><i>parameter</i><b>=</b><i>value ...</i>
44
45       <b>postconf -PX</b> [<b>-v</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <i>service</i><b>/</b><i>type</i><b>/</b><i>parameter ...</i>
46
47   <b>Managing bounce message templates:</b>
48
49       <b>postconf -b</b> [<b>-v</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<i>template</i><b>_</b><i>file</i>]
50
51       <b>postconf -t</b> [<b>-v</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<i>template</i><b>_</b><i>file</i>]
52
53   <b>Managing TLS features:</b>
54
55       <b>postconf -T</b> <i>mode</i> [<b>-v</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>]
56
57   <b>Managing other configuration:</b>
58
59       <b>postconf -a</b>|<b>-A</b>|<b>-l</b>|<b>-m</b> [<b>-v</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>]
60
61<b>DESCRIPTION</b>
62       By default, the <a href="postconf.1.html"><b>postconf</b>(1)</a> command displays the values of <a href="postconf.5.html"><b>main.cf</b></a> con-
63       figuration  parameters,  and  warns  about possible mis-typed parameter
64       names (Postfix 2.9 and later).  The command  can  also  change  <a href="postconf.5.html"><b>main.cf</b></a>
65       configuration parameter values, or display other configuration informa-
66       tion about the Postfix mail system.
67
68       Options:
69
70       <b>-a</b>     List the available SASL  plug-in  types  for  the  Postfix  SMTP
71              server.  The  plug-in  type is selected with the <b><a href="postconf.5.html#smtpd_sasl_type">smtpd_sasl_type</a></b>
72              configuration parameter by specifying one of  the  names  listed
73              below.
74
75              <b>cyrus</b>  This  server  plug-in  is available when Postfix is built
76                     with Cyrus SASL support.
77
78              <b>dovecot</b>
79                     This  server  plug-in  uses  the  Dovecot  authentication
80                     server,  and  is available when Postfix is built with any
81                     form of SASL support.
82
83              This feature is available with Postfix 2.3 and later.
84
85       <b>-A</b>     List the available SASL  plug-in  types  for  the  Postfix  SMTP
86              client.  The plug-in type is selected with the <b><a href="postconf.5.html#smtp_sasl_type">smtp_sasl_type</a></b> or
87              <b><a href="postconf.5.html#lmtp_sasl_type">lmtp_sasl_type</a></b> configuration parameters by specifying one of the
88              names listed below.
89
90              <b>cyrus</b>  This  client  plug-in  is available when Postfix is built
91                     with Cyrus SASL support.
92
93              This feature is available with Postfix 2.3 and later.
94
95       <b>-b</b> [<i>template</i><b>_</b><i>file</i>]
96              Display the message text that appears at the beginning of deliv-
97              ery  status notification (DSN) messages, expanding $<b>name</b> expres-
98              sions with actual values as described in <a href="bounce.5.html"><b>bounce</b>(5)</a>.
99
100              To override the <b><a href="postconf.5.html#bounce_template_file">bounce_template_file</a></b> parameter setting,  specify
101              a  template  file  name  at the end of the "<b>postconf -b</b>" command
102              line. Specify an empty file name to display  built-in  templates
103              (in shell language: "").
104
105              This feature is available with Postfix 2.3 and later.
106
107       <b>-c</b> <i>config</i><b>_</b><i>dir</i>
108              The <a href="postconf.5.html"><b>main.cf</b></a> configuration file is in the named directory instead
109              of the default configuration directory.
110
111       <b>-C</b> <i>class,...</i>
112              When displaying <a href="postconf.5.html"><b>main.cf</b></a> parameters, select only parameters  from
113              the specified class(es):
114
115              <b>builtin</b>
116                     Parameters with built-in names.
117
118              <b>service</b>
119                     Parameters with service-defined names (the first field of
120                     a <a href="master.5.html"><b>master.cf</b></a> entry plus a Postfix-defined suffix).
121
122              <b>user</b>   Parameters with user-defined names.
123
124              <b>all</b>    All the above classes.
125
126              The default is as if "<b>-C all</b>" is specified.
127
128              This feature is available with Postfix 2.9 and later.
129
130       <b>-d</b>     Print <a href="postconf.5.html"><b>main.cf</b></a> default parameter settings instead of actual  set-
131              tings.   Specify  <b>-df</b>  to  fold long lines for human readability
132              (Postfix 2.9 and later).
133
134       <b>-e</b>     Edit the <a href="postconf.5.html"><b>main.cf</b></a> configuration file, and update  parameter  set-
135              tings  with  the  "<i>name=value</i>"  pairs on the <a href="postconf.1.html"><b>postconf</b>(1)</a> command
136              line.
137
138              With <b>-M</b>, edit the <a href="master.5.html"><b>master.cf</b></a> configuration file, and replace  one
139              or  more service entries with new values as specified with "<i>ser-</i>
140              <i>vice/type=value</i>" on the <a href="postconf.1.html"><b>postconf</b>(1)</a> command line.
141
142              With <b>-F</b>, edit the <a href="master.5.html"><b>master.cf</b></a> configuration file, and replace  one
143              or  more  service fields with new values as specified with "<i>ser-</i>
144              <i>vice/type/field=value</i>" on the  <a href="postconf.1.html"><b>postconf</b>(1)</a>  command  line.  Cur-
145              rently,  the  "command" field contains the command name and com-
146              mand arguments.  this may change in the near future, so that the
147              "command" field contains only the command name, and a new "argu-
148              ments" pseudofield contains the command arguments.
149
150              With <b>-P</b>, edit the  <a href="master.5.html"><b>master.cf</b></a>  configuration  file,  and  add  or
151              update  one  or  more  service  parameter  settings  (-o parame-
152              ter=value settings) with new  values  as  specified  with  "<i>ser-</i>
153              <i>vice/type/parameter=value</i>" on the <a href="postconf.1.html"><b>postconf</b>(1)</a> command line.
154
155              In all cases the file is copied to a temporary file then renamed
156              into place.  Specify quotes to protect  special  characters  and
157              whitespace on the <a href="postconf.1.html"><b>postconf</b>(1)</a> command line.
158
159              The  <b>-e</b>  option is no longer needed with Postfix version 2.8 and
160              later.
161
162       <b>-f</b>     Fold long lines when printing <a href="postconf.5.html"><b>main.cf</b></a> or <a href="master.5.html"><b>master.cf</b></a> configuration
163              file entries, for human readability.
164
165              This feature is available with Postfix 2.9 and later.
166
167       <b>-F</b>     Show <a href="master.5.html"><b>master.cf</b></a> per-entry field settings (by default all services
168              and all fields), formatted  as  "<i>service/type/field=value</i>",  one
169              per line. Specify <b>-Ff</b> to fold long lines.
170
171              Specify  one or more "<i>service/type/field</i>" instances on the <a href="postconf.1.html"><b>post-</b></a>
172              <a href="postconf.1.html"><b>conf</b>(1)</a> command line to limit the output to fields of  interest.
173              Trailing  parameter name or service type fields that are omitted
174              will be handled as "*" wildcard fields.
175
176              This feature is available with Postfix 2.11 and later.
177
178       <b>-h</b>     Show parameter or attribute values without the "<i>name</i> =  "  label
179              that normally precedes the value.
180
181       <b>-H</b>     Show  parameter  or  attribute names without the " = <i>value</i>" that
182              normally follows the name.
183
184              This feature is available with Postfix 3.1 and later.
185
186       <b>-l</b>     List the names of all supported mailbox locking methods.   Post-
187              fix supports the following methods:
188
189              <b>flock</b>  A  kernel-based  advisory  locking method for local files
190                     only.  This locking method is available on systems with a
191                     BSD compatible library.
192
193              <b>fcntl</b>  A  kernel-based  advisory  locking  method  for local and
194                     remote files.
195
196              <b>dotlock</b>
197                     An application-level locking method. An application locks
198                     a  file  named  <i>filename</i>  by  creating a file named <i>file-</i>
199                     <i>name</i><b>.lock</b>.  The application is expected to remove its own
200                     lock  file,  as  well  as stale lock files that were left
201                     behind after abnormal program termination.
202
203       <b>-m</b>     List the names of all supported lookup table types.  In  Postfix
204              configuration  files,  lookup tables are specified as <i>type</i><b>:</b><i>name</i>,
205              where <i>type</i> is one of the types listed below. The table <i>name</i> syn-
206              tax  depends  on the lookup table type as described in the <a href="DATABASE_README.html">DATA</a>-
207              <a href="DATABASE_README.html">BASE_README</a> document.
208
209              <b>btree</b>  A sorted, balanced tree structure.  Available on  systems
210                     with support for Berkeley DB databases.
211
212              <b>cdb</b>    A  read-optimized structure with no support for incremen-
213                     tal updates.  Available on systems with support  for  CDB
214                     databases.
215
216                     This feature is available with Postfix 2.2 and later.
217
218              <b>cidr</b>   A   table   that   associates   values   with   Classless
219                     Inter-Domain Routing (CIDR) patterns. This  is  described
220                     in <a href="cidr_table.5.html"><b>cidr_table</b>(5)</a>.
221
222                     This feature is available with Postfix 2.2 and later.
223
224              <b>dbm</b>    An indexed file type based on hashing.  Available on sys-
225                     tems with support for DBM databases.
226
227              <b>environ</b>
228                     The UNIX process environment array. The lookup key is the
229                     environment  variable  name;  the  table name is ignored.
230                     Originally implemented for testing, someone may find this
231                     useful someday.
232
233              <b>fail</b>   A  table that reliably fails all requests. The lookup ta-
234                     ble name is used for logging. This table exists  to  sim-
235                     plify Postfix error tests.
236
237                     This feature is available with Postfix 2.9 and later.
238
239              <b>hash</b>   An indexed file type based on hashing.  Available on sys-
240                     tems with support for Berkeley DB databases.
241
242              <b>inline</b> (read-only)
243                     A non-shared, in-memory lookup table. Example:  "<b><a href="DATABASE_README.html#types">inline</a>:{</b>
244                     <i>key</i><b>=</b><i>value</i><b>,  {</b>  <i>key</i>  <b>=</b>  <i>text with whitespace or comma</i> <b>}}</b>".
245                     Key-value pairs are separated  by  whitespace  or  comma;
246                     with  a key-value pair inside "<b>{}</b>", whitespace is ignored
247                     after the opening "<b>{</b>", around the  "<b>=</b>"  between  key  and
248                     value,  and  before the closing "<b>}</b>". Inline tables elimi-
249                     nate the need to create a database file for  just  a  few
250                     fixed elements.  See also the <i><a href="DATABASE_README.html#types">static</a>:</i> map type.
251
252                     This feature is available with Postfix 3.0 and later.
253
254              <b>internal</b>
255                     A  non-shared, in-memory hash table. Its content are lost
256                     when a process terminates.
257
258              <b>lmdb</b>   OpenLDAP  LMDB  database  (a  memory-mapped,   persistent
259                     file).   Available on systems with support for LMDB data-
260                     bases.  This is described in <a href="lmdb_table.5.html"><b>lmdb_table</b>(5)</a>.
261
262                     This feature is available with Postfix 2.11 and later.
263
264              <b>ldap</b> (read-only)
265                     LDAP database client. This is described in <a href="ldap_table.5.html"><b>ldap_table</b>(5)</a>.
266
267              <b>memcache</b>
268                     Memcache  database  client.  This  is  described  in <a href="memcache_table.5.html"><b>mem-</b></a>
269                     <a href="memcache_table.5.html"><b>cache_table</b>(5)</a>.
270
271                     This feature is available with Postfix 2.9 and later.
272
273              <b>mysql</b> (read-only)
274                     MySQL database client.  Available on systems with support
275                     for  MySQL  databases.   This  is  described in <a href="mysql_table.5.html"><b>mysql_ta-</b></a>
276                     <a href="mysql_table.5.html"><b>ble</b>(5)</a>.
277
278              <b>pcre</b> (read-only)
279                     A lookup table based on Perl Compatible  Regular  Expres-
280                     sions.  The file format is described in <a href="pcre_table.5.html"><b>pcre_table</b>(5)</a>.
281
282              <b>pgsql</b> (read-only)
283                     PostgreSQL   database   client.   This  is  described  in
284                     <a href="pgsql_table.5.html"><b>pgsql_table</b>(5)</a>.
285
286                     This feature is available with Postfix 2.1 and later.
287
288              <b>pipemap</b> (read-only)
289                     A lookup table that  constructs  a  pipeline  of  tables.
290                     Example:  "<b><a href="DATABASE_README.html#types">pipemap</a>:{</b><i>type</i><b>_</b><i>1:name</i><b>_</b><i>1,  ..., type</i><b>_</b><i>n:name</i><b>_</b><i>n</i><b>}</b>".
291                     Each "<a href="DATABASE_README.html#types">pipemap</a>:" query is given to the first table.   Each
292                     lookup result becomes the query for the next table in the
293                     pipeline, and the last table produces the  final  result.
294                     When  any  table  lookup produces no result, the pipeline
295                     produces no result. The first and last characters of  the
296                     "<a href="DATABASE_README.html#types">pipemap</a>:" table name must be "<b>{</b>" and "<b>}</b>".  Within these,
297                     individual maps are separated with comma or whitespace.
298
299                     This feature is available with Postfix 3.0 and later.
300
301              <b>proxy</b>  Postfix <a href="proxymap.8.html"><b>proxymap</b>(8)</a> client for shared access  to  Postfix
302                     databases. The table name syntax is <i>type</i><b>:</b><i>name</i>.
303
304                     This feature is available with Postfix 2.0 and later.
305
306              <b>randmap</b> (read-only)
307                     An  in-memory table that performs random selection. Exam-
308                     ple:  "<b><a href="DATABASE_README.html#types">randmap</a>:{</b><i>result</i><b>_</b><i>1,  ...,  result</i><b>_</b><i>n</i><b>}</b>".  Each  table
309                     query returns a random choice from the specified results.
310                     The first and last characters  of  the  "<a href="DATABASE_README.html#types">randmap</a>:"  table
311                     name  must  be  "<b>{</b>"  and  "<b>}</b>".   Within these, individual
312                     results are separated with comma or whitespace. To give a
313                     specific result more weight, specify it multiple times.
314
315                     This feature is available with Postfix 3.0 and later.
316
317              <b>regexp</b> (read-only)
318                     A  lookup  table  based  on regular expressions. The file
319                     format is described in <a href="regexp_table.5.html"><b>regexp_table</b>(5)</a>.
320
321              <b>sdbm</b>   An indexed file type based on hashing.  Available on sys-
322                     tems with support for SDBM databases.
323
324                     This feature is available with Postfix 2.2 and later.
325
326              <b>socketmap</b> (read-only)
327                     Sendmail-style   socketmap  client.  The  table  name  is
328                     <b>inet</b>:<i>host</i>:<i>port</i>:<i>name</i> for a TCP/IP  server,  or  <b>unix</b>:<i>path-</i>
329                     <i>name</i>:<i>name</i>  for a UNIX-domain server. This is described in
330                     <a href="socketmap_table.5.html"><b>socketmap_table</b>(5)</a>.
331
332                     This feature is available with Postfix 2.10 and later.
333
334              <b>sqlite</b> (read-only)
335                     SQLite database. This is described in <a href="sqlite_table.5.html"><b>sqlite_table</b>(5)</a>.
336
337                     This feature is available with Postfix 2.8 and later.
338
339              <b>static</b> (read-only)
340                     A table that always returns its name  as  lookup  result.
341                     For example, <b><a href="DATABASE_README.html#types">static</a>:foobar</b> always returns the string <b>foo-</b>
342                     <b>bar</b> as lookup result. Specify "<b><a href="DATABASE_README.html#types">static</a>:{</b> <i>text with  white-</i>
343                     <i>space</i>  <b>}</b>"  when the result contains whitespace; this form
344                     ignores whitespace after the opening "<b>{</b>" and  before  the
345                     closing "<b>}</b>". See also the <i><a href="DATABASE_README.html#types">inline</a>:</i> map.
346
347                     The form "<b><a href="DATABASE_README.html#types">static</a>:{</b><i>text</i><b>}</b> is available with Postfix 3.0 and
348                     later.
349
350              <b>tcp</b> (read-only)
351                     TCP/IP client. The protocol is described in <a href="tcp_table.5.html"><b>tcp_table</b>(5)</a>.
352
353              <b>texthash</b> (read-only)
354                     Produces  similar results as <a href="DATABASE_README.html#types">hash</a>: files, except that you
355                     don't need to run the <a href="postmap.1.html"><b>postmap</b>(1)</a> command before  you  can
356                     use  the  file, and that it does not detect changes after
357                     the file is read.
358
359                     This feature is available with Postfix 2.8 and later.
360
361              <b>unionmap</b> (read-only)
362                     A table that sends each query to multiple  lookup  tables
363                     and  that  concatenates  all  found results, separated by
364                     comma.  The table name syntax is the same as for <b>pipemap</b>.
365
366                     This feature is available with Postfix 3.0 and later.
367
368              <b>unix</b> (read-only)
369                     A  limited  view of the UNIX authentication database. The
370                     following tables are implemented:
371
372                     <b>unix:passwd.byname</b>
373                            The table is the UNIX password database.  The  key
374                            is  a  login  name.  The result is a password file
375                            entry in <b>passwd</b>(5) format.
376
377                     <b>unix:group.byname</b>
378                            The table is the UNIX group database. The key is a
379                            group  name.   The result is a group file entry in
380                            <b>group</b>(5) format.
381
382              Other table types may exist depending on how Postfix was  built.
383
384       <b>-M</b>     Show  <a href="master.5.html"><b>master.cf</b></a>  file contents instead of <a href="postconf.5.html"><b>main.cf</b></a> file contents.
385              Specify <b>-Mf</b> to fold long lines for human readability.
386
387              Specify zero or more arguments, each with a <i>service-name</i> or <i>ser-</i>
388              <i>vice-name/service-type</i>  pair,  where  <i>service-name</i>  is the first
389              field of a <a href="master.5.html">master.cf</a> entry and <i>service-type</i>  is  one  of  (<b>inet</b>,
390              <b>unix</b>, <b>fifo</b>, or <b>pass</b>).
391
392              If  <i>service-name</i> or <i>service-name/service-type</i> is specified, only
393              the matching <a href="master.5.html">master.cf</a> entries  will  be  output.  For  example,
394              "<b>postconf  -Mf  smtp</b>" will output all services named "smtp", and
395              "<b>postconf -Mf smtp/inet</b>" will output only the smtp service  that
396              listens  on  the network.  Trailing service type fields that are
397              omitted will be handled as "*" wildcard fields.
398
399              This feature is available with Postfix 2.9 and later. The syntax
400              was  changed  from  "<i>name.type</i>" to "<i>name/type</i>", and "*" wildcard
401              support was added with Postfix 2.11.
402
403       <b>-n</b>     Show only configuration parameters that have explicit <i>name=value</i>
404              settings  in  <a href="postconf.5.html"><b>main.cf</b></a>.  Specify <b>-nf</b> to fold long lines for human
405              readability (Postfix 2.9 and later). To show settings that  dif-
406              fer from built-in defaults only, use the following bash syntax:
407                  comm -23 &lt;(postconf -n) &lt;(postconf -d)
408              Replace  "-23"  with  "-12"  to  show  settings  that  duplicate
409              built-in defaults.
410
411       <b>-o</b> <i>name=value</i>
412              Override <a href="postconf.5.html"><b>main.cf</b></a> parameter settings.
413
414              This feature is available with Postfix 2.10 and later.
415
416       <b>-p</b>     Show <a href="postconf.5.html"><b>main.cf</b></a> parameter settings. This is the default.
417
418              This feature is available with Postfix 2.11 and later.
419
420       <b>-P</b>     Show <a href="master.5.html"><b>master.cf</b></a> service parameter settings (by default  all  ser-
421              vices  and  all  parameters), formatted as "<i>service/type/parame-</i>
422              <i>ter=value</i>", one per line.  Specify <b>-Pf</b> to fold long lines.
423
424              Specify one or more "<i>service/type/parameter</i>"  instances  on  the
425              <a href="postconf.1.html"><b>postconf</b>(1)</a>  command  line  to limit the output to parameters of
426              interest.  Trailing parameter name or service type  fields  that
427              are omitted will be handled as "*" wildcard fields.
428
429              This feature is available with Postfix 2.11 and later.
430
431       <b>-t</b> [<i>template</i><b>_</b><i>file</i>]
432              Display  the templates for text that appears at the beginning of
433              delivery status notification (DSN) messages,  without  expanding
434              $<b>name</b> expressions.
435
436              To  override the <b><a href="postconf.5.html#bounce_template_file">bounce_template_file</a></b> parameter setting, specify
437              a template file name at the end of  the  "<b>postconf  -t</b>"  command
438              line.  Specify  an empty file name to display built-in templates
439              (in shell language: "").
440
441              This feature is available with Postfix 2.3 and later.
442
443       <b>-T</b> <i>mode</i>
444              If Postfix is compiled without TLS support, the <b>-T</b>  option  pro-
445              duces  no  output.   Otherwise, if an invalid <i>mode</i> is specified,
446              the <b>-T</b> option reports an error and exits with a non-zero  status
447              code. The valid modes are:
448
449              <b>compile-version</b>
450                     Output the OpenSSL version that Postfix was compiled with
451                     (i.e. the OpenSSL version in a header file).  The  output
452                     format is the same as with the command "<b>openssl version</b>".
453
454              <b>run-version</b>
455                     Output the OpenSSL version that Postfix is linked with at
456                     runtime (i.e. the OpenSSL version in a shared library).
457
458              <b>public-key-algorithms</b>
459                     Output  the  lower-case names of the supported public-key
460                     algorithms, one per-line.
461
462              This feature is available with Postfix 3.1 and later.
463
464       <b>-v</b>     Enable verbose  logging  for  debugging  purposes.  Multiple  <b>-v</b>
465              options make the software increasingly verbose.
466
467       <b>-x</b>     Expand  <i>$name</i>  in  <a href="postconf.5.html"><b>main.cf</b></a>  or  <a href="master.5.html"><b>master.cf</b></a>  parameter values. The
468              expansion is recursive.
469
470              This feature is available with Postfix 2.10 and later.
471
472       <b>-X</b>     Edit the <a href="postconf.5.html"><b>main.cf</b></a> configuration file, and remove  the  parameters
473              named on the <a href="postconf.1.html"><b>postconf</b>(1)</a> command line.  Specify a list of param-
474              eter names, not "<i>name=value</i>" pairs.
475
476              With <b>-M</b>, edit the <a href="master.5.html"><b>master.cf</b></a> configuration file, and  remove  one
477              or  more service entries as specified with "<i>service/type</i>" on the
478              <a href="postconf.1.html"><b>postconf</b>(1)</a> command line.
479
480              With <b>-P</b>, edit the <a href="master.5.html"><b>master.cf</b></a> configuration file, and  remove  one
481              or more service parameter settings (-o parameter=value settings)
482              as specified with "<i>service/type/parameter</i>"  on  the  <a href="postconf.1.html"><b>postconf</b>(1)</a>
483              command line.
484
485              In all cases the file is copied to a temporary file then renamed
486              into place.  Specify quotes to protect special characters on the
487              <a href="postconf.1.html"><b>postconf</b>(1)</a> command line.
488
489              There  is  no  <a href="postconf.1.html"><b>postconf</b>(1)</a> command to perform the reverse opera-
490              tion.
491
492              This feature is available with Postfix 2.10 and later.   Support
493              for -M and -P was added with Postfix 2.11.
494
495       <b>-#</b>     Edit the <a href="postconf.5.html"><b>main.cf</b></a> configuration file, and comment out the parame-
496              ters named on the <a href="postconf.1.html"><b>postconf</b>(1)</a> command line, so that those param-
497              eters revert to their default values.  Specify a list of parame-
498              ter names, not "<i>name=value</i>" pairs.
499
500              With <b>-M</b>, edit the <a href="master.5.html"><b>master.cf</b></a> configuration file, and comment  out
501              one  or more service entries as specified with "<i>service/type</i>" on
502              the <a href="postconf.1.html"><b>postconf</b>(1)</a> command line.
503
504              In all cases the file is copied to a temporary file then renamed
505              into place.  Specify quotes to protect special characters on the
506              <a href="postconf.1.html"><b>postconf</b>(1)</a> command line.
507
508              There is no <a href="postconf.1.html"><b>postconf</b>(1)</a> command to perform  the  reverse  opera-
509              tion.
510
511              This  feature  is  available with Postfix 2.6 and later. Support
512              for -M was added with Postfix 2.11.
513
514<b>DIAGNOSTICS</b>
515       Problems are reported to the standard error stream.
516
517<b>ENVIRONMENT</b>
518       <b>MAIL_CONFIG</b>
519              Directory with Postfix configuration files.
520
521<b>CONFIGURATION PARAMETERS</b>
522       The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to  this  pro-
523       gram.
524
525       The  text  below provides only a parameter summary. See <a href="postconf.5.html"><b>postconf</b>(5)</a> for
526       more details including examples.
527
528       <b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b>
529              The default location of the Postfix <a href="postconf.5.html">main.cf</a> and  <a href="master.5.html">master.cf</a>  con-
530              figuration files.
531
532       <b><a href="postconf.5.html#bounce_template_file">bounce_template_file</a> (empty)</b>
533              Pathname  of a configuration file with bounce message templates.
534
535<b>FILES</b>
536       /etc/postfix/<a href="postconf.5.html">main.cf</a>, Postfix configuration parameters
537       /etc/postfix/<a href="master.5.html">master.cf</a>, Postfix master daemon configuration
538
539<b>SEE ALSO</b>
540       <a href="bounce.5.html">bounce(5)</a>, bounce template file format
541       <a href="master.5.html">master(5)</a>, <a href="master.5.html">master.cf</a> configuration file syntax
542       <a href="postconf.5.html">postconf(5)</a>, <a href="postconf.5.html">main.cf</a> configuration file syntax
543
544<b>README FILES</b>
545       <a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
546
547<b>LICENSE</b>
548       The Secure Mailer license must be distributed with this software.
549
550<b>AUTHOR(S)</b>
551       Wietse Venema
552       IBM T.J. Watson Research
553       P.O. Box 704
554       Yorktown Heights, NY 10598, USA
555
556       Wietse Venema
557       Google, Inc.
558       111 8th Avenue
559       New York, NY 10011, USA
560
561                                                                   POSTCONF(1)
562</pre> </body> </html>
563