Quelle postconf.1.html

Sprache: HTML

products/Sources/formale Sprachen/C/Postfix/html/postconf.1.html

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"
 "https://www.w3.org/TR/html4/loose.dtd">
<html> <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel='stylesheet' type='text/css' href='postfix-doc.css'>
<title> Postfix manual - postconf(1) </title>
</head> <body> <pre>
POSTCONF(1) POSTCONF(1)

<a name="name">NAME</a>
 postconf - Postfix configuration utility

<a name="synopsis">SYNOPSIS</a>
 Managing <a href="postconf.5.html">main.cf</a>:

 postconf [-dfhHjnopqvx] [-c config_dir] [-C class,...] [parameter ...]

 postconf [-epv] [-c config_dir] parameter=value ...

 postconf -# [-pv] [-c config_dir] parameter ...

 postconf -X [-pv] [-c config_dir] parameter ...

 Managing <a href="master.5.html">master.cf</a> service entries:

 postconf -M [-joqvx] [-c config_dir] [service[/type] ...]

 postconf -M [-ev] [-c config_dir] service/type=value ...

 postconf -M# [-v] [-c config_dir] service/type ...

 postconf -MX [-v] [-c config_dir] service/type ...

 Managing <a href="master.5.html">master.cf</a> service fields:

 postconf -F [-fhHjoqvx] [-c config_dir] [service[/type[/field]] ...]

 postconf -F [-ev] [-c config_dir] service/type/field=value ...

 Managing <a href="master.5.html">master.cf</a> service parameters:

 postconf -P [-fhHjoqvx] [-c config_dir] [service[/type[/parameter]]
 ...]

 postconf -P [-ev] [-c config_dir] service/type/parameter=value ...

 postconf -PX [-v] [-c config_dir] service/type/parameter ...

 Managing bounce message templates:

 postconf -b [-v] [-c config_dir] [template_file]

 postconf -t [-v] [-c config_dir] [template_file]

 Managing TLS features:

 postconf -T mode [-v] [-c config_dir]

 Managing other configuration:

 postconf -a|-A|-l|-m [-v] [-c config_dir]

<a name="description">DESCRIPTION</a>
 By default, the <a href="postconf.1.html">postconf(1)</a> command displays the values of <a href="postconf.5.html">main.cf</a> con-
 figuration parameters, and warns about possible mis-typed parameter
 names (Postfix 2.9 and later). The command can also change <a href="postconf.5.html">main.cf</a>
 configuration parameter values, or display other configuration informa-
 tion about the Postfix mail system.

 Options:

 -a List the available SASL plug-in types for the Postfix SMTP
 server. The plug-in type is selected with the <a href="postconf.5.html#smtpd_sasl_type">smtpd_sasl_type</a>
 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.

 -A List the available SASL plug-in types for the Postfix SMTP
 client. The plug-in type is selected with the <a href="postconf.5.html#smtp_sasl_type">smtp_sasl_type</a> or
 <a href="postconf.5.html#lmtp_sasl_type">lmtp_sasl_type</a> 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.

 -b [template_file]
 Display the message text that appears at the beginning of deliv-
 ery status notification (DSN) messages, expanding $name expres-
 sions with actual values as described in <a href="bounce.5.html">bounce(5)</a>.

 To override the <a href="postconf.5.html#bounce_template_file">bounce_template_file</a> 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.

 -c config_dir
 The <a href="postconf.5.html">main.cf</a> configuration file is in the named directory instead
 of the default configuration directory.

 -C class,...
 When displaying <a href="postconf.5.html">main.cf</a> 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 <a href="master.5.html">master.cf</a> 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.

 -d Print <a href="postconf.5.html">main.cf</a> default parameter settings instead of actual set-
 tings. Specify -df to fold long lines for human readability
 (Postfix 2.9 and later).

 -e Edit the <a href="postconf.5.html">main.cf</a> configuration file, and update parameter set-
 tings with the "name=value" pairs on the <a href="postconf.1.html">postconf(1)</a> command
 line.

 With -M, edit the <a href="master.5.html">master.cf</a> configuration file, and replace one
 or more service entries with new values as specified with "ser-
 vice/type=value" on the <a href="postconf.1.html">postconf(1)</a> command line.

 With -F, edit the <a href="master.5.html">master.cf</a> configuration file, and replace one
 or more service fields with new values as specified with "ser-
 vice/type/field=value" on the <a href="postconf.1.html">postconf(1)</a> command line. Cur-
 rently, the "command" field contains the command name and com-
 mand arguments. This may change in the near future, so that the
 "command" field contains only the command name, and a new "argu-
 ments" pseudofield contains the command arguments.

 With -P, edit the <a href="master.5.html">master.cf</a> configuration file, and add or
 update one or more service parameter settings (-o parame-
 ter=value settings) with new values as specified with "ser-
 vice/type/parameter=value" on the <a href="postconf.1.html">postconf(1)</a> 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 <a href="postconf.1.html">postconf(1)</a> command line.

 The -e option is no longer needed with Postfix version 2.8 and
 later, as it is assumed whenever a value is specified (empty or
 non-empty).

 -f Fold long lines when printing <a href="postconf.5.html">main.cf</a> or <a href="master.5.html">master.cf</a> configuration
 file entries, for human readability.

 This feature is available with Postfix 2.9 and later.

 -F Show <a href="master.5.html">master.cf</a> per-entry field settings (by default all services
 and all fields), formatted as "service/type/field=value", one
 per line. Specify -Ff to fold long lines.

 Specify one or more "service/type/field" instances on the <a href="postconf.1.html">post-</a>
 <a href="postconf.1.html">conf(1)</a> 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.

 -h Show parameter or attribute values without the "name = " label
 that normally precedes the value.

 -H Show parameter or attribute names without the " = value" that
 normally follows the name.

 This feature is available with Postfix 3.1 and later.

 -j JSON output. Format <a href="postconf.5.html">main.cf</a> or <a href="master.5.html">master.cf</a> settings as one {"key":
 "value"} object per line.

 This feature is available with Postfix 3.11 and later.

 -l List the names of all supported mailbox locking methods. Post-
 fix supports the following 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 file-
 name.lock. The application is expected to remove its own
 lock file, as well as stale lock files that were left
 behind after abnormal program termination.

 -m List the names of all supported lookup table types. In Postfix
 configuration files, lookup tables are specified as type:name,
 where type is one of the types listed below. The table name syn-
 tax depends on the lookup table type as described in the <a href="DATABASE_README.html">DATA</a>-
 <a href="DATABASE_README.html">BASE_README</a> 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 incremen-
 tal 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) patterns. This is described
 in <a href="cidr_table.5.html">cidr_table(5)</a>.

 This feature is available with Postfix 2.2 and later.

 dbm An indexed file type based on hashing. Available on sys-
 tems with support for DBM databases.

 debug An adapter for another table that causes all accesses to
 be logged. The table name syntax is type:name. Example
 usage: debug:<a href="DATABASE_README.html#types">hash</a>:/etc/postfix/example. The formats of
 the log messages are unspecified and subject to change.
 Warning: If a query or the underlying table contains sen-
 sitive information (such as a password), that information
 might be logged.

 This feature is available with Postfix 3.11 and later.

 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 ta-
 ble name is used for logging. This table exists to sim-
 plify Postfix error tests.

 This feature is available with Postfix 2.9 and later.

 hash An indexed file type based on hashing. Available on sys-
 tems with support for Berkeley DB databases.

 inline (read-only)
 A non-shared, in-memory lookup table. Example: "<a href="DATABASE_README.html#types">inline</a>:{
 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 elimi-
 nate the need to create a database file for just a few
 fixed elements. See also the <a href="DATABASE_README.html#types">static</a>: 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 terminates.

 lmdb OpenLDAP LMDB database (a memory-mapped, persistent
 file). Available on systems with support for LMDB data-
 bases. This is described in <a href="lmdb_table.5.html">lmdb_table(5)</a>.

 This feature is available with Postfix 2.11 and later.

 ldap (read-only)
 LDAP database client. This is described in <a href="ldap_table.5.html">ldap_table(5)</a>.

 memcache
 Memcache database client. This is described in <a href="memcache_table.5.html">mem-</a>
 <a href="memcache_table.5.html">cache_table(5)</a>.

 This feature is available with Postfix 2.9 and later.

 mongodb
 MongoDB database client. This is described in <a href="mongodb_table.5.html">mongodb_ta-</a>
 <a href="mongodb_table.5.html">ble(5)</a>.

 This feature is available with Postfix 3.9 and later.

 mysql (read-only)
 MySQL database client. Available on systems with support
 for MySQL databases. This is described in <a href="mysql_table.5.html">mysql_ta-</a>
 <a href="mysql_table.5.html">ble(5)</a>.

 pcre (read-only)
 A lookup table based on Perl Compatible Regular Expres-
 sions. The file format is described in <a href="pcre_table.5.html">pcre_table(5)</a>.

 pgsql (read-only)
 PostgreSQL database client. This is described in
 <a href="pgsql_table.5.html">pgsql_table(5)</a>.

 This feature is available with Postfix 2.1 and later.

 pipemap (read-only)
 A lookup table that constructs a pipeline of tables.
 Example: "<a href="DATABASE_README.html#types">pipemap</a>:{type_1:name_1, ..., type_n:name_n}".
 Each "<a href="DATABASE_README.html#types">pipemap</a>:" 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
 "<a href="DATABASE_README.html#types">pipemap</a>:" table name must be "{" and "}". Within these,
 individual maps are separated with comma or whitespace.

 This feature is available with Postfix 3.0 and later.

 proxy Postfix <a href="proxymap.8.html">proxymap(8)</a> 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. Exam-
 ple: "<a href="DATABASE_README.html#types">randmap</a>:{result_1, ..., result_n}". Each table
 query returns a random choice from the specified results.
 The first and last characters of the "<a href="DATABASE_README.html#types">randmap</a>:" table
 name must be "{" and "}". Within these, individual
 results are separated with comma or whitespace. 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 <a href="regexp_table.5.html">regexp_table(5)</a>.

 sdbm An indexed file type based on hashing. Available on sys-
 tems 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:path-
 name:name for a UNIX-domain server. This is described in
 <a href="socketmap_table.5.html">socketmap_table(5)</a>.

 This feature is available with Postfix 2.10 and later.

 sqlite (read-only)
 SQLite database. This is described in <a href="sqlite_table.5.html">sqlite_table(5)</a>.

 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, <a href="DATABASE_README.html#types">static</a>:foobar always returns the string foo-
 bar as lookup result. Specify "<a href="DATABASE_README.html#types">static</a>:{ text with white-
 space }" when the result contains whitespace; this form
 ignores whitespace after the opening "{" and before the
 closing "}". See also the <a href="DATABASE_README.html#types">inline</a>: map.

 The form "<a href="DATABASE_README.html#types">static</a>:{text} is available with Postfix 3.0 and
 later.

 tcp (read-only)
 TCP/IP client. The protocol is described in <a href="tcp_table.5.html">tcp_table(5)</a>.

 texthash (read-only)
 Produces similar results as <a href="DATABASE_README.html#types">hash</a>: files, except that you
 don't need to run the <a href="postmap.1.html">postmap(1)</a> 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 result is a group file entry in
 group(5) format.

 Other table types may exist depending on how Postfix was built.

 -M Show <a href="master.5.html">master.cf</a> file contents instead of <a href="postconf.5.html">main.cf</a> file contents.
 Specify -Mf to fold long lines for human readability.

 Specify zero or more arguments, each with a service-name or ser-
 vice-name/service-type pair, where service-name is the first
 field of a <a href="master.5.html">master.cf</a> 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 <a href="master.5.html">master.cf</a> 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
 listens 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.

 -n Show only configuration parameters that have explicit name=value
 settings in <a href="postconf.5.html">main.cf</a>. Specify -nf to fold long lines for human
 readability (Postfix 2.9 and later). To show settings that dif-
 fer from built-in defaults only, use the following bash syntax:
 LANG=C comm -23 <(postconf -n) <(postconf -d)
 Replace "-23" with "-12" to show settings that duplicate
 built-in defaults.

 -o name=value
 Override <a href="postconf.5.html">main.cf</a> parameter settings. This lets you see the
 effect changing a parameter would have when it is used in other
 configuration parameters, e.g.:
 postconf -x -o stress=yes

 This feature is available with Postfix 2.10 and later.

 -p Show <a href="postconf.5.html">main.cf</a> parameter settings. This is the default.

 This feature is available with Postfix 2.11 and later.

 -P Show <a href="master.5.html">master.cf</a> service parameter settings (by default all ser-
 vices and all parameters), formatted as "service/type/parame-
 ter=value", one per line. Specify -Pf to fold long lines.

 Specify multiple -P options to also list service parameters that
 are not set in <a href="master.5.html">master.cf</a>. This is useful with -x to evaluate the
 impact of <a href="master.5.html">master.cf</a> overrides on other parameter settings.

 Specify one or more "service/type/parameter" instances on the
 <a href="postconf.1.html">postconf(1)</a> 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.

 -q Do not log warnings for deprecated or unused parameters.

 This feature is available with Postfix 3.9 and later.

 -t [template_file]
 Display the templates for text that appears at the beginning of
 delivery status notification (DSN) messages, without expanding
 $name expressions.

 To override the <a href="postconf.5.html#bounce_template_file">bounce_template_file</a> 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.

 -T mode
 If Postfix is compiled without TLS support, the -T option pro-
 duces no output. Otherwise, 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.

 -v Enable verbose logging for debugging purposes. Multiple -v
 options make the software increasingly verbose.

 -x Expand $name in <a href="postconf.5.html">main.cf</a> or <a href="master.5.html">master.cf</a> parameter values. The
 expansion is recursive.

 This feature is available with Postfix 2.10 and later.

 -X Edit the <a href="postconf.5.html">main.cf</a> configuration file, and remove the parameters
 named on the <a href="postconf.1.html">postconf(1)</a> command line. Specify a list of param-
 eter names, not "name=value" pairs.

 With -M, edit the <a href="master.5.html">master.cf</a> configuration file, and remove one
 or more service entries as specified with "service/type" on the
 <a href="postconf.1.html">postconf(1)</a> command line.

 With -P, edit the <a href="master.5.html">master.cf</a> configuration file, and remove one
 or more service parameter settings (-o parameter=value settings)
 as specified with "service/type/parameter" on the <a href="postconf.1.html">postconf(1)</a>
 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
 <a href="postconf.1.html">postconf(1)</a> command line.

 There is no <a href="postconf.1.html">postconf(1)</a> command to perform the reverse opera-
 tion.

 This feature is available with Postfix 2.10 and later. Support
 for -M and -P was added with Postfix 2.11.

 -# Edit the <a href="postconf.5.html">main.cf</a> configuration file, and comment out the parame-
 ters named on the <a href="postconf.1.html">postconf(1)</a> command line, so that those param-
 eters revert to their default values. Specify a list of parame-
 ter names, not "name=value" pairs.

 With -M, edit the <a href="master.5.html">master.cf</a> configuration file, and comment out
 one or more service entries as specified with "service/type" on
 the <a href="postconf.1.html">postconf(1)</a> 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
 <a href="postconf.1.html">postconf(1)</a> command line.

 There is no <a href="postconf.1.html">postconf(1)</a> command to perform the reverse opera-
 tion.

 This feature is available with Postfix 2.6 and later. Support
 for -M was added with Postfix 2.11.

<a name="diagnostics">DIAGNOSTICS</a>
 Problems are reported to the standard error stream.

<a name="environment">ENVIRONMENT</a>
 MAIL_CONFIG
 Directory with Postfix configuration files.

<a name="configuration_parameters">CONFIGURATION PARAMETERS</a>
 The following <a href="postconf.5.html">main.cf</a> parameters are especially relevant to this pro-
 gram.

 The text below provides only a parameter summary. See <a href="postconf.5.html">postconf(5)</a> for
 more details including examples.

 <a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)
 The default location of the Postfix <a href="postconf.5.html">main.cf</a> and <a href="master.5.html">master.cf</a> con-
 figuration files.

 <a href="postconf.5.html#bounce_template_file">bounce_template_file</a> (empty)
 Pathname of a configuration file with bounce message templates.

<a name="files">FILES</a>
 /etc/postfix/<a href="postconf.5.html">main.cf</a>, Postfix configuration parameters
 /etc/postfix/<a href="master.5.html">master.cf</a>, Postfix master daemon configuration

<a name="see_also">SEE ALSO</a>
 <a href="bounce.5.html">bounce(5)</a>, bounce template file format
 <a href="master.5.html">master(5)</a>, <a href="master.5.html">master.cf</a> configuration file syntax
 <a href="postconf.5.html">postconf(5)</a>, <a href="postconf.5.html">main.cf</a> configuration file syntax

<a name="readme_files">README FILES</a>
 <a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview

<a name="license">LICENSE</a>
 The Secure Mailer license must be distributed with this software.

AUTHOR(S)
 Wietse Venema
 IBM T.J. Watson Research
 P.O. Box 704
 Yorktown Heights, NY 10598, USA

 Wietse Venema
 Google, Inc.
 111 8th Avenue
 New York, NY 10011, USA

 POSTCONF(1)
</pre> </body> </html>

Messung V0.5 in Prozent

¤ Dauer der Verarbeitung: 0.20 Sekunden (vorverarbeitet am 2026-08-10) ¤

Wurzel

Suchen

PVS Prover

Isabelle Prover

NIST Cobol Testsuite

Cephes Mathematical Library

Vienna Development Method

Haftungshinweis

Die Informationen auf dieser Webseite wurden nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit, noch Qualität der bereit gestellten Informationen zugesichert.

Bemerkung:

Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.