« back to all changes in this revision
Viewing changes to html/postconf.1.html
- browse files at revision 20
- compare with another revision
- compare with revision 20
- download diff
- download tarball
- view history from revision 20
- Committer: Bazaar Package Importer
- Author(s): Tollef Fog Heen
- Date: 2006-11-27 09:09:56 UTC
- Revision ID: james.westby@ubuntu.com-20061127090956-154brf16pz0kler2
Tags: 2.3.4-1ubuntu1
Remove cdb support as cdb isn't in main in Ubuntu.
added
removed
html/postconf.1.html
19
19
<b>postconf</b> [<b>-btv</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<i>template</i><b>_</b><i>file</i>]
20
20
21
21
<b>DESCRIPTION</b>
22
The <a href="postconf.1.html"><b>postconf</b>(1)</a> command displays the actual values of con-
22
The <a href="postconf.1.html"><b>postconf</b>(1)</a> command displays the actual values of con‐
23
23
figuration parameters, changes configuration parameter
24
24
values, or displays other configuration information about
25
25
the Postfix mail system.
28
28
29
29
<b>-a</b> List the available SASL server plug-in types. The
30
30
SASL plug-in type is selected with the
31
<b><a href="postconf.5.html#smtpd_sasl_type">smtpd_sasl_type</a></b> configuration parameter by specify-
31
<b><a href="postconf.5.html#smtpd_sasl_type">smtpd_sasl_type</a></b> configuration parameter by specify‐
32
32
ing one of the names listed below.
33
33
34
<b>cyrus</b> This server plug-in is available when Post-
34
<b>cyrus</b> This server plug-in is available when Post‐
35
35
fix is built with Cyrus SASL support.
36
36
37
37
<b>dovecot</b>
47
47
parameters by specifying one of the names listed
48
48
below.
49
49
50
<b>cyrus</b> This client plug-in is available when Post-
50
<b>cyrus</b> This client plug-in is available when Post‐
51
51
fix is built with Cyrus SASL support.
52
52
53
53
This feature is available with Postfix 2.3 and
54
54
later.
55
55
56
56
<b>-b</b> [<i>template</i><b>_</b><i>file</i>]
57
Display the message text that appears at the begin-
58
ning of delivery status notification (DSN) mes-
57
Display the message text that appears at the begin‐
58
ning of delivery status notification (DSN) mes‐
59
59
sages, with $<b>name</b> expressions replaced by actual
60
60
values. To override the built-in message text,
61
61
specify a template file at the end of the command
62
62
line, or specify a template file in <a href="postconf.5.html">main.cf</a> with
63
63
the <b><a href="postconf.5.html#bounce_template_file">bounce_template_file</a></b> parameter. To force
64
64
selection of the built-in message text templates,
65
specify an empty template file name (in shell lan-
65
specify an empty template file name (in shell lan‐
66
66
guage: "").
67
67
68
68
This feature is available with Postfix 2.3 and
82
82
line. Use quotes in order to protect shell
83
83
metacharacters and whitespace.
84
84
85
<b>-h</b> Show parameter values only, not the ``name = ''
85
<b>-h</b> Show parameter values only, not the ‘‘name = ’’
86
86
label that normally precedes the value.
87
87
88
88
<b>-l</b> List the names of all supported mailbox locking
108
108
In Postfix configuration files, lookup tables are
109
109
specified as <i>type</i><b>:</b><i>name</i>, where <i>type</i> is one of the
110
110
types listed below. The table <i>name</i> syntax depends
111
on the lookup table type as described in the <a href="DATABASE_README.html">DATA</a>-
112
<a href="DATABASE_README.html">BASE_README</a> document.
111
on the lookup table type as described in the
112
<a href="DATABASE_README.html">DATABASE_README</a> document.
113
113
114
114
<b>btree</b> A sorted, balanced tree structure. This is
115
available on systems with support for Berke-
115
available on systems with support for Berke‐
116
116
ley DB databases.
117
117
118
118
<b>cdb</b> A read-optimized structure with no support
119
119
for incremental updates. This is available
120
120
on systems with support for CDB databases.
121
121
122
<b>cidr</b> A table that associates values with Class-
122
<b>cidr</b> A table that associates values with Class‐
123
123
less Inter-Domain Routing (CIDR) patterns.
124
124
This is described in <a href="cidr_table.5.html"><b>cidr_table</b>(5)</a>.
125
125
146
146
This is described in <a href="mysql_table.5.html"><b>mysql_table</b>(5)</a>.
147
147
148
148
<b>pcre</b> (read-only)
149
A lookup table based on Perl Compatible Reg-
149
A lookup table based on Perl Compatible Reg‐
150
150
ular Expressions. The file format is
151
151
described in <a href="pcre_table.5.html"><b>pcre_table</b>(5)</a>.
152
152
153
153
<b>pgsql</b> (read-only)
154
Perform lookups using the PostgreSQL proto-
154
Perform lookups using the PostgreSQL proto‐
155
155
col. This is described in <a href="pgsql_table.5.html"><b>pgsql_table</b>(5)</a>.
156
156
157
157
<b>proxy</b> (read-only)
161
161
162
162
<b>regexp</b> (read-only)
163
163
A lookup table based on regular expressions.
164
The file format is described in <a href="regexp_table.5.html"><b>regexp_ta-</b></a>
165
<a href="regexp_table.5.html"><b>ble</b>(5)</a>.
164
The file format is described in <b>regexp_ta‐</b>
165
<b>ble</b>(5).
166
166
167
167
<b>sdbm</b> An indexed file type based on hashing. This
168
168
is available on systems with support for
181
181
2.2.
182
182
183
183
<b>unix</b> (read-only)
184
A limited way to query the UNIX authentica-
184
A limited way to query the UNIX authentica‐
185
185
tion database. The following tables are
186
186
implemented:
187
187
188
188
<b>unix:passwd.byname</b>
189
The table is the UNIX password data-
190
base. The key is a login name. The
191
result is a password file entry in
192
<b>passwd</b>(5) format.
189
The table is the UNIX password
190
database. The key is a login name.
191
The result is a password file entry
192
in <b>passwd</b>(5) format.
193
193
194
194
<b>unix:group.byname</b>
195
The table is the UNIX group database.
196
The key is a group name. The result
197
is a group file entry in <b>group</b>(5)
198
format.
195
The table is the UNIX group
196
database. The key is a group name.
197
The result is a group file entry in
198
<b>group</b>(5) format.
199
199
200
Other table types may exist depending on how Post-
200
Other table types may exist depending on how Post‐
201
201
fix was built.
202
202
203
203
<b>-n</b> Print parameter settings that are not left at their
205
205
specified in <a href="postconf.5.html">main.cf</a>.
206
206
207
207
<b>-t</b> [<i>template</i><b>_</b><i>file</i>]
208
Display the templates for delivery status notifica-
209
tion (DSN) messages. To override the built-in tem-
208
Display the templates for delivery status notifica‐
209
tion (DSN) messages. To override the built-in tem‐
210
210
plates, specify a template file at the end of the
211
211
command line, or specify a template file in <a href="postconf.5.html">main.cf</a>
212
212
with the <b><a href="postconf.5.html#bounce_template_file">bounce_template_file</a></b> parameter. To force
216
216
This feature is available with Postfix 2.3 and
217
217
later.
218
218
219
<b>-v</b> Enable verbose logging for debugging purposes. Mul-
219
<b>-v</b> Enable verbose logging for debugging purposes. Mul‐
220
220
tiple <b>-v</b> options make the software increasingly
221
221
verbose.
222
222
234
234
The text below provides only a parameter summary. See
235
235
<a href="postconf.5.html"><b>postconf</b>(5)</a> for more details including examples.
236
236
237
<b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b>
237
<b><a href="postconf.5.html#config_directory">config_directory</a> (see ’postconf -d’ output)</b>
238
238
The default location of the Postfix <a href="postconf.5.html">main.cf</a> and
239
239
<a href="master.5.html">master.cf</a> configuration files.
240
240
241
241
<b><a href="postconf.5.html#bounce_template_file">bounce_template_file</a> (empty)</b>
242
Pathname of a configuration file with bounce mes-
242
Pathname of a configuration file with bounce mes‐
243
243
sage templates.
244
244
245
245
<b>FILES</b>
Loggerhead is a web-based interface for Breezy
Version: 2.0.1