POSTCONF(1) POSTCONF(1)
NAME
postconf - Postfix configuration utility
SYNOPSIS
postconf [-dhnv] [-c config_dir] [parameter ...]
postconf [-aAmlv] [-c config_dir]
postconf [-ev] [-c config_dir] [parameter=value ...]
postconf [-#v] [-c config_dir] [parameter ...]
postconf [-btv] [-c config_dir] [template_file]
DESCRIPTION
The postconf(1) command displays the actual values of con-
figuration parameters, changes configuration parameter
values, or displays other configuration information about
the Postfix mail system.
Options:
-a List the available SASL server plug-in types. The
SASL plug-in type is selected with the
smtpd_sasl_type configuration parameter by specify-
ing one of the names listed below.
cyrus This server plug-in is available when Post-
fix is built with Cyrus SASL support.
dovecot
This server plug-in uses the Dovecot authen-
tication server, and is available when Post-
fix is built with any form of SASL support.
This feature is available with Postfix 2.3 and
later.
-A 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.
cyrus This client plug-in is available when Post-
fix 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 begin-
ning of delivery status notification (DSN) mes-
sages, with $name expressions replaced by actual
values. To override the built-in message text,
specify a template file at the end of the command
line, or specify a template file in main.cf with
the bounce_template_file parameter. To force
selection of the built-in message text templates,
specify an empty template file name (in shell lan-
guage: "").
This feature is available with Postfix 2.3 and
later.
-c config_dir
The main.cf configuration file is in the named
directory instead of the default configuration
directory.
-d Print default parameter settings instead of actual
settings.
-e Edit the main.cf configuration file. The file is
copied to a temporary file then renamed into place.
Parameters and values are specified on the command
line. Use quotes in order to protect shell
metacharacters and whitespace.
-h Show parameter values only, not the ``name = ''
label that normally precedes the value.
-l List the names of all supported mailbox locking
methods. Postfix 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 filename.lock. The
application is expected to remove its own
lock file, as well as stale lock files that
were left behind after abnormal 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 syntax depends
on the lookup table type as described in the DATA-
BASE_README document.
btree A sorted, balanced tree structure. This is
available on systems with support for Berke-
ley DB databases.
cdb A read-optimized structure with no support
for incremental updates. This is available
on systems with support for CDB databases.
cidr A table that associates values with Class-
less Inter-Domain Routing (CIDR) patterns.
This is described in cidr_table(5).
dbm An indexed file type based on hashing. This
is available on systems with support for DBM
databases.
environ
The UNIX process environment array. The
lookup key is the variable name. Originally
implemented for testing, someone may find
this useful someday.
hash An indexed file type based on hashing. This
is available on systems with support for
Berkeley DB databases.
ldap (read-only)
Perform lookups using the LDAP protocol.
This is described in ldap_table(5).
mysql (read-only)
Perform lookups using the MYSQL protocol.
This is described in mysql_table(5).
pcre (read-only)
A lookup table based on Perl Compatible Reg-
ular Expressions. The file format is
described in pcre_table(5).
pgsql (read-only)
Perform lookups using the PostgreSQL proto-
col. This is described in pgsql_table(5).
proxy (read-only)
A lookup table that is implemented via the
Postfix proxymap(8) service. The table name
syntax is type:name.
regexp (read-only)
A lookup table based on regular expressions.
The file format is described in regexp_ta-
ble(5).
sdbm An indexed file type based on hashing. This
is available on systems with support for
SDBM databases.
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)
Perform lookups using a simple request-reply
protocol that is described in tcp_table(5).
This feature is not included with the stable
Postfix release.
unix (read-only)
A limited way to query the UNIX authentica-
tion database. The following tables are
implemented:
unix:passwd.byname
The table is the UNIX password data-
base. 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 Post-
fix was built.
-n Print parameter settings that are not left at their
built-in default value, because they are explicitly
specified in main.cf.
-t [template_file]
Display the templates for delivery status notifica-
tion (DSN) messages. To override the built-in tem-
plates, specify a template file at the end of the
command line, or specify a template file in main.cf
with the bounce_template_file parameter. To force
selection of the built-in templates, specify an
empty template file name (in shell language: "").
This feature is available with Postfix 2.3 and
later.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
-# Edit the main.cf configuration file. The file is
copied to a temporary file then renamed into place.
The parameters specified on the command line are
commented-out, so that they revert to their default
values. Specify a list of parameter names, not
name=value pairs. There is no postconf command to
perform the reverse operation.
This feature is available with Postfix 2.6 and
later.
DIAGNOSTICS
Problems are reported to the standard error stream.
ENVIRONMENT
MAIL_CONFIG
Directory with Postfix configuration files.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program.
The text below provides only a parameter summary. See
postconf(5) for more details including examples.
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 mes-
sage templates.
FILES
/etc/postfix/main.cf, Postfix configuration parameters
SEE ALSO
bounce(5), bounce template file format
postconf(5), configuration parameters
README FILES
DATABASE_README, Postfix lookup table overview
LICENSE
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
POSTCONF(1)
@
1.1.1.1
log
@Import Postfix 2.6.2.
@
text
@@
1.1.1.2
log
@Import Postfix 2.7.1. Major changes since Postfix 2.6.6:
- Improved before-queue content filter performance. With
"smtpd_proxy_options = speed_adjust", the Postfix SMTP server
receives the entire message before it connects to a before-queue
content filter. Typically, this allows Postfix to handle the same
mail load with fewer content filter processes.
- Improved address verification performance. The verify database is now
persistent by default, and it is automatically cleaned periodically. Under
overload conditions, the Postfix SMTP server no longer waits up to 6 seconds
for an address probe to complete.
- Support for reputation management based on the local SMTP client IP address.
This is typically implemented with "FILTER transportname:" actions in access
maps or header/body checks, and mail delivery transports in master.cf with
unique smtp_bind_address values.
@
text
@a142 4
internal
A non-shared, in-memory hash table. Its con-
tent are lost when a process terminates.
d144 1
a144 1
Perform lookups using the LDAP protocol.
d148 1
a148 1
Perform lookups using the MYSQL protocol.
d153 1
a153 1
ular Expressions. The file format is
d157 1
a157 1
Perform lookups using the PostgreSQL proto-
d161 2
a162 2
A lookup table that is implemented via the
Postfix proxymap(8) service. The table name
d167 1
a167 1
The file format is described in regexp_ta-
d171 1
a171 1
is available on systems with support for
d175 3
a177 3
A table that always returns its name as
lookup result. For example, static:foobar
always returns the string foobar as lookup
d182 1
a182 1
protocol that is described in tcp_table(5).
d187 1
a187 1
A limited way to query the UNIX authentica-
d192 3
a194 3
The table is the UNIX password data-
base. The key is a login name. The
result is a password file entry in
d199 2
a200 2
The key is a group name. The result
is a group file entry in group(5)
d203 1
a203 1
Other table types may exist depending on how Post-
d212 2
a213 2
tion (DSN) messages. To override the built-in tem-
plates, specify a template file at the end of the
d215 2
a216 2
with the bounce_template_file parameter. To force
selection of the built-in templates, specify an
d219 1
a219 1
This feature is available with Postfix 2.3 and
d223 1
a223 1
tiple -v options make the software increasingly
d226 1
a226 1
-# Edit the main.cf configuration file. The file is
d228 1
a228 1
The parameters specified on the command line are
d230 2
a231 2
values. Specify a list of parameter names, not
name=value pairs. There is no postconf command to
d234 1
a234 1
This feature is available with Postfix 2.6 and
d245 1
a245 1
The following main.cf parameters are especially relevant
d248 1
a248 1
The text below provides only a parameter summary. See
d252 1
a252 1
The default location of the Postfix main.cf and
d256 1
a256 1
Pathname of a configuration file with bounce mes-
d270 1
a270 1
The Secure Mailer license must be distributed with this
@
1.1.1.2.2.1
log
@Sync with HEAD
@
text
@d88 2
a89 2
With Postfix version 2.8 and later, the -e is no
longer needed.
d91 1
a91 4
-h Show parameter values only, not the "name = " label
that normally precedes the value.
-l List the names of all supported mailbox locking
d94 3
a96 3
flock A kernel-based advisory locking method for
local files only. This locking method is
available on systems with a BSD compatible
d99 1
a99 1
fcntl A kernel-based advisory locking method for
d103 5
a107 5
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
d111 4
a114 4
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 DATA-
d117 1
a117 1
btree A sorted, balanced tree structure. This is
d121 2
a122 2
cdb A read-optimized structure with no support
for incremental updates. This is available
d125 2
a126 2
cidr A table that associates values with Class-
less Inter-Domain Routing (CIDR) patterns.
d135 2
a136 2
lookup key is the variable name. Originally
implemented for testing, someone may find
d140 1
a140 1
is available on systems with support for
d148 1
a148 1
Perform lookups using the LDAP protocol.
d152 1
a152 1
Perform lookups using the MYSQL protocol.
d157 1
a157 1
ular Expressions. The file format is
d161 1
a161 1
Perform lookups using the PostgreSQL proto-
d165 2
a166 2
A lookup table that is implemented via the
Postfix proxymap(8) service. The table name
d171 1
a171 1
The file format is described in regexp_ta-
d175 1
a175 1
is available on systems with support for
a177 4
sqlite (read-only)
Perform lookups from SQLite database files.
This is described in sqlite_table(5).
d187 2
a188 7
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.
d191 1
a191 1
A limited way to query the UNIX authentica-
d196 3
a198 3
The table is the UNIX password data-
base. The key is a login name. The
result is a password file entry in
d203 2
a204 2
The key is a group name. The result
is a group file entry in group(5)
d207 1
a207 1
Other table types may exist depending on how Post-
d216 2
a217 2
tion (DSN) messages. To override the built-in tem-
plates, specify a template file at the end of the
d219 2
a220 2
with the bounce_template_file parameter. To force
selection of the built-in templates, specify an
d223 1
a223 1
This feature is available with Postfix 2.3 and
d227 1
a227 1
tiple -v options make the software increasingly
d230 1
a230 1
-# Edit the main.cf configuration file. The file is
d232 1
a232 1
The parameters specified on the command line are
d234 2
a235 2
values. Specify a list of parameter names, not
name=value pairs. There is no postconf command to
d238 1
a238 1
This feature is available with Postfix 2.6 and
d249 1
a249 1
The following main.cf parameters are especially relevant
d252 1
a252 1
The text below provides only a parameter summary. See
d256 1
a256 1
The default location of the Postfix main.cf and
d260 1
a260 1
Pathname of a configuration file with bounce mes-
d274 1
a274 1
The Secure Mailer license must be distributed with this
@
1.1.1.3
log
@Import Postfix 2.8.1. Changes since version 2.7.*:
Postfix stable release 2.8.0 is available. This release continues the
move towards improving code and documentation, and making the system
better prepared for changes in the threat environment.
The postscreen daemon (a zombie blocker in front of Postfix) is now
included with the stable release. postscreen now supports TLS and can
log the rejected sender, recipient and helo information. See the
POSTSCREEN_README file for recommended usage scenarios.
Support for DNS whitelisting (permit_rhswl_client), and for pattern
matching to filter the responses from DNS white/blacklist servers
(e.g., reject_rhsbl_client zen.spamhaus.org=127.0.0.[1..10]).
Improved message tracking across SMTP-based content filters; the
after-filter SMTP server can log the before-filter queue ID (the
XCLIENT protocol was extended).
Read-only support for sqlite databases. See sqlite_table(5) and
SQLITE_README.
Support for 'footers' that are appended to SMTP server "reject"
responses. See "smtpd_reject_footer" in the postconf(5) manpage.
@
text
@d88 2
a89 2
With Postfix version 2.8 and later, the -e is no
longer needed.
d91 1
a91 4
-h Show parameter values only, not the "name = " label
that normally precedes the value.
-l List the names of all supported mailbox locking
d94 3
a96 3
flock A kernel-based advisory locking method for
local files only. This locking method is
available on systems with a BSD compatible
d99 1
a99 1
fcntl A kernel-based advisory locking method for
d103 5
a107 5
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
d111 4
a114 4
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 DATA-
d117 1
a117 1
btree A sorted, balanced tree structure. This is
d121 2
a122 2
cdb A read-optimized structure with no support
for incremental updates. This is available
d125 2
a126 2
cidr A table that associates values with Class-
less Inter-Domain Routing (CIDR) patterns.
d135 2
a136 2
lookup key is the variable name. Originally
implemented for testing, someone may find
d140 1
a140 1
is available on systems with support for
d148 1
a148 1
Perform lookups using the LDAP protocol.
d152 1
a152 1
Perform lookups using the MYSQL protocol.
d157 1
a157 1
ular Expressions. The file format is
d161 1
a161 1
Perform lookups using the PostgreSQL proto-
d165 2
a166 2
A lookup table that is implemented via the
Postfix proxymap(8) service. The table name
d171 1
a171 1
The file format is described in regexp_ta-
d175 1
a175 1
is available on systems with support for
a177 4
sqlite (read-only)
Perform lookups from SQLite database files.
This is described in sqlite_table(5).
d187 2
a188 7
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.
d191 1
a191 1
A limited way to query the UNIX authentica-
d196 3
a198 3
The table is the UNIX password data-
base. The key is a login name. The
result is a password file entry in
d203 2
a204 2
The key is a group name. The result
is a group file entry in group(5)
d207 1
a207 1
Other table types may exist depending on how Post-
d216 2
a217 2
tion (DSN) messages. To override the built-in tem-
plates, specify a template file at the end of the
d219 2
a220 2
with the bounce_template_file parameter. To force
selection of the built-in templates, specify an
d223 1
a223 1
This feature is available with Postfix 2.3 and
d227 1
a227 1
tiple -v options make the software increasingly
d230 1
a230 1
-# Edit the main.cf configuration file. The file is
d232 1
a232 1
The parameters specified on the command line are
d234 2
a235 2
values. Specify a list of parameter names, not
name=value pairs. There is no postconf command to
d238 1
a238 1
This feature is available with Postfix 2.6 and
d249 1
a249 1
The following main.cf parameters are especially relevant
d252 1
a252 1
The text below provides only a parameter summary. See
d256 1
a256 1
The default location of the Postfix main.cf and
d260 1
a260 1
Pathname of a configuration file with bounce mes-
d274 1
a274 1
The Secure Mailer license must be distributed with this
@
1.1.1.4
log
@Import Postfix 2.8.3:
Postfix releases 2.8.3, 2.7.4, 2.6.10 and 2.5.13 are available. These contain
a fix for CVE-2011-1720 which affects Postfix SMTP server configurations that
use Cyrus SASL authentication. Besides full releases, patches are available
for Postfix 1.1 and later.
This defect was introduced with the Postfix SASL patch, and is present in all
Postfix versions where the command "postconf mail_release_date" reports a
value of 20000314 (March 14, 2000) or greater.
Note: CVE-2011-1720 does not affect Postfix SMTP servers that use Dovecot
SASL authentication. It also does not affect the common Postfix SMTP server
configurations that use only Cyrus SASL mechanisms PLAIN and LOGIN.
More details will be available at http://www.postfix.org/CVE-2011-1720.html.
@
text
@d91 2
a92 2
-h Show parameter values only, not the "name = " label
that normally precedes the value.
@
1.1.1.4.10.1
log
@resync with head
@
text
@d13 1
a13 1
Managing main.cf:
d15 1
a15 2
postconf [-dfhnv] [-c config_dir] [-C class,...] [parame-
ter ...]
a20 6
Managing master.cf:
postconf [-fMv] [-c config_dir] [service ...]
Managing bounce message templates:
a22 4
Managing other configuration:
postconf [-aAlmv] [-c config_dir]
d24 4
a27 6
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.
d31 2
a32 2
-a List the available SASL server plug-in types. The
SASL plug-in type is selected with the
d36 1
a36 1
cyrus This server plug-in is available when Post-
d42 1
a42 1
fix is built with any form of SASL support.
d44 1
a44 1
This feature is available with Postfix 2.3 and
d47 4
a50 4
-A 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
d53 1
a53 1
cyrus This client plug-in is available when Post-
d56 1
a56 1
This feature is available with Postfix 2.3 and
d61 9
a69 12
ning of delivery status notification (DSN) mes-
sages, replacing $name expressions with actual val-
ues as described in bounce(5).
To override the built-in templates, specify a tem-
plate file name at the end of the postconf(1) com-
mand line, or specify a file name in main.cf with
the bounce_template_file parameter.
To force selection of the built-in templates, spec-
ify an empty template file name on the postconf(1)
command line (in shell language: "").
d79 2
a80 17
-C class,...
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.
d82 5
a86 3
-d Print main.cf default parameter settings instead of
actual settings. Specify -df to fold long lines
for human readability (Postfix 2.9 and later).
d88 2
a89 6
-e Edit the main.cf configuration file, and update
parameter settings with the "name=value" pairs on
the postconf(1) command line. 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.
d91 2
a92 11
The -e is no longer needed with Postfix version 2.8
and later.
-f Fold long lines when printing main.cf or master.cf
configuration file entries, for human readability.
This feature is available with Postfix 2.9 and
later.
-h Show main.cf parameter values without the "name = "
label that normally precedes the value.
a141 5
fail A table that reliably fails all requests.
The lookup table name is used for logging.
This table exists to simplify Postfix error
tests.
d143 1
a143 1
is available on systems with support for
d151 1
a151 1
Perform lookups using the LDAP protocol.
a153 4
memcache
Perform lookups using the memcache protocol.
This is described in memcache_table(5).
d167 2
a168 1
proxy A lookup table that is implemented via the
d187 1
a187 1
lookup result. For example, static:foobar
d198 1
a198 1
postmap(1) command before you can use the
d222 3
a224 21
-M Show master.cf file contents instead of main.cf
file contents. Specify -Mf to fold long lines for
human readability.
If service ... is specified, only the matching ser-
vices will be output. For example, "postconf -Mf
inet" will output all services that listen on the
network.
Specify zero or more arguments, each with a ser-
vice-type name (inet, unix, fifo, or pass) or with
a service-name.service-type pair, where service-
name is the first field of a master.cf entry.
This feature is available with Postfix 2.9 and
later.
-n Print main.cf parameter settings that are explic-
itly specified in main.cf. Specify -nf to fold
long lines for human readability (Postfix 2.9 and
later).
d227 7
a233 12
Display the templates for text that appears at the
beginning of delivery status notification (DSN)
messages, without expanding $name expressions.
To override the built-in templates, specify a tem-
plate file name at the end of the postconf(1) com-
mand line, or specify a file name in main.cf with
the bounce_template_file parameter.
To force selection of the built-in templates, spec-
ify an empty template file name on the postconf(1)
command line (in shell language: "").
d235 1
a235 1
This feature is available with Postfix 2.3 and
d239 1
a239 1
tiple -v options make the software increasingly
d242 7
a248 8
-# Edit the main.cf configuration file, and comment
out the parameters given on the postconf(1) command
line, so that those parameters revert to their
default values. The file is copied to a temporary
file then renamed into place. Specify a list of
parameter names, not name=value pairs. There is no
postconf(1) command to perform the reverse opera-
tion.
a276 1
/etc/postfix/master.cf, Postfix master daemon configuraton
d280 1
a280 2
master(5), master.cf configuration file syntax
postconf(5), main.cf configuration file syntax
@
1.1.1.4.10.2
log
@Rebase to HEAD as of a few days ago.
@
text
@d15 2
a16 1
postconf [-dfhnopvx] [-c config_dir] [-C class,...] [parameter ...]
d18 1
a18 1
postconf [-epv] [-c config_dir] parameter=value ...
d20 1
a20 1
postconf -# [-pv] [-c config_dir] parameter ...
d22 1
a22 1
postconf -X [-pv] [-c config_dir] parameter ...
d24 1
a24 23
Managing master.cf service entries:
postconf -M [-fovx] [-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 master.cf service fields:
postconf -F [-fovx] [-c config_dir] [service[/type[/field]] ...]
postconf -F [-ev] [-c config_dir] service/type/field=value ...
Managing master.cf service parameters:
postconf -P [-fovx] [-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 ...
d28 1
a28 3
postconf -b [-v] [-c config_dir] [template_file]
postconf -t [-v] [-c config_dir] [template_file]
d32 1
a32 1
postconf -a|-A|-l|-m [-v] [-c config_dir]
d35 6
a40 5
By default, the postconf(1) command displays the values of main.cf con-
figuration parameters, and warns about possible mis-typed parameter
names (Postfix 2.9 and later). It can also change main.cf configura-
tion parameter values, or display other configuration information about
the Postfix mail system.
d44 4
a47 3
-a List the available SASL server plug-in types. The SASL plug-in
type is selected with the smtpd_sasl_type configuration parame-
ter by specifying one of the names listed below.
d49 2
a50 2
cyrus This server plug-in is available when Postfix is built
with Cyrus SASL support.
d53 11
a63 9
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 client plug-in types. The SASL plug-in
type is selected with the smtp_sasl_type or lmtp_sasl_type con-
figuration parameters by specifying one of the names listed
d66 2
a67 2
cyrus This client plug-in is available when Postfix is built
with Cyrus SASL support.
d69 2
a70 1
This feature is available with Postfix 2.3 and later.
d73 13
a85 11
Display the message text that appears at the beginning of deliv-
ery status notification (DSN) messages, replacing $name expres-
sions with actual values as described in bounce(5).
To override the built-in templates, specify a template file name
at the end of the postconf(1) command line, or specify a file
name in main.cf with the bounce_template_file parameter.
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
language: "").
d87 2
a88 1
This feature is available with Postfix 2.3 and later.
d91 3
a93 2
The main.cf configuration file is in the named directory instead
of the default configuration directory.
d96 2
a97 2
When displaying main.cf parameters, select only parameters from
the specified class(es):
d103 3
a105 2
Parameters with service-defined names (the first field of
a master.cf entry plus a Postfix-defined suffix).
d113 13
a125 1
This feature is available with Postfix 2.9 and later.
d127 2
a128 28
-d Print main.cf 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 main.cf configuration file, and update parameter set-
tings with the "name=value" pairs on the postconf(1) command
line.
With -M, edit the master.cf configuration file, and replace one
or more service entries with new values as specified with "ser-
vice/type=value" on the postconf(1) command line.
With -F, edit the master.cf configuration file, and replace one
or more service fields with new values as specied with "ser-
vice/type/field=value" on the postconf(1) 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 master.cf configuration file, and add or
update one or more service parameter settings (-o parame-
ter=value settings) with new values as specied with "ser-
vice/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.
d130 1
a130 1
The -e option is no longer needed with Postfix version 2.8 and
d133 2
a134 13
-f Fold long lines when printing main.cf or master.cf configuration
file entries, for human readability.
This feature is available with Postfix 2.9 and later.
-F 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.
Specify one or more "service/type/field" instances on the post-
conf(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.
d136 2
a137 1
This feature is available with Postfix 2.11 and later.
d139 4
a142 2
-h Show parameter or attribute values without the "name = " label
that normally precedes the value.
d144 2
a145 9
-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.
d148 12
a159 10
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 DATA-
d162 11
a172 2
btree A sorted, balanced tree structure. Available on systems
with support for Berkeley DB databases.
d174 2
a175 2
cdb A read-optimized structure with no support for incremen-
tal updates. Available on systems with support for CDB
a177 7
cidr A table that associates values with Classless Inter-
Domain Routing (CIDR) patterns. This is described in
cidr_table(5).
dbm An indexed file type based on hashing. Available on sys-
tems with support for DBM databases.
d179 13
a191 10
The UNIX process environment array. The lookup key is the
variable name. Originally implemented for testing, some-
one 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.
hash An indexed file type based on hashing. Available on sys-
tems with support for Berkeley DB databases.
d194 2
a195 6
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 lmdb_table(5).
d198 2
a199 1
LDAP database client. This is described in ldap_table(5).
d202 2
a203 2
Memcache database client. This is described in mem-
cache_table(5).
d206 2
a207 3
MySQL database client. Available on systems with support
for MySQL databases. This is described in mysql_ta-
ble(5).
d210 3
a212 2
A lookup table based on Perl Compatible Regular Expres-
sions. The file format is described in pcre_table(5).
d215 2
a216 2
PostgreSQL database client. This is described in
pgsql_table(5).
d218 3
a220 2
proxy Postfix proxymap(8) client for shared access to Postfix
databases. The table name syntax is type:name.
d223 7
a229 11
A lookup table based on regular expressions. The file
format is described in regexp_table(5).
sdbm An indexed file type based on hashing. Available on sys-
tems 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:path-
name:name for a UNIX-domain server. This is described in
socketmap_table(5).
d232 2
a233 1
SQLite database. This is described in sqlite_table(5).
d236 4
a239 3
A table that always returns its name as lookup result.
For example, static:foobar always returns the string foo-
bar as lookup result.
d242 2
a243 1
TCP/IP client. The protocol is described in tcp_table(5).
d246 5
a250 4
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.
d253 3
a255 2
A limited view of the UNIX authentication database. The
following tables are implemented:
d258 4
a261 3
The table is the UNIX password database. The key
is a login name. The result is a password file
entry in passwd(5) format.
d264 21
a284 3
The table is the UNIX group database. The key is a
group name. The result is a group file entry in
group(5) format.
d286 2
a287 24
Other table types may exist depending on how Postfix was built.
-M Show master.cf file contents instead of main.cf 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 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
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 main.cf. Specify -nf to fold long lines for human
readability (Postfix 2.9 and later).
d289 4
a292 20
-o name=value
Override main.cf parameter settings.
This feature is available with Postfix 2.10 and later.
-p Show main.cf parameter settings. This is the default.
This feature is available with Postfix 2.11 and later.
-P Show master.cf service parameter settings (by default all ser-
vices and all parameters). formatted as one "ser-
vice/type/parameter=value" 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.
d295 12
a306 3
Display the templates for text that appears at the beginning of
delivery status notification (DSN) messages, without expanding
$name expressions.
d308 2
a309 3
To override the built-in templates, specify a template file name
at the end of the postconf(1) command line, or specify a file
name in main.cf with the bounce_template_file parameter.
d311 11
a321 32
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
language: "").
This feature is available with Postfix 2.3 and later.
-v Enable verbose logging for debugging purposes. Multiple -v
options make the software increasingly verbose.
-x Expand $name in main.cf or master.cf parameter values. The
expansion is recursive.
This feature is available with Postfix 2.10 and later.
-X Edit the main.cf configuration file, and remove the parameters
named on the postconf(1) command line. Specify a list of param-
eter 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 parameter settings (-o parameter=value settings)
as specied with "service/type/parameter" on the postconf(1) com-
mand 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 opera-
d324 2
a325 21
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 parame-
ters named on the postconf(1) 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 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 opera-
tion.
This feature is available with Postfix 2.6 and later. Support
for -M was added with Postfix 2.11.
d335 2
a336 2
The following main.cf parameters are especially relevant to this pro-
gram.
d338 2
a339 2
The text below provides only a parameter summary. See postconf(5) for
more details including examples.
d342 2
a343 2
The default location of the Postfix main.cf and master.cf con-
figuration files.
d346 2
a347 1
Pathname of a configuration file with bounce message templates.
d351 1
a351 1
/etc/postfix/master.cf, Postfix master daemon configuration
d354 3
a356 3
bounce(5), bounce template file format master(5), master.cf
configuration file syntax postconf(5), main.cf configuration
file syntax
d362 2
a363 1
The Secure Mailer license must be distributed with this software.
@
1.1.1.4.4.1
log
@sync with head
@
text
@d13 1
a13 1
Managing main.cf:
d15 1
a15 2
postconf [-dfhnv] [-c config_dir] [-C class,...] [parame-
ter ...]
a20 6
Managing master.cf:
postconf [-fMv] [-c config_dir] [service ...]
Managing bounce message templates:
a22 4
Managing other configuration:
postconf [-aAlmv] [-c config_dir]
d24 4
a27 6
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.
d31 2
a32 2
-a List the available SASL server plug-in types. The
SASL plug-in type is selected with the
d36 1
a36 1
cyrus This server plug-in is available when Post-
d42 1
a42 1
fix is built with any form of SASL support.
d44 1
a44 1
This feature is available with Postfix 2.3 and
d47 4
a50 4
-A 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
d53 1
a53 1
cyrus This client plug-in is available when Post-
d56 1
a56 1
This feature is available with Postfix 2.3 and
d61 9
a69 12
ning of delivery status notification (DSN) mes-
sages, replacing $name expressions with actual val-
ues as described in bounce(5).
To override the built-in templates, specify a tem-
plate file name at the end of the postconf(1) com-
mand line, or specify a file name in main.cf with
the bounce_template_file parameter.
To force selection of the built-in templates, spec-
ify an empty template file name on the postconf(1)
command line (in shell language: "").
d79 2
a80 17
-C class,...
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.
d82 5
a86 3
-d Print main.cf default parameter settings instead of
actual settings. Specify -df to fold long lines
for human readability (Postfix 2.9 and later).
d88 2
a89 6
-e Edit the main.cf configuration file, and update
parameter settings with the "name=value" pairs on
the postconf(1) command line. 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.
d91 2
a92 11
The -e is no longer needed with Postfix version 2.8
and later.
-f Fold long lines when printing main.cf or master.cf
configuration file entries, for human readability.
This feature is available with Postfix 2.9 and
later.
-h Show main.cf parameter values without the "name = "
label that normally precedes the value.
a141 5
fail A table that reliably fails all requests.
The lookup table name is used for logging.
This table exists to simplify Postfix error
tests.
d143 1
a143 1
is available on systems with support for
d151 1
a151 1
Perform lookups using the LDAP protocol.
a153 4
memcache
Perform lookups using the memcache protocol.
This is described in memcache_table(5).
d167 2
a168 1
proxy A lookup table that is implemented via the
d187 1
a187 1
lookup result. For example, static:foobar
d198 1
a198 1
postmap(1) command before you can use the
d222 3
a224 21
-M Show master.cf file contents instead of main.cf
file contents. Specify -Mf to fold long lines for
human readability.
If service ... is specified, only the matching ser-
vices will be output. For example, "postconf -Mf
inet" will output all services that listen on the
network.
Specify zero or more arguments, each with a ser-
vice-type name (inet, unix, fifo, or pass) or with
a service-name.service-type pair, where service-
name is the first field of a master.cf entry.
This feature is available with Postfix 2.9 and
later.
-n Print main.cf parameter settings that are explic-
itly specified in main.cf. Specify -nf to fold
long lines for human readability (Postfix 2.9 and
later).
d227 7
a233 12
Display the templates for text that appears at the
beginning of delivery status notification (DSN)
messages, without expanding $name expressions.
To override the built-in templates, specify a tem-
plate file name at the end of the postconf(1) com-
mand line, or specify a file name in main.cf with
the bounce_template_file parameter.
To force selection of the built-in templates, spec-
ify an empty template file name on the postconf(1)
command line (in shell language: "").
d235 1
a235 1
This feature is available with Postfix 2.3 and
d239 1
a239 1
tiple -v options make the software increasingly
d242 7
a248 8
-# Edit the main.cf configuration file, and comment
out the parameters given on the postconf(1) command
line, so that those parameters revert to their
default values. The file is copied to a temporary
file then renamed into place. Specify a list of
parameter names, not name=value pairs. There is no
postconf(1) command to perform the reverse opera-
tion.
a276 1
/etc/postfix/master.cf, Postfix master daemon configuraton
d280 1
a280 2
master(5), master.cf configuration file syntax
postconf(5), main.cf configuration file syntax
@
1.1.1.4.4.2
log
@sync with head.
for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.
this commit was splitted into small chunks to avoid
a limitation of cvs. ("Protocol error: too many arguments")
@
text
@d15 2
a16 2
postconf [-dfhnovx] [-c config_dir] [-C class,...] [param-
eter ...]
d20 1
a20 1
postconf [-#vX] [-c config_dir] [parameter ...]
d24 1
a24 1
postconf [-fMovx] [-c config_dir] [service ...]
d118 1
a118 1
parameter settings with the "name=value" pairs on
d153 1
a153 2
were left behind after abnormal program ter-
mination.
a230 9
socketmap (read-only)
Query a Sendmail-style socketmap server. The
name of the table specifies
inet:host:port:socketmap-name for a TCP-
based server, or unix:pathname:socketmap-
name for a UNIX-domain server. In both
cases, socketmap-name is the name of the
socketmap.
d289 4
a292 10
-n Show only configuration parameters that have
explicit name=value settings in main.cf. Specify
-nf to fold long lines for human readability (Post-
fix 2.9 and later).
-o name=value
Override main.cf parameter settings.
This feature is available with Postfix 2.10 and
later.
d295 2
a296 2
Display the templates for text that appears at the
beginning of delivery status notification (DSN)
d299 3
a301 3
To override the built-in templates, specify a tem-
plate file name at the end of the postconf(1) com-
mand line, or specify a file name in main.cf with
d305 1
a305 1
ify an empty template file name on the postconf(1)
d308 1
a308 1
This feature is available with Postfix 2.3 and
d312 1
a312 1
tiple -v options make the software increasingly
d315 8
a322 24
-x Expand $name in main.cf or master.cf parameter val-
ues. The expansion is recursive.
This feature is available with Postfix 2.10 and
later.
-X Edit the main.cf configuration file, and remove the
parameters named on the postconf(1) command line.
The file is copied to a temporary file then renamed
into place. Specify a list of parameter names, not
"name=value" pairs. There is no postconf(1) com-
mand to perform the reverse operation.
This feature is available with Postfix 2.10 and
later.
-# 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. The file is copied to a temporary
file then renamed into place. Specify a list of
parameter names, not "name=value" pairs. There is
no postconf(1) command to perform the reverse oper-
ation.
d324 1
a324 1
This feature is available with Postfix 2.6 and
d335 1
a335 1
The following main.cf parameters are especially relevant
d338 1
a338 1
The text below provides only a parameter summary. See
d342 1
a342 1
The default location of the Postfix main.cf and
d346 1
a346 1
Pathname of a configuration file with bounce mes-
d362 1
a362 1
The Secure Mailer license must be distributed with this
@
1.1.1.5
log
@Import Postfix 2.9.5. Major changes since version 2.8.x:
- Support for long, non-repeating, queue IDs (queue file names). The
main benefit of non-repeating names is simpler logfile analysis. See
the description of "enable_long_queue_ids" in postconf(5) for
details.
- Memcache client support, and support to share postscreen(8) and
verify(8) caches via the proxymap server. Details about memcache
support are in memcache_table(5) and MEMCACHE_README.
- Gradual degradation: if a database is unavailable (can't open, most
read or write errors) a Postfix daemon will log a warning and
continue providing the services that don't depend on that table,
instead of immediately terminating with a fatal error. To terminate
immediately when a database file can't be opened, specify
"daemon_table_open_error_is_fatal = yes".
- Revised postconf(1) command. It warns about unused parameter
name=value settings in main.cf or master.cf (likely mistakes),
understands "dynamic" parameter names such as names that depend on
the name of a master.cf entry (finally, "postconf -n" shows all
parameter settings), and it can display main.cf and master.cf in a
more user-friendly format (postconf -nf, postconf -Mf).
- Read/write deadline support in the SMTP client and server to defend
against application-level DOS attacks that very slowly write or read
data one byte at a time.
@
text
@d13 1
a13 1
Managing main.cf:
d15 1
a15 2
postconf [-dfhnv] [-c config_dir] [-C class,...] [parame-
ter ...]
a20 6
Managing master.cf:
postconf [-fMv] [-c config_dir] [service ...]
Managing bounce message templates:
a22 4
Managing other configuration:
postconf [-aAlmv] [-c config_dir]
d24 4
a27 6
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.
d31 2
a32 2
-a List the available SASL server plug-in types. The
SASL plug-in type is selected with the
d36 1
a36 1
cyrus This server plug-in is available when Post-
d42 1
a42 1
fix is built with any form of SASL support.
d44 1
a44 1
This feature is available with Postfix 2.3 and
d47 4
a50 4
-A 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
d53 1
a53 1
cyrus This client plug-in is available when Post-
d56 1
a56 1
This feature is available with Postfix 2.3 and
d61 9
a69 12
ning of delivery status notification (DSN) mes-
sages, replacing $name expressions with actual val-
ues as described in bounce(5).
To override the built-in templates, specify a tem-
plate file name at the end of the postconf(1) com-
mand line, or specify a file name in main.cf with
the bounce_template_file parameter.
To force selection of the built-in templates, spec-
ify an empty template file name on the postconf(1)
command line (in shell language: "").
d79 2
a80 17
-C class,...
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.
d82 5
a86 3
-d Print main.cf default parameter settings instead of
actual settings. Specify -df to fold long lines
for human readability (Postfix 2.9 and later).
d88 2
a89 6
-e Edit the main.cf configuration file, and update
parameter settings with the "name=value" pairs on
the postconf(1) command line. 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.
d91 2
a92 11
The -e is no longer needed with Postfix version 2.8
and later.
-f Fold long lines when printing main.cf or master.cf
configuration file entries, for human readability.
This feature is available with Postfix 2.9 and
later.
-h Show main.cf parameter values without the "name = "
label that normally precedes the value.
a141 5
fail A table that reliably fails all requests.
The lookup table name is used for logging.
This table exists to simplify Postfix error
tests.
d143 1
a143 1
is available on systems with support for
d151 1
a151 1
Perform lookups using the LDAP protocol.
a153 4
memcache
Perform lookups using the memcache protocol.
This is described in memcache_table(5).
d167 2
a168 1
proxy A lookup table that is implemented via the
d187 1
a187 1
lookup result. For example, static:foobar
d198 1
a198 1
postmap(1) command before you can use the
d222 3
a224 21
-M Show master.cf file contents instead of main.cf
file contents. Specify -Mf to fold long lines for
human readability.
If service ... is specified, only the matching ser-
vices will be output. For example, "postconf -Mf
inet" will output all services that listen on the
network.
Specify zero or more arguments, each with a ser-
vice-type name (inet, unix, fifo, or pass) or with
a service-name.service-type pair, where service-
name is the first field of a master.cf entry.
This feature is available with Postfix 2.9 and
later.
-n Print main.cf parameter settings that are explic-
itly specified in main.cf. Specify -nf to fold
long lines for human readability (Postfix 2.9 and
later).
d227 7
a233 12
Display the templates for text that appears at the
beginning of delivery status notification (DSN)
messages, without expanding $name expressions.
To override the built-in templates, specify a tem-
plate file name at the end of the postconf(1) com-
mand line, or specify a file name in main.cf with
the bounce_template_file parameter.
To force selection of the built-in templates, spec-
ify an empty template file name on the postconf(1)
command line (in shell language: "").
d235 1
a235 1
This feature is available with Postfix 2.3 and
d239 1
a239 1
tiple -v options make the software increasingly
d242 7
a248 8
-# Edit the main.cf configuration file, and comment
out the parameters given on the postconf(1) command
line, so that those parameters revert to their
default values. The file is copied to a temporary
file then renamed into place. Specify a list of
parameter names, not name=value pairs. There is no
postconf(1) command to perform the reverse opera-
tion.
a276 1
/etc/postfix/master.cf, Postfix master daemon configuraton
d280 1
a280 2
master(5), master.cf configuration file syntax
postconf(5), main.cf configuration file syntax
@
1.1.1.6
log
@Import Postfix 2.10.2. Major changes since version 2.9.* are:
- Separation of relay policy (with smtpd_relay_restrictions) from spam policy
(with smtpd_{client, helo, sender, recipient}_restrictions), which makes
accidental open relay configuration less likely. The default is backwards
compatible.
- HAproxy load-balancer support for postscreen(8) and smtpd(8). The nginx
proxy was already supported by Postfix 2.9 smtpd(8), using XCLIENT commands.
- Support for the TLSv1 and TLSv2 protocols, as well as support to turn them
off if needed for inter-operability.
- Laptop-friendly configuration. By default, Postfix now uses UNIX-domain
sockets instead of FIFOs, and thus avoids MTIME file system updates on an
idle mail system.
- Revised postconf(1) command. The "-x" option expands $name in a parameter
value (both main.cf and master.cf); the "-o name=value" option overrides
a main.cf parameter setting; and postconf(1) now warns about a $name that
has no name=value setting.
- Sendmail-style "socketmap" lookup tables.
@
text
@d15 2
a16 2
postconf [-dfhnovx] [-c config_dir] [-C class,...] [param-
eter ...]
d20 1
a20 1
postconf [-#vX] [-c config_dir] [parameter ...]
d24 1
a24 1
postconf [-fMovx] [-c config_dir] [service ...]
d118 1
a118 1
parameter settings with the "name=value" pairs on
d153 1
a153 2
were left behind after abnormal program ter-
mination.
a230 9
socketmap (read-only)
Query a Sendmail-style socketmap server. The
name of the table specifies
inet:host:port:socketmap-name for a TCP-
based server, or unix:pathname:socketmap-
name for a UNIX-domain server. In both
cases, socketmap-name is the name of the
socketmap.
d289 4
a292 10
-n Show only configuration parameters that have
explicit name=value settings in main.cf. Specify
-nf to fold long lines for human readability (Post-
fix 2.9 and later).
-o name=value
Override main.cf parameter settings.
This feature is available with Postfix 2.10 and
later.
d295 2
a296 2
Display the templates for text that appears at the
beginning of delivery status notification (DSN)
d299 3
a301 3
To override the built-in templates, specify a tem-
plate file name at the end of the postconf(1) com-
mand line, or specify a file name in main.cf with
d305 1
a305 1
ify an empty template file name on the postconf(1)
d308 1
a308 1
This feature is available with Postfix 2.3 and
d312 1
a312 1
tiple -v options make the software increasingly
d315 8
a322 24
-x Expand $name in main.cf or master.cf parameter val-
ues. The expansion is recursive.
This feature is available with Postfix 2.10 and
later.
-X Edit the main.cf configuration file, and remove the
parameters named on the postconf(1) command line.
The file is copied to a temporary file then renamed
into place. Specify a list of parameter names, not
"name=value" pairs. There is no postconf(1) com-
mand to perform the reverse operation.
This feature is available with Postfix 2.10 and
later.
-# 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. The file is copied to a temporary
file then renamed into place. Specify a list of
parameter names, not "name=value" pairs. There is
no postconf(1) command to perform the reverse oper-
ation.
d324 1
a324 1
This feature is available with Postfix 2.6 and
d335 1
a335 1
The following main.cf parameters are especially relevant
d338 1
a338 1
The text below provides only a parameter summary. See
d342 1
a342 1
The default location of the Postfix main.cf and
d346 1
a346 1
Pathname of a configuration file with bounce mes-
d362 1
a362 1
The Secure Mailer license must be distributed with this
@
1.1.1.6.2.1
log
@Rebase.
@
text
@d15 2
a16 1
postconf [-dfhnopvx] [-c config_dir] [-C class,...] [parameter ...]
d18 1
a18 1
postconf [-epv] [-c config_dir] parameter=value ...
d20 1
a20 1
postconf -# [-pv] [-c config_dir] parameter ...
d22 1
a22 1
postconf -X [-pv] [-c config_dir] parameter ...
d24 1
a24 23
Managing master.cf service entries:
postconf -M [-fovx] [-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 master.cf service fields:
postconf -F [-fovx] [-c config_dir] [service[/type[/field]] ...]
postconf -F [-ev] [-c config_dir] service/type/field=value ...
Managing master.cf service parameters:
postconf -P [-fovx] [-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 ...
d28 1
a28 3
postconf -b [-v] [-c config_dir] [template_file]
postconf -t [-v] [-c config_dir] [template_file]
d32 1
a32 1
postconf -a|-A|-l|-m [-v] [-c config_dir]
d35 6
a40 5
By default, the postconf(1) command displays the values of main.cf con-
figuration parameters, and warns about possible mis-typed parameter
names (Postfix 2.9 and later). It can also change main.cf configura-
tion parameter values, or display other configuration information about
the Postfix mail system.
d44 4
a47 3
-a List the available SASL server plug-in types. The SASL plug-in
type is selected with the smtpd_sasl_type configuration parame-
ter by specifying one of the names listed below.
d49 2
a50 2
cyrus This server plug-in is available when Postfix is built
with Cyrus SASL support.
d53 11
a63 9
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 client plug-in types. The SASL plug-in
type is selected with the smtp_sasl_type or lmtp_sasl_type con-
figuration parameters by specifying one of the names listed
d66 2
a67 2
cyrus This client plug-in is available when Postfix is built
with Cyrus SASL support.
d69 2
a70 1
This feature is available with Postfix 2.3 and later.
d73 13
a85 11
Display the message text that appears at the beginning of deliv-
ery status notification (DSN) messages, replacing $name expres-
sions with actual values as described in bounce(5).
To override the built-in templates, specify a template file name
at the end of the postconf(1) command line, or specify a file
name in main.cf with the bounce_template_file parameter.
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
language: "").
d87 2
a88 1
This feature is available with Postfix 2.3 and later.
d91 3
a93 2
The main.cf configuration file is in the named directory instead
of the default configuration directory.
d96 2
a97 2
When displaying main.cf parameters, select only parameters from
the specified class(es):
d103 3
a105 2
Parameters with service-defined names (the first field of
a master.cf entry plus a Postfix-defined suffix).
d113 13
a125 1
This feature is available with Postfix 2.9 and later.
d127 2
a128 28
-d Print main.cf 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 main.cf configuration file, and update parameter set-
tings with the "name=value" pairs on the postconf(1) command
line.
With -M, edit the master.cf configuration file, and replace one
or more service entries with new values as specified with "ser-
vice/type=value" on the postconf(1) command line.
With -F, edit the master.cf configuration file, and replace one
or more service fields with new values as specied with "ser-
vice/type/field=value" on the postconf(1) 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 master.cf configuration file, and add or
update one or more service parameter settings (-o parame-
ter=value settings) with new values as specied with "ser-
vice/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.
d130 1
a130 1
The -e option is no longer needed with Postfix version 2.8 and
d133 2
a134 4
-f Fold long lines when printing main.cf or master.cf configuration
file entries, for human readability.
This feature is available with Postfix 2.9 and later.
d136 2
a137 3
-F 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.
d139 4
a142 4
Specify one or more "service/type/field" instances on the post-
conf(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.
d144 2
a145 14
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.
-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.
d148 13
a160 10
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 DATA-
d163 11
a173 2
btree A sorted, balanced tree structure. Available on systems
with support for Berkeley DB databases.
d175 2
a176 2
cdb A read-optimized structure with no support for incremen-
tal updates. Available on systems with support for CDB
a178 7
cidr A table that associates values with Classless Inter-
Domain Routing (CIDR) patterns. This is described in
cidr_table(5).
dbm An indexed file type based on hashing. Available on sys-
tems with support for DBM databases.
d180 13
a192 10
The UNIX process environment array. The lookup key is the
variable name. Originally implemented for testing, some-
one 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.
hash An indexed file type based on hashing. Available on sys-
tems with support for Berkeley DB databases.
d195 2
a196 6
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 lmdb_table(5).
d199 2
a200 1
LDAP database client. This is described in ldap_table(5).
d203 2
a204 2
Memcache database client. This is described in mem-
cache_table(5).
d207 2
a208 3
MySQL database client. Available on systems with support
for MySQL databases. This is described in mysql_ta-
ble(5).
d211 3
a213 2
A lookup table based on Perl Compatible Regular Expres-
sions. The file format is described in pcre_table(5).
d216 2
a217 2
PostgreSQL database client. This is described in
pgsql_table(5).
d219 3
a221 2
proxy Postfix proxymap(8) client for shared access to Postfix
databases. The table name syntax is type:name.
d224 7
a230 5
A lookup table based on regular expressions. The file
format is described in regexp_table(5).
sdbm An indexed file type based on hashing. Available on sys-
tems with support for SDBM databases.
d233 7
a239 4
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
socketmap_table(5).
d242 2
a243 1
SQLite database. This is described in sqlite_table(5).
d246 4
a249 3
A table that always returns its name as lookup result.
For example, static:foobar always returns the string foo-
bar as lookup result.
d252 2
a253 1
TCP/IP client. The protocol is described in tcp_table(5).
d256 5
a260 4
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.
d263 3
a265 2
A limited view of the UNIX authentication database. The
following tables are implemented:
d268 4
a271 3
The table is the UNIX password database. The key
is a login name. The result is a password file
entry in passwd(5) format.
d274 29
a302 28
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 master.cf file contents instead of main.cf 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 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
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 main.cf. Specify -nf to fold long lines for human
readability (Postfix 2.9 and later).
d307 2
a308 17
This feature is available with Postfix 2.10 and later.
-p Show main.cf parameter settings. This is the default.
This feature is available with Postfix 2.11 and later.
-P Show master.cf service parameter settings (by default all ser-
vices and all parameters). formatted as one "ser-
vice/type/parameter=value" 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.
d311 12
a322 3
Display the templates for text that appears at the beginning of
delivery status notification (DSN) messages, without expanding
$name expressions.
d324 2
a325 3
To override the built-in templates, specify a template file name
at the end of the postconf(1) command line, or specify a file
name in main.cf with the bounce_template_file parameter.
d327 3
a329 3
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
language: "").
d331 2
a332 1
This feature is available with Postfix 2.3 and later.
d334 2
a335 2
-v Enable verbose logging for debugging purposes. Multiple -v
options make the software increasingly verbose.
d337 6
a342 2
-x Expand $name in main.cf or master.cf parameter values. The
expansion is recursive.
d344 2
a345 1
This feature is available with Postfix 2.10 and later.
d347 8
a354 3
-X Edit the main.cf configuration file, and remove the parameters
named on the postconf(1) command line. Specify a list of param-
eter names, not "name=value" pairs.
d356 2
a357 37
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 parameter settings (-o parameter=value settings)
as specied with "service/type/parameter" on the postconf(1) com-
mand 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 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 main.cf configuration file, and comment out the parame-
ters named on the postconf(1) 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 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 opera-
tion.
This feature is available with Postfix 2.6 and later. Support
for -M was added with Postfix 2.11.
d367 2
a368 2
The following main.cf parameters are especially relevant to this pro-
gram.
d370 2
a371 2
The text below provides only a parameter summary. See postconf(5) for
more details including examples.
d374 2
a375 2
The default location of the Postfix main.cf and master.cf con-
figuration files.
d378 2
a379 1
Pathname of a configuration file with bounce message templates.
d383 1
a383 1
/etc/postfix/master.cf, Postfix master daemon configuration
d386 3
a388 3
bounce(5), bounce template file format master(5), master.cf
configuration file syntax postconf(5), main.cf configuration
file syntax
d394 2
a395 1
The Secure Mailer license must be distributed with this software.
@
1.1.1.7
log
@Import Postfix 2.11.1. The main changes since version 2.10.* are:
- Support for PKI-less TLS server certificate verification with DANE
(DNS-based Authentication of Named Entities) where the CA public key
or the server certificate is identified via DNSSEC lookup. This
requires a DNS resolver that validates DNSSEC replies. The problem
with conventional PKI is that there are literally hundreds of
organizations world-wide that can provide a certificate in anyone's
name. DANE limits trust to the people who control the target DNS
zone and its parent zones.
- A new postscreen_dnsbl_whitelist_threshold feature to allow clients
to skip postscreen tests based on their DNSBL score. This can
eliminate email delays due to "after 220 greeting" protocol tests,
which otherwise require that a client reconnects before it can
deliver mail. Some providers such as Google don't retry from the
same IP address, and that can result in large email delivery delays.
- The recipient_delimiter feature now supports different delimiters,
for example both "+" and "-". As before, this implementation
recognizes exactly one delimiter character per email address, and
exactly one address extension per email address.
- Advanced master.cf query/update support to access service attributes
as "name = value" pairs. For example to turn off chroot on all
services use "postconf -F '*/*/chroot = n'", and to change/add a
"-o name=value" setting use "postconf -P 'smtp/inet/name = value'".
This was developed primarily to allow automated tools to manage Postfix
systems without having to parse Postfix configuration files.
@
text
@d15 2
a16 1
postconf [-dfhnopvx] [-c config_dir] [-C class,...] [parameter ...]
d18 1
a18 1
postconf [-epv] [-c config_dir] parameter=value ...
d20 1
a20 1
postconf -# [-pv] [-c config_dir] parameter ...
d22 1
a22 1
postconf -X [-pv] [-c config_dir] parameter ...
d24 1
a24 23
Managing master.cf service entries:
postconf -M [-fovx] [-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 master.cf service fields:
postconf -F [-fovx] [-c config_dir] [service[/type[/field]] ...]
postconf -F [-ev] [-c config_dir] service/type/field=value ...
Managing master.cf service parameters:
postconf -P [-fovx] [-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 ...
d28 1
a28 3
postconf -b [-v] [-c config_dir] [template_file]
postconf -t [-v] [-c config_dir] [template_file]
d32 1
a32 1
postconf -a|-A|-l|-m [-v] [-c config_dir]
d35 6
a40 5
By default, the postconf(1) command displays the values of main.cf con-
figuration parameters, and warns about possible mis-typed parameter
names (Postfix 2.9 and later). It can also change main.cf configura-
tion parameter values, or display other configuration information about
the Postfix mail system.
d44 4
a47 3
-a List the available SASL server plug-in types. The SASL plug-in
type is selected with the smtpd_sasl_type configuration parame-
ter by specifying one of the names listed below.
d49 2
a50 2
cyrus This server plug-in is available when Postfix is built
with Cyrus SASL support.
d53 11
a63 9
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 client plug-in types. The SASL plug-in
type is selected with the smtp_sasl_type or lmtp_sasl_type con-
figuration parameters by specifying one of the names listed
d66 2
a67 2
cyrus This client plug-in is available when Postfix is built
with Cyrus SASL support.
d69 2
a70 1
This feature is available with Postfix 2.3 and later.
d73 13
a85 11
Display the message text that appears at the beginning of deliv-
ery status notification (DSN) messages, replacing $name expres-
sions with actual values as described in bounce(5).
To override the built-in templates, specify a template file name
at the end of the postconf(1) command line, or specify a file
name in main.cf with the bounce_template_file parameter.
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
language: "").
d87 2
a88 1
This feature is available with Postfix 2.3 and later.
d91 3
a93 2
The main.cf configuration file is in the named directory instead
of the default configuration directory.
d96 2
a97 2
When displaying main.cf parameters, select only parameters from
the specified class(es):
d103 3
a105 2
Parameters with service-defined names (the first field of
a master.cf entry plus a Postfix-defined suffix).
d113 13
a125 1
This feature is available with Postfix 2.9 and later.
d127 2
a128 28
-d Print main.cf 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 main.cf configuration file, and update parameter set-
tings with the "name=value" pairs on the postconf(1) command
line.
With -M, edit the master.cf configuration file, and replace one
or more service entries with new values as specified with "ser-
vice/type=value" on the postconf(1) command line.
With -F, edit the master.cf configuration file, and replace one
or more service fields with new values as specied with "ser-
vice/type/field=value" on the postconf(1) 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 master.cf configuration file, and add or
update one or more service parameter settings (-o parame-
ter=value settings) with new values as specied with "ser-
vice/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.
d130 1
a130 1
The -e option is no longer needed with Postfix version 2.8 and
d133 2
a134 4
-f Fold long lines when printing main.cf or master.cf configuration
file entries, for human readability.
This feature is available with Postfix 2.9 and later.
d136 2
a137 3
-F 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.
d139 4
a142 4
Specify one or more "service/type/field" instances on the post-
conf(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.
d144 2
a145 14
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.
-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.
d148 13
a160 10
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 DATA-
d163 11
a173 2
btree A sorted, balanced tree structure. Available on systems
with support for Berkeley DB databases.
d175 2
a176 2
cdb A read-optimized structure with no support for incremen-
tal updates. Available on systems with support for CDB
a178 7
cidr A table that associates values with Classless Inter-
Domain Routing (CIDR) patterns. This is described in
cidr_table(5).
dbm An indexed file type based on hashing. Available on sys-
tems with support for DBM databases.
d180 13
a192 10
The UNIX process environment array. The lookup key is the
variable name. Originally implemented for testing, some-
one 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.
hash An indexed file type based on hashing. Available on sys-
tems with support for Berkeley DB databases.
d195 2
a196 6
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 lmdb_table(5).
d199 2
a200 1
LDAP database client. This is described in ldap_table(5).
d203 2
a204 2
Memcache database client. This is described in mem-
cache_table(5).
d207 2
a208 3
MySQL database client. Available on systems with support
for MySQL databases. This is described in mysql_ta-
ble(5).
d211 3
a213 2
A lookup table based on Perl Compatible Regular Expres-
sions. The file format is described in pcre_table(5).
d216 2
a217 2
PostgreSQL database client. This is described in
pgsql_table(5).
d219 3
a221 2
proxy Postfix proxymap(8) client for shared access to Postfix
databases. The table name syntax is type:name.
d224 7
a230 5
A lookup table based on regular expressions. The file
format is described in regexp_table(5).
sdbm An indexed file type based on hashing. Available on sys-
tems with support for SDBM databases.
d233 7
a239 4
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
socketmap_table(5).
d242 2
a243 1
SQLite database. This is described in sqlite_table(5).
d246 4
a249 3
A table that always returns its name as lookup result.
For example, static:foobar always returns the string foo-
bar as lookup result.
d252 2
a253 1
TCP/IP client. The protocol is described in tcp_table(5).
d256 5
a260 4
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.
d263 3
a265 2
A limited view of the UNIX authentication database. The
following tables are implemented:
d268 4
a271 3
The table is the UNIX password database. The key
is a login name. The result is a password file
entry in passwd(5) format.
d274 29
a302 28
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 master.cf file contents instead of main.cf 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 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
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 main.cf. Specify -nf to fold long lines for human
readability (Postfix 2.9 and later).
d307 2
a308 17
This feature is available with Postfix 2.10 and later.
-p Show main.cf parameter settings. This is the default.
This feature is available with Postfix 2.11 and later.
-P Show master.cf service parameter settings (by default all ser-
vices and all parameters). formatted as one "ser-
vice/type/parameter=value" 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.
d311 12
a322 3
Display the templates for text that appears at the beginning of
delivery status notification (DSN) messages, without expanding
$name expressions.
d324 2
a325 3
To override the built-in templates, specify a template file name
at the end of the postconf(1) command line, or specify a file
name in main.cf with the bounce_template_file parameter.
d327 3
a329 3
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
language: "").
d331 2
a332 1
This feature is available with Postfix 2.3 and later.
d334 2
a335 2
-v Enable verbose logging for debugging purposes. Multiple -v
options make the software increasingly verbose.
d337 6
a342 2
-x Expand $name in main.cf or master.cf parameter values. The
expansion is recursive.
d344 2
a345 1
This feature is available with Postfix 2.10 and later.
d347 8
a354 3
-X Edit the main.cf configuration file, and remove the parameters
named on the postconf(1) command line. Specify a list of param-
eter names, not "name=value" pairs.
d356 2
a357 37
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 parameter settings (-o parameter=value settings)
as specied with "service/type/parameter" on the postconf(1) com-
mand 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 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 main.cf configuration file, and comment out the parame-
ters named on the postconf(1) 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 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 opera-
tion.
This feature is available with Postfix 2.6 and later. Support
for -M was added with Postfix 2.11.
d367 2
a368 2
The following main.cf parameters are especially relevant to this pro-
gram.
d370 2
a371 2
The text below provides only a parameter summary. See postconf(5) for
more details including examples.
d374 2
a375 2
The default location of the Postfix main.cf and master.cf con-
figuration files.
d378 2
a379 1
Pathname of a configuration file with bounce message templates.
d383 1
a383 1
/etc/postfix/master.cf, Postfix master daemon configuration
d386 3
a388 3
bounce(5), bounce template file format master(5), master.cf
configuration file syntax postconf(5), main.cf configuration
file syntax
d394 2
a395 1
The Secure Mailer license must be distributed with this software.
@
1.1.1.7.10.1
log
@Sync with HEAD
@
text
@d13 1
a13 1
Managing main.cf:
d15 1
a15 1
postconf [-dfhHnopvx] [-c config_dir] [-C class,...] [parameter ...]
d23 1
a23 1
Managing master.cf service entries:
d33 1
a33 1
Managing master.cf service fields:
d35 1
a35 1
postconf -F [-fhHovx] [-c config_dir] [service[/type[/field]] ...]
d39 1
a39 1
Managing master.cf service parameters:
d41 1
a41 1
postconf -P [-fhHovx] [-c config_dir] [service[/type[/parameter]] ...]
d47 1
a47 1
Managing bounce message templates:
d53 1
a53 5
Managing TLS features:
postconf -T mode [-v] [-c config_dir]
Managing other configuration:
d59 2
a60 2
figuration parameters, and warns about possible mis-typed parameter
names (Postfix 2.9 and later). It can also change main.cf configura-
d66 2
a67 2
-a List the available SASL server plug-in types. The SASL plug-in
type is selected with the smtpd_sasl_type configuration parame-
d70 1
a70 1
cyrus This server plug-in is available when Postfix is built
d75 1
a75 1
server, and is available when Postfix is built with any
d80 3
a82 3
-A List the available SASL client plug-in types. The SASL plug-in
type is selected with the smtp_sasl_type or lmtp_sasl_type con-
figuration parameters by specifying one of the names listed
d85 1
a85 1
cyrus This client plug-in is available when Postfix is built
d92 1
a92 1
ery status notification (DSN) messages, replacing $name expres-
d96 1
a96 1
at the end of the postconf(1) command line, or specify a file
d99 2
a100 2
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
d110 1
a110 1
When displaying main.cf parameters, select only parameters from
d128 2
a129 2
-d Print main.cf default parameter settings instead of actual set-
tings. Specify -df to fold long lines for human readability
d132 2
a133 2
-e Edit the main.cf configuration file, and update parameter set-
tings with the "name=value" pairs on the postconf(1) command
d136 2
a137 2
With -M, edit the master.cf configuration file, and replace one
or more service entries with new values as specified with "ser-
d140 4
a143 4
With -F, edit the master.cf configuration file, and replace one
or more service fields with new values as specied with "ser-
vice/type/field=value" on the postconf(1) command line. Cur-
rently, the "command" field contains the command name and com-
d148 3
a150 3
With -P, edit the master.cf configuration file, and add or
update one or more service parameter settings (-o parame-
ter=value settings) with new values as specied with "ser-
d154 1
a154 1
into place. Specify quotes to protect special characters and
d157 1
a157 1
The -e option is no longer needed with Postfix version 2.8 and
d166 2
a167 2
and all fields), formatted as "service/type/field=value", one
per line. Specify -Ff to fold long lines.
d169 3
a171 3
Specify one or more "service/type/field" instances on the post-
conf(1) command line to limit the output to fields of interest.
Trailing parameter name or service type fields that are omitted
d176 1
a176 1
-h Show parameter or attribute values without the "name = " label
a178 5
-H Show parameter or attribute names without the " = value" that
normally follows the name.
This feature is available with Postfix 3.1 and later.
d209 3
a211 3
cidr A table that associates values with Classless
Inter-Domain Routing (CIDR) patterns. This is described
in cidr_table(5).
a227 9
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;
whitespace after "{" and before "}" is ignored. Inline
tables eliminate the need to create a database file for
just a few fixed elements. See also the static: map
type.
a255 11
pipemap (read-only)
A lookup table that constructs a pipeline of tables.
Example: "pipemap:{type_1:name_1, ..., type_n:name_n}".
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,
individual maps are separated with comma or whitespace.
a258 9
randmap (read-only)
An in-memory table that performs random selection. Exam-
ple: "randmap:{result_1, ..., result_n}". 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 whitespace. To give a
specific result more weight, specify it multiple times.
d278 1
a278 4
bar as lookup result. Specify "static:{ text with white-
space }" when the result contains whitespace; this form
ignores whitespace after "{" and before "}". See also the
inline: map.
d284 3
a286 3
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
a288 5
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.
d338 7
a344 6
vices and all parameters), formatted as "service/type/parame-
ter=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
d350 2
a351 2
Display the templates for text that appears at the beginning of
delivery status notification (DSN) messages, without expanding
d355 1
a355 1
at the end of the postconf(1) command line, or specify a file
d358 2
a359 2
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
d364 1
a364 22
-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
d367 1
a367 1
-x Expand $name in main.cf or master.cf parameter values. The
d372 1
a372 1
-X Edit the main.cf configuration file, and remove the parameters
d376 2
a377 2
With -M, edit the master.cf configuration file, and remove one
or more service entries as specified with "service/type" on the
d380 1
a380 1
With -P, edit the master.cf configuration file, and remove one
d389 1
a389 1
There is no postconf(1) command to perform the reverse opera-
d392 1
a392 1
This feature is available with Postfix 2.10 and later. Support
d400 2
a401 2
With -M, edit the master.cf configuration file, and comment out
one or more service entries as specified with "service/type" on
d408 1
a408 1
There is no postconf(1) command to perform the reverse opera-
d411 1
a411 1
This feature is available with Postfix 2.6 and later. Support
d422 1
a422 1
The following main.cf parameters are especially relevant to this pro-
d425 1
a425 1
The text below provides only a parameter summary. See postconf(5) for
d429 1
a429 1
The default location of the Postfix main.cf and master.cf con-
d433 1
a433 1
Pathname of a configuration file with bounce message templates.
d440 3
a442 3
bounce(5), bounce template file format
master(5), master.cf configuration file syntax
postconf(5), main.cf configuration file syntax
a455 5
Wietse Venema
Google, Inc.
111 8th Avenue
New York, NY 10011, USA
@
1.1.1.7.6.1
log
@Sync with HEAD
@
text
@d13 1
a13 1
Managing main.cf:
d15 1
a15 1
postconf [-dfhHnopvx] [-c config_dir] [-C class,...] [parameter ...]
d23 1
a23 1
Managing master.cf service entries:
d33 1
a33 1
Managing master.cf service fields:
d35 1
a35 1
postconf -F [-fhHovx] [-c config_dir] [service[/type[/field]] ...]
d39 1
a39 1
Managing master.cf service parameters:
d41 1
a41 1
postconf -P [-fhHovx] [-c config_dir] [service[/type[/parameter]] ...]
d47 1
a47 1
Managing bounce message templates:
d53 1
a53 5
Managing TLS features:
postconf -T mode [-v] [-c config_dir]
Managing other configuration:
d59 2
a60 2
figuration parameters, and warns about possible mis-typed parameter
names (Postfix 2.9 and later). It can also change main.cf configura-
d66 2
a67 2
-a List the available SASL server plug-in types. The SASL plug-in
type is selected with the smtpd_sasl_type configuration parame-
d70 1
a70 1
cyrus This server plug-in is available when Postfix is built
d75 1
a75 1
server, and is available when Postfix is built with any
d80 3
a82 3
-A List the available SASL client plug-in types. The SASL plug-in
type is selected with the smtp_sasl_type or lmtp_sasl_type con-
figuration parameters by specifying one of the names listed
d85 1
a85 1
cyrus This client plug-in is available when Postfix is built
d92 1
a92 1
ery status notification (DSN) messages, replacing $name expres-
d96 1
a96 1
at the end of the postconf(1) command line, or specify a file
d99 2
a100 2
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
d110 1
a110 1
When displaying main.cf parameters, select only parameters from
d128 2
a129 2
-d Print main.cf default parameter settings instead of actual set-
tings. Specify -df to fold long lines for human readability
d132 2
a133 2
-e Edit the main.cf configuration file, and update parameter set-
tings with the "name=value" pairs on the postconf(1) command
d136 2
a137 2
With -M, edit the master.cf configuration file, and replace one
or more service entries with new values as specified with "ser-
d140 4
a143 4
With -F, edit the master.cf configuration file, and replace one
or more service fields with new values as specied with "ser-
vice/type/field=value" on the postconf(1) command line. Cur-
rently, the "command" field contains the command name and com-
d148 3
a150 3
With -P, edit the master.cf configuration file, and add or
update one or more service parameter settings (-o parame-
ter=value settings) with new values as specied with "ser-
d154 1
a154 1
into place. Specify quotes to protect special characters and
d157 1
a157 1
The -e option is no longer needed with Postfix version 2.8 and
d166 2
a167 2
and all fields), formatted as "service/type/field=value", one
per line. Specify -Ff to fold long lines.
d169 3
a171 3
Specify one or more "service/type/field" instances on the post-
conf(1) command line to limit the output to fields of interest.
Trailing parameter name or service type fields that are omitted
d176 1
a176 1
-h Show parameter or attribute values without the "name = " label
a178 5
-H Show parameter or attribute names without the " = value" that
normally follows the name.
This feature is available with Postfix 3.1 and later.
d209 3
a211 3
cidr A table that associates values with Classless
Inter-Domain Routing (CIDR) patterns. This is described
in cidr_table(5).
a227 9
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;
whitespace after "{" and before "}" is ignored. Inline
tables eliminate the need to create a database file for
just a few fixed elements. See also the static: map
type.
a255 11
pipemap (read-only)
A lookup table that constructs a pipeline of tables.
Example: "pipemap:{type_1:name_1, ..., type_n:name_n}".
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,
individual maps are separated with comma or whitespace.
a258 9
randmap (read-only)
An in-memory table that performs random selection. Exam-
ple: "randmap:{result_1, ..., result_n}". 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 whitespace. To give a
specific result more weight, specify it multiple times.
d278 1
a278 4
bar as lookup result. Specify "static:{ text with white-
space }" when the result contains whitespace; this form
ignores whitespace after "{" and before "}". See also the
inline: map.
d284 3
a286 3
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
a288 5
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.
d338 7
a344 6
vices and all parameters), formatted as "service/type/parame-
ter=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
d350 2
a351 2
Display the templates for text that appears at the beginning of
delivery status notification (DSN) messages, without expanding
d355 1
a355 1
at the end of the postconf(1) command line, or specify a file
d358 2
a359 2
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
d364 1
a364 22
-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
d367 1
a367 1
-x Expand $name in main.cf or master.cf parameter values. The
d372 1
a372 1
-X Edit the main.cf configuration file, and remove the parameters
d376 2
a377 2
With -M, edit the master.cf configuration file, and remove one
or more service entries as specified with "service/type" on the
d380 1
a380 1
With -P, edit the master.cf configuration file, and remove one
d389 1
a389 1
There is no postconf(1) command to perform the reverse opera-
d392 1
a392 1
This feature is available with Postfix 2.10 and later. Support
d400 2
a401 2
With -M, edit the master.cf configuration file, and comment out
one or more service entries as specified with "service/type" on
d408 1
a408 1
There is no postconf(1) command to perform the reverse opera-
d411 1
a411 1
This feature is available with Postfix 2.6 and later. Support
d422 1
a422 1
The following main.cf parameters are especially relevant to this pro-
d425 1
a425 1
The text below provides only a parameter summary. See postconf(5) for
d429 1
a429 1
The default location of the Postfix main.cf and master.cf con-
d433 1
a433 1
Pathname of a configuration file with bounce message templates.
d440 3
a442 3
bounce(5), bounce template file format
master(5), master.cf configuration file syntax
postconf(5), main.cf configuration file syntax
a455 5
Wietse Venema
Google, Inc.
111 8th Avenue
New York, NY 10011, USA
@
1.1.1.8
log
@The stable Postfix release is called postfix-3.0.x where 3=major
release number, 0=minor release number, x=patchlevel. The stable
release never changes except for patches that address bugs or
emergencies. Patches change the patchlevel and the release date.
New features are developed in snapshot releases. These are called
postfix-3.1-yyyymmdd where yyyymmdd is the release date (yyyy=year,
mm=month, dd=day). Patches are never issued for snapshot releases;
instead, a new snapshot is released.
The mail_release_date configuration parameter (format: yyyymmdd)
specifies the release date of a stable release or snapshot release.
If you upgrade from Postfix 2.10 or earlier, read RELEASE_NOTES-2.11
before proceeding.
Notes for distribution maintainers
----------------------------------
* New backwards-compatibility safety net.
With NEW Postfix installs, you MUST install a main.cf file with
the setting "compatibility_level = 2". See conf/main.cf for an
example.
With UPGRADES of existing Postfix systems, you MUST NOT change the
main.cf compatibility_level setting, nor add this setting if it
does not exist.
Several Postfix default settings have changed with Postfix 3.0. To
avoid massive frustration with existing Postfix installations,
Postfix 3.0 comes with a safety net that forces Postfix to keep
running with backwards-compatible main.cf and master.cf default
settings. This safety net depends on the main.cf compatibility_level
setting (default: 0). Details are in COMPATIBILITY_README.
* New Postfix build system.
The Postfix build/install procedure has changed to support Postfix
dynamically-linked libraries and database plugins. These must not
be "shared" with non-Postfix programs, and therefore must not be
installed in a public directory.
To avoid massive frustration due to broken patches, PLEASE BUILD
POSTFIX FIRST WITHOUT APPLYING ANY PATCHES. Follow the INSTALL
instructions (see "Building with Postfix dynamically-linked libraries
and database plugins"), and see how things work and what the
dynamically-linked libraries, database plugin, and configuration
files look like. Then, go ahead and perform your platform-specific
customizations. The INSTALL section "Tips for distribution maintainers"
has further suggestions.
Major changes - critical
------------------------
[Incompat 20140714] After upgrading Postfix, "postfix reload" (or
start/stop) is required. Several Postfix-internal protocols have
been extended to support SMTPUTF8. Failure to reload or restart
will result in mail staying queued, while Postfix daemons log
warning messages about unexpected attributes.
Major changes - default settings
--------------------------------
[Incompat 20141009] The default settings have changed for relay_domains
(new: empty, old: $mydestination) and mynetworks_style (new: host,
old: subnet). However the backwards-compatibility safety net will
prevent these changes from taking effect, giving the system
administrator the option to make an old default setting permanent
in main.cf or to adopt the new default setting, before turning off
backwards compatibility. See COMPATIBILITY_README for details.
[Incompat 20141001] A new backwards-compatibility safety net forces
Postfix to run with backwards-compatible main.cf and master.cf
default settings after an upgrade to a newer but incompatible Postfix
version. See COMPATIBILITY_README for details.
While the backwards-compatible default settings are in effect,
Postfix logs what services or what email would be affected by the
incompatible change. Based on this the administrator can make some
backwards-compatibility settings permanent in main.cf or master.cf,
before turning off backwards compatibility.
See postconf.5.html#compatibility_level for details.
[Incompat 20141001] The default settings
have changed for append_dot_mydomain (new: no. old: yes), master.cf
chroot (new: n, old: y), and smtputf8 (new: yes, old: no).
Major changes - access control
------------------------------
[Feature 20141119] Support for BCC actions in header/body_checks
and milter_header_checks. There is no limit on the number of BCC
actions that may be specified, other than the implicit limit due
to finite storage. BCC support will not be implemented in Postfix
delivery agent header/body_checks.
It works in the same way as always_bcc and sender/recipient_bcc_maps:
there can be only one address per action, recipients are added with
the NOTIFY=NONE delivery status notification option, and duplicate
recipients are ignored (with the same delivery status notification
options).
[Incompat 20141009] The default settings have changed for relay_domains
(new: empty, old: $mydestination) and mynetworks_style (new: host,
old: subnet). However the backwards-compatibility safety net will
prevent these changes from taking effect, giving the system
administrator the option to make an old default setting permanent
in main.cf or to adopt the new default setting, before turning off
backwards compatibility. See COMPATIBILITY_README for details.
[Feature 20140618] New INFO action in access(5) tables, for consistency
with header/body_checks.
[Feature 20140620] New check_xxx_a_access (for xxx in client,
reverse_client, helo, sender, recipient) implements access control
on all A and AAAA IP addresses for respectively the client hostname,
helo parameter, sender domain or recipient domain. This complements
the existing check_xxx_mx_access and check_xxx_ns_access features.
Major changes - address rewriting
---------------------------------
[Incompat 20141001] The default settings have changed for
append_dot_mydomain (new: no. old: yes), master.cf chroot (new:
n, old: y), and smtputf8 (new: yes, old: no).
Major changes - address verification
------------------------------------
[Feature 20141227] The new smtp_address_verify_target parameter
(default: rcpt) specifies what protocol stage decides if a recipient
is valid. Specify "data" for servers that reject invalid recipients
in response to the DATA command.
Major changes - database support
--------------------------------
[Feature 20140512] Support for Berkeley DB version 6.
[Feature 20140618] The "randmap" lookup table performs random
selection. This may be used to implement load balancing, for example:
/etc/postfix/transport:
# Deliver my own domain as usual.
example.com :
.example.com :
/etc/postfix/main.cf:
transport_maps =
# Deliver my own domain as usual.
hash:/etc/postfix/transport
# Deliver other domains via randomly-selected relayhosts
randmap:{smtp:smtp0.example.com, smtp:smtp1.example.com}
A variant of this can randomly select SMTP clients with different
smtp_bind_address settings.
To implement different weights, specify lookup results multiple
times. For example, to choose smtp:smtp1.example.com twice as often
as smtp:smtp0.example.com, specify smtp:smtp1.example.com twice.
A future version may support randmap:/path/to/file to load a list
of results from file.
[Feature 20140618] As the name suggests, the "pipemap" table
implements a pipeline of lookup tables. The name of the table
specifies the pipeline as a sequence of tables. For example, the
following prevents SMTP mail to system accounts that have "nologin"
as their login shell:
/etc/postfix/main.cf:
local_recipient_maps =
pipemap:{unix:passwd.byname, pcre:/etc/postfix/no-nologin.pcre}
alias_maps
/etc/postfix/no-nologin.pcre:
!/nologin/ whatever
Each "pipemap:" query is given to the first table. Each table
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 entire pipeline produces no result.
A future version may support pipemap:/path/to/file to load a list
of lookup tables from file.
[Feature 20140924] Support for unionmap, with the same syntax as
pipemap. This sends a query to all tables, and concatenates non-empty
results, separated by comma.
[Feature 20131121] The "static" lookup table now supports whitespace
when invoked as "static:{ text with whitespace }", so that it can
be used, for example, at the end of smtpd_mumble_restrictions as
"check_mumble_access static:{reject text...}".
[Feature 20141126] "inline:{key=value, { key = text with comma/space}}"
avoids the need to create a database for just a few entries.
Major changes - delivery status notifications
---------------------------------------------
[Feature 20140321] Delivery status filter support, to replace the
delivery status codes and explanatory text of successful or
unsuccessful deliveries by Postfix mail delivery agents.
This was originally implemented for sites that want to turn certain
soft delivery errors into hard delivery errors, but it can also be
used to censor out information from delivery confirmation reports.
This feature is implemented as a filter that replaces the three-number
enhanced status code and descriptive text in Postfix delivery agent
success, bounce, or defer messages. Note: this will not override
"soft_bounce=yes", and this will not change a successful delivery
status into an unsuccessful status or vice versa.
The first example turns specific soft TLS errors into hard
errors, by overriding the first number in the enhanced status code.
/etc/postfix/main.cf:
smtp_delivery_status_filter = pcre:/etc/postfix/smtp_dsn_filter
/etc/postfix/smtp_dsn_filter:
/^4(\.\d+\.\d+ TLS is required, but host \S+ refused to start TLS: .+)/ 5$1
/^4(\.\d+\.\d+ TLS is required, but was not offered by host .+)/ 5$1
The second example removes the destination command name and file
name from local(8) successful delivery reports, so that they will
not be reported when a sender requests confirmation of delivery.
/etc/postfix/main.cf:
local_delivery_status_filter = pcre:/etc/postfix/local_dsn_filter
/etc/postfix/local_dsn_filter:
/^(2\S+ delivered to file).+/ $1
/^(2\S+ delivered to command).+/ $1
This feature is supported in the lmtp(8), local(8), pipe(8), smtp(8)
and virtual(8) delivery agents. That is, all delivery agents that
actually deliver mail. It will not be implemented in the error and
retry pseudo-delivery agents.
The new main.cf parameters and default values are:
default_delivery_status_filter =
lmtp_delivery_status_filter = $default_delivery_status_filter
local_delivery_status_filter = $default_delivery_status_filter
pipe_delivery_status_filter = $default_delivery_status_filter
smtp_delivery_status_filter = $default_delivery_status_filter
virtual_delivery_status_filter = $default_delivery_status_filter
See the postconf(5) manpage for more details.
[Incompat 20140618] The pipe(8) delivery agent will now log a limited
amount of command output upon successful delivery, and will report
that output in "SUCCESS" delivery status reports. This is another
good reason to disable inbound DSN requests at the Internet perimeter.
[Feature 20140907] With "confirm_delay_cleared = yes", Postfix
informs the sender when delayed mail leaves the queue (this is in
addition to the delay_warning_time feature that warns when mail is
still queued). This feature is disabled by default, because it can
result in a sudden burst of notifications when the queue drains at
the end of a prolonged network outage.
Major changes - dns
-------------------
[Feature 20141128] Support for DNS server reply filters in the
Postfix SMTP/LMTP client and SMTP server. This helps to work around
mail delivery problems with sites that have incorrect DNS information.
Note: this has no effect on the implicit DNS lookups that are made
by nsswitch.conf or equivalent mechanisms.
This feature renders each lookup result as one line of text in
standard zone-file format as shown below. The class field is always
"IN", the preference field exists only for MX records, the names
of hosts, domains, etc. end in ".", and those names are in ASCII
form (xn--mumble form for internationalized domain names).
name ttl class type preference value
---------------------------------------------------------
postfix.org. 86400 IN MX 10 mail.cloud9.net.
Typically, one would match this text with a regexp: or pcre: table.
When a match is found, the table lookup result specifies an action.
By default, the table query and the action name are case-insensitive.
Currently, only the IGNORE action is implemented.
For safety reasons, Postfix logs a warning or defers mail delivery
when a DNS reply filter removes all lookup results from a successful
query.
The Postfix SMTP/LMTP client uses the smtp_dns_reply_filter and
lmtp_dns_reply_filter features only for Postfix SMTP client lookups
of MX, A, and AAAAA records to locate a remote SMTP or LMTP server,
including lookups that implement the features reject_unverified_sender
and reject_unverified_recipient. The filters are not used for lookups
made through nsswitch.conf and similar mechanisms.
The Postfix SMTP server uses the smtpd_dns_reply_filter feature
only for Postfix SMTP server lookups of MX, A, AAAAA, and TXT records
to implement the features reject_unknown_helo_hostname,
reject_unknown_sender_domain, reject_unknown_recipient_domain,
reject_rbl_*, and reject_rhsbl_*. The filter is not used for lookups
made through nsswitch.conf and similar mechanisms, such as lookups
of the remote SMTP client name.
[Feature 20141126] Nullmx support (MX records with a null hostname).
This change affects error messages only. The Postfix SMTP client
already bounced mail for such domains, and the Postfix SMTP server
already rejected such domains with reject_unknown_sender/recipient_domain.
This feature introduces a new SMTP server configuration parameter
nullmx_reject_code (default: 556).
Major changes - dynamic linking
-------------------------------
[Feature 20140530] Support to build Postfix with Postfix
dynamically-linked libraries, and with dynamically-loadable database
clients. These MUST NOT be used by non-Postfix programs. Postfix
dynamically-linked libraries introduce minor runtime overhead and
result in smaller Postfix executable files. Dynamically-loadable
database clients are useful when you distribute or install pre-compiled
packages. Postfix 3.0 supports dynamic loading for CDB, LDAP, LMDB,
MYSQL, PCRE, PGSQL, SDBM, and SQLITE database clients.
This implementation is based on Debian code by LaMont Jones, initially
ported by Viktor Dukhovni. Currently, support exists for recent
versions of Linux, FreeBSD, MacOS X, and for the ancient Solaris 9.
To support Postfix dynamically-linked libraries and dynamically-loadable
database clients, the Postfix build procedure had to be changed
(specifically, the files makedefs and Makefile.in, and the files
postfix-install and post-install that install or update Postfix).
[Incompat 20140530] The Postfix 3.0 build procedure expects that
you specify database library dependencies with variables named
AUXLIBS_CDB, AUXLIBS_LDAP, etc. With Postfix 3.0 and later, the
old AUXLIBS variable still supports building a statically-loaded
CDB etc. database client, but only the new AUXLIBS_CDB etc. variables
support building a dynamically-loaded or statically-loaded CDB etc.
database client. See CDB_README, LDAP_README, etc. for details.
Failure to follow this advice will defeat the purpose of dynamic
database client loading. Every Postfix executable file will have
database library dependencies. And that was exactly what dynamic
database client loading was meant to avoid.
Major changes - future proofing
-------------------------------
[Cleanup 20141224] The changes described here have no visible effect
on Postfix behavior, but they make Postfix code easier to maintain,
and therefore make new functionality easier to add.
* Compile-time argument typechecks of non-printf/scanf-like variadic
function argument lists.
* Deprecating the use of "char *" for non-text purposes such as
memory allocation and pointers to application context for call-back
functions. This dates from long-past days before void * became
universally available.
* Replace integer types for counters and sizes with size_t or ssize_t
equivalents. This eliminates some wasteful 64<->32bit conversions
on 64-bit systems.
Major changes - installation pathnames
--------------------------------------
[Incompat 20140625] For compliance with file system policies, some
non-executable files have been moved from $daemon_directory to the
directory specified with the new meta_directory configuration
parameter which has the same default value as the config_directory
parameter. This change affects non-executable files that are shared
between multiple Postfix instances such as postfix-files, dynamicmaps.cf,
and multi-instance template files.
For backwards compatibility with Postfix 2.6 .. 2.11, specify
"meta_directory = $daemon_directory" in main.cf before installing
or upgrading Postfix, or specify "meta_directory = /path/name" on
the "make makefiles", "make install" or "make upgrade" command line.
Major changes - milter
----------------------
[Feature 20140928] Support for per-Milter settings that override
main.cf parameters. For details see the section "Advanced policy
client configuration" in the SMTPD_POLICY_README document.
Here is an example that uses both old and new syntax:
smtpd_milters = { inet:127.0.0.1:port1, default_action=accept, ... },
inet:127.0.0.1:port2, ...
The supported attribute names are: command_timeout, connect_timeout,
content_timeout, default_action, and protocol. These have the same
names as the corresponding main.cf parameters, without the "milter_"
prefix.
The per-milter settings are specified as attribute=value pairs
separated by comma or space; specify { name = value } to allow
spaces around the "=" or within an attribute value.
[Feature 20141018] DMARC compatibility: when a Milter inserts a
header ABOVE Postfix's own Received: header, Postfix no longer
exposes its own Received: header to Milters (violating protocol)
and Postfix no longer hides the Milter-inserted header from Milters
(wtf).
Major changes - parameter syntax
--------------------------------
[Feature 20140921] In preparation for configurable mail headers and
logging, new main.cf support for if-then-else expressions:
${name?{text1}:{text2}}
and for logical expressions:
${{text1}=={text2}?{text3}:{text4}}
${{text1}!={text2}?{text3}:{text4}}
Whitespace before and after {text} is ignored. This can help to
make complex expressions more readable. See the postconf(5) manpage
for further details.
[Feature 20140928] Support for whitespace in daemon command-line
arguments. For details, see the "Command name + arguments" section
in the master(5) manpage. Example:
smtpd -o { parameter = value containing whitespace } ...
The { ... } form is also available for non-option command-line
arguments in master.cf, for example:
pipe ... argv=command { argument containing whitespace } ...
In both cases, whitespace immediately after "{" and before "}"
is ignored.
[Feature 20141005] Postfix import_environment and export_environment
now allow "{ name=value }" to protect whitespace in attribute values.
[Feature 20141006] The new message_drop_header parameter replaces
a hard-coded table that specifies what message headers the cleanup
daemon will remove. The list of supported header names covers RFC
5321, 5322, MIME RFCs, and some historical names.
Major changes - pipe daemon
---------------------------
[Incompat 20140618] The pipe(8) delivery agent will now log a limited
amount of command output upon successful delivery, and will report
that output in "SUCCESS" delivery status reports. This is another
good reason to disable inbound DSN requests at the Internet perimeter.
Major changes - policy client
-----------------------------
[Feature 20140703] This release introduces three new configuration
parameters that control error recovery for failed SMTPD policy
requests.
* smtpd_policy_service_default_action (default: 451 4.3.5 Server
configuration problem): The default action when an SMTPD policy
service request fails.
* smtpd_policy_service_try_limit (default: 2): The maximal number
of attempts to send an SMTPD policy service request before
giving up. This must be a number greater than zero.
* smtpd_policy_service_retry_delay (default: 1s): The delay between
attempts to resend a failed SMTPD policy service request. This
must be a number greater than zero.
See postconf(5) for details and limitations.
[Feature 20140928] Support for per-policy service settings that
override main.cf parameters. For details see the section "Different
settings for different Milter applications" in the MILTER_README
document.
Here is an example that uses both old and new syntax:
smtpd_recipient_restrictions = ...
check_policy_service { inet:127.0.0.1:port3, default_action=DUNNO }
check_policy_service inet:127.0.0.1:port4
...
The per-policy service settings are specified as attribute=value pairs
separated by comma or space; specify { name = value } to allow
spaces around the "=" or within an attribute value.
The supported attribute names are: default_action, max_idle, max_ttl,
request_limit, retry_delay, timeout, try_limit. These have the same
names as the corresponding main.cf parameters, without the
"smtpd_policy_service_" prefix.
[Feature 20140505] A client port attribute was added to the policy
delegation protocol.
[Feature 20140630] New smtpd_policy_service_request_limit feature to
limit the number of requests per Postfix SMTP server policy connection.
This is a workaround to avoid error-recovery delays with policy
servers that cannot maintain a persistent connection.
Major changes - position-independent executables
------------------------------------------------
[Feature 20150205] Preliminary support for building position-independent
executables (PIE), tested on Fedora Core 20, Ubuntu 14.04, FreeBSD
9 and 10, and NetBSD 6. Specify:
$ make makefiles pie=yes ...other arguments...
On some systems, PIE is used by the ASLR exploit mitigation technique
(ASLR = Address-Space Layout Randomization). Whether specifying
"pie=yes" has any effect at all depends on the compiler. Reportedly,
some compilers always produce PIE executables.
Major changes - postscreen
--------------------------
[Feature 20140501] Configurable time limit (postscreen_dnsbl_timeout)
for DNSBL or DNSWL lookups. This is separate from the timeouts in
the dnsblog(8) daemon which are controlled by system resolver(3)
routines.
Major changes - session fingerprint
-----------------------------------
[Feature 20140801] The Postfix SMTP server now logs at the end of
a session how many times an SMTP command was successfully invoked,
followed by the total number of invocations if some invocations
were unsuccessful.
This logging will enough to diagnose many problems without using
verbose logging or network sniffer.
Normal session, no TLS:
disconnect from name[addr] ehlo=1 mail=1 rcpt=1 data=1 quit=1
Normal session. with TLS:
disconnect from name[addr] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1
All recipients rejected, no ESMTP command pipelining:
disconnect from name[addr] ehlo=1 mail=1 rcpt=0/1 quit=1
All recipients rejected, with ESMTP command pipelining:
disconnect from name[addr] ehlo=1 mail=1 rcpt=0/1 data=0/1 rset=1 quit=1
Password guessing bot, hangs up without QUIT:
disconnect from name[addr] ehlo=1 auth=0/1
Mis-configured client trying to use TLS wrappermode on port 587:
disconnect from name[addr] unknown=0/1
Logfile analyzers can trigger on the presence of "/". It indicates
that Postfix rejected at least one command.
[Feature 20150118] As a late addition, the SMTP server now also
logs the total number of commands (as "commands=x/y") even when the
client did not send any commands. This helps logfile analyzers to
recognize sessions without commands.
Major changes - smtp client
---------------------------
[Feature 20141227] The new smtp_address_verify_target parameter
(default: rcpt) determines what protocol stage decides if a recipient
is valid. Specify "data" for servers that reject recipients after
the DATA command.
Major changes - smtputf8
------------------------
[Incompat 20141001] The default settings have changed for
append_dot_mydomain (new: no, old: yes), master.cf chroot (new:
n, old: y), and smtputf8 (new: yes, old: no).
[Incompat 20140714] After upgrading Postfix, "postfix reload" (or
start/stop) is required. Several Postfix-internal protocols have
been extended to support SMTPUTF8. Failure to reload or restart
will result in mail staying queued, while Postfix daemons log
warning messages about unexpected attributes.
[Feature 20140715] Support for Email Address Internationalization
(EAI) as defined in RFC 6531..6533. This supports UTF-8 in SMTP/LMTP
sender addresses, recipient addresses, and message header values.
The implementation is based on initial work by Arnt Gulbrandsen
that was funded by CNNIC.
See SMTPUTF8_README for a description of Postfix SMTPUTF8 support.
[Feature 20150112] UTF-8 Casefolding support for Postfix lookup
tables and matchlists (mydestination, relay_domains, etc.). This
is enabled only with "smtpuf8 = yes".
[Feature 20150112] With smtputf8_enable=yes, SMTP commands with
UTF-8 syntax errors are rejected, table lookup results with invalid
UTF-8 syntax are handled as configuration errors, and UTF-8 syntax
errors in policy server replies result in execution of the policy
server's default action.
Major changes - tls support
---------------------------
(see "Major changes - delivery status notifications" above for
turning 4XX soft errors into 5XX bounces when a remote SMTP server
does not offer STARTTLS support).
[Feature 20140209] the Postfix SMTP client now also falls back to
plaintext when TLS fails AFTER the TLS protocol handshake.
[Feature 20140218] The Postfix SMTP client now requires that a queue
file is older than $minimal_backoff_time, before falling back from
failed TLS to plaintext (both during or after the TLS handshake).
[Feature 20141021] Per IETF TLS WG consensus, the tls_session_ticket_cipher
default setting was changed from aes-128-cbc to aes-256-cbc.
[Feature 20150116] TLS wrappermode support in the Postfix smtp(8)
client (new smtp_tls_wrappermode parameter) and in posttls-finger(1)
(new -w option). There still is life in that deprecated protocol,
and people should not have to jump hoops with stunnel.
@
text
@d13 1
a13 1
Managing main.cf:
d15 1
a15 1
postconf [-dfhHnopvx] [-c config_dir] [-C class,...] [parameter ...]
d23 1
a23 1
Managing master.cf service entries:
d33 1
a33 1
Managing master.cf service fields:
d35 1
a35 1
postconf -F [-fhHovx] [-c config_dir] [service[/type[/field]] ...]
d39 1
a39 1
Managing master.cf service parameters:
d41 1
a41 1
postconf -P [-fhHovx] [-c config_dir] [service[/type[/parameter]] ...]
d47 1
a47 1
Managing bounce message templates:
d53 1
a53 5
Managing TLS features:
postconf -T mode [-v] [-c config_dir]
Managing other configuration:
d59 2
a60 2
figuration parameters, and warns about possible mis-typed parameter
names (Postfix 2.9 and later). It can also change main.cf configura-
d66 2
a67 2
-a List the available SASL server plug-in types. The SASL plug-in
type is selected with the smtpd_sasl_type configuration parame-
d70 1
a70 1
cyrus This server plug-in is available when Postfix is built
d75 1
a75 1
server, and is available when Postfix is built with any
d80 3
a82 3
-A List the available SASL client plug-in types. The SASL plug-in
type is selected with the smtp_sasl_type or lmtp_sasl_type con-
figuration parameters by specifying one of the names listed
d85 1
a85 1
cyrus This client plug-in is available when Postfix is built
d92 1
a92 1
ery status notification (DSN) messages, replacing $name expres-
d96 1
a96 1
at the end of the postconf(1) command line, or specify a file
d99 2
a100 2
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
d110 1
a110 1
When displaying main.cf parameters, select only parameters from
d128 2
a129 2
-d Print main.cf default parameter settings instead of actual set-
tings. Specify -df to fold long lines for human readability
d132 2
a133 2
-e Edit the main.cf configuration file, and update parameter set-
tings with the "name=value" pairs on the postconf(1) command
d136 2
a137 2
With -M, edit the master.cf configuration file, and replace one
or more service entries with new values as specified with "ser-
d140 4
a143 4
With -F, edit the master.cf configuration file, and replace one
or more service fields with new values as specied with "ser-
vice/type/field=value" on the postconf(1) command line. Cur-
rently, the "command" field contains the command name and com-
d148 3
a150 3
With -P, edit the master.cf configuration file, and add or
update one or more service parameter settings (-o parame-
ter=value settings) with new values as specied with "ser-
d154 1
a154 1
into place. Specify quotes to protect special characters and
d157 1
a157 1
The -e option is no longer needed with Postfix version 2.8 and
d166 2
a167 2
and all fields), formatted as "service/type/field=value", one
per line. Specify -Ff to fold long lines.
d169 3
a171 3
Specify one or more "service/type/field" instances on the post-
conf(1) command line to limit the output to fields of interest.
Trailing parameter name or service type fields that are omitted
d176 1
a176 1
-h Show parameter or attribute values without the "name = " label
a178 5
-H Show parameter or attribute names without the " = value" that
normally follows the name.
This feature is available with Postfix 3.1 and later.
d209 3
a211 3
cidr A table that associates values with Classless
Inter-Domain Routing (CIDR) patterns. This is described
in cidr_table(5).
a227 9
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;
whitespace after "{" and before "}" is ignored. Inline
tables eliminate the need to create a database file for
just a few fixed elements. See also the static: map
type.
a255 11
pipemap (read-only)
A lookup table that constructs a pipeline of tables.
Example: "pipemap:{type_1:name_1, ..., type_n:name_n}".
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,
individual maps are separated with comma or whitespace.
a258 9
randmap (read-only)
An in-memory table that performs random selection. Exam-
ple: "randmap:{result_1, ..., result_n}". 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 whitespace. To give a
specific result more weight, specify it multiple times.
d278 1
a278 4
bar as lookup result. Specify "static:{ text with white-
space }" when the result contains whitespace; this form
ignores whitespace after "{" and before "}". See also the
inline: map.
d284 3
a286 3
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
a288 5
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.
d338 7
a344 6
vices and all parameters), formatted as "service/type/parame-
ter=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
d350 2
a351 2
Display the templates for text that appears at the beginning of
delivery status notification (DSN) messages, without expanding
d355 1
a355 1
at the end of the postconf(1) command line, or specify a file
d358 2
a359 2
To force selection of the built-in templates, specify an empty
template file name on the postconf(1) command line (in shell
d364 1
a364 22
-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
d367 1
a367 1
-x Expand $name in main.cf or master.cf parameter values. The
d372 1
a372 1
-X Edit the main.cf configuration file, and remove the parameters
d376 2
a377 2
With -M, edit the master.cf configuration file, and remove one
or more service entries as specified with "service/type" on the
d380 1
a380 1
With -P, edit the master.cf configuration file, and remove one
d389 1
a389 1
There is no postconf(1) command to perform the reverse opera-
d392 1
a392 1
This feature is available with Postfix 2.10 and later. Support
d400 2
a401 2
With -M, edit the master.cf configuration file, and comment out
one or more service entries as specified with "service/type" on
d408 1
a408 1
There is no postconf(1) command to perform the reverse opera-
d411 1
a411 1
This feature is available with Postfix 2.6 and later. Support
d422 1
a422 1
The following main.cf parameters are especially relevant to this pro-
d425 1
a425 1
The text below provides only a parameter summary. See postconf(5) for
d429 1
a429 1
The default location of the Postfix main.cf and master.cf con-
d433 1
a433 1
Pathname of a configuration file with bounce message templates.
d440 3
a442 3
bounce(5), bounce template file format
master(5), master.cf configuration file syntax
postconf(5), main.cf configuration file syntax
a455 5
Wietse Venema
Google, Inc.
111 8th Avenue
New York, NY 10011, USA
@
1.1.1.8.14.1
log
@Pull up the following, requeste by kim in ticket #1779:
external/ibm-public/postfix/dist/README_FILES/BDAT_README up to 1.1.1.2
external/ibm-public/postfix/dist/README_FILES/MAILLOG_README up to 1.1.1.4
external/ibm-public/postfix/dist/README_FILES/POSTSCREEN_3_5_README up to 1.1.1.1
external/ibm-public/postfix/dist/html/BDAT_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/html/MAILLOG_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/makedefs.1.html up to 1.1.1.3
external/ibm-public/postfix/dist/html/postlogd.8.html up to 1.1.1.3
external/ibm-public/postfix/dist/html/POSTSCREEN_3_5_README.html up to 1.1.1.2
external/ibm-public/postfix/dist/html/postfix-doc.css up to 1.1.1.1
external/ibm-public/postfix/dist/man/man1/makedefs.1 up to 1.3
external/ibm-public/postfix/dist/man/man8/postlogd.8 up to 1.3
external/ibm-public/postfix/dist/mantools/missing-proxy-read-maps up to 1.1.1.3
external/ibm-public/postfix/dist/mantools/spelldiff up to 1.1.1.1
external/ibm-public/postfix/dist/mantools/check-double-cc up to 1.1.1.2
external/ibm-public/postfix/dist/mantools/check-double-install-proto-text up to 1.1.1.2
external/ibm-public/postfix/dist/mantools/check-double-proto-html up to 1.1.1.2
external/ibm-public/postfix/dist/mantools/comment.c up to 1.2
external/ibm-public/postfix/dist/mantools/check-postfix-files up to 1.1.1.2
external/ibm-public/postfix/dist/mantools/check-spell-cc up to 1.1.1.2
external/ibm-public/postfix/dist/mantools/check-spell-install-proto-text up to 1.1.1.2
external/ibm-public/postfix/dist/mantools/check-spell-proto-html up to 1.1.1.2
external/ibm-public/postfix/dist/mantools/deroff up to 1.1.1.1
external/ibm-public/postfix/dist/mantools/find-double up to 1.1.1.1
external/ibm-public/postfix/dist/mantools/check-double-history up to 1.1.1.1
external/ibm-public/postfix/dist/mantools/check-spell-history up to 1.1.1.1
external/ibm-public/postfix/dist/mantools/check-table-proto up to 1.1.1.1
external/ibm-public/postfix/dist/proto/BDAT_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/proto/MAILLOG_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/POSTSCREEN_3_5_README.html up to 1.1.1.2
external/ibm-public/postfix/dist/proto/stop.double-cc up to 1.1.1.2
external/ibm-public/postfix/dist/proto/stop.double-install-proto-text up to 1.1.1.1
external/ibm-public/postfix/dist/proto/stop.double-proto-html up to 1.1.1.2
external/ibm-public/postfix/dist/proto/stop.spell-cc up to 1.1.1.2
external/ibm-public/postfix/dist/proto/stop.spell-proto-html up to 1.1.1.2
external/ibm-public/postfix/dist/proto/stop.double-history up to 1.1.1.1
external/ibm-public/postfix/dist/proto/stop.spell-history up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/bounce_notify_util_tester.c up to 1.2
external/ibm-public/postfix/dist/src/bounce/logfile-no-msgid-no-eoh-event up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/logfile-no-msgid-with-eoh-event up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/logfile-with-msgid-no-eoh-event up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/logfile-with-msgid-with-eoh-event up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/logfile-with-msgid-with-filter up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/logfile-with-msgid-with-long-line up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/msgfile-no-msgid-no-eoh-event up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/msgfile-no-msgid-with-eoh-event up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/msgfile-with-msgid-no-eoh-event up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/msgfile-with-msgid-with-eoh-event up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/obs_template_test.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/msgfile-with-msgid-with-filter up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/msgfile-with-msgid-with-long-line up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/no-msgid-no-eoh-event-no-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/no-msgid-no-eoh-event-with-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/no-msgid-with-eoh-event-no-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/no-msgid-with-eoh-event-with-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/with-msgid-no-eoh-event-no-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/with-msgid-no-eoh-event-with-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/with-msgid-with-eoh-event-no-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/with-msgid-with-eoh-event-with-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/with-msgid-with-filter-no-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/with-msgid-with-filter-with-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/with-msgid-with-long-line-no-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/bounce/with-msgid-with-long-line-with-thread.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in13e up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in13f up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in13g up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in13h up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in13i up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref13e up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref13f up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref13g up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref13h up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref13i up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/test-queue-file13e up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/test-queue-file13f up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/test-queue-file13g up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/test-queue-file13h up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/test-queue-file13i up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in17a up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in17b up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in17c up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in17d up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in17e up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in17f up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.in17g up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17a1 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17a2 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17b1 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17b2 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17c1 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17c2 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17d1 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17d2 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17e1 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17e2 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17f1 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17f2 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17g1 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref17g2 up to 1.1.1.1
external/ibm-public/postfix/dist/src/cleanup/test-queue-file17 up to 1.1.1.1
external/ibm-public/postfix/dist/src/dns/dns_str_resflags.c up to 1.3
external/ibm-public/postfix/dist/src/dns/dns_sec.c up to 1.2
external/ibm-public/postfix/dist/src/global/header_body_checks_strip.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/info_log_addr_form.c up to 1.2
external/ibm-public/postfix/dist/src/global/info_log_addr_form.h up to 1.2
external/ibm-public/postfix/dist/src/global/mail_addr_crunch.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/mail_addr_crunch.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/mail_addr_find.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/map_search.c up to 1.4
external/ibm-public/postfix/dist/src/global/map_search.h up to 1.2
external/ibm-public/postfix/dist/src/global/mail_addr_find.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/mail_addr_form.c up to 1.2
external/ibm-public/postfix/dist/src/global/mail_addr_form.h up to 1.2
external/ibm-public/postfix/dist/src/global/mail_addr_map.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/maillog_client.c up to 1.3
external/ibm-public/postfix/dist/src/global/maillog_client.h up to 1.2
external/ibm-public/postfix/dist/src/global/map_search.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/global/normalize_mailhost_addr.c up to 1.3
external/ibm-public/postfix/dist/src/global/normalize_mailhost_addr.h up to 1.2
external/ibm-public/postfix/dist/src/global/off_cvt.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/off_cvt.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/quote_822_local.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/global/quote_822_local.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/global/quote_flags.c up to 1.2
external/ibm-public/postfix/dist/src/global/reject_deliver_request.c up to 1.2
external/ibm-public/postfix/dist/src/global/compat_level.c up to 1.3
external/ibm-public/postfix/dist/src/global/compat_level.h up to 1.3
external/ibm-public/postfix/dist/src/global/test_main.c up to 1.2
external/ibm-public/postfix/dist/src/global/compat_level_convert.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/compat_level_convert.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/compat_level_expand.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/compat_level_expand.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/config_known_tcp_ports.c up to 1.2
external/ibm-public/postfix/dist/src/global/config_known_tcp_ports.h up to 1.2
external/ibm-public/postfix/dist/src/global/config_known_tcp_ports.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/delivered_hdr.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/hfrom_format.c up to 1.2
external/ibm-public/postfix/dist/src/global/hfrom_format.h up to 1.2
external/ibm-public/postfix/dist/src/global/hfrom_format.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/login_sender_match.c up to 1.2
external/ibm-public/postfix/dist/src/global/login_sender_match.h up to 1.2
external/ibm-public/postfix/dist/src/global/login_sender_match.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/global/sasl_mech_filter.c up to 1.2
external/ibm-public/postfix/dist/src/global/sasl_mech_filter.h up to 1.2
external/ibm-public/postfix/dist/src/global/test_main.h up to 1.2
external/ibm-public/postfix/dist/src/master/dgram_server.c up to 1.3
external/ibm-public/postfix/dist/src/postconf/extract_cfg.sh up to 1.1.1.1
external/ibm-public/postfix/dist/src/postconf/test64.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/postconf/test65.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/postconf/test66.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/postconf/test67.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/postconf/test68.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/postconf/test69.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/postconf/test70.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/postconf/test71.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/postmap/file_test.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/postmap/file_test.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/postmap/quote_test.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/postmap/quote_test.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/postmap/lmdb_abb up to 1.1.1.1
external/ibm-public/postfix/dist/src/postmap/lmdb_abb.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/smtp/smtp_misc.c up to 1.2
external/ibm-public/postfix/dist/src/smtp/smtp_map11.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/smtpd/smtpd_addr_valid.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtpd/smtpd_addr_valid.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/tls/bad-back-to-back-keys.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/bad-back-to-back-keys.pem.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/bad-ec-cert-before-key.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/bad-ec-cert-before-key.pem.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/bad-key-cert-mismatch.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/bad-key-cert-mismatch.pem.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/bad-rsa-key-last.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/bad-rsa-key-last.pem.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/ecca-cert.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/ecca-pkey.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/ecee-cert.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/ecee-pkey.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/ecroot-cert.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/ecroot-pkey.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/good-mixed-keyfirst.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/good-mixed-keyfirst.pem.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/good-mixed-keylast.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/good-mixed-keylast.pem.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/good-mixed-keymiddle.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/good-mixed-keymiddle.pem.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/goodchains.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/goodchains.pem.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/mkcert.sh up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/rsaca-cert.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/rsaca-pkey.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/rsaee-cert.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/rsaee-pkey.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/rsaroot-cert.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/rsaroot-pkey.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/tls_proxy_client_misc.c up to 1.4
external/ibm-public/postfix/dist/src/tls/tls_proxy_client_print.c up to 1.4
external/ibm-public/postfix/dist/src/tls/tls_proxy_client_scan.c up to 1.4
external/ibm-public/postfix/dist/src/tls/tls_proxy_context_print.c up to 1.3
external/ibm-public/postfix/dist/src/tls/tls_proxy_context_scan.c up to 1.3
external/ibm-public/postfix/dist/src/tls/tls_proxy_server_print.c up to 1.3
external/ibm-public/postfix/dist/src/tls/tls_proxy_server_scan.c up to 1.3
external/ibm-public/postfix/dist/src/tls/warn-mixed-multi-key.pem up to 1.1.1.1
external/ibm-public/postfix/dist/src/tls/warn-mixed-multi-key.pem.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/trivial-rewrite/transport.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/trivial-rewrite/transport.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/mkmap_db.c up to 1.2
external/ibm-public/postfix/dist/src/util/mkmap.h up to 1.2
external/ibm-public/postfix/dist/src/util/argv_attr.h up to 1.3
external/ibm-public/postfix/dist/src/util/argv_attr_print.c up to 1.3
external/ibm-public/postfix/dist/src/util/argv_attr_scan.c up to 1.3
external/ibm-public/postfix/dist/src/util/byte_mask.c up to 1.2
external/ibm-public/postfix/dist/src/util/byte_mask.h up to 1.2
external/ibm-public/postfix/dist/src/util/byte_mask.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/byte_mask.ref0 up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/byte_mask.ref1 up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/byte_mask.ref2 up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_file.c up to 1.3
external/ibm-public/postfix/dist/src/util/dict_cidr_file.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/logwriter.c up to 1.2
external/ibm-public/postfix/dist/src/util/dict_cidr_file.map up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_cidr_file.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_inline_file.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_pcre_file.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_pcre_file.map up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_pcre_file.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_pipe_test.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_pipe_test.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_random.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_random_file.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_regexp_file.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_regexp_file.map up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_regexp_file.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_static_file.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_thash.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_thash.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_union_test.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_union_test.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/logwriter.h up to 1.2
external/ibm-public/postfix/dist/src/util/miss_endif_cidr.map up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/miss_endif_cidr.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/miss_endif_pcre.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/miss_endif_re.map up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/miss_endif_regexp.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/msg_logger.c up to 1.3
external/ibm-public/postfix/dist/src/util/msg_logger.h up to 1.2
external/ibm-public/postfix/dist/src/util/split_qnameval.c up to 1.2
external/ibm-public/postfix/dist/src/util/unix_dgram_connect.c up to 1.3
external/ibm-public/postfix/dist/src/util/unix_dgram_listen.c up to 1.3
external/ibm-public/postfix/dist/src/util/vbuf_print_test.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/vbuf_print_test.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/vstream_test.in up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/vstream_test.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/vstring_test.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/sane_strtol.c up to 1.2
external/ibm-public/postfix/dist/src/util/argv_split_at.c up to 1.2
external/ibm-public/postfix/dist/src/util/dict_stream.c up to 1.2
external/ibm-public/postfix/dist/src/util/dict_inline_cidr.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_inline_pcre.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_inline_regexp.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/dict_stream.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/find_inet.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/hash_fnv.c up to 1.3
external/ibm-public/postfix/dist/src/util/hash_fnv.h up to 1.3
external/ibm-public/postfix/dist/src/util/known_tcp_ports.c up to 1.2
external/ibm-public/postfix/dist/src/util/known_tcp_ports.h up to 1.2
external/ibm-public/postfix/dist/src/util/known_tcp_ports.ref up to 1.1.1.1
external/ibm-public/postfix/dist/src/util/ldseed.c up to 1.2
external/ibm-public/postfix/dist/src/util/ldseed.h up to 1.2
external/ibm-public/postfix/dist/src/util/mystrtok.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/sane_strtol.h up to 1.2
external/ibm-public/postfix/dist/src/util/inet_addr_sizes.c up to 1.2
external/ibm-public/postfix/dist/src/util/inet_addr_sizes.h up to 1.2
external/ibm-public/postfix/dist/src/util/inet_prefix_top.c up to 1.2
external/ibm-public/postfix/dist/src/util/inet_prefix_top.h up to 1.2
external/ibm-public/postfix/dist/src/util/mkmap_cdb.c up to 1.2
external/ibm-public/postfix/dist/src/util/mkmap_dbm.c up to 1.2
external/ibm-public/postfix/dist/src/util/mkmap_fail.c up to 1.2
external/ibm-public/postfix/dist/src/util/mkmap_lmdb.c up to 1.2
external/ibm-public/postfix/dist/src/util/mkmap_open.c up to 1.2
external/ibm-public/postfix/dist/src/util/mkmap_sdbm.c up to 1.2
external/ibm-public/postfix/dist/src/postlogd/Makefile.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/postlogd/postlogd.c up to 1.3
external/ibm-public/postfix/dist/RELEASE_NOTES-3.1 up to 1.1.1.1
external/ibm-public/postfix/dist/RELEASE_NOTES-3.2 up to 1.1.1.1
external/ibm-public/postfix/dist/RELEASE_NOTES-3.3 up to 1.1.1.1
external/ibm-public/postfix/dist/RELEASE_NOTES-3.4 up to 1.1.1.1
external/ibm-public/postfix/dist/RELEASE_NOTES-3.5 up to 1.1.1.1
external/ibm-public/postfix/dist/RELEASE_NOTES-3.6 up to 1.1.1.1
external/ibm-public/postfix/dist/WISHLIST up to 1.1.1.2
external/ibm-public/postfix/dist/RELEASE_NOTES-3.7 up to 1.1.1.1
external/ibm-public/postfix/dist/README_FILES/CYRUS_README delete
external/ibm-public/postfix/dist/src/global/mkmap.h delete
external/ibm-public/postfix/dist/src/global/mkmap_cdb.c delete
external/ibm-public/postfix/dist/src/global/mkmap_db.c delete
external/ibm-public/postfix/dist/src/global/mkmap_dbm.c delete
external/ibm-public/postfix/dist/src/global/mkmap_fail.c delete
external/ibm-public/postfix/dist/src/global/mkmap_lmdb.c delete
external/ibm-public/postfix/dist/src/global/mkmap_open.c delete
external/ibm-public/postfix/dist/src/global/mkmap_sdbm.c delete
external/ibm-public/postfix/dist/src/smtp/map11_map delete
external/ibm-public/postfix/dist/src/tls/tls_proxy_print.c delete
external/ibm-public/postfix/dist/src/tls/tls_proxy_scan.c delete
external/ibm-public/postfix/dist/src/util/percentm.c delete
external/ibm-public/postfix/dist/src/util/percentm.h delete
external/ibm-public/postfix/Makefile.inc up to 1.31 (+patch)
external/ibm-public/postfix/dist/AAAREADME up to 1.1.1.4
external/ibm-public/postfix/dist/HISTORY up to 1.1.1.29
external/ibm-public/postfix/dist/INSTALL up to 1.1.1.9
external/ibm-public/postfix/dist/LICENSE up to 1.1.1.2
external/ibm-public/postfix/dist/Makefile up to 1.1.1.3
external/ibm-public/postfix/dist/Makefile.in up to 1.1.1.10
external/ibm-public/postfix/dist/Makefile.init up to 1.1.1.3
external/ibm-public/postfix/dist/RELEASE_NOTES up to 1.1.1.17
external/ibm-public/postfix/dist/TLS_ACKNOWLEDGEMENTS up to 1.1.1.2
external/ibm-public/postfix/dist/TLS_CHANGES up to 1.1.1.2
external/ibm-public/postfix/dist/TLS_LICENSE up to 1.1.1.2
external/ibm-public/postfix/dist/US_PATENT_6321267 up to 1.1.1.2
external/ibm-public/postfix/dist/makedefs up to 1.16
external/ibm-public/postfix/dist/postfix-env.sh up to 1.1.1.2
external/ibm-public/postfix/dist/postfix-install up to 1.8
external/ibm-public/postfix/dist/README_FILES/AAAREADME up to 1.1.1.6
external/ibm-public/postfix/dist/README_FILES/ADDRESS_CLASS_README up to 1.1.1.2
external/ibm-public/postfix/dist/README_FILES/ADDRESS_REWRITING_README up to 1.1.1.5
external/ibm-public/postfix/dist/README_FILES/ADDRESS_VERIFICATION_README up to 1.10
external/ibm-public/postfix/dist/README_FILES/BACKSCATTER_README up to 1.1.1.5
external/ibm-public/postfix/dist/README_FILES/BASIC_CONFIGURATION_README up to 1.1.1.6
external/ibm-public/postfix/dist/README_FILES/BUILTIN_FILTER_README up to 1.1.1.3
external/ibm-public/postfix/dist/README_FILES/COMPATIBILITY_README up to 1.1.1.3
external/ibm-public/postfix/dist/README_FILES/CONNECTION_CACHE_README up to 1.1.1.5
external/ibm-public/postfix/dist/README_FILES/DATABASE_README up to 1.1.1.9
external/ibm-public/postfix/dist/README_FILES/DB_README up to 1.1.1.3
external/ibm-public/postfix/dist/README_FILES/DEBUG_README up to 1.1.1.5
external/ibm-public/postfix/dist/README_FILES/FILTER_README up to 1.1.1.4
external/ibm-public/postfix/dist/README_FILES/FORWARD_SECRECY_README up to 1.1.1.5
external/ibm-public/postfix/dist/README_FILES/INSTALL up to 1.10
external/ibm-public/postfix/dist/README_FILES/IPV6_README up to 1.1.1.4
external/ibm-public/postfix/dist/README_FILES/LDAP_README up to 1.1.1.4
external/ibm-public/postfix/dist/README_FILES/LINUX_README up to 1.1.1.3
external/ibm-public/postfix/dist/README_FILES/LMDB_README up to 1.1.1.3
external/ibm-public/postfix/dist/README_FILES/MILTER_README up to 1.1.1.9
external/ibm-public/postfix/dist/README_FILES/MULTI_INSTANCE_README up to 1.1.1.7
external/ibm-public/postfix/dist/README_FILES/MYSQL_README up to 1.1.1.5
external/ibm-public/postfix/dist/README_FILES/OVERVIEW up to 1.1.1.5
external/ibm-public/postfix/dist/README_FILES/PCRE_README up to 1.1.1.3
external/ibm-public/postfix/dist/README_FILES/PGSQL_README up to 1.1.1.4
external/ibm-public/postfix/dist/README_FILES/POSTSCREEN_README up to 1.1.1.7
external/ibm-public/postfix/dist/README_FILES/QSHAPE_README up to 1.1.1.4
external/ibm-public/postfix/dist/README_FILES/RELEASE_NOTES up to 1.1.1.17
external/ibm-public/postfix/dist/README_FILES/SASL_README up to 1.1.1.11
external/ibm-public/postfix/dist/README_FILES/SCHEDULER_README up to 1.1.1.4
external/ibm-public/postfix/dist/README_FILES/SMTPD_ACCESS_README up to 1.1.1.6
external/ibm-public/postfix/dist/README_FILES/SMTPD_POLICY_README up to 1.1.1.7
external/ibm-public/postfix/dist/README_FILES/SMTPD_PROXY_README up to 1.1.1.6
external/ibm-public/postfix/dist/README_FILES/SMTPUTF8_README up to 1.1.1.3
external/ibm-public/postfix/dist/README_FILES/SOHO_README up to 1.1.1.4
external/ibm-public/postfix/dist/README_FILES/SQLITE_README up to 1.1.1.4
external/ibm-public/postfix/dist/README_FILES/STANDARD_CONFIGURATION_README up to 1.1.1.6
external/ibm-public/postfix/dist/README_FILES/STRESS_README up to 1.1.1.6
external/ibm-public/postfix/dist/README_FILES/TLS_LEGACY_README up to 1.1.1.3
external/ibm-public/postfix/dist/README_FILES/TLS_README up to 1.14
external/ibm-public/postfix/dist/README_FILES/TUNING_README up to 1.1.1.5
external/ibm-public/postfix/dist/README_FILES/VIRTUAL_README up to 1.1.1.3
external/ibm-public/postfix/dist/README_FILES/XCLIENT_README up to 1.1.1.4
external/ibm-public/postfix/dist/conf/LICENSE up to 1.1.1.2
external/ibm-public/postfix/dist/conf/TLS_LICENSE up to 1.1.1.2
external/ibm-public/postfix/dist/conf/access up to 1.1.1.8
external/ibm-public/postfix/dist/conf/aliases up to 1.1.1.5
external/ibm-public/postfix/dist/conf/canonical up to 1.1.1.5
external/ibm-public/postfix/dist/conf/generic up to 1.1.1.4
external/ibm-public/postfix/dist/conf/header_checks up to 1.1.1.6
external/ibm-public/postfix/dist/conf/main.cf up to 1.10
external/ibm-public/postfix/dist/conf/master.cf up to 1.11
external/ibm-public/postfix/dist/conf/post-install up to 1.4
external/ibm-public/postfix/dist/conf/postfix-files up to 1.9
external/ibm-public/postfix/dist/conf/postfix-script up to 1.4
external/ibm-public/postfix/dist/conf/postfix-tls-script up to 1.5
external/ibm-public/postfix/dist/conf/postmulti-script up to 1.3
external/ibm-public/postfix/dist/conf/relocated up to 1.1.1.3
external/ibm-public/postfix/dist/conf/transport up to 1.1.1.5
external/ibm-public/postfix/dist/conf/virtual up to 1.1.1.6
external/ibm-public/postfix/dist/html/ADDRESS_CLASS_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/html/ADDRESS_REWRITING_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/ADDRESS_VERIFICATION_README.html up to 1.11
external/ibm-public/postfix/dist/html/BACKSCATTER_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/BASIC_CONFIGURATION_README.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/BUILTIN_FILTER_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/CDB_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/COMPATIBILITY_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/CONNECTION_CACHE_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/CONTENT_INSPECTION_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/html/DATABASE_README.html up to 1.1.1.10
external/ibm-public/postfix/dist/html/DB_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/DEBUG_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/DSN_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/html/ETRN_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/FILTER_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/FORWARD_SECRECY_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/INSTALL.html up to 1.10
external/ibm-public/postfix/dist/html/IPV6_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/LDAP_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/LINUX_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/LMDB_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/LOCAL_RECIPIENT_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/html/MAILDROP_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/MEMCACHE_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/html/MILTER_README.html up to 1.1.1.9
external/ibm-public/postfix/dist/html/MULTI_INSTANCE_README.html up to 1.1.1.9
external/ibm-public/postfix/dist/html/MYSQL_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/Makefile.in up to 1.1.1.7
external/ibm-public/postfix/dist/html/NFS_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/html/OVERVIEW.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/PACKAGE_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/PCRE_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/PGSQL_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/POSTSCREEN_README.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/QSHAPE_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/RESTRICTION_CLASS_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/SASL_README.html up to 1.1.1.11
external/ibm-public/postfix/dist/html/SCHEDULER_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/SMTPD_ACCESS_README.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/SMTPD_POLICY_README.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/SMTPD_PROXY_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/SMTPUTF8_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/SOHO_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/SQLITE_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/STANDARD_CONFIGURATION_README.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/STRESS_README.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/TLS_LEGACY_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/TLS_README.html up to 1.15
external/ibm-public/postfix/dist/html/TUNING_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/UUCP_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/VERP_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/VIRTUAL_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/XCLIENT_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/XFORWARD_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/access.5.html up to 1.1.1.9
external/ibm-public/postfix/dist/html/aliases.5.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/anvil.8.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/bounce.5.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/bounce.8.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/canonical.5.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/cidr_table.5.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/cleanup.8.html up to 1.1.1.9
external/ibm-public/postfix/dist/html/defer.8.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/discard.8.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/dnsblog.8.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/error.8.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/flush.8.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/generic.5.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/header_checks.5.html up to 1.1.1.9
external/ibm-public/postfix/dist/html/index.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/ldap_table.5.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/lmdb_table.5.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/lmtp.8.html up to 1.1.1.12
external/ibm-public/postfix/dist/html/local.8.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/mailq.1.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/master.5.html up to 1.1.1.9
external/ibm-public/postfix/dist/html/master.8.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/memcache_table.5.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/mysql_table.5.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/newaliases.1.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/nisplus_table.5.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/oqmgr.8.html up to 1.1.1.9
external/ibm-public/postfix/dist/html/pcre_table.5.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/pgsql_table.5.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/pickup.8.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/pipe.8.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/postalias.1.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/postcat.1.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/postconf.1.html up to 1.1.1.11
external/ibm-public/postfix/dist/html/postconf.5.html up to 1.19
external/ibm-public/postfix/dist/html/postdrop.1.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/postfix-manuals.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/postfix-tls.1.html up to 1.1.1.3
external/ibm-public/postfix/dist/html/postfix-wrapper.5.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/postfix.1.html up to 1.1.1.9
external/ibm-public/postfix/dist/html/postkick.1.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/postlock.1.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/postlog.1.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/postmap.1.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/postmulti.1.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/postqueue.1.html up to 1.1.1.9
external/ibm-public/postfix/dist/html/postscreen.8.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/postsuper.1.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/posttls-finger.1.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/proxymap.8.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/qmgr.8.html up to 1.1.1.9
external/ibm-public/postfix/dist/html/qmqp-sink.1.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/qmqp-source.1.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/qmqpd.8.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/qshape.1.html up to 1.1.1.4
external/ibm-public/postfix/dist/html/regexp_table.5.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/relocated.5.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/scache.8.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/sendmail.1.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/showq.8.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/smtp-sink.1.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/smtp-source.1.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/smtp.8.html up to 1.1.1.12
external/ibm-public/postfix/dist/html/smtpd.8.html up to 1.1.1.13
external/ibm-public/postfix/dist/html/socketmap_table.5.html up to 1.1.1.5
external/ibm-public/postfix/dist/html/spawn.8.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/sqlite_table.5.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/tcp_table.5.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/tlsmgr.8.html up to 1.1.1.6
external/ibm-public/postfix/dist/html/tlsproxy.8.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/trace.8.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/transport.5.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/trivial-rewrite.8.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/verify.8.html up to 1.1.1.8
external/ibm-public/postfix/dist/html/virtual.5.html up to 1.1.1.7
external/ibm-public/postfix/dist/html/virtual.8.html up to 1.1.1.7
external/ibm-public/postfix/dist/man/Makefile.in up to 1.1.1.7
external/ibm-public/postfix/dist/man/man1/postalias.1 up to 1.4
external/ibm-public/postfix/dist/man/man1/postcat.1 up to 1.4
external/ibm-public/postfix/dist/man/man1/postconf.1 up to 1.4
external/ibm-public/postfix/dist/man/man1/postdrop.1 up to 1.4
external/ibm-public/postfix/dist/man/man1/postfix-tls.1 up to 1.3
external/ibm-public/postfix/dist/man/man1/postfix.1 up to 1.6
external/ibm-public/postfix/dist/man/man1/postkick.1 up to 1.3
external/ibm-public/postfix/dist/man/man1/postlock.1 up to 1.3
external/ibm-public/postfix/dist/man/man1/postlog.1 up to 1.5
external/ibm-public/postfix/dist/man/man1/postmap.1 up to 1.4
external/ibm-public/postfix/dist/man/man1/postmulti.1 up to 1.4
external/ibm-public/postfix/dist/man/man1/postqueue.1 up to 1.5
external/ibm-public/postfix/dist/man/man1/postsuper.1 up to 1.4
external/ibm-public/postfix/dist/man/man1/posttls-finger.1 up to 1.5
external/ibm-public/postfix/dist/man/man1/sendmail.1 up to 1.4
external/ibm-public/postfix/dist/man/man1/smtp-sink.1 up to 1.3
external/ibm-public/postfix/dist/man/man5/access.5 up to 1.4
external/ibm-public/postfix/dist/man/man5/aliases.5 up to 1.5
external/ibm-public/postfix/dist/man/man5/canonical.5 up to 1.4
external/ibm-public/postfix/dist/man/man5/cidr_table.5 up to 1.5
external/ibm-public/postfix/dist/man/man5/generic.5 up to 1.4
external/ibm-public/postfix/dist/man/man5/header_checks.5 up to 1.3
external/ibm-public/postfix/dist/man/man5/ldap_table.5 up to 1.5
external/ibm-public/postfix/dist/man/man5/lmdb_table.5 up to 1.3
external/ibm-public/postfix/dist/man/man5/master.5 up to 1.4
external/ibm-public/postfix/dist/man/man5/mysql_table.5 up to 1.5
external/ibm-public/postfix/dist/man/man5/pcre_table.5 up to 1.4
external/ibm-public/postfix/dist/man/man5/pgsql_table.5 up to 1.5
external/ibm-public/postfix/dist/man/man5/postconf.5 up to 1.19
external/ibm-public/postfix/dist/man/man5/regexp_table.5 up to 1.4
external/ibm-public/postfix/dist/man/man5/relocated.5 up to 1.3
external/ibm-public/postfix/dist/man/man5/socketmap_table.5 up to 1.3
external/ibm-public/postfix/dist/man/man5/sqlite_table.5 up to 1.4
external/ibm-public/postfix/dist/man/man5/tcp_table.5 up to 1.3
external/ibm-public/postfix/dist/man/man5/transport.5 up to 1.4
external/ibm-public/postfix/dist/man/man5/virtual.5 up to 1.5
external/ibm-public/postfix/dist/man/man8/anvil.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/bounce.8 up to 1.4
external/ibm-public/postfix/dist/man/man8/cleanup.8 up to 1.4
external/ibm-public/postfix/dist/man/man8/discard.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/dnsblog.8 up to 1.4
external/ibm-public/postfix/dist/man/man8/error.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/flush.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/local.8 up to 1.4
external/ibm-public/postfix/dist/man/man8/master.8 up to 1.4
external/ibm-public/postfix/dist/man/man8/oqmgr.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/pickup.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/pipe.8 up to 1.4
external/ibm-public/postfix/dist/man/man8/postscreen.8 up to 1.5
external/ibm-public/postfix/dist/man/man8/proxymap.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/qmgr.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/qmqpd.8 up to 1.4
external/ibm-public/postfix/dist/man/man8/scache.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/showq.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/smtp.8 up to 1.5
external/ibm-public/postfix/dist/man/man8/smtpd.8 up to 1.5
external/ibm-public/postfix/dist/man/man8/spawn.8 up to 1.4
external/ibm-public/postfix/dist/man/man8/tlsmgr.8 up to 1.3
external/ibm-public/postfix/dist/man/man8/tlsproxy.8 up to 1.5
external/ibm-public/postfix/dist/man/man8/trivial-rewrite.8 up to 1.4
external/ibm-public/postfix/dist/man/man8/verify.8 up to 1.4
external/ibm-public/postfix/dist/man/man8/virtual.8 up to 1.4
external/ibm-public/postfix/dist/mantools/ccformat up to 1.1.1.3
external/ibm-public/postfix/dist/mantools/check-postlink up to 1.1.1.3
external/ibm-public/postfix/dist/mantools/fixman up to 1.1.1.3
external/ibm-public/postfix/dist/mantools/make-relnotes up to 1.1.1.3
external/ibm-public/postfix/dist/mantools/make_soho_readme up to 1.1.1.4
external/ibm-public/postfix/dist/mantools/makemanidx up to 1.1.1.4
external/ibm-public/postfix/dist/mantools/man2html up to 1.1.1.5
external/ibm-public/postfix/dist/mantools/manlint up to 1.1.1.2
external/ibm-public/postfix/dist/mantools/manspell up to 1.1.1.2
external/ibm-public/postfix/dist/mantools/postconf2man up to 1.1.1.5
external/ibm-public/postfix/dist/mantools/postlink up to 1.1.1.13
external/ibm-public/postfix/dist/mantools/readme2html up to 1.1.1.2
external/ibm-public/postfix/dist/mantools/spell up to 1.1.1.3
external/ibm-public/postfix/dist/mantools/srctoman up to 1.1.1.3
external/ibm-public/postfix/dist/proto/ADDRESS_CLASS_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/proto/ADDRESS_REWRITING_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/proto/ADDRESS_VERIFICATION_README.html up to 1.11
external/ibm-public/postfix/dist/proto/BACKSCATTER_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/proto/BASIC_CONFIGURATION_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/proto/BUILTIN_FILTER_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/CDB_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/COMPATIBILITY_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/CONNECTION_CACHE_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/proto/CONTENT_INSPECTION_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/proto/DATABASE_README.html up to 1.1.1.10
external/ibm-public/postfix/dist/proto/DB_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/DEBUG_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/proto/DSN_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/proto/ETRN_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/proto/FILTER_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/proto/FORWARD_SECRECY_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/proto/INSTALL.html up to 1.10
external/ibm-public/postfix/dist/proto/IPV6_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/LDAP_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/proto/LINUX_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/LMDB_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/LOCAL_RECIPIENT_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/proto/MAILDROP_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/MEMCACHE_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/proto/MILTER_README.html up to 1.1.1.9
external/ibm-public/postfix/dist/proto/MULTI_INSTANCE_README.html up to 1.1.1.8
external/ibm-public/postfix/dist/proto/MYSQL_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/proto/Makefile.in up to 1.1.1.7
external/ibm-public/postfix/dist/proto/NFS_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/proto/OVERVIEW.html up to 1.1.1.6
external/ibm-public/postfix/dist/proto/PACKAGE_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/proto/PCRE_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/PGSQL_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/POSTSCREEN_README.html up to 1.1.1.8
external/ibm-public/postfix/dist/proto/QSHAPE_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/RESTRICTION_CLASS_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/SASL_README.html up to 1.1.1.11
external/ibm-public/postfix/dist/proto/SCHEDULER_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/proto/SMTPD_ACCESS_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/proto/SMTPD_POLICY_README.html up to 1.1.1.7
external/ibm-public/postfix/dist/proto/SMTPD_PROXY_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/proto/SMTPUTF8_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/SQLITE_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/STANDARD_CONFIGURATION_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/proto/STRESS_README.html up to 1.1.1.7
external/ibm-public/postfix/dist/proto/TLS_LEGACY_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/TLS_README.html up to 1.14
external/ibm-public/postfix/dist/proto/TUNING_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/proto/UUCP_README.html up to 1.1.1.3
external/ibm-public/postfix/dist/proto/VERP_README.html up to 1.1.1.5
external/ibm-public/postfix/dist/proto/VIRTUAL_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/XCLIENT_README.html up to 1.1.1.6
external/ibm-public/postfix/dist/proto/XFORWARD_README.html up to 1.1.1.4
external/ibm-public/postfix/dist/proto/access up to 1.1.1.8
external/ibm-public/postfix/dist/proto/aliases up to 1.1.1.6
external/ibm-public/postfix/dist/proto/canonical up to 1.1.1.5
external/ibm-public/postfix/dist/proto/cidr_table up to 1.1.1.6
external/ibm-public/postfix/dist/proto/generic up to 1.1.1.4
external/ibm-public/postfix/dist/proto/header_checks up to 1.1.1.7
external/ibm-public/postfix/dist/proto/ldap_table up to 1.1.1.7
external/ibm-public/postfix/dist/proto/lmdb_table up to 1.1.1.3
external/ibm-public/postfix/dist/proto/master up to 1.1.1.8
external/ibm-public/postfix/dist/proto/mysql_table up to 1.1.1.8
external/ibm-public/postfix/dist/proto/pcre_table up to 1.1.1.6
external/ibm-public/postfix/dist/proto/pgsql_table up to 1.1.1.8
external/ibm-public/postfix/dist/proto/postconf.html.prolog up to 1.1.1.5
external/ibm-public/postfix/dist/proto/postconf.man.prolog up to 1.1.1.4
external/ibm-public/postfix/dist/proto/postconf.proto up to 1.19
external/ibm-public/postfix/dist/proto/regexp_table up to 1.1.1.6
external/ibm-public/postfix/dist/proto/relocated up to 1.1.1.3
external/ibm-public/postfix/dist/proto/socketmap_table up to 1.1.1.3
external/ibm-public/postfix/dist/proto/sqlite_table up to 1.1.1.5
external/ibm-public/postfix/dist/proto/stop up to 1.1.1.7
external/ibm-public/postfix/dist/proto/tcp_table up to 1.1.1.4
external/ibm-public/postfix/dist/proto/transport up to 1.1.1.5
external/ibm-public/postfix/dist/proto/virtual up to 1.1.1.6
external/ibm-public/postfix/dist/src/anvil/Makefile.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/anvil/anvil.c up to 1.4
external/ibm-public/postfix/dist/src/bounce/2template_test.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/bounce/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/bounce/bounce.c up to 1.4
external/ibm-public/postfix/dist/src/bounce/bounce_notify_util.c up to 1.4
external/ibm-public/postfix/dist/src/bounce/bounce_service.h up to 1.3
external/ibm-public/postfix/dist/src/bounce/bounce_template.c up to 1.4
external/ibm-public/postfix/dist/src/bounce/bounce_template.h up to 1.3
external/ibm-public/postfix/dist/src/bounce/bounce_templates.c up to 1.3
external/ibm-public/postfix/dist/src/bounce/template_test.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/cleanup/Makefile.in up to 1.1.1.9
external/ibm-public/postfix/dist/src/cleanup/cleanup.c up to 1.8
external/ibm-public/postfix/dist/src/cleanup/cleanup.h up to 1.10
external/ibm-public/postfix/dist/src/cleanup/cleanup_addr.c up to 1.3
external/ibm-public/postfix/dist/src/cleanup/cleanup_api.c up to 1.4
external/ibm-public/postfix/dist/src/cleanup/cleanup_body_edit.c up to 1.3
external/ibm-public/postfix/dist/src/cleanup/cleanup_envelope.c up to 1.5
external/ibm-public/postfix/dist/src/cleanup/cleanup_init.c up to 1.7
external/ibm-public/postfix/dist/src/cleanup/cleanup_map11.c up to 1.3
external/ibm-public/postfix/dist/src/cleanup/cleanup_map1n.c up to 1.4
external/ibm-public/postfix/dist/src/cleanup/cleanup_message.c up to 1.4
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.c up to 1.5
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref13c up to 1.1.1.2
external/ibm-public/postfix/dist/src/cleanup/cleanup_milter.ref13d up to 1.1.1.2
external/ibm-public/postfix/dist/src/cleanup/cleanup_out.c up to 1.3
external/ibm-public/postfix/dist/src/cleanup/cleanup_out_recipient.c up to 1.4
external/ibm-public/postfix/dist/src/cleanup/cleanup_region.c up to 1.3
external/ibm-public/postfix/dist/src/cleanup/cleanup_state.c up to 1.4
external/ibm-public/postfix/dist/src/discard/Makefile.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/discard/discard.c up to 1.3
external/ibm-public/postfix/dist/src/dns/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/dns/dns.h up to 1.6
external/ibm-public/postfix/dist/src/dns/dns_lookup.c up to 1.8
external/ibm-public/postfix/dist/src/dns/dns_rr.c up to 1.3
external/ibm-public/postfix/dist/src/dns/dns_rr_eq_sa.c up to 1.3
external/ibm-public/postfix/dist/src/dns/dns_rr_eq_sa.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/dns/dns_rr_eq_sa.ref up to 1.1.1.5
external/ibm-public/postfix/dist/src/dns/dns_rr_to_pa.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/dns/dns_rr_to_sa.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/dns/dns_sa_to_rr.c up to 1.3
external/ibm-public/postfix/dist/src/dns/dns_sa_to_rr.ref up to 1.1.1.5
external/ibm-public/postfix/dist/src/dns/dns_strrecord.c up to 1.3
external/ibm-public/postfix/dist/src/dns/dns_strtype.c up to 1.2
external/ibm-public/postfix/dist/src/dns/dnsbl_ttl_127.0.0.1_bind_ncache.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/dns/dnsbl_ttl_127.0.0.1_bind_plain.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/dns/dnsbl_ttl_127.0.0.2_bind_plain.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/dns/error.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/dns/mxonly_test.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/dns/no-a.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/dns/no-aaaa.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/dns/no-mx.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/dns/nullmx_test.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/dns/nxdomain_test.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/dns/test_dns_lookup.c up to 1.3
external/ibm-public/postfix/dist/src/dnsblog/Makefile.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/dnsblog/dnsblog.c up to 1.4
external/ibm-public/postfix/dist/src/error/Makefile.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/error/error.c up to 1.3
external/ibm-public/postfix/dist/src/flush/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/flush/flush.c up to 1.4
external/ibm-public/postfix/dist/src/fsstone/Makefile.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/global/Makefile.in up to 1.1.1.10
external/ibm-public/postfix/dist/src/global/abounce.c up to 1.3
external/ibm-public/postfix/dist/src/global/anvil_clnt.c up to 1.4
external/ibm-public/postfix/dist/src/global/anvil_clnt.h up to 1.3
external/ibm-public/postfix/dist/src/global/been_here.c up to 1.4
external/ibm-public/postfix/dist/src/global/been_here.h up to 1.3
external/ibm-public/postfix/dist/src/global/bounce.c up to 1.3
external/ibm-public/postfix/dist/src/global/bounce_log.c up to 1.3
external/ibm-public/postfix/dist/src/global/cleanup_strerror.c up to 1.2
external/ibm-public/postfix/dist/src/global/cleanup_user.h up to 1.3
external/ibm-public/postfix/dist/src/global/clnt_stream.c up to 1.4
external/ibm-public/postfix/dist/src/global/clnt_stream.h up to 1.2
external/ibm-public/postfix/dist/src/global/db_common.c up to 1.3
external/ibm-public/postfix/dist/src/global/debug_peer.c up to 1.3
external/ibm-public/postfix/dist/src/global/defer.c up to 1.3
external/ibm-public/postfix/dist/src/global/deliver_pass.c up to 1.3
external/ibm-public/postfix/dist/src/global/deliver_request.c up to 1.3
external/ibm-public/postfix/dist/src/global/deliver_request.h up to 1.3
external/ibm-public/postfix/dist/src/global/delivered_hdr.c up to 1.3
external/ibm-public/postfix/dist/src/global/dict_ldap.c up to 1.5
external/ibm-public/postfix/dist/src/global/dict_memcache.c up to 1.3
external/ibm-public/postfix/dist/src/global/dict_mysql.c up to 1.4
external/ibm-public/postfix/dist/src/global/dict_pgsql.c up to 1.4
external/ibm-public/postfix/dist/src/global/dict_proxy.c up to 1.3
external/ibm-public/postfix/dist/src/global/dict_proxy.h up to 1.3
external/ibm-public/postfix/dist/src/global/dict_sqlite.c up to 1.4
external/ibm-public/postfix/dist/src/global/dsb_scan.c up to 1.3
external/ibm-public/postfix/dist/src/global/dsb_scan.h up to 1.2
external/ibm-public/postfix/dist/src/global/dsn_print.c up to 1.3
external/ibm-public/postfix/dist/src/global/dsn_print.h up to 1.2
external/ibm-public/postfix/dist/src/global/dynamicmaps.c up to 1.4
external/ibm-public/postfix/dist/src/global/ehlo_mask.c up to 1.3
external/ibm-public/postfix/dist/src/global/ehlo_mask.h up to 1.3
external/ibm-public/postfix/dist/src/global/flush_clnt.c up to 1.3
external/ibm-public/postfix/dist/src/global/haproxy_srvr.c up to 1.3
external/ibm-public/postfix/dist/src/global/haproxy_srvr.h up to 1.2
external/ibm-public/postfix/dist/src/global/header_body_checks.c up to 1.3
external/ibm-public/postfix/dist/src/global/header_body_checks.h up to 1.3
external/ibm-public/postfix/dist/src/global/log_adhoc.c up to 1.3
external/ibm-public/postfix/dist/src/global/mail_addr_crunch.c up to 1.3
external/ibm-public/postfix/dist/src/global/mail_addr_crunch.h up to 1.2
external/ibm-public/postfix/dist/src/global/mail_addr_find.c up to 1.4
external/ibm-public/postfix/dist/src/global/mail_addr_find.h up to 1.2
external/ibm-public/postfix/dist/src/global/mail_addr_map.c up to 1.3
external/ibm-public/postfix/dist/src/global/mail_addr_map.h up to 1.2
external/ibm-public/postfix/dist/src/global/mail_command_client.c up to 1.4
external/ibm-public/postfix/dist/src/global/mail_conf.c up to 1.3
external/ibm-public/postfix/dist/src/global/mail_conf.h up to 1.3
external/ibm-public/postfix/dist/src/global/mail_conf_int.c up to 1.3
external/ibm-public/postfix/dist/src/global/mail_conf_long.c up to 1.2
external/ibm-public/postfix/dist/src/global/mail_conf_nint.c up to 1.2
external/ibm-public/postfix/dist/src/global/mail_conf_time.c up to 1.4
external/ibm-public/postfix/dist/src/global/mail_copy.c up to 1.3
external/ibm-public/postfix/dist/src/global/mail_dict.c up to 1.3
external/ibm-public/postfix/dist/src/global/mail_error.c up to 1.2
external/ibm-public/postfix/dist/src/global/mail_params.c up to 1.5
external/ibm-public/postfix/dist/src/global/mail_params.h up to 1.19
external/ibm-public/postfix/dist/src/global/mail_parm_split.c up to 1.3
external/ibm-public/postfix/dist/src/global/mail_proto.h up to 1.5
external/ibm-public/postfix/dist/src/global/mail_queue.h up to 1.3
external/ibm-public/postfix/dist/src/global/mail_stream.c up to 1.3
external/ibm-public/postfix/dist/src/global/mail_task.c up to 1.3
external/ibm-public/postfix/dist/src/global/mail_version.h up to 1.6
external/ibm-public/postfix/dist/src/global/maps.c up to 1.4
external/ibm-public/postfix/dist/src/global/maps.h up to 1.2
external/ibm-public/postfix/dist/src/global/maps.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/global/memcache_proto.c up to 1.3
external/ibm-public/postfix/dist/src/global/mime_state.c up to 1.3
external/ibm-public/postfix/dist/src/global/mkmap_proxy.c up to 1.2
external/ibm-public/postfix/dist/src/global/msg_stats.h up to 1.2
external/ibm-public/postfix/dist/src/global/msg_stats_print.c up to 1.3
external/ibm-public/postfix/dist/src/global/msg_stats_scan.c up to 1.3
external/ibm-public/postfix/dist/src/global/namadr_list.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/global/namadr_list.ref up to 1.1.1.5
external/ibm-public/postfix/dist/src/global/off_cvt.c up to 1.2
external/ibm-public/postfix/dist/src/global/opened.c up to 1.2
external/ibm-public/postfix/dist/src/global/post_mail.c up to 1.4
external/ibm-public/postfix/dist/src/global/post_mail.h up to 1.3
external/ibm-public/postfix/dist/src/global/quote_822_local.c up to 1.3
external/ibm-public/postfix/dist/src/global/quote_822_local.h up to 1.2
external/ibm-public/postfix/dist/src/global/quote_flags.h up to 1.2
external/ibm-public/postfix/dist/src/global/rcpt_buf.c up to 1.4
external/ibm-public/postfix/dist/src/global/rcpt_buf.h up to 1.2
external/ibm-public/postfix/dist/src/global/rcpt_print.c up to 1.3
external/ibm-public/postfix/dist/src/global/rcpt_print.h up to 1.2
external/ibm-public/postfix/dist/src/global/rec_type.h up to 1.3
external/ibm-public/postfix/dist/src/global/record.c up to 1.4
external/ibm-public/postfix/dist/src/global/resolve_clnt.c up to 1.4
external/ibm-public/postfix/dist/src/global/resolve_clnt.h up to 1.2
external/ibm-public/postfix/dist/src/global/rewrite_clnt.c up to 1.3
external/ibm-public/postfix/dist/src/global/scache.h up to 1.3
external/ibm-public/postfix/dist/src/global/scache_clnt.c up to 1.3
external/ibm-public/postfix/dist/src/global/sent.c up to 1.3
external/ibm-public/postfix/dist/src/global/server_acl.c up to 1.3
external/ibm-public/postfix/dist/src/global/server_acl.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/global/server_acl.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/global/smtp_reply_footer.c up to 1.3
external/ibm-public/postfix/dist/src/global/smtp_stream.c up to 1.5
external/ibm-public/postfix/dist/src/global/smtp_stream.h up to 1.4
external/ibm-public/postfix/dist/src/global/smtputf8.h up to 1.3
external/ibm-public/postfix/dist/src/global/split_addr.c up to 1.3
external/ibm-public/postfix/dist/src/global/split_addr.h up to 1.2
external/ibm-public/postfix/dist/src/global/strip_addr.c up to 1.4
external/ibm-public/postfix/dist/src/global/strip_addr.h up to 1.2
external/ibm-public/postfix/dist/src/global/strip_addr.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/global/trace.c up to 1.3
external/ibm-public/postfix/dist/src/global/uxtext.c up to 1.3
external/ibm-public/postfix/dist/src/global/verify.c up to 1.4
external/ibm-public/postfix/dist/src/global/verify_clnt.c up to 1.3
external/ibm-public/postfix/dist/src/global/verify_sender_addr.c up to 1.4
external/ibm-public/postfix/dist/src/global/xtext.c up to 1.3
external/ibm-public/postfix/dist/src/local/Makefile.in up to 1.1.1.8
external/ibm-public/postfix/dist/src/local/alias.c up to 1.3
external/ibm-public/postfix/dist/src/local/forward.c up to 1.4
external/ibm-public/postfix/dist/src/local/local.c up to 1.4
external/ibm-public/postfix/dist/src/local/local_expand.c up to 1.3
external/ibm-public/postfix/dist/src/local/mailbox.c up to 1.4
external/ibm-public/postfix/dist/src/local/unknown.c up to 1.8
external/ibm-public/postfix/dist/src/master/Makefile.in up to 1.1.1.7
external/ibm-public/postfix/dist/src/master/event_server.c up to 1.4
external/ibm-public/postfix/dist/src/master/mail_server.h up to 1.4
external/ibm-public/postfix/dist/src/master/master.c up to 1.4
external/ibm-public/postfix/dist/src/master/master.h up to 1.2
external/ibm-public/postfix/dist/src/master/master_conf.c up to 1.2
external/ibm-public/postfix/dist/src/master/master_ent.c up to 1.4
external/ibm-public/postfix/dist/src/master/master_listen.c up to 1.2
external/ibm-public/postfix/dist/src/master/master_monitor.c up to 1.3
external/ibm-public/postfix/dist/src/master/master_proto.h up to 1.2
external/ibm-public/postfix/dist/src/master/master_sig.c up to 1.3
external/ibm-public/postfix/dist/src/master/master_spawn.c up to 1.3
external/ibm-public/postfix/dist/src/master/master_vars.c up to 1.3
external/ibm-public/postfix/dist/src/master/master_wakeup.c up to 1.3
external/ibm-public/postfix/dist/src/master/multi_server.c up to 1.4
external/ibm-public/postfix/dist/src/master/single_server.c up to 1.4
external/ibm-public/postfix/dist/src/master/trigger_server.c up to 1.4
external/ibm-public/postfix/dist/src/milter/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/milter/milter.c up to 1.5
external/ibm-public/postfix/dist/src/milter/milter.h up to 1.4
external/ibm-public/postfix/dist/src/milter/milter8.c up to 1.5
external/ibm-public/postfix/dist/src/milter/milter_macros.c up to 1.3
external/ibm-public/postfix/dist/src/milter/test-milter.c up to 1.3
external/ibm-public/postfix/dist/src/oqmgr/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/oqmgr/qmgr.c up to 1.3
external/ibm-public/postfix/dist/src/oqmgr/qmgr.h up to 1.3
external/ibm-public/postfix/dist/src/oqmgr/qmgr_active.c up to 1.3
external/ibm-public/postfix/dist/src/oqmgr/qmgr_deliver.c up to 1.3
external/ibm-public/postfix/dist/src/oqmgr/qmgr_entry.c up to 1.3
external/ibm-public/postfix/dist/src/oqmgr/qmgr_error.c up to 1.2
external/ibm-public/postfix/dist/src/oqmgr/qmgr_feedback.c up to 1.2
external/ibm-public/postfix/dist/src/oqmgr/qmgr_message.c up to 1.4
external/ibm-public/postfix/dist/src/pickup/Makefile.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/pickup/pickup.c up to 1.4
external/ibm-public/postfix/dist/src/pipe/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/pipe/pipe.c up to 1.4
external/ibm-public/postfix/dist/src/postalias/Makefile.in up to 1.1.1.6
external/ibm-public/postfix/dist/src/postalias/fail_test.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/postalias/fail_test.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/postalias/postalias.c up to 1.5
external/ibm-public/postfix/dist/src/postcat/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/postcat/postcat.c up to 1.4
external/ibm-public/postfix/dist/src/postconf/Makefile.in up to 1.1.1.11
external/ibm-public/postfix/dist/src/postconf/extract.awk up to 1.1.1.6
external/ibm-public/postfix/dist/src/postconf/install_vars.h up to 1.2
external/ibm-public/postfix/dist/src/postconf/postconf.c up to 1.4
external/ibm-public/postfix/dist/src/postconf/postconf.h up to 1.4
external/ibm-public/postfix/dist/src/postconf/postconf_builtin.c up to 1.4
external/ibm-public/postfix/dist/src/postconf/postconf_dbms.c up to 1.5
external/ibm-public/postfix/dist/src/postconf/postconf_edit.c up to 1.3
external/ibm-public/postfix/dist/src/postconf/postconf_lookup.c up to 1.4
external/ibm-public/postfix/dist/src/postconf/postconf_main.c up to 1.4
external/ibm-public/postfix/dist/src/postconf/postconf_master.c up to 1.8
external/ibm-public/postfix/dist/src/postconf/postconf_misc.c up to 1.3
external/ibm-public/postfix/dist/src/postconf/postconf_user.c up to 1.4
external/ibm-public/postfix/dist/src/postconf/test28.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/postconf/test29.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/postconf/test34.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/postconf/test35.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/postconf/test40.ref up to 1.1.1.4
external/ibm-public/postfix/dist/src/postconf/test41.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/postconf/test42.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/postconf/test43.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/postconf/test44.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/postconf/test58.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/postconf/test59.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/postdrop/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/postdrop/postdrop.c up to 1.4
external/ibm-public/postfix/dist/src/postfix/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/postfix/postfix.c up to 1.6
external/ibm-public/postfix/dist/src/postkick/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/postkick/postkick.c up to 1.4
external/ibm-public/postfix/dist/src/postlock/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/postlock/postlock.c up to 1.4
external/ibm-public/postfix/dist/src/postlog/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/postlog/postlog.c up to 1.5
external/ibm-public/postfix/dist/src/postmap/Makefile.in up to 1.1.1.7
external/ibm-public/postfix/dist/src/postmap/fail_test.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/postmap/fail_test.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/postmap/postmap.c up to 1.5
external/ibm-public/postfix/dist/src/postmulti/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/postmulti/postmulti.c up to 1.4
external/ibm-public/postfix/dist/src/postqueue/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/postqueue/postqueue.c up to 1.5
external/ibm-public/postfix/dist/src/postqueue/showq_compat.c up to 1.4
external/ibm-public/postfix/dist/src/postqueue/showq_json.c up to 1.4
external/ibm-public/postfix/dist/src/postscreen/Makefile.in up to 1.1.1.7
external/ibm-public/postfix/dist/src/postscreen/postscreen.c up to 1.5
external/ibm-public/postfix/dist/src/postscreen/postscreen.h up to 1.4
external/ibm-public/postfix/dist/src/postscreen/postscreen_dnsbl.c up to 1.4
external/ibm-public/postfix/dist/src/postscreen/postscreen_early.c up to 1.4
external/ibm-public/postfix/dist/src/postscreen/postscreen_endpt.c up to 1.4
external/ibm-public/postfix/dist/src/postscreen/postscreen_haproxy.c up to 1.3
external/ibm-public/postfix/dist/src/postscreen/postscreen_haproxy.h up to 1.2
external/ibm-public/postfix/dist/src/postscreen/postscreen_misc.c up to 1.4
external/ibm-public/postfix/dist/src/postscreen/postscreen_send.c up to 1.3
external/ibm-public/postfix/dist/src/postscreen/postscreen_smtpd.c up to 1.5
external/ibm-public/postfix/dist/src/postscreen/postscreen_starttls.c up to 1.4
external/ibm-public/postfix/dist/src/postscreen/postscreen_state.c up to 1.4
external/ibm-public/postfix/dist/src/postscreen/postscreen_tests.c up to 1.4
external/ibm-public/postfix/dist/src/postsuper/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/postsuper/postsuper.c up to 1.4
external/ibm-public/postfix/dist/src/posttls-finger/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/posttls-finger/posttls-finger.c up to 1.5
external/ibm-public/postfix/dist/src/proxymap/Makefile.in up to 1.1.1.6
external/ibm-public/postfix/dist/src/proxymap/proxymap.c up to 1.4
external/ibm-public/postfix/dist/src/qmgr/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/qmgr/qmgr.c up to 1.3
external/ibm-public/postfix/dist/src/qmgr/qmgr.h up to 1.3
external/ibm-public/postfix/dist/src/qmgr/qmgr_active.c up to 1.3
external/ibm-public/postfix/dist/src/qmgr/qmgr_deliver.c up to 1.3
external/ibm-public/postfix/dist/src/qmgr/qmgr_entry.c up to 1.3
external/ibm-public/postfix/dist/src/qmgr/qmgr_error.c up to 1.2
external/ibm-public/postfix/dist/src/qmgr/qmgr_feedback.c up to 1.2
external/ibm-public/postfix/dist/src/qmgr/qmgr_message.c up to 1.4
external/ibm-public/postfix/dist/src/qmqpd/Makefile.in up to 1.1.1.6
external/ibm-public/postfix/dist/src/qmqpd/qmqpd.c up to 1.4
external/ibm-public/postfix/dist/src/qmqpd/qmqpd_peer.c up to 1.3
external/ibm-public/postfix/dist/src/scache/Makefile.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/scache/scache.c up to 1.4
external/ibm-public/postfix/dist/src/sendmail/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/sendmail/sendmail.c up to 1.4
external/ibm-public/postfix/dist/src/showq/Makefile.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/showq/showq.c up to 1.5
external/ibm-public/postfix/dist/src/smtp/Makefile.in up to 1.1.1.10
external/ibm-public/postfix/dist/src/smtp/lmtp_params.c up to 1.5
external/ibm-public/postfix/dist/src/smtp/smtp.c up to 1.13
external/ibm-public/postfix/dist/src/smtp/smtp.h up to 1.5
external/ibm-public/postfix/dist/src/smtp/smtp_addr.c up to 1.5
external/ibm-public/postfix/dist/src/smtp/smtp_addr.h up to 1.3
external/ibm-public/postfix/dist/src/smtp/smtp_chat.c up to 1.4
external/ibm-public/postfix/dist/src/smtp/smtp_connect.c up to 1.5
external/ibm-public/postfix/dist/src/smtp/smtp_key.c up to 1.3
external/ibm-public/postfix/dist/src/smtp/smtp_map11.c up to 1.3
external/ibm-public/postfix/dist/src/smtp/smtp_map11.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtp/smtp_params.c up to 1.5
external/ibm-public/postfix/dist/src/smtp/smtp_proto.c up to 1.5
external/ibm-public/postfix/dist/src/smtp/smtp_rcpt.c up to 1.3
external/ibm-public/postfix/dist/src/smtp/smtp_reuse.c up to 1.4
external/ibm-public/postfix/dist/src/smtp/smtp_sasl_auth_cache.c up to 1.3
external/ibm-public/postfix/dist/src/smtp/smtp_sasl_glue.c up to 1.3
external/ibm-public/postfix/dist/src/smtp/smtp_sasl_proto.c up to 1.3
external/ibm-public/postfix/dist/src/smtp/smtp_session.c up to 1.5
external/ibm-public/postfix/dist/src/smtp/smtp_state.c up to 1.3
external/ibm-public/postfix/dist/src/smtp/smtp_tls_policy.c up to 1.4
external/ibm-public/postfix/dist/src/smtp/smtp_trouble.c up to 1.3
external/ibm-public/postfix/dist/src/smtpd/Makefile.in up to 1.1.1.11
external/ibm-public/postfix/dist/src/smtpd/pfilter.c up to 1.2 (+patch)
external/ibm-public/postfix/dist/src/smtpd/smtpd.c up to 1.20
external/ibm-public/postfix/dist/src/smtpd/smtpd.h up to 1.5
external/ibm-public/postfix/dist/src/smtpd/smtpd_acl.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtpd/smtpd_acl.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtpd/smtpd_chat.c up to 1.4
external/ibm-public/postfix/dist/src/smtpd/smtpd_chat.h up to 1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_check.c up to 1.6
external/ibm-public/postfix/dist/src/smtpd/smtpd_check.h up to 1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_check.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_check.in2 up to 1.1.1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_check.in3 up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtpd/smtpd_check.ref up to 1.1.1.5
external/ibm-public/postfix/dist/src/smtpd/smtpd_check.ref2 up to 1.1.1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_check_backup.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_check_backup.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_check_dsn.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtpd/smtpd_check_dsn.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtpd/smtpd_dns_filter.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtpd/smtpd_dnswl.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/smtpd/smtpd_dnswl.ref up to 1.1.1.4
external/ibm-public/postfix/dist/src/smtpd/smtpd_error.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtpd/smtpd_error.ref up to 1.1.1.4
external/ibm-public/postfix/dist/src/smtpd/smtpd_exp.in up to 1.1.1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_exp.ref up to 1.1.1.5
external/ibm-public/postfix/dist/src/smtpd/smtpd_expand.h up to 1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_haproxy.c up to 1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_milter.c up to 1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_nullmx.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtpd/smtpd_nullmx.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/smtpd/smtpd_peer.c up to 1.5
external/ibm-public/postfix/dist/src/smtpd/smtpd_proxy.c up to 1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_resolve.c up to 1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_resolve.h up to 1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_sasl_glue.c up to 1.5
external/ibm-public/postfix/dist/src/smtpd/smtpd_sasl_proto.c up to 1.3
external/ibm-public/postfix/dist/src/smtpd/smtpd_server.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/smtpd/smtpd_server.ref up to 1.1.1.4
external/ibm-public/postfix/dist/src/smtpd/smtpd_state.c up to 1.2
external/ibm-public/postfix/dist/src/smtpstone/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/smtpstone/smtp-sink.c up to 1.3
external/ibm-public/postfix/dist/src/smtpstone/smtp-source.c up to 1.3
external/ibm-public/postfix/dist/src/spawn/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/spawn/spawn.c up to 1.4
external/ibm-public/postfix/dist/src/tls/Makefile.in up to 1.1.1.10
external/ibm-public/postfix/dist/src/tls/tls.h up to 1.5
external/ibm-public/postfix/dist/src/tls/tls_bio_ops.c up to 1.1.1.6
external/ibm-public/postfix/dist/src/tls/tls_certkey.c up to 1.4
external/ibm-public/postfix/dist/src/tls/tls_client.c up to 1.13
external/ibm-public/postfix/dist/src/tls/tls_dane.c up to 1.5
external/ibm-public/postfix/dist/src/tls/tls_dh.c up to 1.5
external/ibm-public/postfix/dist/src/tls/tls_fprint.c up to 1.4
external/ibm-public/postfix/dist/src/tls/tls_mgr.c up to 1.4
external/ibm-public/postfix/dist/src/tls/tls_misc.c up to 1.5
external/ibm-public/postfix/dist/src/tls/tls_proxy.h up to 1.4
external/ibm-public/postfix/dist/src/tls/tls_proxy_clnt.c up to 1.4
external/ibm-public/postfix/dist/src/tls/tls_rsa.c up to 1.4
external/ibm-public/postfix/dist/src/tls/tls_scache.c up to 1.4
external/ibm-public/postfix/dist/src/tls/tls_server.c up to 1.12
external/ibm-public/postfix/dist/src/tls/tls_session.c up to 1.3
external/ibm-public/postfix/dist/src/tls/tls_verify.c up to 1.4
external/ibm-public/postfix/dist/src/tlsmgr/Makefile.in up to 1.1.1.6
external/ibm-public/postfix/dist/src/tlsmgr/tlsmgr.c up to 1.4
external/ibm-public/postfix/dist/src/tlsproxy/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/tlsproxy/tlsproxy.c up to 1.6
external/ibm-public/postfix/dist/src/tlsproxy/tlsproxy.h up to 1.2
external/ibm-public/postfix/dist/src/tlsproxy/tlsproxy_state.c up to 1.3
external/ibm-public/postfix/dist/src/trivial-rewrite/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/trivial-rewrite/resolve.c up to 1.4
external/ibm-public/postfix/dist/src/trivial-rewrite/rewrite.c up to 1.3
external/ibm-public/postfix/dist/src/trivial-rewrite/transport.c up to 1.4
external/ibm-public/postfix/dist/src/trivial-rewrite/trivial-rewrite.c up to 1.4
external/ibm-public/postfix/dist/src/trivial-rewrite/trivial-rewrite.h up to 1.3
external/ibm-public/postfix/dist/src/util/Makefile.in up to 1.1.1.11
external/ibm-public/postfix/dist/src/util/allascii.c up to 1.3
external/ibm-public/postfix/dist/src/util/alldig.c up to 1.2
external/ibm-public/postfix/dist/src/util/argv.c up to 1.4
external/ibm-public/postfix/dist/src/util/argv.h up to 1.4
external/ibm-public/postfix/dist/src/util/attr.h up to 1.5
external/ibm-public/postfix/dist/src/util/attr_clnt.c up to 1.3
external/ibm-public/postfix/dist/src/util/attr_clnt.h up to 1.3
external/ibm-public/postfix/dist/src/util/attr_print0.c up to 1.3
external/ibm-public/postfix/dist/src/util/attr_print64.c up to 1.3
external/ibm-public/postfix/dist/src/util/attr_print_plain.c up to 1.3
external/ibm-public/postfix/dist/src/util/attr_scan0.c up to 1.3
external/ibm-public/postfix/dist/src/util/attr_scan0.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/util/attr_scan64.c up to 1.3
external/ibm-public/postfix/dist/src/util/attr_scan64.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/util/attr_scan_plain.c up to 1.3
external/ibm-public/postfix/dist/src/util/attr_scan_plain.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/util/auto_clnt.c up to 1.4
external/ibm-public/postfix/dist/src/util/auto_clnt.h up to 1.2
external/ibm-public/postfix/dist/src/util/base32_code.h up to 1.3
external/ibm-public/postfix/dist/src/util/base64_code.h up to 1.3
external/ibm-public/postfix/dist/src/util/binhash.c up to 1.3
external/ibm-public/postfix/dist/src/util/binhash.h up to 1.3
external/ibm-public/postfix/dist/src/util/casefold.c up to 1.3
external/ibm-public/postfix/dist/src/util/check_arg.h up to 1.3
external/ibm-public/postfix/dist/src/util/cidr_match.c up to 1.4
external/ibm-public/postfix/dist/src/util/cidr_match.h up to 1.2
external/ibm-public/postfix/dist/src/util/clean_env.c up to 1.3
external/ibm-public/postfix/dist/src/util/clean_env.h up to 1.2
external/ibm-public/postfix/dist/src/util/connect.h up to 1.2
external/ibm-public/postfix/dist/src/util/dict.c up to 1.4
external/ibm-public/postfix/dist/src/util/dict.h up to 1.5
external/ibm-public/postfix/dist/src/util/dict_alloc.c up to 1.3
external/ibm-public/postfix/dist/src/util/dict_cache.c up to 1.4
external/ibm-public/postfix/dist/src/util/dict_cdb.c up to 1.3
external/ibm-public/postfix/dist/src/util/dict_cdb.h up to 1.2
external/ibm-public/postfix/dist/src/util/dict_cidr.c up to 1.5
external/ibm-public/postfix/dist/src/util/dict_cidr.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/dict_cidr.map up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/dict_cidr.ref up to 1.1.1.4
external/ibm-public/postfix/dist/src/util/dict_db.c up to 1.4
external/ibm-public/postfix/dist/src/util/dict_db.h up to 1.4
external/ibm-public/postfix/dist/src/util/dict_dbm.h up to 1.2
external/ibm-public/postfix/dist/src/util/dict_fail.c up to 1.2
external/ibm-public/postfix/dist/src/util/dict_fail.h up to 1.2
external/ibm-public/postfix/dist/src/util/dict_inline.c up to 1.4
external/ibm-public/postfix/dist/src/util/dict_lmdb.c up to 1.4
external/ibm-public/postfix/dist/src/util/dict_lmdb.h up to 1.3
external/ibm-public/postfix/dist/src/util/dict_open.c up to 1.4
external/ibm-public/postfix/dist/src/util/dict_pcre.c up to 1.5
external/ibm-public/postfix/dist/src/util/dict_pcre.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/dict_pcre.map up to 1.1.1.3
external/ibm-public/postfix/dist/src/util/dict_pcre.ref up to 1.1.1.4
external/ibm-public/postfix/dist/src/util/dict_random.c up to 1.4
external/ibm-public/postfix/dist/src/util/dict_random.h up to 1.3
external/ibm-public/postfix/dist/src/util/dict_regexp.c up to 1.5
external/ibm-public/postfix/dist/src/util/dict_regexp.map up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/dict_regexp.ref up to 1.1.1.3
external/ibm-public/postfix/dist/src/util/dict_sdbm.h up to 1.2
external/ibm-public/postfix/dist/src/util/dict_static.c up to 1.4
external/ibm-public/postfix/dist/src/util/dict_thash.c up to 1.4
external/ibm-public/postfix/dist/src/util/dict_thash.map up to 1.1.1.3
external/ibm-public/postfix/dist/src/util/dict_union.c up to 1.3
external/ibm-public/postfix/dist/src/util/dict_utf8.c up to 1.3
external/ibm-public/postfix/dist/src/util/dict_utf8_test.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/dup2_pass_on_exec.c up to 1.2
external/ibm-public/postfix/dist/src/util/edit_file.c up to 1.4
external/ibm-public/postfix/dist/src/util/edit_file.h up to 1.3
external/ibm-public/postfix/dist/src/util/extpar.c up to 1.4
external/ibm-public/postfix/dist/src/util/find_inet.c up to 1.3
external/ibm-public/postfix/dist/src/util/gccw.c up to 1.2
external/ibm-public/postfix/dist/src/util/hex_code.c up to 1.3
external/ibm-public/postfix/dist/src/util/hex_code.h up to 1.4
external/ibm-public/postfix/dist/src/util/hex_quote.c up to 1.2
external/ibm-public/postfix/dist/src/util/host_port.h up to 1.3
external/ibm-public/postfix/dist/src/util/htable.c up to 1.4
external/ibm-public/postfix/dist/src/util/inet_addr_host.c up to 1.3
external/ibm-public/postfix/dist/src/util/inet_addr_list.in up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/inet_addr_list.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/inet_connect.c up to 1.3
external/ibm-public/postfix/dist/src/util/inet_listen.c up to 1.3
external/ibm-public/postfix/dist/src/util/inet_proto.c up to 1.4
external/ibm-public/postfix/dist/src/util/inet_proto.h up to 1.2
external/ibm-public/postfix/dist/src/util/killme_after.c up to 1.2
external/ibm-public/postfix/dist/src/util/listen.h up to 1.3
external/ibm-public/postfix/dist/src/util/load_lib.c up to 1.3
external/ibm-public/postfix/dist/src/util/lstat_as.h up to 1.3
external/ibm-public/postfix/dist/src/util/mac_expand.c up to 1.4
external/ibm-public/postfix/dist/src/util/mac_expand.h up to 1.4
external/ibm-public/postfix/dist/src/util/mac_expand.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/util/mac_expand.ref up to 1.1.1.4
external/ibm-public/postfix/dist/src/util/mac_parse.h up to 1.3
external/ibm-public/postfix/dist/src/util/make_dirs.c up to 1.2
external/ibm-public/postfix/dist/src/util/match_list.c up to 1.3
external/ibm-public/postfix/dist/src/util/match_ops.c up to 1.3
external/ibm-public/postfix/dist/src/util/midna_domain.c up to 1.4
external/ibm-public/postfix/dist/src/util/midna_domain.h up to 1.4
external/ibm-public/postfix/dist/src/util/midna_domain_test.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/msg_output.c up to 1.4
external/ibm-public/postfix/dist/src/util/msg_output.h up to 1.3
external/ibm-public/postfix/dist/src/util/msg_syslog.c up to 1.2
external/ibm-public/postfix/dist/src/util/msg_syslog.h up to 1.3
external/ibm-public/postfix/dist/src/util/mvect.c up to 1.3
external/ibm-public/postfix/dist/src/util/myaddrinfo.c up to 1.3
external/ibm-public/postfix/dist/src/util/myaddrinfo.h up to 1.3
external/ibm-public/postfix/dist/src/util/myaddrinfo.ref up to 1.1.1.5
external/ibm-public/postfix/dist/src/util/myaddrinfo4.ref up to 1.1.1.2
external/ibm-public/postfix/dist/src/util/myflock.c up to 1.3
external/ibm-public/postfix/dist/src/util/myflock.h up to 1.3
external/ibm-public/postfix/dist/src/util/mymalloc.c up to 1.4
external/ibm-public/postfix/dist/src/util/mymalloc.h up to 1.4
external/ibm-public/postfix/dist/src/util/mystrtok.c up to 1.4
external/ibm-public/postfix/dist/src/util/name_mask.c up to 1.3
external/ibm-public/postfix/dist/src/util/nbbio.c up to 1.3
external/ibm-public/postfix/dist/src/util/netstring.c up to 1.3
external/ibm-public/postfix/dist/src/util/peekfd.c up to 1.3
external/ibm-public/postfix/dist/src/util/printable.c up to 1.3
external/ibm-public/postfix/dist/src/util/recv_pass_attr.c up to 1.3
external/ibm-public/postfix/dist/src/util/sane_fsops.h up to 1.3
external/ibm-public/postfix/dist/src/util/sane_link.c up to 1.2
external/ibm-public/postfix/dist/src/util/sane_rename.c up to 1.2
external/ibm-public/postfix/dist/src/util/sane_socketpair.h up to 1.3
external/ibm-public/postfix/dist/src/util/slmdb.c up to 1.4
external/ibm-public/postfix/dist/src/util/sock_addr.c up to 1.3
external/ibm-public/postfix/dist/src/util/sock_addr.h up to 1.2
external/ibm-public/postfix/dist/src/util/split_nameval.c up to 1.2
external/ibm-public/postfix/dist/src/util/stat_as.h up to 1.3
external/ibm-public/postfix/dist/src/util/stringops.h up to 1.5
external/ibm-public/postfix/dist/src/util/sys_compat.c up to 1.3
external/ibm-public/postfix/dist/src/util/sys_defs.h up to 1.14
external/ibm-public/postfix/dist/src/util/timed_wait.h up to 1.3
external/ibm-public/postfix/dist/src/util/unix_pass_fd_fix.c up to 1.2
external/ibm-public/postfix/dist/src/util/unix_send_fd.c up to 1.8
external/ibm-public/postfix/dist/src/util/unsafe.c up to 1.2
external/ibm-public/postfix/dist/src/util/valid_hostname.c up to 1.3
external/ibm-public/postfix/dist/src/util/valid_hostname.h up to 1.2
external/ibm-public/postfix/dist/src/util/vbuf.c up to 1.3
external/ibm-public/postfix/dist/src/util/vbuf_print.c up to 1.4
external/ibm-public/postfix/dist/src/util/vstream.c up to 1.4
external/ibm-public/postfix/dist/src/util/vstream.h up to 1.4
external/ibm-public/postfix/dist/src/util/vstream_tweak.c up to 1.3
external/ibm-public/postfix/dist/src/util/vstring.c up to 1.4
external/ibm-public/postfix/dist/src/util/vstring.h up to 1.4
external/ibm-public/postfix/dist/src/util/vstring_vstream.c up to 1.2
external/ibm-public/postfix/dist/src/util/vstring_vstream.h up to 1.3
external/ibm-public/postfix/dist/src/util/watchdog.c up to 1.3
external/ibm-public/postfix/dist/src/verify/Makefile.in up to 1.1.1.6
external/ibm-public/postfix/dist/src/verify/verify.c up to 1.4
external/ibm-public/postfix/dist/src/virtual/Makefile.in up to 1.1.1.5
external/ibm-public/postfix/dist/src/virtual/mailbox.c up to 1.3
external/ibm-public/postfix/dist/src/virtual/virtual.c up to 1.4
external/ibm-public/postfix/dist/src/xsasl/Makefile.in up to 1.1.1.4
external/ibm-public/postfix/dist/src/xsasl/xsasl.h up to 1.3
external/ibm-public/postfix/dist/src/xsasl/xsasl_cyrus_client.c up to 1.3
external/ibm-public/postfix/dist/src/xsasl/xsasl_cyrus_server.c up to 1.4
external/ibm-public/postfix/dist/src/xsasl/xsasl_dovecot_server.c up to 1.4
external/ibm-public/postfix/dist/src/xsasl/xsasl_saslc_client.c up to 1.2
external/ibm-public/postfix/dist/src/xsasl/xsasl_server.c up to 1.2
external/ibm-public/postfix/lib/dns/Makefile up to 1.4
external/ibm-public/postfix/lib/global/Makefile up to 1.10
external/ibm-public/postfix/lib/masterlib/Makefile up to 1.3
external/ibm-public/postfix/lib/milter/Makefile up to 1.2
external/ibm-public/postfix/lib/tls/Makefile up to 1.4
external/ibm-public/postfix/lib/util/Makefile up to 1.11
external/ibm-public/postfix/lib/xsasl/Makefile up to 1.3
external/ibm-public/postfix/libexec/smtp/Makefile up to 1.4
external/ibm-public/postfix/libexec/smtpd/Makefile up to 1.9 (+patch)
external/ibm-public/postfix/libexec/tlsproxy/Makefile up to 1.2
external/ibm-public/postfix/sbin/postconf/Makefile up to 1.9
doc/3RDPARTY (apply patch)
Update Postfix to 3.8.4.
@
text
@d4 1
a4 2
d64 3
a66 3
names (Postfix 2.9 and later). The command can also change main.cf
configuration parameter values, or display other configuration informa-
tion about the Postfix mail system.
d70 3
a72 4
-a List the 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 one of the names listed
below.
d74 1
a74 1
cyrus This server plug-in is available when Postfix is built
d79 1
a79 1
server, and is available when Postfix is built with any
d84 4
a87 4
-A List the available SASL plug-in types for the Postfix SMTP
client. The plug-in type is selected with the smtp_sasl_type or
lmtp_sasl_type configuration parameters by specifying one of the
names listed below.
d89 1
a89 1
cyrus This client plug-in is available when Postfix is built
d96 1
a96 1
ery status notification (DSN) messages, expanding $name expres-
d99 7
a105 4
To override the bounce_template_file 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: "").
d145 1
a145 1
or more service fields with new values as specified with "ser-
d148 1
a148 1
mand arguments. This may change in the near future, so that the
d154 1
a154 1
ter=value settings) with new values as specified with "ser-
d162 1
a162 2
later, as it is assumed whenever a value is specified (empty or
non-empty).
d170 1
a170 1
and all fields), formatted as "service/type/field=value", one
d173 3
a175 3
Specify one or more "service/type/field" instances on the post-
conf(1) command line to limit the output to fields of interest.
Trailing parameter name or service type fields that are omitted
d180 1
a180 1
-h Show parameter or attribute values without the "name = " label
d183 1
a183 1
-H Show parameter or attribute names without the " = value" that
d188 1
a188 1
-l List the names of all supported mailbox locking methods. Post-
d191 1
a191 1
flock A kernel-based advisory locking method for local files
d195 1
a195 1
fcntl A kernel-based advisory locking method for local and
d200 1
a200 1
a file named filename by creating a file named file-
d202 1
a202 1
lock file, as well as stale lock files that were left
d205 2
a206 2
-m List the names of all supported lookup table types. In Postfix
configuration files, lookup tables are specified as type:name,
d208 1
a208 1
tax depends on the lookup table type as described in the DATA-
d211 1
a211 1
btree A sorted, balanced tree structure. Available on systems
d214 2
a215 2
cdb A read-optimized structure with no support for incremen-
tal updates. Available on systems with support for CDB
a217 2
This feature is available with Postfix 2.2 and later.
d219 1
a219 1
Inter-Domain Routing (CIDR) patterns. This is described
a221 2
This feature is available with Postfix 2.2 and later.
d227 2
a228 3
environment variable name; the table name is ignored.
Originally implemented for testing, someone may find this
useful someday.
a233 2
This feature is available with Postfix 2.9 and later.
d241 4
a244 7
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 static: map type.
This feature is available with Postfix 3.0 and later.
d247 1
a247 1
A non-shared, in-memory hash table. Its content are lost
d250 2
a251 2
lmdb OpenLDAP LMDB database (a memory-mapped, persistent
file). Available on systems with support for LMDB data-
a253 2
This feature is available with Postfix 2.11 and later.
d258 1
a258 1
Memcache database client. This is described in mem-
a260 2
This feature is available with Postfix 2.9 and later.
d263 1
a263 1
for MySQL databases. This is described in mysql_ta-
d267 1
a267 1
A lookup table based on Perl Compatible Regular Expres-
d271 1
a271 1
PostgreSQL database client. This is described in
a273 2
This feature is available with Postfix 2.1 and later.
d275 3
a277 3
A lookup table that constructs a pipeline of tables.
Example: "pipemap:{type_1:name_1, ..., type_n:name_n}".
Each "pipemap:" query is given to the first table. Each
d279 3
a281 3
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
d285 1
a285 3
This feature is available with Postfix 3.0 and later.
proxy Postfix proxymap(8) client for shared access to Postfix
a287 2
This feature is available with Postfix 2.0 and later.
d289 1
a289 1
An in-memory table that performs random selection. Exam-
d292 2
a293 2
The first and last characters of the "randmap:" table
name must be "{" and "}". Within these, individual
a296 2
This feature is available with Postfix 3.0 and later.
d298 1
a298 1
A lookup table based on regular expressions. The file
a303 2
This feature is available with Postfix 2.2 and later.
d305 3
a307 3
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
a309 2
This feature is available with Postfix 2.10 and later.
a312 2
This feature is available with Postfix 2.8 and later.
d314 1
a314 1
A table that always returns its name as lookup result.
d316 4
a319 7
bar as lookup result. Specify "static:{ text with white-
space }" when the result contains whitespace; this form
ignores whitespace after the opening "{" and before the
closing "}". See also the inline: map.
The form "static:{text} is available with Postfix 3.0 and
later.
a329 2
This feature is available with Postfix 2.8 and later.
a334 2
This feature is available with Postfix 3.0 and later.
d372 1
a372 5
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.
d375 1
a375 4
Override main.cf 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
d399 7
a405 4
To override the bounce_template_file 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: "").
d410 3
a412 3
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
d417 1
a417 1
(i.e. the OpenSSL version in a header file). The output
d425 1
a425 1
Output the lower-case names of the supported public-key
d430 1
a430 1
-v Enable verbose logging for debugging purposes. Multiple -v
d433 1
a433 1
-x Expand $name in main.cf or master.cf parameter values. The
d438 1
a438 1
-X Edit the main.cf configuration file, and remove the parameters
d442 2
a443 2
With -M, edit the master.cf configuration file, and remove one
or more service entries as specified with "service/type" on the
d446 1
a446 1
With -P, edit the master.cf configuration file, and remove one
d448 2
a449 2
as specified with "service/type/parameter" on the postconf(1)
command line.
d455 1
a455 1
There is no postconf(1) command to perform the reverse opera-
d458 1
a458 1
This feature is available with Postfix 2.10 and later. Support
d466 2
a467 2
With -M, edit the master.cf configuration file, and comment out
one or more service entries as specified with "service/type" on
d474 1
a474 1
There is no postconf(1) command to perform the reverse opera-
d477 1
a477 1
This feature is available with Postfix 2.6 and later. Support
d488 1
a488 1
The following main.cf parameters are especially relevant to this pro-
d491 1
a491 1
The text below provides only a parameter summary. See postconf(5) for
d495 1
a495 1
The default location of the Postfix main.cf and master.cf con-
d499 1
a499 1
Pathname of a configuration file with bounce message templates.
@
1.1.1.8.12.1
log
@Merge changes from current as of 20200406
@
text
@d64 3
a66 3
names (Postfix 2.9 and later). The command can also change main.cf
configuration parameter values, or display other configuration informa-
tion about the Postfix mail system.
d70 3
a72 4
-a List the 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 one of the names listed
below.
d74 1
a74 1
cyrus This server plug-in is available when Postfix is built
d79 1
a79 1
server, and is available when Postfix is built with any
d84 4
a87 4
-A List the available SASL plug-in types for the Postfix SMTP
client. The plug-in type is selected with the smtp_sasl_type or
lmtp_sasl_type configuration parameters by specifying one of the
names listed below.
d89 1
a89 1
cyrus This client plug-in is available when Postfix is built
d96 1
a96 1
ery status notification (DSN) messages, expanding $name expres-
d99 7
a105 4
To override the bounce_template_file 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: "").
d145 1
a145 1
or more service fields with new values as specified with "ser-
d154 1
a154 1
ter=value settings) with new values as specified with "ser-
a217 2
This feature is available with Postfix 2.2 and later.
a221 2
This feature is available with Postfix 2.2 and later.
d227 2
a228 3
environment variable name; the table name is ignored.
Originally implemented for testing, someone may find this
useful someday.
d230 2
a231 2
fail A table that reliably fails all requests. The lookup ta-
ble name is used for logging. This table exists to sim-
a233 2
This feature is available with Postfix 2.9 and later.
d238 7
a244 10
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 elimi-
nate 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.
a253 2
This feature is available with Postfix 2.11 and later.
a260 2
This feature is available with Postfix 2.9 and later.
a273 2
This feature is available with Postfix 2.1 and later.
a284 2
This feature is available with Postfix 3.0 and later.
a287 2
This feature is available with Postfix 2.0 and later.
a296 2
This feature is available with Postfix 3.0 and later.
a303 2
This feature is available with Postfix 2.2 and later.
a309 2
This feature is available with Postfix 2.10 and later.
a312 2
This feature is available with Postfix 2.8 and later.
d318 2
a319 5
ignores whitespace after the opening "{" and before the
closing "}". See also the inline: map.
The form "static:{text} is available with Postfix 3.0 and
later.
d325 3
a327 3
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
a329 2
This feature is available with Postfix 2.8 and later.
d331 2
a332 2
A table that sends each query to multiple lookup tables
and that concatenates all found results, separated by
a334 2
This feature is available with Postfix 3.0 and later.
d336 1
a336 1
A limited view of the UNIX authentication database. The
d340 2
a341 2
The table is the UNIX password database. The key
is a login name. The result is a password file
d346 1
a346 1
group name. The result is a group file entry in
d349 1
a349 1
Other table types may exist depending on how Postfix was built.
d351 1
a351 1
-M Show master.cf file contents instead of main.cf file contents.
d355 2
a356 2
vice-name/service-type pair, where service-name is the first
field of a master.cf entry and service-type is one of (inet,
d359 5
a363 5
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
listens on the network. Trailing service type fields that are
d367 1
a367 1
was changed from "name.type" to "name/type", and "*" wildcard
d371 2
a372 6
settings in main.cf. 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:
comm -23 <(postconf -n) <(postconf -d)
Replace "-23" with "-12" to show settings that duplicate
built-in defaults.
d383 2
a384 2
-P Show master.cf service parameter settings (by default all ser-
vices and all parameters), formatted as "service/type/parame-
d387 3
a389 3
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
d395 2
a396 2
Display the templates for text that appears at the beginning of
delivery status notification (DSN) messages, without expanding
d399 7
a405 4
To override the bounce_template_file 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: "").
d448 2
a449 2
as specified with "service/type/parameter" on the postconf(1)
command line.
@
1.1.1.9
log
@This is the Postfix 3.5 (stable) release.
The stable Postfix release is called postfix-3.5.x where 3=major
release number, 5=minor release number, x=patchlevel. The stable
release never changes except for patches that address bugs or
emergencies. Patches change the patchlevel and the release date.
New features are developed in snapshot releases. These are called
postfix-3.6-yyyymmdd where yyyymmdd is the release date (yyyy=year,
mm=month, dd=day). Patches are never issued for snapshot releases;
instead, a new snapshot is released.
The mail_release_date configuration parameter (format: yyyymmdd)
specifies the release date of a stable release or snapshot release.
If you upgrade from Postfix 3.3 or earlier, read RELEASE_NOTES-3.4
before proceeding.
License change
---------------
This software is distributed with a dual license: in addition to the
historical IBM Public License 1.0, it is now also distributed with the
more recent Eclipse Public License 2.0. Recipients can choose to take
the software under the license of their choice. Those who are more
comfortable with the IPL can continue with that license.
Major changes - multiple relayhost in SMTP
------------------------------------------
[Feature 20200111] the Postfix SMTP and LMTP client support a list
of nexthop destinations separated by comma or whitespace. These
destinations will be tried in the specified order.
The list form can be specified in relayhost, transport_maps,
default_transport, and sender_dependent_default_transport_maps.
Examples:
/etc/postfix/main.cf:
relayhost = foo.example, bar.example
default_transport = smtp:foo.example, bar.example.
NOTE: this is an SMTP and LMTP client feature. It does not work for
other Postfix delivery agents.
Major changes - certificate access
----------------------------------
[Feature 20190517] Search order support for check_ccert_access.
Search order support for other tables is in design (canonical_maps,
virtual_alias_maps, transport_maps, etc.).
The following check_ccert_access setting uses the built-in search
order: it first looks up the client certificate fingerprint, then
the client certificate public-key fingerprint, and it stops when a
decision is made.
/etc/postfix/main.cf:
smtpd_mumble_restrictions =
...
check_ccert_access hash:/etc/postfix/ccert-access
...
The following setting, with explicit search order, produces the
exact same result:
/etc/postfix/main.cf:
smtpd_mumble_restrictions =
...
check_ccert_access {
hash:/etc/postfix/ccert-access {
search_order = cert_fingerprint, pubkey_fingerprint } }
...
Support is planned for other certificate features.
Major changes - dovecot usability
---------------------------------
[Feature 20190615] The SMTP+LMTP delivery agent can now prepend
Delivered-To, X-Original-To and Return-Path headers, just like the
pipe(8) and local(8) delivery agents.
This uses the "flags=DORX" command-line flags in master.cf. See the
smtp(8) manpage for details.
This obsoletes the "lmtp_assume_final = yes" setting, and replaces
it with "flags=...X...", for consistency with the pipe(8) delivery
agent.
Major changes - forced expiration
---------------------------------
[Feature 20200202] Support to force-expire email messages. This
introduces new postsuper(1) command-line options to request expiration,
and additional information in mailq(1) or postqueue(1) output.
The forced-to-expire status is stored in a queue file attribute.
An expired message is returned to the sender when the queue manager
attempts to deliver that message (note that Postfix will never
deliver messages in the hold queue).
The postsuper(1) -e and -f options both set the forced-to-expire
queue file attribute. The difference is that -f will also release
a message if it is in the hold queue. With -e, such a message would
not be returned to the sender until it is released with -f or -H.
In the mailq(1) or postqueue(1) -p output, a forced-to-expire message
is indicated with # after the queue file name. In postqueue(1) JSON
output, there is a new per-message field "forced_expire" (with value
true or false) that shows the forced-to-expire status.
Major changes - haproxy2 protocol
---------------------------------
[Feature 20200112] Support for the haproxy v2 protocol. The Postfix
implementation supports TCP over IPv4 and IPv6, as well as non-proxied
connections; the latter are typically used for heartbeat tests.
The haproxy v2 protocol introduces no additional Postfix configuration.
The Postfix smtpd(8) and postscreen(8) daemons accept both v1 and
v2 protocol versions.
Major changes - logging
-----------------------
[Incompat 20191109] Postfix daemon processes now log the from= and
to= addresses in external (quoted) form in non-debug logging (info,
warning, etc.). This means that when an address localpart contains
spaces or other special characters, the localpart will be quoted,
for example:
from=<"name with spaces"@@example.com>
Older Postfix versions would log the internal (unquoted) form:
from=
POSTCONF(1) POSTCONF(1)
NAME
postconf - Postfix configuration utility
SYNOPSIS
postconf [-dhnv] [-c config_dir] [parameter ...]
postconf [-aAmlv] [-c config_dir]
postconf [-ev] [-c config_dir] [parameter=value ...]
postconf [-#v] [-c config_dir] [parameter ...]
postconf [-btv] [-c config_dir] [template_file]
DESCRIPTION
The postconf(1) command displays the actual values of con-
figuration parameters, changes configuration parameter
values, or displays other configuration information about
the Postfix mail system.
Options:
-a List the available SASL server plug-in types. The
SASL plug-in type is selected with the
smtpd_sasl_type configuration parameter by specify-
ing one of the names listed below.
cyrus This server plug-in is available when Post-
fix is built with Cyrus SASL support.
dovecot
This server plug-in uses the Dovecot authen-
tication server, and is available when Post-
fix is built with any form of SASL support.
This feature is available with Postfix 2.3 and
later.
-A 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.
cyrus This client plug-in is available when Post-
fix 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 begin-
ning of delivery status notification (DSN) mes-
sages, with $name expressions replaced by actual
values. To override the built-in message text,
specify a template file at the end of the command
line, or specify a template file in main.cf with
the bounce_template_file parameter. To force
selection of the built-in message text templates,
specify an empty template file name (in shell lan-
guage: "").
This feature is available with Postfix 2.3 and
later.
-c config_dir
The main.cf configuration file is in the named
directory instead of the default configuration
directory.
-d Print default parameter settings instead of actual
settings.
-e Edit the main.cf configuration file. The file is
copied to a temporary file then renamed into place.
Parameters and values are specified on the command
line. Use quotes in order to protect shell
metacharacters and whitespace.
-h Show parameter values only, not the ``name = ''
label that normally precedes the value.
-l List the names of all supported mailbox locking
methods. Postfix 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 filename.lock. The
application is expected to remove its own
lock file, as well as stale lock files that
were left behind after abnormal 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 syntax depends
on the lookup table type as described in the DATA-
BASE_README document.
btree A sorted, balanced tree structure. This is
available on systems with support for Berke-
ley DB databases.
cdb A read-optimized structure with no support
for incremental updates. This is available
on systems with support for CDB databases.
cidr A table that associates values with Class-
less Inter-Domain Routing (CIDR) patterns.
This is described in cidr_table(5).
dbm An indexed file type based on hashing. This
is available on systems with support for DBM
databases.
environ
The UNIX process environment array. The
lookup key is the variable name. Originally
implemented for testing, someone may find
this useful someday.
hash An indexed file type based on hashing. This
is available on systems with support for
Berkeley DB databases.
ldap (read-only)
Perform lookups using the LDAP protocol.
This is described in ldap_table(5).
mysql (read-only)
Perform lookups using the MYSQL protocol.
This is described in mysql_table(5).
pcre (read-only)
A lookup table based on Perl Compatible Reg-
ular Expressions. The file format is
described in pcre_table(5).
pgsql (read-only)
Perform lookups using the PostgreSQL proto-
col. This is described in pgsql_table(5).
proxy (read-only)
A lookup table that is implemented via the
Postfix proxymap(8) service. The table name
syntax is type:name.
regexp (read-only)
A lookup table based on regular expressions.
The file format is described in regexp_ta-
ble(5).
sdbm An indexed file type based on hashing. This
is available on systems with support for
SDBM databases.
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)
Perform lookups using a simple request-reply
protocol that is described in tcp_table(5).
This feature is not included with the stable
Postfix release.
unix (read-only)
A limited way to query the UNIX authentica-
tion database. The following tables are
implemented:
unix:passwd.byname
The table is the UNIX password data-
base. 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 Post-
fix was built.
-n Print parameter settings that are not left at their
built-in default value, because they are explicitly
specified in main.cf.
-t [template_file]
Display the templates for delivery status notifica-
tion (DSN) messages. To override the built-in tem-
plates, specify a template file at the end of the
command line, or specify a template file in main.cf
with the bounce_template_file parameter. To force
selection of the built-in templates, specify an
empty template file name (in shell language: "").
This feature is available with Postfix 2.3 and
later.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
-# Edit the main.cf configuration file. The file is
copied to a temporary file then renamed into place.
The parameters specified on the command line are
commented-out, so that they revert to their default
values. Specify a list of parameter names, not
name=value pairs. There is no postconf command to
perform the reverse operation.
This feature is available with Postfix 2.6 and
later.
DIAGNOSTICS
Problems are reported to the standard error stream.
ENVIRONMENT
MAIL_CONFIG
Directory with Postfix configuration files.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program.
The text below provides only a parameter summary. See
postconf(5) for more details including examples.
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 mes-
sage templates.
FILES
/etc/postfix/main.cf, Postfix configuration parameters
SEE ALSO
bounce(5), bounce template file format
postconf(5), configuration parameters
README FILES
DATABASE_README, Postfix lookup table overview
LICENSE
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
POSTCONF(1)
@
1.1.1.1.2.1
log
@file postconf.1.html was added on branch netbsd-5 on 2009-09-15 06:02:15 +0000
@
text
@d1 280
@
1.1.1.1.2.2
log
@Apply patch (requested by tron in ticket #944):
Update Postfix to 2.6.5.
@
text
@a0 280
POSTCONF(1) POSTCONF(1)
NAME
postconf - Postfix configuration utility
SYNOPSIS
postconf [-dhnv] [-c config_dir] [parameter ...]
postconf [-aAmlv] [-c config_dir]
postconf [-ev] [-c config_dir] [parameter=value ...]
postconf [-#v] [-c config_dir] [parameter ...]
postconf [-btv] [-c config_dir] [template_file]
DESCRIPTION
The postconf(1) command displays the actual values of con-
figuration parameters, changes configuration parameter
values, or displays other configuration information about
the Postfix mail system.
Options:
-a List the available SASL server plug-in types. The
SASL plug-in type is selected with the
smtpd_sasl_type configuration parameter by specify-
ing one of the names listed below.
cyrus This server plug-in is available when Post-
fix is built with Cyrus SASL support.
dovecot
This server plug-in uses the Dovecot authen-
tication server, and is available when Post-
fix is built with any form of SASL support.
This feature is available with Postfix 2.3 and
later.
-A 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.
cyrus This client plug-in is available when Post-
fix 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 begin-
ning of delivery status notification (DSN) mes-
sages, with $name expressions replaced by actual
values. To override the built-in message text,
specify a template file at the end of the command
line, or specify a template file in main.cf with
the bounce_template_file parameter. To force
selection of the built-in message text templates,
specify an empty template file name (in shell lan-
guage: "").
This feature is available with Postfix 2.3 and
later.
-c config_dir
The main.cf configuration file is in the named
directory instead of the default configuration
directory.
-d Print default parameter settings instead of actual
settings.
-e Edit the main.cf configuration file. The file is
copied to a temporary file then renamed into place.
Parameters and values are specified on the command
line. Use quotes in order to protect shell
metacharacters and whitespace.
-h Show parameter values only, not the ``name = ''
label that normally precedes the value.
-l List the names of all supported mailbox locking
methods. Postfix 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 filename.lock. The
application is expected to remove its own
lock file, as well as stale lock files that
were left behind after abnormal 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 syntax depends
on the lookup table type as described in the DATA-
BASE_README document.
btree A sorted, balanced tree structure. This is
available on systems with support for Berke-
ley DB databases.
cdb A read-optimized structure with no support
for incremental updates. This is available
on systems with support for CDB databases.
cidr A table that associates values with Class-
less Inter-Domain Routing (CIDR) patterns.
This is described in cidr_table(5).
dbm An indexed file type based on hashing. This
is available on systems with support for DBM
databases.
environ
The UNIX process environment array. The
lookup key is the variable name. Originally
implemented for testing, someone may find
this useful someday.
hash An indexed file type based on hashing. This
is available on systems with support for
Berkeley DB databases.
ldap (read-only)
Perform lookups using the LDAP protocol.
This is described in ldap_table(5).
mysql (read-only)
Perform lookups using the MYSQL protocol.
This is described in mysql_table(5).
pcre (read-only)
A lookup table based on Perl Compatible Reg-
ular Expressions. The file format is
described in pcre_table(5).
pgsql (read-only)
Perform lookups using the PostgreSQL proto-
col. This is described in pgsql_table(5).
proxy (read-only)
A lookup table that is implemented via the
Postfix proxymap(8) service. The table name
syntax is type:name.
regexp (read-only)
A lookup table based on regular expressions.
The file format is described in regexp_ta-
ble(5).
sdbm An indexed file type based on hashing. This
is available on systems with support for
SDBM databases.
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)
Perform lookups using a simple request-reply
protocol that is described in tcp_table(5).
This feature is not included with the stable
Postfix release.
unix (read-only)
A limited way to query the UNIX authentica-
tion database. The following tables are
implemented:
unix:passwd.byname
The table is the UNIX password data-
base. 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 Post-
fix was built.
-n Print parameter settings that are not left at their
built-in default value, because they are explicitly
specified in main.cf.
-t [template_file]
Display the templates for delivery status notifica-
tion (DSN) messages. To override the built-in tem-
plates, specify a template file at the end of the
command line, or specify a template file in main.cf
with the bounce_template_file parameter. To force
selection of the built-in templates, specify an
empty template file name (in shell language: "").
This feature is available with Postfix 2.3 and
later.
-v Enable verbose logging for debugging purposes. Mul-
tiple -v options make the software increasingly
verbose.
-# Edit the main.cf configuration file. The file is
copied to a temporary file then renamed into place.
The parameters specified on the command line are
commented-out, so that they revert to their default
values. Specify a list of parameter names, not
name=value pairs. There is no postconf command to
perform the reverse operation.
This feature is available with Postfix 2.6 and
later.
DIAGNOSTICS
Problems are reported to the standard error stream.
ENVIRONMENT
MAIL_CONFIG
Directory with Postfix configuration files.
CONFIGURATION PARAMETERS
The following main.cf parameters are especially relevant
to this program.
The text below provides only a parameter summary. See
postconf(5) for more details including examples.
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 mes-
sage templates.
FILES
/etc/postfix/main.cf, Postfix configuration parameters
SEE ALSO
bounce(5), bounce template file format
postconf(5), configuration parameters
README FILES
DATABASE_README, Postfix lookup table overview
LICENSE
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
POSTCONF(1)
@
1.1.1.1.2.3
log
@Pull up following revision(s) (requested by tron in ticket #1425):
Update Postfix to version 2.7.1:
- Improved before-queue content filter performance. With
"smtpd_proxy_options = speed_adjust", the Postfix SMTP server
receives the entire message before it connects to a before-queue
content filter. Typically, this allows Postfix to handle the same
mail load with fewer content filter processes.
- Improved address verification performance. The verify database is now
persistent by default, and it is automatically cleaned periodically.
Under overload conditions, the Postfix SMTP server no longer waits
up to 6 seconds for an address probe to complete.
- Support for reputation management based on the local SMTP client
IP address. This is typically implemented with
"FILTER transportname:" actions in access maps or header/body checks,
and mail delivery transports in master.cf with
unique smtp_bind_address values.
@
text
@a142 4
internal
A non-shared, in-memory hash table. Its con-
tent are lost when a process terminates.
d144 1
a144 1
Perform lookups using the LDAP protocol.
d148 1
a148 1
Perform lookups using the MYSQL protocol.
d153 1
a153 1
ular Expressions. The file format is
d157 1
a157 1
Perform lookups using the PostgreSQL proto-
d161 2
a162 2
A lookup table that is implemented via the
Postfix proxymap(8) service. The table name
d167 1
a167 1
The file format is described in regexp_ta-
d171 1
a171 1
is available on systems with support for
d175 3
a177 3
A table that always returns its name as
lookup result. For example, static:foobar
always returns the string foobar as lookup
d182 1
a182 1
protocol that is described in tcp_table(5).
d187 1
a187 1
A limited way to query the UNIX authentica-
d192 3
a194 3
The table is the UNIX password data-
base. The key is a login name. The
result is a password file entry in
d199 2
a200 2
The key is a group name. The result
is a group file entry in group(5)
d203 1
a203 1
Other table types may exist depending on how Post-
d212 2
a213 2
tion (DSN) messages. To override the built-in tem-
plates, specify a template file at the end of the
d215 2
a216 2
with the bounce_template_file parameter. To force
selection of the built-in templates, specify an
d219 1
a219 1
This feature is available with Postfix 2.3 and
d223 1
a223 1
tiple -v options make the software increasingly
d226 1
a226 1
-# Edit the main.cf configuration file. The file is
d228 1
a228 1
The parameters specified on the command line are
d230 2
a231 2
values. Specify a list of parameter names, not
name=value pairs. There is no postconf command to
d234 1
a234 1
This feature is available with Postfix 2.6 and
d245 1
a245 1
The following main.cf parameters are especially relevant
d248 1
a248 1
The text below provides only a parameter summary. See
d252 1
a252 1
The default location of the Postfix main.cf and
d256 1
a256 1
Pathname of a configuration file with bounce mes-
d270 1
a270 1
The Secure Mailer license must be distributed with this
@