1POSTCONF(1) General Commands Manual POSTCONF(1)
2
6 postconf - Postfix configuration utility
7
9 postconf [-dhnv] [-c config_dir] [parameter ...]
10 postconf [-aAmlv] [-c config_dir]
12 postconf [-ev] [-c config_dir] [parameter=value ...]
14 postconf [-btv] [-c config_dir] [template_file]
16
18 The postconf(1) command displays the actual values of configuration
19 parameters, changes configuration parameter values, or displays other
20 configuration information about the Postfix mail system.
21 Options:
23 -a List the available SASL server plug-in types. The SASL plug-in
25 type is selected with the smtpd_sasl_type configuration parame‐
26 ter by specifying one of the names listed below.
27 cyrus This server plug-in is available when Postfix is built
29 with Cyrus SASL support.
30 dovecot
32 This server plug-in requires the Dovecot authentication
33 server.
34 This feature is available with Postfix 2.3 and later.
36 -A List the available SASL client plug-in types. The SASL plug-in
38 type is selected with the smtp_sasl_type or lmtp_sasl_type con‐
39 figuration parameters by specifying one of the names listed
40 below.
41 cyrus This client plug-in is available when Postfix is built
43 with Cyrus SASL support.
44 This feature is available with Postfix 2.3 and later.
46 -b [template_file]
48 Display the message text that appears at the beginning of deliv‐
49 ery status notification (DSN) messages, with $name expressions
50 replaced by actual values. To override the built-in message
51 text, specify a template file at the end of the command line, or
52 specify a template file in main.cf with the bounce_template_file
53 parameter. To force selection of the built-in message text tem‐
54 plates, specify an empty template file name (in shell language:
55 "").
56 This feature is available with Postfix 2.3 and later.
58 -c config_dir
60 The main.cf configuration file is in the named directory instead
61 of the default configuration directory.
62 -d Print default parameter settings instead of actual settings.
64 -e Edit the main.cf configuration file. The file is copied to a
66 temporary file then renamed into place. Parameters and values
67 are specified on the command line. Use quotes in order to pro‐
68 tect shell metacharacters and whitespace.
69 -h Show parameter values only, not the ``name = '' label that nor‐
71 mally precedes the value.
72 -l List the names of all supported mailbox locking methods. Post‐
74 fix supports the following methods:
75 flock A kernel-based advisory locking method for local files
77 only. This locking method is available on systems with a
78 BSD compatible library.
79 fcntl A kernel-based advisory locking method for local and
81 remote files.
82 dotlock
84 An application-level locking method. An application locks
85 a file named filename by creating a file named file‐
86 name.lock. The application is expected to remove its own
87 lock file, as well as stale lock files that were left
88 behind after abnormal termination.
89 -m List the names of all supported lookup table types. In Postfix
91 configuration files, lookup tables are specified as type:name,
92 where type is one of the types listed below. The table name syn‐
93 tax depends on the lookup table type as described in the DATA‐
94 BASE_README document.
95 btree A sorted, balanced tree structure. This is available on
97 systems with support for Berkeley DB databases.
98 cdb A read-optimized structure with no support for incremen‐
100 tal updates. This is available on systems with support
101 for CDB databases.
102 cidr A table that associates values with Classless Inter-
104 Domain Routing (CIDR) patterns. This is described in
105 cidr_table(5).
106 dbm An indexed file type based on hashing. This is available
108 on systems with support for DBM databases.
109 environ
111 The UNIX process environment array. The lookup key is the
112 variable name. Originally implemented for testing, some‐
113 one may find this useful someday.
114 hash An indexed file type based on hashing. This is available
116 on systems with support for Berkeley DB databases.
117 ldap (read-only)
119 Perform lookups using the LDAP protocol. This is
120 described in ldap_table(5).
121 mysql (read-only)
123 Perform lookups using the MYSQL protocol. This is
124 described in mysql_table(5).
125 pcre (read-only)
127 A lookup table based on Perl Compatible Regular Expres‐
128 sions. The file format is described in pcre_table(5).
129 pgsql (read-only)
131 Perform lookups using the PostgreSQL protocol. This is
132 described in pgsql_table(5).
133 proxy (read-only)
135 A lookup table that is implemented via the Postfix prox‐
136 ymap(8) service. The table name syntax is type:name.
137 regexp (read-only)
139 A lookup table based on regular expressions. The file
140 format is described in regexp_table(5).
141 sdbm An indexed file type based on hashing. This is available
143 on systems with support for SDBM databases.
144 static (read-only)
146 A table that always returns its name as lookup result.
147 For example, static:foobar always returns the string foo‐
148 bar as lookup result.
149 tcp (read-only)
151 Perform lookups using a simple request-reply protocol
152 that is described in tcp_table(5). This feature is not
153 included with the stable Postfix release.
154 unix (read-only)
156 A limited way to query the UNIX authentication database.
157 The following tables are implemented:
158 unix:passwd.byname
160 The table is the UNIX password database. The key
161 is a login name. The result is a password file
162 entry in passwd(5) format.
163 unix:group.byname
165 The table is the UNIX group database. The key is a
166 group name. The result is a group file entry in
167 group(5) format.
168 Other table types may exist depending on how Postfix was built.
170 -n Print parameter settings that are not left at their built-in
172 default value, because they are explicitly specified in main.cf.
173 -t [template_file]
175 Display the templates for delivery status notification (DSN)
176 messages. To override the built-in templates, specify a template
177 file at the end of the command line, or specify a template file
178 in main.cf with the bounce_template_file parameter. To force
179 selection of the built-in templates, specify an empty template
180 file name (in shell language: "").
181 This feature is available with Postfix 2.3 and later.
183 -v Enable verbose logging for debugging purposes. Multiple -v
185 options make the software increasingly verbose.
186
188 Problems are reported to the standard error stream.
189
191 MAIL_CONFIG
192 Directory with Postfix configuration files.
193
195 The following main.cf parameters are especially relevant to this pro‐
196 gram.
197 The text below provides only a parameter summary. See postconf(5) for
199 more details including examples.
200 config_directory (see 'postconf -d' output)
202 The default location of the Postfix main.cf and master.cf con‐
203 figuration files.
204 bounce_template_file (empty)
206 Pathname of a configuration file with bounce message templates.
207
209 /etc/postfix/main.cf, Postfix configuration parameters
210
212 bounce(5), bounce template file format
213 postconf(5), configuration parameters
214
216 Use "postconf readme_directory" or "postconf html_directory" to locate
217 this information.
218 DATABASE_README, Postfix lookup table overview
219
221 The Secure Mailer license must be distributed with this software.
222
224 Wietse Venema
225 IBM T.J. Watson Research
226 P.O. Box 704
227 Yorktown Heights, NY 10598, USA
228 POSTCONF(1)