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=utf-8"> 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, as it is assumed whenever a value is specified (empty or 161 non-empty). 162 163 <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 164 file entries, for human readability. 165 166 This feature is available with Postfix 2.9 and later. 167 168 <b>-F</b> Show <a href="master.5.html"><b>master.cf</b></a> per-entry field settings (by default all services 169 and all fields), formatted as "<i>service/type/field=value</i>", one 170 per line. Specify <b>-Ff</b> to fold long lines. 171 172 Specify one or more "<i>service/type/field</i>" instances on the <a href="postconf.1.html"><b>post-</b></a> 173 <a href="postconf.1.html"><b>conf</b>(1)</a> command line to limit the output to fields of interest. 174 Trailing parameter name or service type fields that are omitted 175 will be handled as "*" wildcard fields. 176 177 This feature is available with Postfix 2.11 and later. 178 179 <b>-h</b> Show parameter or attribute values without the "<i>name</i> = " label 180 that normally precedes the value. 181 182 <b>-H</b> Show parameter or attribute names without the " = <i>value</i>" that 183 normally follows the name. 184 185 This feature is available with Postfix 3.1 and later. 186 187 <b>-l</b> List the names of all supported mailbox locking methods. Post- 188 fix supports the following methods: 189 190 <b>flock</b> A kernel-based advisory locking method for local files 191 only. This locking method is available on systems with a 192 BSD compatible library. 193 194 <b>fcntl</b> A kernel-based advisory locking method for local and 195 remote files. 196 197 <b>dotlock</b> 198 An application-level locking method. An application locks 199 a file named <i>filename</i> by creating a file named <i>file-</i> 200 <i>name</i><b>.lock</b>. The application is expected to remove its own 201 lock file, as well as stale lock files that were left 202 behind after abnormal program termination. 203 204 <b>-m</b> List the names of all supported lookup table types. In Postfix 205 configuration files, lookup tables are specified as <i>type</i><b>:</b><i>name</i>, 206 where <i>type</i> is one of the types listed below. The table <i>name</i> syn- 207 tax depends on the lookup table type as described in the <a href="DATABASE_README.html">DATA</a>- 208 <a href="DATABASE_README.html">BASE_README</a> document. 209 210 <b>btree</b> A sorted, balanced tree structure. Available on systems 211 with support for Berkeley DB databases. 212 213 <b>cdb</b> A read-optimized structure with no support for incremen- 214 tal updates. Available on systems with support for CDB 215 databases. 216 217 This feature is available with Postfix 2.2 and later. 218 219 <b>cidr</b> A table that associates values with Classless 220 Inter-Domain Routing (CIDR) patterns. This is described 221 in <a href="cidr_table.5.html"><b>cidr_table</b>(5)</a>. 222 223 This feature is available with Postfix 2.2 and later. 224 225 <b>dbm</b> An indexed file type based on hashing. Available on sys- 226 tems with support for DBM databases. 227 228 <b>environ</b> 229 The UNIX process environment array. The lookup key is the 230 environment variable name; the table name is ignored. 231 Originally implemented for testing, someone may find this 232 useful someday. 233 234 <b>fail</b> A table that reliably fails all requests. The lookup ta- 235 ble name is used for logging. This table exists to sim- 236 plify Postfix error tests. 237 238 This feature is available with Postfix 2.9 and later. 239 240 <b>hash</b> An indexed file type based on hashing. Available on sys- 241 tems with support for Berkeley DB databases. 242 243 <b>inline</b> (read-only) 244 A non-shared, in-memory lookup table. Example: "<b><a href="DATABASE_README.html#types">inline</a>:{</b> 245 <i>key</i><b>=</b><i>value</i><b>, {</b> <i>key</i> <b>=</b> <i>text with whitespace or comma</i> <b>}}</b>". 246 Key-value pairs are separated by whitespace or comma; 247 with a key-value pair inside "<b>{}</b>", whitespace is ignored 248 after the opening "<b>{</b>", around the "<b>=</b>" between key and 249 value, and before the closing "<b>}</b>". Inline tables elimi- 250 nate the need to create a database file for just a few 251 fixed elements. See also the <i><a href="DATABASE_README.html#types">static</a>:</i> map type. 252 253 This feature is available with Postfix 3.0 and later. 254 255 <b>internal</b> 256 A non-shared, in-memory hash table. Its content are lost 257 when a process terminates. 258 259 <b>lmdb</b> OpenLDAP LMDB database (a memory-mapped, persistent 260 file). Available on systems with support for LMDB data- 261 bases. This is described in <a href="lmdb_table.5.html"><b>lmdb_table</b>(5)</a>. 262 263 This feature is available with Postfix 2.11 and later. 264 265 <b>ldap</b> (read-only) 266 LDAP database client. This is described in <a href="ldap_table.5.html"><b>ldap_table</b>(5)</a>. 267 268 <b>memcache</b> 269 Memcache database client. This is described in <a href="memcache_table.5.html"><b>mem-</b></a> 270 <a href="memcache_table.5.html"><b>cache_table</b>(5)</a>. 271 272 This feature is available with Postfix 2.9 and later. 273 274 <b>mysql</b> (read-only) 275 MySQL database client. Available on systems with support 276 for MySQL databases. This is described in <a href="mysql_table.5.html"><b>mysql_ta-</b></a> 277 <a href="mysql_table.5.html"><b>ble</b>(5)</a>. 278 279 <b>pcre</b> (read-only) 280 A lookup table based on Perl Compatible Regular Expres- 281 sions. The file format is described in <a href="pcre_table.5.html"><b>pcre_table</b>(5)</a>. 282 283 <b>pgsql</b> (read-only) 284 PostgreSQL database client. This is described in 285 <a href="pgsql_table.5.html"><b>pgsql_table</b>(5)</a>. 286 287 This feature is available with Postfix 2.1 and later. 288 289 <b>pipemap</b> (read-only) 290 A lookup table that constructs a pipeline of tables. 291 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>". 292 Each "<a href="DATABASE_README.html#types">pipemap</a>:" query is given to the first table. Each 293 lookup result becomes the query for the next table in the 294 pipeline, and the last table produces the final result. 295 When any table lookup produces no result, the pipeline 296 produces no result. The first and last characters of the 297 "<a href="DATABASE_README.html#types">pipemap</a>:" table name must be "<b>{</b>" and "<b>}</b>". Within these, 298 individual maps are separated with comma or whitespace. 299 300 This feature is available with Postfix 3.0 and later. 301 302 <b>proxy</b> Postfix <a href="proxymap.8.html"><b>proxymap</b>(8)</a> client for shared access to Postfix 303 databases. The table name syntax is <i>type</i><b>:</b><i>name</i>. 304 305 This feature is available with Postfix 2.0 and later. 306 307 <b>randmap</b> (read-only) 308 An in-memory table that performs random selection. Exam- 309 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 310 query returns a random choice from the specified results. 311 The first and last characters of the "<a href="DATABASE_README.html#types">randmap</a>:" table 312 name must be "<b>{</b>" and "<b>}</b>". Within these, individual 313 results are separated with comma or whitespace. To give a 314 specific result more weight, specify it multiple times. 315 316 This feature is available with Postfix 3.0 and later. 317 318 <b>regexp</b> (read-only) 319 A lookup table based on regular expressions. The file 320 format is described in <a href="regexp_table.5.html"><b>regexp_table</b>(5)</a>. 321 322 <b>sdbm</b> An indexed file type based on hashing. Available on sys- 323 tems with support for SDBM databases. 324 325 This feature is available with Postfix 2.2 and later. 326 327 <b>socketmap</b> (read-only) 328 Sendmail-style socketmap client. The table name is 329 <b>inet</b>:<i>host</i>:<i>port</i>:<i>name</i> for a TCP/IP server, or <b>unix</b>:<i>path-</i> 330 <i>name</i>:<i>name</i> for a UNIX-domain server. This is described in 331 <a href="socketmap_table.5.html"><b>socketmap_table</b>(5)</a>. 332 333 This feature is available with Postfix 2.10 and later. 334 335 <b>sqlite</b> (read-only) 336 SQLite database. This is described in <a href="sqlite_table.5.html"><b>sqlite_table</b>(5)</a>. 337 338 This feature is available with Postfix 2.8 and later. 339 340 <b>static</b> (read-only) 341 A table that always returns its name as lookup result. 342 For example, <b><a href="DATABASE_README.html#types">static</a>:foobar</b> always returns the string <b>foo-</b> 343 <b>bar</b> as lookup result. Specify "<b><a href="DATABASE_README.html#types">static</a>:{</b> <i>text with white-</i> 344 <i>space</i> <b>}</b>" when the result contains whitespace; this form 345 ignores whitespace after the opening "<b>{</b>" and before the 346 closing "<b>}</b>". See also the <i><a href="DATABASE_README.html#types">inline</a>:</i> map. 347 348 The form "<b><a href="DATABASE_README.html#types">static</a>:{</b><i>text</i><b>}</b> is available with Postfix 3.0 and 349 later. 350 351 <b>tcp</b> (read-only) 352 TCP/IP client. The protocol is described in <a href="tcp_table.5.html"><b>tcp_table</b>(5)</a>. 353 354 <b>texthash</b> (read-only) 355 Produces similar results as <a href="DATABASE_README.html#types">hash</a>: files, except that you 356 don't need to run the <a href="postmap.1.html"><b>postmap</b>(1)</a> command before you can 357 use the file, and that it does not detect changes after 358 the file is read. 359 360 This feature is available with Postfix 2.8 and later. 361 362 <b>unionmap</b> (read-only) 363 A table that sends each query to multiple lookup tables 364 and that concatenates all found results, separated by 365 comma. The table name syntax is the same as for <b>pipemap</b>. 366 367 This feature is available with Postfix 3.0 and later. 368 369 <b>unix</b> (read-only) 370 A limited view of the UNIX authentication database. The 371 following tables are implemented: 372 373 <b>unix:passwd.byname</b> 374 The table is the UNIX password database. The key 375 is a login name. The result is a password file 376 entry in <b>passwd</b>(5) format. 377 378 <b>unix:group.byname</b> 379 The table is the UNIX group database. The key is a 380 group name. The result is a group file entry in 381 <b>group</b>(5) format. 382 383 Other table types may exist depending on how Postfix was built. 384 385 <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. 386 Specify <b>-Mf</b> to fold long lines for human readability. 387 388 Specify zero or more arguments, each with a <i>service-name</i> or <i>ser-</i> 389 <i>vice-name/service-type</i> pair, where <i>service-name</i> is the first 390 field of a <a href="master.5.html">master.cf</a> entry and <i>service-type</i> is one of (<b>inet</b>, 391 <b>unix</b>, <b>fifo</b>, or <b>pass</b>). 392 393 If <i>service-name</i> or <i>service-name/service-type</i> is specified, only 394 the matching <a href="master.5.html">master.cf</a> entries will be output. For example, 395 "<b>postconf -Mf smtp</b>" will output all services named "smtp", and 396 "<b>postconf -Mf smtp/inet</b>" will output only the smtp service that 397 listens on the network. Trailing service type fields that are 398 omitted will be handled as "*" wildcard fields. 399 400 This feature is available with Postfix 2.9 and later. The syntax 401 was changed from "<i>name.type</i>" to "<i>name/type</i>", and "*" wildcard 402 support was added with Postfix 2.11. 403 404 <b>-n</b> Show only configuration parameters that have explicit <i>name=value</i> 405 settings in <a href="postconf.5.html"><b>main.cf</b></a>. Specify <b>-nf</b> to fold long lines for human 406 readability (Postfix 2.9 and later). To show settings that dif- 407 fer from built-in defaults only, use the following bash syntax: 408 LANG=C comm -23 <(postconf -n) <(postconf -d) 409 Replace "-23" with "-12" to show settings that duplicate 410 built-in defaults. 411 412 <b>-o</b> <i>name=value</i> 413 Override <a href="postconf.5.html"><b>main.cf</b></a> parameter settings. This lets you see the 414 effect changing a parameter would have when it is used in other 415 configuration parameters, e.g.: 416 postconf -x -o stress=yes 417 418 This feature is available with Postfix 2.10 and later. 419 420 <b>-p</b> Show <a href="postconf.5.html"><b>main.cf</b></a> parameter settings. This is the default. 421 422 This feature is available with Postfix 2.11 and later. 423 424 <b>-P</b> Show <a href="master.5.html"><b>master.cf</b></a> service parameter settings (by default all ser- 425 vices and all parameters), formatted as "<i>service/type/parame-</i> 426 <i>ter=value</i>", one per line. Specify <b>-Pf</b> to fold long lines. 427 428 Specify one or more "<i>service/type/parameter</i>" instances on the 429 <a href="postconf.1.html"><b>postconf</b>(1)</a> command line to limit the output to parameters of 430 interest. Trailing parameter name or service type fields that 431 are omitted will be handled as "*" wildcard fields. 432 433 This feature is available with Postfix 2.11 and later. 434 435 <b>-t</b> [<i>template</i><b>_</b><i>file</i>] 436 Display the templates for text that appears at the beginning of 437 delivery status notification (DSN) messages, without expanding 438 $<b>name</b> expressions. 439 440 To override the <b><a href="postconf.5.html#bounce_template_file">bounce_template_file</a></b> parameter setting, specify 441 a template file name at the end of the "<b>postconf -t</b>" command 442 line. Specify an empty file name to display built-in templates 443 (in shell language: ""). 444 445 This feature is available with Postfix 2.3 and later. 446 447 <b>-T</b> <i>mode</i> 448 If Postfix is compiled without TLS support, the <b>-T</b> option pro- 449 duces no output. Otherwise, if an invalid <i>mode</i> is specified, 450 the <b>-T</b> option reports an error and exits with a non-zero status 451 code. The valid modes are: 452 453 <b>compile-version</b> 454 Output the OpenSSL version that Postfix was compiled with 455 (i.e. the OpenSSL version in a header file). The output 456 format is the same as with the command "<b>openssl version</b>". 457 458 <b>run-version</b> 459 Output the OpenSSL version that Postfix is linked with at 460 runtime (i.e. the OpenSSL version in a shared library). 461 462 <b>public-key-algorithms</b> 463 Output the lower-case names of the supported public-key 464 algorithms, one per-line. 465 466 This feature is available with Postfix 3.1 and later. 467 468 <b>-v</b> Enable verbose logging for debugging purposes. Multiple <b>-v</b> 469 options make the software increasingly verbose. 470 471 <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 472 expansion is recursive. 473 474 This feature is available with Postfix 2.10 and later. 475 476 <b>-X</b> Edit the <a href="postconf.5.html"><b>main.cf</b></a> configuration file, and remove the parameters 477 named on the <a href="postconf.1.html"><b>postconf</b>(1)</a> command line. Specify a list of param- 478 eter names, not "<i>name=value</i>" pairs. 479 480 With <b>-M</b>, edit the <a href="master.5.html"><b>master.cf</b></a> configuration file, and remove one 481 or more service entries as specified with "<i>service/type</i>" on the 482 <a href="postconf.1.html"><b>postconf</b>(1)</a> command line. 483 484 With <b>-P</b>, edit the <a href="master.5.html"><b>master.cf</b></a> configuration file, and remove one 485 or more service parameter settings (-o parameter=value settings) 486 as specified with "<i>service/type/parameter</i>" on the <a href="postconf.1.html"><b>postconf</b>(1)</a> 487 command line. 488 489 In all cases the file is copied to a temporary file then renamed 490 into place. Specify quotes to protect special characters on the 491 <a href="postconf.1.html"><b>postconf</b>(1)</a> command line. 492 493 There is no <a href="postconf.1.html"><b>postconf</b>(1)</a> command to perform the reverse opera- 494 tion. 495 496 This feature is available with Postfix 2.10 and later. Support 497 for -M and -P was added with Postfix 2.11. 498 499 <b>-#</b> Edit the <a href="postconf.5.html"><b>main.cf</b></a> configuration file, and comment out the parame- 500 ters named on the <a href="postconf.1.html"><b>postconf</b>(1)</a> command line, so that those param- 501 eters revert to their default values. Specify a list of parame- 502 ter names, not "<i>name=value</i>" pairs. 503 504 With <b>-M</b>, edit the <a href="master.5.html"><b>master.cf</b></a> configuration file, and comment out 505 one or more service entries as specified with "<i>service/type</i>" on 506 the <a href="postconf.1.html"><b>postconf</b>(1)</a> command line. 507 508 In all cases the file is copied to a temporary file then renamed 509 into place. Specify quotes to protect special characters on the 510 <a href="postconf.1.html"><b>postconf</b>(1)</a> command line. 511 512 There is no <a href="postconf.1.html"><b>postconf</b>(1)</a> command to perform the reverse opera- 513 tion. 514 515 This feature is available with Postfix 2.6 and later. Support 516 for -M was added with Postfix 2.11. 517 518<b>DIAGNOSTICS</b> 519 Problems are reported to the standard error stream. 520 521<b>ENVIRONMENT</b> 522 <b>MAIL_CONFIG</b> 523 Directory with Postfix configuration files. 524 525<b>CONFIGURATION PARAMETERS</b> 526 The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro- 527 gram. 528 529 The text below provides only a parameter summary. See <a href="postconf.5.html"><b>postconf</b>(5)</a> for 530 more details including examples. 531 532 <b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b> 533 The default location of the Postfix <a href="postconf.5.html">main.cf</a> and <a href="master.5.html">master.cf</a> con- 534 figuration files. 535 536 <b><a href="postconf.5.html#bounce_template_file">bounce_template_file</a> (empty)</b> 537 Pathname of a configuration file with bounce message templates. 538 539<b>FILES</b> 540 /etc/postfix/<a href="postconf.5.html">main.cf</a>, Postfix configuration parameters 541 /etc/postfix/<a href="master.5.html">master.cf</a>, Postfix master daemon configuration 542 543<b>SEE ALSO</b> 544 <a href="bounce.5.html">bounce(5)</a>, bounce template file format 545 <a href="master.5.html">master(5)</a>, <a href="master.5.html">master.cf</a> configuration file syntax 546 <a href="postconf.5.html">postconf(5)</a>, <a href="postconf.5.html">main.cf</a> configuration file syntax 547 548<b>README FILES</b> 549 <a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview 550 551<b>LICENSE</b> 552 The Secure Mailer license must be distributed with this software. 553 554<b>AUTHOR(S)</b> 555 Wietse Venema 556 IBM T.J. Watson Research 557 P.O. Box 704 558 Yorktown Heights, NY 10598, USA 559 560 Wietse Venema 561 Google, Inc. 562 111 8th Avenue 563 New York, NY 10011, USA 564 565 POSTCONF(1) 566</pre> </body> </html> 567