Manual browser: postconf(1)
|POSTCONF(1)||General Commands Manual||POSTCONF(1)|
NAMEpostconf - Postfix configuration utility
By default, the postconf(1) command displays the values of main.cf configuration parameters, and warns about possible mis-typed parameter names (Postfix 2.9 and later). It can also change main.cf configuration parameter values, or display other configuration information about the Postfix mail system.
- List the available SASL server plug-in types. The SASL plug-in type is selected with the smtpd_sasl_type configuration parameter by specifying one of the names listed below.
- This server plug-in is available when Postfix is built with Cyrus SASL support.
- 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.
- List the available SASL client plug-in types. The SASL plug-in type is selected with the smtp_sasl_type or lmtp_sasl_type configuration parameters by specifying one of the names listed below.
- 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 delivery status notification (DSN) messages, replacing $ name expressions with actual values as described in bounce(5).
- -c config_dir
- The main.cf configuration file is in the named directory instead of the default configuration directory.
- -C class,...
- When displaying main.cf parameters, select only parameters from the specified class(es):
- Parameters with built-in names.
- Parameters with service-defined names (the first field of a master.cf entry plus a Postfix-defined suffix).
- Parameters with user-defined names.
- All the above classes.
The default is as if "-C all" is specified.
- Print main.cf default parameter settings instead of actual settings. Specify -df to fold long lines for human readability (Postfix 2.9 and later).
Edit the main.cf configuration file, and update parameter settings with the " name=value" pairs on the postconf(1) command line.
Fold long lines when printing main.cf or master.cf configuration file entries, for human readability.
Show master.cf per-entry field settings (by default all services and all fields), formatted as one " service/type/field=value" per line. Specify -Ff to fold long lines.
- Show parameter or attribute values without the "name = " label that normally precedes the value.
- List the names of all supported mailbox locking methods. Postfix supports the following methods:
- A kernel-based advisory locking method for local files only. This locking method is available on systems with a BSD compatible library.
- A kernel-based advisory locking method for local and remote files.
- 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 abnormal program termination.
- 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 syntax depends on the lookup table type as described in the DATABASE_README document.
- A sorted, balanced tree structure. Available on systems with support for Berkeley DB databases.
- A read-optimized structure with no support for incremental updates. Available on systems with support for CDB databases.
- A table that associates values with Classless Inter-Domain Routing (CIDR) patterns. This is described in cidr_table(5).
- An indexed file type based on hashing. Available on systems with support for DBM databases.
- The UNIX process environment array. The lookup key is the variable name. Originally implemented for testing, someone may find this useful someday.
- A table that reliably fails all requests. The lookup table name is used for logging. This table exists to simplify Postfix error tests.
- An indexed file type based on hashing. Available on systems with support for Berkeley DB databases.
- A non-shared, in-memory hash table. Its content are lost when a process terminates.
- OpenLDAP LMDB database (a memory-mapped, persistent file). Available on systems with support for LMDB databases. This is described in lmdb_table(5).
- ldap (read-only)
- LDAP database client. This is described in ldap_table(5).
- Memcache database client. This is described in memcache_table(5).
- mysql (read-only)
- MySQL database client. Available on systems with support for MySQL databases. This is described in mysql_table(5).
- pcre (read-only)
- A lookup table based on Perl Compatible Regular Expressions. The file format is described in pcre_table(5).
- pgsql (read-only)
- PostgreSQL database client. This is described in pgsql_table(5).
- Postfix proxymap(8) client for shared access to Postfix databases. The table name syntax is type:name.
- regexp (read-only)
- A lookup table based on regular expressions. The file format is described in regexp_table(5).
- An indexed file type based on hashing. Available on systems with support for SDBM databases.
- 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 described in socketmap_table(5).
- sqlite (read-only)
- SQLite database. This is described in sqlite_table(5).
- static (read-only)
- A table that always returns its name as lookup result. For example, static:foobar always returns the string foobar as lookup result.
- tcp (read-only)
- TCP/IP client. The protocol is described in tcp_table(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.
- unix (read-only)
A limited view of the UNIX authentication database. The following tables are implemented:
- The table is the UNIX password database. The key is a login name. The result is a password file entry in passwd(5) format.
- 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.
Show master.cf file contents instead of main.cf file contents. Specify -Mf to fold long lines for human readability.
- Show only configuration parameters that have explicit name=value settings in main.cf. Specify -nf to fold long lines for human readability (Postfix 2.9 and later).
- -o name=value
Override main.cf parameter settings.
Show main.cf parameter settings. This is the default.
Show master.cf service parameter settings (by default all services and all parameters). formatted as one " service/type/parameter=value" per line. Specify -Pf to fold long lines.
- -t [template_file]
Display the templates for text that appears at the beginning of delivery status notification (DSN) messages, without expanding $ name expressions.
- Enable verbose logging for debugging purposes. Multiple -v options make the software increasingly verbose.
Expand $name in main.cf or master.cf parameter values. The expansion is recursive.
Edit the main.cf configuration file, and remove the parameters named on the postconf(1) command line. Specify a list of parameter names, not " name=value" pairs.
Edit the main.cf configuration file, and comment out the parameters named on the postconf(1) command line, so that those parameters revert to their default values. Specify a list of parameter names, not " name=value" pairs.
Problems are reported to the standard error stream.
- Directory with Postfix configuration files.
The following main.cf parameters are especially relevant to this program.
- config_directory (see 'postconf -d' output)
- The default location of the Postfix main.cf and master.cf configuration files.
- bounce_template_file (empty)
- Pathname of a configuration file with bounce message templates.
/etc/postfix/main.cf, Postfix configuration parameters
/etc/postfix/master.cf, Postfix master daemon configuration
bounce(5), bounce template file format master(5), master.cf
configuration file syntax postconf(5), main.cf configuration
Use "postconf readme_directory" or "postconf html_directory" to locate this information.
DATABASE_README, Postfix lookup table overview
The Secure Mailer license must be distributed with this software.
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA