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