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