{ "content": [ { "type": "text", "text": "# POSTCONF (man)\n\n## NAME\n\npostconf - Postfix configuration utility\n\n## DESCRIPTION\n\nBy default, the postconf(1) command displays the values of main.cf configuration parameters,\nand warns about possible mis-typed parameter names (Postfix 2.9 and later). The command can\nalso change main.cf configuration parameter values, or display other configuration informa‐\ntion about the Postfix mail system.\n\n## TLDR\n\n> Postfix configuration utility.\n\n- Specify the directory of the `main.cf` configuration file instead of the default configuration directory:\n `postconf -c {{path/to/configuration_directory}}`\n- Edit the `main.cf` configuration file and update parameter settings with the \"name=value\" pairs:\n `postconf -e`\n- Print the default parameter settings of the `main.cf` instead of the actual settings:\n `postconf -d`\n- Display parameters only from the specified class:\n `postconf -C {{builtin|service|user|all}}`\n- List available SASL plug-in types for the Postfix SMTP server. The plug-in type is selected with the `smtpd_sasl_type` configuration parameter by specifying `cyrus` or `dovecot` as the name:\n `postconf -a`\n- List the names of all supported lookup table types. Lookup tables are specified as `type:name` in configuration files where the type can be `btree`, `cdb`, `hash`, `mysql`, etc:\n `postconf -m`\n\n*Source: tldr-pages*\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS** (7 subsections)\n- **DESCRIPTION** (23 subsections)\n- **DIAGNOSTICS**\n- **ENVIRONMENT**\n- **CONFIGURATION PARAMETERS**\n- **FILES**\n- **SEE ALSO**\n- **README FILES**\n- **LICENSE**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "POSTCONF", "section": "", "mode": "man", "summary": "postconf - Postfix configuration utility", "synopsis": "", "tldr_summary": "Postfix configuration utility.", "tldr_examples": [ { "description": "Specify the directory of the `main.cf` configuration file instead of the default configuration directory", "command": "postconf -c {{path/to/configuration_directory}}" }, { "description": "Edit the `main.cf` configuration file and update parameter settings with the \"name=value\" pairs", "command": "postconf -e" }, { "description": "Print the default parameter settings of the `main.cf` instead of the actual settings", "command": "postconf -d" }, { "description": "Display parameters only from the specified class", "command": "postconf -C {{builtin|service|user|all}}" }, { "description": "List available SASL plug-in types for the Postfix SMTP server. The plug-in type is selected with the `smtpd_sasl_type` configuration parameter by specifying `cyrus` or `dovecot` as the name", "command": "postconf -a" }, { "description": "List the names of all supported lookup table types. Lookup tables are specified as `type:name` in configuration files where the type can be `btree`, `cdb`, `hash`, `mysql`, etc", "command": "postconf -m" } ], "tldr_source": "official", "flags": [ { "flag": "-a", "long": null, "arg": null, "description": "selected with the smtpdsasltype configuration parameter by specifying one of the names listed below. cyrus This server plug-in is available when Postfix is built with Cyrus SASL support. dovecot This server plug-in uses the Dovecot authentication server, and is available when Postfix is built with any form of SASL support. This feature is available with Postfix 2.3 and later." }, { "flag": "-A", "long": null, "arg": null, "description": "is selected with the smtpsasltype or lmtpsasltype configuration parameters by specifying one of the names listed below. cyrus This client plug-in is available when Postfix is built with Cyrus SASL support. This feature is available with Postfix 2.3 and later." }, { "flag": "-b", "long": null, "arg": null, "description": "Display the message text that appears at the beginning of delivery status notification (DSN) messages, expanding $name expressions with actual values as described in bounce(5). To override the bouncetemplatefile parameter setting, specify a template file name at the end of the \"postconf -b\" command line. Specify an empty file name to display built-in templates (in shell language: \"\"). This feature is available with Postfix 2.3 and later." }, { "flag": "-c", "long": null, "arg": null, "description": "The main.cf configuration file is in the named directory instead of the default con‐ figuration directory." }, { "flag": "-C", "long": null, "arg": null, "description": "When displaying main.cf parameters, select only parameters from the specified class(es): builtin Parameters with built-in names. service Parameters with service-defined names (the first field of a master.cf entry plus a Postfix-defined suffix). user Parameters with user-defined names. all All the above classes. The default is as if \"-C all\" is specified. This feature is available with Postfix 2.9 and later." }, { "flag": "-d", "long": null, "arg": null, "description": "fold long lines for human readability (Postfix 2.9 and later)." }, { "flag": "-e", "long": null, "arg": null, "description": "\"name=value\" pairs on the postconf(1) command line. With -M, edit the master.cf configuration file, and replace one or more service en‐ tries with new values as specified with \"service/type=value\" on the postconf(1) com‐ mand line. With -F, edit the master.cf configuration file, and replace one or more service fields with new values as specified with \"service/type/field=value\" on the postconf(1) com‐ mand line. Currently, the \"command\" field contains the command name and command argu‐ ments. this may change in the near future, so that the \"command\" field contains only the command name, and a new \"arguments\" pseudofield contains the command arguments. With -P, edit the master.cf configuration file, and add or update one or more service parameter settings (-o parameter=value settings) with new values as specified with \"service/type/parameter=value\" on the postconf(1) command line. In all cases the file is copied to a temporary file then renamed into place. Specify quotes to protect special characters and whitespace on the postconf(1) command line. The -e option is no longer needed with Postfix version 2.8 and later." }, { "flag": "-f", "long": null, "arg": null, "description": "man readability. This feature is available with Postfix 2.9 and later." }, { "flag": "-F", "long": null, "arg": null, "description": "matted as \"service/type/field=value\", one per line. Specify -Ff to fold long lines. Specify one or more \"service/type/field\" instances on the postconf(1) command line to limit the output to fields of interest. Trailing parameter name or service type fields that are omitted will be handled as \"*\" wildcard fields. This feature is available with Postfix 2.11 and later." }, { "flag": "-h", "long": null, "arg": null, "description": "the value." }, { "flag": "-H", "long": null, "arg": null, "description": "name. This feature is available with Postfix 3.1 and later." }, { "flag": "-l", "long": null, "arg": null, "description": "ing methods: flock A kernel-based advisory locking method for local files only. This locking method is available on systems with a BSD compatible library. fcntl A kernel-based advisory locking method for local and remote files. dotlock An application-level locking method. An application locks a file named filename by creating a file named filename.lock. The application is expected to remove its own lock file, as well as stale lock files that were left behind after ab‐ normal program termination." }, { "flag": "-m", "long": null, "arg": null, "description": "lookup tables are specified as type:name, where type is one of the types listed below. The table name syntax depends on the lookup table type as described in the DATA‐ BASEREADME document. btree A sorted, balanced tree structure. Available on systems with support for Berkeley DB databases. cdb A read-optimized structure with no support for incremental updates. Available on systems with support for CDB databases. This feature is available with Postfix 2.2 and later. cidr A table that associates values with Classless Inter-Domain Routing (CIDR) pat‐ terns. This is described in cidrtable(5). This feature is available with Postfix 2.2 and later. dbm An indexed file type based on hashing. Available on systems with support for DBM databases. environ The UNIX process environment array. The lookup key is the environment variable name; the table name is ignored. Originally implemented for testing, someone may find this useful someday. fail A table that reliably fails all requests. The lookup table name is used for logging. This table exists to simplify Postfix error tests. This feature is available with Postfix 2.9 and later. hash An indexed file type based on hashing. Available on systems with support for Berkeley DB databases. inline (read-only) A non-shared, in-memory lookup table. Example: \"inline:{ key=value, { key = text with whitespace or comma }}\". Key-value pairs are separated by whitespace or comma; with a key-value pair inside \"{}\", whitespace is ignored after the opening \"{\", around the \"=\" between key and value, and before the closing \"}\". Inline tables eliminate the need to create a database file for just a few fixed elements. See also the static: map type. This feature is available with Postfix 3.0 and later. internal A non-shared, in-memory hash table. Its content are lost when a process termi‐ nates. lmdb OpenLDAP LMDB database (a memory-mapped, persistent file). Available on sys‐ tems with support for LMDB databases. This is described in lmdbtable(5). This feature is available with Postfix 2.11 and later. ldap (read-only) LDAP database client. This is described in ldaptable(5). memcache Memcache database client. This is described in memcachetable(5). This feature is available with Postfix 2.9 and later. mysql (read-only) MySQL database client. Available on systems with support for MySQL databases. This is described in mysqltable(5). pcre (read-only) A lookup table based on Perl Compatible Regular Expressions. The file format is described in pcretable(5). pgsql (read-only) PostgreSQL database client. This is described in pgsqltable(5). This feature is available with Postfix 2.1 and later. pipemap (read-only) A lookup table that constructs a pipeline of tables. Example: \"pipemap:{type1:name1, ..., typen:namen}\". Each \"pipemap:\" query is given to the first table. Each lookup result becomes the query for the next table in the pipeline, and the last table produces the final result. When any table lookup produces no result, the pipeline produces no result. The first and last characters of the \"pipemap:\" table name must be \"{\" and \"}\". Within these, in‐ dividual maps are separated with comma or whitespace. This feature is available with Postfix 3.0 and later. proxy Postfix proxymap(8) client for shared access to Postfix databases. The table name syntax is type:name. This feature is available with Postfix 2.0 and later. randmap (read-only) An in-memory table that performs random selection. Example: \"randmap:{result1, ..., resultn}\". Each table query returns a random choice from the specified results. The first and last characters of the \"randmap:\" table name must be \"{\" and \"}\". Within these, individual results are separated with comma or white‐ space. To give a specific result more weight, specify it multiple times. This feature is available with Postfix 3.0 and later. regexp (read-only) A lookup table based on regular expressions. The file format is described in regexptable(5). sdbm An indexed file type based on hashing. Available on systems with support for SDBM databases. This feature is available with Postfix 2.2 and later. socketmap (read-only) Sendmail-style socketmap client. The table name is inet:host:port:name for a TCP/IP server, or unix:pathname:name for a UNIX-domain server. This is de‐ scribed in socketmaptable(5). This feature is available with Postfix 2.10 and later. sqlite (read-only) SQLite database. This is described in sqlitetable(5). This feature is available with Postfix 2.8 and later. static (read-only) A table that always returns its name as lookup result. For example, static:foo‐‐ bar always returns the string foobar as lookup result. Specify \"static:{ text with whitespace }\" when the result contains whitespace; this form ignores whitespace after the opening \"{\" and before the closing \"}\". See also the in‐ line: map. The form \"static:{text} is available with Postfix 3.0 and later. tcp (read-only) TCP/IP client. The protocol is described in tcptable(5). texthash (read-only) Produces similar results as hash: files, except that you don't need to run the postmap(1) command before you can use the file, and that it does not detect changes after the file is read. This feature is available with Postfix 2.8 and later. unionmap (read-only) A table that sends each query to multiple lookup tables and that concatenates all found results, separated by comma. The table name syntax is the same as for pipemap. This feature is available with Postfix 3.0 and later. unix (read-only) A limited view of the UNIX authentication database. The following tables are implemented: unix:passwd.byname The table is the UNIX password database. The key is a login name. The result is a password file entry in passwd(5) format. unix:group.byname The table is the UNIX group database. The key is a group name. The re‐ sult is a group file entry in group(5) format. Other table types may exist depending on how Postfix was built." }, { "flag": "-M", "long": null, "arg": null, "description": "long lines for human readability. Specify zero or more arguments, each with a service-name or service-name/service-type pair, where service-name is the first field of a master.cf entry and service-type is one of (inet, unix, fifo, or pass). If service-name or service-name/service-type is specified, only the matching master.cf entries will be output. For example, \"postconf -Mf smtp\" will output all services named \"smtp\", and \"postconf -Mf smtp/inet\" will output only the smtp service that lis‐ tens on the network. Trailing service type fields that are omitted will be handled as \"*\" wildcard fields. This feature is available with Postfix 2.9 and later. The syntax was changed from \"name.type\" to \"name/type\", and \"*\" wildcard support was added with Postfix 2.11." }, { "flag": "-n", "long": null, "arg": null, "description": "Specify -nf to fold long lines for human readability (Postfix 2.9 and later). To show settings that differ from built-in defaults only, use the following bash syntax: comm -23 <(postconf -n) <(postconf -d) Replace \"-23\" with \"-12\" to show settings that duplicate built-in defaults." }, { "flag": "-o", "long": null, "arg": null, "description": "Override main.cf parameter settings. This feature is available with Postfix 2.10 and later." }, { "flag": "-p", "long": null, "arg": null, "description": "This feature is available with Postfix 2.11 and later." }, { "flag": "-P", "long": null, "arg": null, "description": "ters), formatted as \"service/type/parameter=value\", one per line. Specify -Pf to fold long lines. Specify one or more \"service/type/parameter\" instances on the postconf(1) command line to limit the output to parameters of interest. Trailing parameter name or service type fields that are omitted will be handled as \"*\" wildcard fields. This feature is available with Postfix 2.11 and later." }, { "flag": "-t", "long": null, "arg": null, "description": "Display the templates for text that appears at the beginning of delivery status noti‐ fication (DSN) messages, without expanding $name expressions. To override the bouncetemplatefile parameter setting, specify a template file name at the end of the \"postconf -t\" command line. Specify an empty file name to display built-in templates (in shell language: \"\"). This feature is available with Postfix 2.3 and later." }, { "flag": "-T", "long": null, "arg": null, "description": "If Postfix is compiled without TLS support, the -T option produces no output. Other‐ wise, if an invalid mode is specified, the -T option reports an error and exits with a non-zero status code. The valid modes are: compile-version Output the OpenSSL version that Postfix was compiled with (i.e. the OpenSSL version in a header file). The output format is the same as with the command \"openssl version\". run-version Output the OpenSSL version that Postfix is linked with at runtime (i.e. the OpenSSL version in a shared library). public-key-algorithms Output the lower-case names of the supported public-key algorithms, one per-line. This feature is available with Postfix 3.1 and later." }, { "flag": "-v", "long": null, "arg": null, "description": "increasingly verbose." }, { "flag": "-x", "long": null, "arg": null, "description": "This feature is available with Postfix 2.10 and later." }, { "flag": "-X", "long": null, "arg": null, "description": "conf(1) command line. Specify a list of parameter names, not \"name=value\" pairs. With -M, edit the master.cf configuration file, and remove one or more service entries as specified with \"service/type\" on the postconf(1) command line. With -P, edit the master.cf configuration file, and remove one or more service parame‐ ter settings (-o parameter=value settings) as specified with \"service/type/parameter\" on the postconf(1) command line. In all cases the file is copied to a temporary file then renamed into place. Specify quotes to protect special characters on the postconf(1) command line. There is no postconf(1) command to perform the reverse operation. This feature is available with Postfix 2.10 and later. Support for -M and -P was added with Postfix 2.11. -# Edit the main.cf configuration file, and comment out the parameters named on the post‐‐ conf(1) command line, so that those parameters revert to their default values. Spec‐ ify a list of parameter names, not \"name=value\" pairs. With -M, edit the master.cf configuration file, and comment out one or more service entries as specified with \"service/type\" on the postconf(1) command line. In all cases the file is copied to a temporary file then renamed into place. Specify quotes to protect special characters on the postconf(1) command line. There is no postconf(1) command to perform the reverse operation. This feature is available with Postfix 2.6 and later. Support for -M was added with Postfix 2.11." } ], "examples": [], "see_also": [ { "name": "bounce", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/bounce/5/json" }, { "name": "master", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/master/5/json" }, { "name": "postconf", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/postconf/5/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 1, "subsections": [ { "name": "Managing main.cf:", "lines": 8 }, { "name": "Managing master.cf service entries:", "lines": 8 }, { "name": "Managing master.cf service fields:", "lines": 4 }, { "name": "Managing master.cf service parameters:", "lines": 6 }, { "name": "Managing bounce message templates:", "lines": 4 }, { "name": "Managing TLS features:", "lines": 2 }, { "name": "Managing other configuration:", "lines": 2 } ] }, { "name": "DESCRIPTION", "lines": 7, "subsections": [ { "name": "-a", "lines": 11, "flag": "-a" }, { "name": "-A", "lines": 7, "flag": "-A" }, { "name": "-b", "lines": 10, "flag": "-b" }, { "name": "-c", "lines": 3, "flag": "-c" }, { "name": "-C", "lines": 18, "flag": "-C" }, { "name": "-d -df", "lines": 2, "flag": "-d" }, { "name": "-e", "lines": 21, "flag": "-e" }, { "name": "-f", "lines": 4, "flag": "-f" }, { "name": "-F", "lines": 8, "flag": "-F" }, { "name": "-h", "lines": 2, "flag": "-h" }, { "name": "-H", "lines": 4, "flag": "-H" }, { "name": "-l", "lines": 13, "flag": "-l" }, { "name": "-m", "lines": 159, "flag": "-m" }, { "name": "-M -Mf", "lines": 15, "flag": "-M" }, { "name": "-n", "lines": 5, "flag": "-n" }, { "name": "-o", "lines": 4, "flag": "-o" }, { "name": "-p", "lines": 2, "flag": "-p" }, { "name": "-P", "lines": 9, "flag": "-P" }, { "name": "-t", "lines": 9, "flag": "-t" }, { "name": "-T", "lines": 19, "flag": "-T" }, { "name": "-v -v", "lines": 2, "flag": "-v" }, { "name": "-x", "lines": 2, "flag": "-x" }, { "name": "-X", "lines": 32, "flag": "-X" } ] }, { "name": "DIAGNOSTICS", "lines": 2, "subsections": [] }, { "name": "ENVIRONMENT", "lines": 3, "subsections": [] }, { "name": "CONFIGURATION PARAMETERS", "lines": 11, "subsections": [] }, { "name": "FILES", "lines": 3, "subsections": [] }, { "name": "SEE ALSO", "lines": 4, "subsections": [] }, { "name": "README FILES", "lines": 3, "subsections": [] }, { "name": "LICENSE", "lines": 16, "subsections": [] } ], "sections": { "NAME": { "content": "postconf - Postfix configuration utility\n", "subsections": [] }, "SYNOPSIS": { "content": "", "subsections": [ { "name": "Managing main.cf:", "content": "postconf [-dfhHnopvx] [-c configdir] [-C class,...] [parameter ...]\n\npostconf [-epv] [-c configdir] parameter=value ...\n\npostconf -# [-pv] [-c configdir] parameter ...\n\npostconf -X [-pv] [-c configdir] parameter ...\n" }, { "name": "Managing master.cf service entries:", "content": "postconf -M [-fovx] [-c configdir] [service[/type] ...]\n\npostconf -M [-ev] [-c configdir] service/type=value ...\n\npostconf -M# [-v] [-c configdir] service/type ...\n\npostconf -MX [-v] [-c configdir] service/type ...\n" }, { "name": "Managing master.cf service fields:", "content": "postconf -F [-fhHovx] [-c configdir] [service[/type[/field]] ...]\n\npostconf -F [-ev] [-c configdir] service/type/field=value ...\n" }, { "name": "Managing master.cf service parameters:", "content": "postconf -P [-fhHovx] [-c configdir] [service[/type[/parameter]] ...]\n\npostconf -P [-ev] [-c configdir] service/type/parameter=value ...\n\npostconf -PX [-v] [-c configdir] service/type/parameter ...\n" }, { "name": "Managing bounce message templates:", "content": "postconf -b [-v] [-c configdir] [templatefile]\n\npostconf -t [-v] [-c configdir] [templatefile]\n" }, { "name": "Managing TLS features:", "content": "postconf -T mode [-v] [-c configdir]\n" }, { "name": "Managing other configuration:", "content": "postconf -a|-A|-l|-m [-v] [-c configdir]\n" } ] }, "DESCRIPTION": { "content": "By default, the postconf(1) command displays the values of main.cf configuration parameters,\nand warns about possible mis-typed parameter names (Postfix 2.9 and later). The command can\nalso change main.cf configuration parameter values, or display other configuration informa‐\ntion about the Postfix mail system.\n\nOptions:\n", "subsections": [ { "name": "-a", "content": "selected with the smtpdsasltype configuration parameter by specifying one of the\nnames listed below.\n\ncyrus This server plug-in is available when Postfix is built with Cyrus SASL support.\n\ndovecot\nThis server plug-in uses the Dovecot authentication server, and is available\nwhen Postfix is built with any form of SASL support.\n\nThis feature is available with Postfix 2.3 and later.\n", "flag": "-a" }, { "name": "-A", "content": "is selected with the smtpsasltype or lmtpsasltype configuration parameters by\nspecifying one of the names listed below.\n\ncyrus This client plug-in is available when Postfix is built with Cyrus SASL support.\n\nThis feature is available with Postfix 2.3 and later.\n", "flag": "-A" }, { "name": "-b", "content": "Display the message text that appears at the beginning of delivery status notification\n(DSN) messages, expanding $name expressions with actual values as described in\nbounce(5).\n\nTo override the bouncetemplatefile parameter setting, specify a template file name\nat the end of the \"postconf -b\" command line. Specify an empty file name to display\nbuilt-in templates (in shell language: \"\").\n\nThis feature is available with Postfix 2.3 and later.\n", "flag": "-b" }, { "name": "-c", "content": "The main.cf configuration file is in the named directory instead of the default con‐\nfiguration directory.\n", "flag": "-c" }, { "name": "-C", "content": "When displaying main.cf parameters, select only parameters from the specified\nclass(es):\n\nbuiltin\nParameters with built-in names.\n\nservice\nParameters with service-defined names (the first field of a master.cf entry\nplus a Postfix-defined suffix).\n\nuser Parameters with user-defined names.\n\nall All the above classes.\n\nThe default is as if \"-C all\" is specified.\n\nThis feature is available with Postfix 2.9 and later.\n", "flag": "-C" }, { "name": "-d -df", "content": "fold long lines for human readability (Postfix 2.9 and later).\n", "flag": "-d" }, { "name": "-e", "content": "\"name=value\" pairs on the postconf(1) command line.\n\nWith -M, edit the master.cf configuration file, and replace one or more service en‐\ntries with new values as specified with \"service/type=value\" on the postconf(1) com‐\nmand line.\n\nWith -F, edit the master.cf configuration file, and replace one or more service fields\nwith new values as specified with \"service/type/field=value\" on the postconf(1) com‐\nmand line. Currently, the \"command\" field contains the command name and command argu‐\nments. this may change in the near future, so that the \"command\" field contains only\nthe command name, and a new \"arguments\" pseudofield contains the command arguments.\n\nWith -P, edit the master.cf configuration file, and add or update one or more service\nparameter settings (-o parameter=value settings) with new values as specified with\n\"service/type/parameter=value\" on the postconf(1) command line.\n\nIn all cases the file is copied to a temporary file then renamed into place. Specify\nquotes to protect special characters and whitespace on the postconf(1) command line.\n\nThe -e option is no longer needed with Postfix version 2.8 and later.\n", "flag": "-e" }, { "name": "-f", "content": "man readability.\n\nThis feature is available with Postfix 2.9 and later.\n", "flag": "-f" }, { "name": "-F", "content": "matted as \"service/type/field=value\", one per line. Specify -Ff to fold long lines.\n\nSpecify one or more \"service/type/field\" instances on the postconf(1) command line to\nlimit the output to fields of interest. Trailing parameter name or service type\nfields that are omitted will be handled as \"*\" wildcard fields.\n\nThis feature is available with Postfix 2.11 and later.\n", "flag": "-F" }, { "name": "-h", "content": "the value.\n", "flag": "-h" }, { "name": "-H", "content": "name.\n\nThis feature is available with Postfix 3.1 and later.\n", "flag": "-H" }, { "name": "-l", "content": "ing methods:\n\nflock A kernel-based advisory locking method for local files only. This locking\nmethod is available on systems with a BSD compatible library.\n\nfcntl A kernel-based advisory locking method for local and remote files.\n\ndotlock\nAn application-level locking method. An application locks a file named filename\nby creating a file named filename.lock. The application is expected to remove\nits own lock file, as well as stale lock files that were left behind after ab‐\nnormal program termination.\n", "flag": "-l" }, { "name": "-m", "content": "lookup tables are specified as type:name, where type is one of the types listed below.\nThe table name syntax depends on the lookup table type as described in the DATA‐\nBASEREADME document.\n\nbtree A sorted, balanced tree structure. Available on systems with support for\nBerkeley DB databases.\n\ncdb A read-optimized structure with no support for incremental updates. Available\non systems with support for CDB databases.\n\nThis feature is available with Postfix 2.2 and later.\n\ncidr A table that associates values with Classless Inter-Domain Routing (CIDR) pat‐\nterns. This is described in cidrtable(5).\n\nThis feature is available with Postfix 2.2 and later.\n\ndbm An indexed file type based on hashing. Available on systems with support for\nDBM databases.\n\nenviron\nThe UNIX process environment array. The lookup key is the environment variable\nname; the table name is ignored. Originally implemented for testing, someone\nmay find this useful someday.\n\nfail A table that reliably fails all requests. The lookup table name is used for\nlogging. This table exists to simplify Postfix error tests.\n\nThis feature is available with Postfix 2.9 and later.\n\nhash An indexed file type based on hashing. Available on systems with support for\nBerkeley DB databases.\n\ninline (read-only)\nA non-shared, in-memory lookup table. Example: \"inline:{ key=value, { key =\ntext with whitespace or comma }}\". Key-value pairs are separated by whitespace\nor comma; with a key-value pair inside \"{}\", whitespace is ignored after the\nopening \"{\", around the \"=\" between key and value, and before the closing \"}\".\nInline tables eliminate the need to create a database file for just a few fixed\nelements. See also the static: map type.\n\nThis feature is available with Postfix 3.0 and later.\n\ninternal\nA non-shared, in-memory hash table. Its content are lost when a process termi‐\nnates.\n\nlmdb OpenLDAP LMDB database (a memory-mapped, persistent file). Available on sys‐\ntems with support for LMDB databases. This is described in lmdbtable(5).\n\nThis feature is available with Postfix 2.11 and later.\n\nldap (read-only)\nLDAP database client. This is described in ldaptable(5).\n\nmemcache\nMemcache database client. This is described in memcachetable(5).\n\nThis feature is available with Postfix 2.9 and later.\n\nmysql (read-only)\nMySQL database client. Available on systems with support for MySQL databases.\nThis is described in mysqltable(5).\n\npcre (read-only)\nA lookup table based on Perl Compatible Regular Expressions. The file format\nis described in pcretable(5).\n\npgsql (read-only)\nPostgreSQL database client. This is described in pgsqltable(5).\n\nThis feature is available with Postfix 2.1 and later.\n\npipemap (read-only)\nA lookup table that constructs a pipeline of tables. Example:\n\"pipemap:{type1:name1, ..., typen:namen}\". Each \"pipemap:\" query is given\nto the first table. Each lookup result becomes the query for the next table in\nthe pipeline, and the last table produces the final result. When any table\nlookup produces no result, the pipeline produces no result. The first and last\ncharacters of the \"pipemap:\" table name must be \"{\" and \"}\". Within these, in‐\ndividual maps are separated with comma or whitespace.\n\nThis feature is available with Postfix 3.0 and later.\n\nproxy Postfix proxymap(8) client for shared access to Postfix databases. The table\nname syntax is type:name.\n\nThis feature is available with Postfix 2.0 and later.\n\nrandmap (read-only)\nAn in-memory table that performs random selection. Example: \"randmap:{result1,\n..., resultn}\". Each table query returns a random choice from the specified\nresults. The first and last characters of the \"randmap:\" table name must be \"{\"\nand \"}\". Within these, individual results are separated with comma or white‐\nspace. To give a specific result more weight, specify it multiple times.\n\nThis feature is available with Postfix 3.0 and later.\n\nregexp (read-only)\nA lookup table based on regular expressions. The file format is described in\nregexptable(5).\n\nsdbm An indexed file type based on hashing. Available on systems with support for\nSDBM databases.\n\nThis feature is available with Postfix 2.2 and later.\n\nsocketmap (read-only)\nSendmail-style socketmap client. The table name is inet:host:port:name for a\nTCP/IP server, or unix:pathname:name for a UNIX-domain server. This is de‐\nscribed in socketmaptable(5).\n\nThis feature is available with Postfix 2.10 and later.\n\nsqlite (read-only)\nSQLite database. This is described in sqlitetable(5).\n\nThis feature is available with Postfix 2.8 and later.\n\nstatic (read-only)\nA table that always returns its name as lookup result. For example, static:foo‐‐\nbar always returns the string foobar as lookup result. Specify \"static:{ text\nwith whitespace }\" when the result contains whitespace; this form ignores\nwhitespace after the opening \"{\" and before the closing \"}\". See also the in‐\nline: map.\n\nThe form \"static:{text} is available with Postfix 3.0 and later.\n\ntcp (read-only)\nTCP/IP client. The protocol is described in tcptable(5).\n\ntexthash (read-only)\nProduces similar results as hash: files, except that you don't need to run the\npostmap(1) command before you can use the file, and that it does not detect\nchanges after the file is read.\n\nThis feature is available with Postfix 2.8 and later.\n\nunionmap (read-only)\nA table that sends each query to multiple lookup tables and that concatenates\nall found results, separated by comma. The table name syntax is the same as\nfor pipemap.\n\nThis feature is available with Postfix 3.0 and later.\n\nunix (read-only)\nA limited view of the UNIX authentication database. The following tables are\nimplemented:\n\nunix:passwd.byname\nThe table is the UNIX password database. The key is a login name. The\nresult is a password file entry in passwd(5) format.\n\nunix:group.byname\nThe table is the UNIX group database. The key is a group name. The re‐\nsult is a group file entry in group(5) format.\n\nOther table types may exist depending on how Postfix was built.\n", "flag": "-m" }, { "name": "-M -Mf", "content": "long lines for human readability.\n\nSpecify zero or more arguments, each with a service-name or service-name/service-type\npair, where service-name is the first field of a master.cf entry and service-type is\none of (inet, unix, fifo, or pass).\n\nIf service-name or service-name/service-type is specified, only the matching master.cf\nentries will be output. For example, \"postconf -Mf smtp\" will output all services\nnamed \"smtp\", and \"postconf -Mf smtp/inet\" will output only the smtp service that lis‐\ntens on the network. Trailing service type fields that are omitted will be handled as\n\"*\" wildcard fields.\n\nThis feature is available with Postfix 2.9 and later. The syntax was changed from\n\"name.type\" to \"name/type\", and \"*\" wildcard support was added with Postfix 2.11.\n", "flag": "-M" }, { "name": "-n", "content": "Specify -nf to fold long lines for human readability (Postfix 2.9 and later). To show\nsettings that differ from built-in defaults only, use the following bash syntax:\ncomm -23 <(postconf -n) <(postconf -d)\nReplace \"-23\" with \"-12\" to show settings that duplicate built-in defaults.\n", "flag": "-n" }, { "name": "-o", "content": "Override main.cf parameter settings.\n\nThis feature is available with Postfix 2.10 and later.\n", "flag": "-o" }, { "name": "-p", "content": "This feature is available with Postfix 2.11 and later.\n", "flag": "-p" }, { "name": "-P", "content": "ters), formatted as \"service/type/parameter=value\", one per line. Specify -Pf to fold\nlong lines.\n\nSpecify one or more \"service/type/parameter\" instances on the postconf(1) command line\nto limit the output to parameters of interest. Trailing parameter name or service\ntype fields that are omitted will be handled as \"*\" wildcard fields.\n\nThis feature is available with Postfix 2.11 and later.\n", "flag": "-P" }, { "name": "-t", "content": "Display the templates for text that appears at the beginning of delivery status noti‐\nfication (DSN) messages, without expanding $name expressions.\n\nTo override the bouncetemplatefile parameter setting, specify a template file name\nat the end of the \"postconf -t\" command line. Specify an empty file name to display\nbuilt-in templates (in shell language: \"\").\n\nThis feature is available with Postfix 2.3 and later.\n", "flag": "-t" }, { "name": "-T", "content": "If Postfix is compiled without TLS support, the -T option produces no output. Other‐\nwise, if an invalid mode is specified, the -T option reports an error and exits with a\nnon-zero status code. The valid modes are:\n\ncompile-version\nOutput the OpenSSL version that Postfix was compiled with (i.e. the OpenSSL\nversion in a header file). The output format is the same as with the command\n\"openssl version\".\n\nrun-version\nOutput the OpenSSL version that Postfix is linked with at runtime (i.e. the\nOpenSSL version in a shared library).\n\npublic-key-algorithms\nOutput the lower-case names of the supported public-key algorithms, one\nper-line.\n\nThis feature is available with Postfix 3.1 and later.\n", "flag": "-T" }, { "name": "-v -v", "content": "increasingly verbose.\n", "flag": "-v" }, { "name": "-x", "content": "This feature is available with Postfix 2.10 and later.\n", "flag": "-x" }, { "name": "-X", "content": "conf(1) command line. Specify a list of parameter names, not \"name=value\" pairs.\n\nWith -M, edit the master.cf configuration file, and remove one or more service entries\nas specified with \"service/type\" on the postconf(1) command line.\n\nWith -P, edit the master.cf configuration file, and remove one or more service parame‐\nter settings (-o parameter=value settings) as specified with \"service/type/parameter\"\non the postconf(1) command line.\n\nIn all cases the file is copied to a temporary file then renamed into place. Specify\nquotes to protect special characters on the postconf(1) command line.\n\nThere is no postconf(1) command to perform the reverse operation.\n\nThis feature is available with Postfix 2.10 and later. Support for -M and -P was\nadded with Postfix 2.11.\n\n-# Edit the main.cf configuration file, and comment out the parameters named on the post‐‐\nconf(1) command line, so that those parameters revert to their default values. Spec‐\nify a list of parameter names, not \"name=value\" pairs.\n\nWith -M, edit the master.cf configuration file, and comment out one or more service\nentries as specified with \"service/type\" on the postconf(1) command line.\n\nIn all cases the file is copied to a temporary file then renamed into place. Specify\nquotes to protect special characters on the postconf(1) command line.\n\nThere is no postconf(1) command to perform the reverse operation.\n\nThis feature is available with Postfix 2.6 and later. Support for -M was added with\nPostfix 2.11.\n", "flag": "-X" } ] }, "DIAGNOSTICS": { "content": "Problems are reported to the standard error stream.\n", "subsections": [] }, "ENVIRONMENT": { "content": "MAILCONFIG\nDirectory with Postfix configuration files.\n", "subsections": [] }, "CONFIGURATION PARAMETERS": { "content": "The following main.cf parameters are especially relevant to this program.\n\nThe text below provides only a parameter summary. See postconf(5) for more details including\nexamples.\n\nconfigdirectory (see 'postconf -d' output)\nThe default location of the Postfix main.cf and master.cf configuration files.\n\nbouncetemplatefile (empty)\nPathname of a configuration file with bounce message templates.\n", "subsections": [] }, "FILES": { "content": "/etc/postfix/main.cf, Postfix configuration parameters\n/etc/postfix/master.cf, Postfix master daemon configuration\n", "subsections": [] }, "SEE ALSO": { "content": "bounce(5), bounce template file format\nmaster(5), master.cf configuration file syntax\npostconf(5), main.cf configuration file syntax\n", "subsections": [] }, "README FILES": { "content": "Use \"postconf readmedirectory\" or \"postconf htmldirectory\" to locate this information.\nDATABASEREADME, Postfix lookup table overview\n", "subsections": [] }, "LICENSE": { "content": "The Secure Mailer license must be distributed with this software.\n\nAUTHOR(S)\nWietse Venema\nIBM T.J. Watson Research\nP.O. Box 704\nYorktown Heights, NY 10598, USA\n\nWietse Venema\nGoogle, Inc.\n111 8th Avenue\nNew York, NY 10011, USA\n\n\n\nPOSTCONF(1)", "subsections": [] } } } }