trivial-rewrite

title: trivial-rewrite(8)

text:
# trivial-rewrite(8)

## NAME
trivial-rewrite - Postfix address rewriting and resolving daemon

## SYNOPSIS

```
trivial-rewrite [generic Postfix daemon options]
```

## DESCRIPTION

The trivial-rewrite(8) daemon processes three types of client service requests:

rewrite context address

Rewrite an address to standard form, according to the address rewriting context:

local

Append the domain names specified with $myorigin or $mydomain to incomplete addresses; do swap_bangpath and allow_percent_hack processing as described below, and strip source routed addresses (@site,@site:user@domain) to user@domain form.

remote

Append the domain name specified with $remote_header_rewrite_domain to incomplete addresses. Otherwise the result is identical to that of the local address rewriting context. This prevents Postfix from appending the local domain to spam from poorly written remote clients.

resolve sender address

Resolve the address to a (transport, nexthop, recipient, flags) quadruple. The meaning of the results is as follows:

transport

The delivery agent to use. This is the first field of an entry in the master.cf file.

nexthop

The host to send to and optional delivery method information.

recipient

The envelope recipient address that is passed on to nexthop.

flags

The address class, whether the address requires relaying, whether the address has problems, and whether the request failed.

verify sender address

Resolve the address for address verification purposes.

## SERVER PROCESS MANAGEMENT

```

```

The trivial-rewrite(8) servers run under control by the Postfix master(8) server. Each server can handle multiple simultaneous connections. When all servers are busy while a client connects, the master creates a new server process, provided that the trivial-rewrite server process limit is not exceeded. Each trivial-rewrite server terminates after serving at least $max_use clients of after $max_idle seconds of idle time.

## STANDARDS

```

```

None. The command does not interact with the outside world.

## SECURITY

```

```

The trivial-rewrite(8) daemon is not security sensitive. By default, this daemon does not talk to remote or local users. It can run at a fixed low privilege in a chrooted environment.

## DIAGNOSTICS

Problems and transactions are logged to syslogd(8) or postlogd(8).

## CONFIGURATION PARAMETERS

```

```

On busy mail systems a long time may pass before a main.cf change affecting trivial-rewrite(8) is picked up. Use the command "postfix reload" to speed up a change.

The text below provides only a parameter summary. See postconf(5) for more details including examples.

## COMPATIBILITY CONTROLS

```

```

resolve_dequoted_address (yes)

Resolve a recipient address safely instead of correctly, by looking inside quotes.

Available with Postfix version 2.1 and later:

resolve_null_domain (no)

Resolve an address that ends in the "@" null domain as if the local hostname were specified, instead of rejecting the address as invalid.

Available with Postfix version 2.3 and later:

resolve_numeric_domain (no)

Resolve "user@ipaddress" as "user@[ipaddress]", instead of rejecting the address as invalid.

Available with Postfix version 2.5 and later:

allow_min_user (no)

Allow a sender or recipient address to have `-' as the first character.

## ADDRESS REWRITING CONTROLS

```

```

myorigin ($myhostname)

The domain name that locally-posted mail appears to come from, and that locally posted mail is delivered to.

allow_percent_hack (yes)

Enable the rewriting of the form "user%domain" to "user@domain".

append_at_myorigin (yes)

With locally submitted mail, append the string "@$myorigin" to mail addresses without domain information.

append_dot_mydomain (Postfix >= 3.0: no, Postfix < 3.0: yes)

With locally submitted mail, append the string ".$mydomain" to addresses that have no ".domain" information.

recipient_delimiter (empty)

The set of characters that can separate an email address localpart, user name, or a .forward file name from its extension.

swap_bangpath (yes)

Enable the rewriting of "site!user" into "user@site".

Available in Postfix 2.2 and later:

remote_header_rewrite_domain (empty)

Rewrite or add message headers in mail from remote clients if the remote_header_rewrite_domain parameter value is non-empty, updating incomplete addresses with the domain specified in the remote_header_rewrite_domain parameter, and adding missing headers.

## ROUTING CONTROLS

```

```

The following is applicable to Postfix version 2.0 and later. Earlier versions do not have support for: virtual_transport, relay_transport, virtual_alias_domains, virtual_mailbox_domains or proxy_interfaces.

local_transport (local:$myhostname)

The default mail delivery transport and next-hop destination for final delivery to domains listed with mydestination, and for [ipaddress] destinations that match $inet_interfaces or $proxy_interfaces.

virtual_transport (virtual)

The default mail delivery transport and next-hop destination for final delivery to domains listed with $virtual_mailbox_domains.

relay_transport (relay)

The default mail delivery transport and next-hop destination for remote delivery to domains listed with $relay_domains.

default_transport (smtp)

The default mail delivery transport and next-hop destination for destinations that do not match $mydestination, $inet_interfaces, $proxy_interfaces, $virtual_alias_domains, $virtual_mailbox_domains, or $relay_domains.

parent_domain_matches_subdomains (see 'postconf -d' output)

A list of Postfix features where the pattern "example.com" also matches subdomains of example.com, instead of requiring an explicit ".example.com" pattern.

relayhost (empty)

The next-hop destination(s) for non-local mail; overrides non-local domains in recipient addresses.

transport_maps (empty)

Optional lookup tables with mappings from recipient address to (message delivery transport, next-hop destination).

Available in Postfix version 2.3 and later:

sender_dependent_relayhost_maps (empty)

A sender-dependent override for the global relayhost parameter setting.

Available in Postfix version 2.5 and later:

empty_address_relayhost_maps_lookup_key (<>)

The sender_dependent_relayhost_maps search string that will be used instead of the null sender address.

Available in Postfix version 2.7 and later:

empty_address_default_transport_maps_lookup_key (<>)

The sender_dependent_default_transport_maps search string that will be used instead of the null sender address.

sender_dependent_default_transport_maps (empty)

A sender-dependent override for the global default_transport parameter setting.

## ADDRESS VERIFICATION CONTROLS

```

```

Postfix version 2.1 introduces sender and recipient address verification. This feature is implemented by sending probe email messages that are not actually delivered. By default, address verification probes use the same route as regular mail. To override specific aspects of message routing for address verification probes, specify one or more of the following:

address_verify_local_transport ($local_transport)

Overrides the local_transport parameter setting for address verification probes.

address_verify_virtual_transport ($virtual_transport)

Overrides the virtual_transport parameter setting for address verification probes.

address_verify_relay_transport ($relay_transport)

Overrides the relay_transport parameter setting for address verification probes.

address_verify_default_transport ($default_transport)

Overrides the default_transport parameter setting for address verification probes.

address_verify_relayhost ($relayhost)

Overrides the relayhost parameter setting for address verification probes.

address_verify_transport_maps ($transport_maps)

Overrides the transport_maps parameter setting for address verification probes.

Available in Postfix version 2.3 and later:

address_verify_sender_dependent_relayhost_maps ($sender_dependent_relayhost_maps)

Overrides the sender_dependent_relayhost_maps parameter setting for address verification probes.

Available in Postfix version 2.7 and later:

address_verify_sender_dependent_default_transport_maps ($sender_dependent_default_transport_maps)

Overrides the sender_dependent_default_transport_maps parameter setting for address verification probes.

## MISCELLANEOUS CONTROLS

```

```

config_directory (see 'postconf -d' output)

The default location of the Postfix main.cf and master.cf configuration files.

daemon_timeout (18000s)

How much time a Postfix daemon process may take to handle a request before it is terminated by a built-in watchdog timer.

empty_address_recipient (MAILER-DAEMON)

The recipient of mail addressed to the null address.

ipc_timeout (3600s)

The time limit for sending or receiving information over an internal communication channel.

max_idle (100s)

The maximum amount of time that an idle Postfix daemon process waits for an incoming connection before terminating voluntarily.

max_use (100)

The maximal number of incoming connections that a Postfix daemon process will service before terminating voluntarily.

relocated_maps (empty)

Optional lookup tables with new contact information for users or domains that no longer exist.

process_id (read-only)

The process ID of a Postfix command or daemon process.

process_name (read-only)

The process name of a Postfix command or daemon process.

queue_directory (see 'postconf -d' output)

The location of the Postfix top-level queue directory.

show_user_unknown_table_name (yes)

Display the name of the recipient table in the "User unknown" responses.

syslog_facility (mail)

The syslog facility of Postfix logging.

syslog_name (see 'postconf -d' output)

A prefix that is prepended to the process name in syslog records, so that, for example, "smtpd" becomes "prefix/smtpd".

Available in Postfix version 2.0 and later:

helpful_warnings (yes)

Log warnings about problematic configuration settings, and provide helpful suggestions.

Available in Postfix 3.3 and later:

service_name (read-only)

The master.cf service name of a Postfix daemon process.

## SEE ALSO

```
postconf(5), configuration parameters
transport(5), transport table format
relocated(5), format of the "user has moved" table
master(8), process manager
postlogd(8), Postfix logging
syslogd(8), system logging
```

## README FILES

```

```

Use "postconf readme_directory" or "postconf html_directory" to locate this information.

```
ADDRESS_CLASS_README, Postfix address classes howto
ADDRESS_VERIFICATION_README, Postfix address verification
```

## 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
Wietse Venema
Google, Inc.
111 8th Avenue
New York, NY 10011, USA
```


verify

package: postfix

title: verify(8)

text:
# verify(8)

## NAME
verify - Postfix address verification server

## SYNOPSIS

```
verify [generic Postfix daemon options]
```

## DESCRIPTION

The verify(8) address verification server maintains a record of what recipient addresses are known to be deliverable or undeliverable.

Addresses are verified by injecting probe messages into the Postfix queue. Probe messages are run through all the routing and rewriting machinery except for final delivery, and are discarded rather than being deferred or bounced.

Address verification relies on the answer from the nearest MTA for the specified address, and will therefore not detect all undeliverable addresses.

The verify(8) server is designed to run under control by the Postfix master server. It maintains an optional persistent database. To avoid being interrupted by "postfix stop" in the middle of a database update, the process runs in a separate process group.

The verify(8) server implements the following requests:

update address status text

Update the status and text of the specified address.

query address

Look up the status and text for the specified address. If the status is unknown, a probe is sent and an "in progress" status is returned.

## SECURITY

```

```

The address verification server is not security-sensitive. It does not talk to the network, and it does not talk to local users. The verify server can run chrooted at fixed low privilege.

The address verification server can be coerced to store unlimited amounts of garbage. Limiting the cache expiry time trades one problem (disk space exhaustion) for another one (poor response time to client requests).

With Postfix version 2.5 and later, the verify(8) server no longer uses root privileges when opening the address_verify_map cache file. The file should now be stored under the Postfix-owned data_directory. As a migration aid, an attempt to open a cache file under a non-Postfix directory is redirected to the Postfix-owned data_directory, and a warning is logged.

## DIAGNOSTICS

Problems and transactions are logged to syslogd(8) or postlogd(8).

## BUGS

Address verification probe messages add additional traffic to the mail queue. Recipient verification may cause an increased load on down-stream servers in the case of a dictionary attack or a flood of backscatter bounces. Sender address verification may cause your site to be denylisted by some providers.

If the persistent database ever gets corrupted then the world comes to an end and human intervention is needed. This violates a basic Postfix principle.

## CONFIGURATION PARAMETERS

```

```

Changes to main.cf are not picked up automatically, as verify(8) processes are long-lived. Use the command "postfix reload" after a configuration change.

The text below provides only a parameter summary. See postconf(5) for more details including examples.

## PROBE MESSAGE CONTROLS

```

```

address_verify_sender ($double_bounce_sender)

The sender address to use in address verification probes; prior to Postfix 2.5 the default was "postmaster".

Available with Postfix 2.9 and later:

address_verify_sender_ttl (0s)

The time between changes in the time-dependent portion of address verification probe sender addresses.

## CACHE CONTROLS

```

```

address_verify_map (see 'postconf -d' output)

Lookup table for persistent address verification status storage.

address_verify_positive_expire_time (31d)

The time after which a successful probe expires from the address verification cache.

address_verify_positive_refresh_time (7d)

The time after which a successful address verification probe needs to be refreshed.

address_verify_negative_cache (yes)

Enable caching of failed address verification probe results.

address_verify_negative_expire_time (3d)

The time after which a failed probe expires from the address verification cache.

address_verify_negative_refresh_time (3h)

The time after which a failed address verification probe needs to be refreshed.

Available with Postfix 2.7 and later:

address_verify_cache_cleanup_interval (12h)

The amount of time between verify(8) address verification database cleanup runs.

## PROBE MESSAGE ROUTING CONTROLS

```

```

By default, probe messages are delivered via the same route as regular messages. The following parameters can be used to override specific message routing mechanisms.

address_verify_relayhost ($relayhost)

Overrides the relayhost parameter setting for address verification probes.

address_verify_transport_maps ($transport_maps)

Overrides the transport_maps parameter setting for address verification probes.

address_verify_local_transport ($local_transport)

Overrides the local_transport parameter setting for address verification probes.

address_verify_virtual_transport ($virtual_transport)

Overrides the virtual_transport parameter setting for address verification probes.

address_verify_relay_transport ($relay_transport)

Overrides the relay_transport parameter setting for address verification probes.

address_verify_default_transport ($default_transport)

Overrides the default_transport parameter setting for address verification probes.

Available in Postfix 2.3 and later:

address_verify_sender_dependent_relayhost_maps ($sender_dependent_relayhost_maps)

Overrides the sender_dependent_relayhost_maps parameter setting for address verification probes.

Available in Postfix 2.7 and later:

address_verify_sender_dependent_default_transport_maps ($sender_dependent_default_transport_maps)

Overrides the sender_dependent_default_transport_maps parameter setting for address verification probes.

## SMTPUTF8 CONTROLS

```

```

Preliminary SMTPUTF8 support is introduced with Postfix 3.0.

smtputf8_autodetect_classes (sendmail, verify)

Detect that a message requires SMTPUTF8 support for the specified mail origin classes.

Available in Postfix version 3.2 and later:

enable_idna2003_compatibility (no)

Enable 'transitional' compatibility between IDNA2003 and IDNA2008, when converting UTF-8 domain names to/from the ASCII form that is used for DNS lookups.

## MISCELLANEOUS CONTROLS

```

```

config_directory (see 'postconf -d' output)

The default location of the Postfix main.cf and master.cf configuration files.

daemon_timeout (18000s)

How much time a Postfix daemon process may take to handle a request before it is terminated by a built-in watchdog timer.

ipc_timeout (3600s)

The time limit for sending or receiving information over an internal communication channel.

process_id (read-only)

The process ID of a Postfix command or daemon process.

process_name (read-only)

The process name of a Postfix command or daemon process.

queue_directory (see 'postconf -d' output)

The location of the Postfix top-level queue directory.

syslog_facility (mail)

The syslog facility of Postfix logging.

syslog_name (see 'postconf -d' output)

A prefix that is prepended to the process name in syslog records, so that, for example, "smtpd" becomes "prefix/smtpd".

Available in Postfix 3.3 and later:

service_name (read-only)

The master.cf service name of a Postfix daemon process.

## SEE ALSO

```
smtpd(8), Postfix SMTP server
cleanup(8), enqueue Postfix message
postconf(5), configuration parameters
postlogd(8), Postfix logging
syslogd(8), system logging
```

## README FILES

```

```

Use "postconf readme_directory" or "postconf html_directory" to locate this information.

```
ADDRESS_VERIFICATION_README, address verification howto
```

## LICENSE

```

```

The Secure Mailer license must be distributed with this software.

## HISTORY

This service was introduced with Postfix version 2.1.

## AUTHOR(S)

```
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
Wietse Venema
Google, Inc.
111 8th Avenue
New York, NY 10011, USA
```


virtual

title: virtual(8)

text:
# virtual(8)

## NAME
virtual - Postfix virtual domain mail delivery agent

## SYNOPSIS

```
virtual [generic Postfix daemon options]
```

## DESCRIPTION

The virtual(8) delivery agent is designed for virtual mail hosting services. Originally based on the Postfix local(8) delivery agent, this agent looks up recipients with map lookups of their full recipient address, instead of using hard-coded unix password file lookups of the address local part only.

This delivery agent only delivers mail. Other features such as mail forwarding, out-of-office notifications, etc., must be configured via virtual_alias maps or via similar lookup mechanisms.

## MAILBOX LOCATION

```

```

The mailbox location is controlled by the virtual_mailbox_base and virtual_mailbox_maps configuration parameters (see below). The virtual_mailbox_maps table is indexed by the recipient address as described under TABLE SEARCH ORDER below.

The mailbox pathname is constructed as follows:

```
  $virtual_mailbox_base/$virtual_mailbox_maps(recipient)
```

where recipient is the full recipient address.

## UNIX MAILBOX FORMAT

```

```

When the mailbox location does not end in /, the message is delivered in UNIX mailbox format. This format stores multiple messages in one textfile.

The virtual(8) delivery agent prepends a "From sender time_stamp" envelope header to each message, prepends a Delivered-To: message header with the envelope recipient address, prepends an X-Original-To: header with the recipient address as given to Postfix, prepends a Return-Path: message header with the envelope sender address, prepends a > character to lines beginning with "From ", and appends an empty line.

The mailbox is locked for exclusive access while delivery is in progress. In case of problems, an attempt is made to truncate the mailbox to its original length.

## QMAIL MAILDIR FORMAT

```

```

When the mailbox location ends in /, the message is delivered in qmail maildir format. This format stores one message per file.

The virtual(8) delivery agent prepends a Delivered-To: message header with the final envelope recipient address, prepends an X-Original-To: header with the recipient address as given to Postfix, and prepends a Return-Path: message header with the envelope sender address.

By definition, maildir format does not require application-level file locking during mail delivery or retrieval.

## MAILBOX OWNERSHIP

```

```

Mailbox ownership is controlled by the virtual_uid_maps and virtual_gid_maps lookup tables, which are indexed with the full recipient address. Each table provides a string with the numerical user and group ID, respectively.

The virtual_minimum_uid parameter imposes a lower bound on numerical user ID values that may be specified in any virtual_uid_maps.

## CASE FOLDING

```

```

All delivery decisions are made using the full recipient address, folded to lower case. See also the next section for a few exceptions with optional address extensions.

## TABLE SEARCH ORDER

```

```

Normally, a lookup table is specified as a text file that serves as input to the postmap(1) command. The result, an indexed file in dbm or db format, is used for fast searching by the mail system.

The search order is as follows. The search stops upon the first successful lookup.

- When the recipient has an optional address extension the user+extension@domain.tld address is looked up first. With Postfix versions before 2.1, the optional address extension is always ignored.

- The user@domain.tld address, without address extension, is looked up next.

- Finally, the recipient @domain is looked up.

When the table is provided via other means such as NIS, LDAP or SQL, the same lookups are done as for ordinary indexed files.

Alternatively, a table can be provided as a regular-expression map where patterns are given as regular expressions. In that case, only the full recipient address is given to the regular-expression map.

## SECURITY

```

```

The virtual(8) delivery agent is not security sensitive, provided that the lookup tables with recipient user/group ID information are adequately protected. This program is not designed to run chrooted.

The virtual(8) delivery agent disallows regular expression substitution of $1 etc. in regular expression lookup tables, because that would open a security hole.

The virtual(8) delivery agent will silently ignore requests to use the proxymap(8) server. Instead it will open the table directly. Before Postfix version 2.2, the virtual delivery agent will terminate with a fatal error.

## STANDARDS

```
RFC 822 (ARPA Internet Text Messages)
```

## DIAGNOSTICS

Mail bounces when the recipient has no mailbox or when the recipient is over disk quota. In all other problem cases, mail for an existing recipient is deferred and a warning is logged.

Problems and transactions are logged to syslogd(8) or postlogd(8). Corrupted message files are marked so that the queue manager can move them to the corrupt queue afterwards.

Depending on the setting of the notify_classes parameter, the postmaster is notified of bounces and of other trouble.

## BUGS

This delivery agent supports address extensions in email addresses and in lookup table keys, but does not propagate address extension information to the result of table lookup.

Postfix should have lookup tables that can return multiple result attributes. In order to avoid the inconvenience of maintaining three tables, use an LDAP or MYSQL database.

## CONFIGURATION PARAMETERS

```

```

Changes to main.cf are picked up automatically, as virtual(8) processes run for only a limited amount of time. Use the command "postfix reload" to speed up a change.

The text below provides only a parameter summary. See postconf(5) for more details including examples.

## MAILBOX DELIVERY CONTROLS

```

```

virtual_mailbox_base (empty)

A prefix that the virtual(8) delivery agent prepends to all pathname results from $virtual_mailbox_maps table lookups.

virtual_mailbox_maps (empty)

Optional lookup tables with all valid addresses in the domains that match $virtual_mailbox_domains.

virtual_minimum_uid (500)

The minimum user ID value that the virtual(8) delivery agent accepts as a result from $virtual_uid_maps table lookup.

virtual_uid_maps (empty)

Lookup tables with the per-recipient user ID that the virtual(8) delivery agent uses while writing to the recipient's mailbox.

virtual_gid_maps (empty)

Lookup tables with the per-recipient group ID for virtual(8) mailbox delivery.

Available in Postfix version 2.0 and later:

virtual_mailbox_domains ($virtual_mailbox_maps)

Postfix is the final destination for the specified list of domains; mail is delivered via the $virtual_transport mail delivery transport.

virtual_transport (virtual)

The default mail delivery transport and next-hop destination for final delivery to domains listed with $virtual_mailbox_domains.

Available in Postfix version 2.5.3 and later:

strict_mailbox_ownership (yes)

Defer delivery when a mailbox file is not owned by its recipient.

## LOCKING CONTROLS

```

```

virtual_mailbox_lock (see 'postconf -d' output)

How to lock a UNIX-style virtual(8) mailbox before attempting delivery.

deliver_lock_attempts (20)

The maximal number of attempts to acquire an exclusive lock on a mailbox file or bounce(8) logfile.

deliver_lock_delay (1s)

The time between attempts to acquire an exclusive lock on a mailbox file or bounce(8) logfile.

stale_lock_time (500s)

The time after which a stale exclusive mailbox lockfile is removed.

## RESOURCE AND RATE CONTROLS

```

```

virtual_mailbox_limit (51200000)

The maximal size in bytes of an individual virtual(8) mailbox or maildir file, or zero (no limit).

Implemented in the qmgr(8) daemon:

virtual_destination_concurrency_limit ($default_destination_concurrency_limit)

The maximal number of parallel deliveries to the same destination via the virtual message delivery transport.

virtual_destination_recipient_limit ($default_destination_recipient_limit)

The maximal number of recipients per message for the virtual message delivery transport.

## MISCELLANEOUS CONTROLS

```

```

config_directory (see 'postconf -d' output)

The default location of the Postfix main.cf and master.cf configuration files.

daemon_timeout (18000s)

How much time a Postfix daemon process may take to handle a request before it is terminated by a built-in watchdog timer.

delay_logging_resolution_limit (2)

The maximal number of digits after the decimal point when logging sub-second delay values.

ipc_timeout (3600s)

The time limit for sending or receiving information over an internal communication channel.

max_idle (100s)

The maximum amount of time that an idle Postfix daemon process waits for an incoming connection before terminating voluntarily.

max_use (100)

The maximal number of incoming connections that a Postfix daemon process will service before terminating voluntarily.

process_id (read-only)

The process ID of a Postfix command or daemon process.

process_name (read-only)

The process name of a Postfix command or daemon process.

queue_directory (see 'postconf -d' output)

The location of the Postfix top-level queue directory.

syslog_facility (mail)

The syslog facility of Postfix logging.

syslog_name (see 'postconf -d' output)

A prefix that is prepended to the process name in syslog records, so that, for example, "smtpd" becomes "prefix/smtpd".

Available in Postfix version 3.0 and later:

virtual_delivery_status_filter ($default_delivery_status_filter)

Optional filter for the virtual(8) delivery agent to change the delivery status code or explanatory text of successful or unsuccessful deliveries.

Available in Postfix version 3.3 and later:

enable_original_recipient (yes)

Enable support for the original recipient address after an address is rewritten to a different address (for example with aliasing or with canonical mapping).

service_name (read-only)

The master.cf service name of a Postfix daemon process.

Available in Postfix 3.5 and later:

info_log_address_format (external)

The email address form that will be used in non-debug logging (info, warning, etc.).

## SEE ALSO

```
qmgr(8), queue manager
bounce(8), delivery status reports
postconf(5), configuration parameters
postlogd(8), Postfix logging
syslogd(8), system logging
```

## README_FILES

```
Use "postconf readme_directory" or
"postconf html_directory" to locate this information.
VIRTUAL_README, domain hosting howto
```

## LICENSE

```

```

The Secure Mailer license must be distributed with this software.

## HISTORY

This delivery agent was originally based on the Postfix local delivery agent. Modifications mainly consisted of removing code that either was not applicable or that was not safe in this context: aliases, ~user/.forward files, delivery to "|command" or to /file/name.

The Delivered-To: message header appears in the qmail system by Daniel Bernstein.

The maildir structure appears in the qmail system by Daniel Bernstein.

## AUTHOR(S)

```
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
Wietse Venema
Google, Inc.
111 8th Avenue
New York, NY 10011, USA
Andrew McNamara
andrewm@connect.com.au
connect.com.au Pty. Ltd.
Level 3, 213 Miller St
North Sydney 2060, NSW, Australia
```


tlsmgr

package: postfix-tls

title: tlsmgr(8)

text:
# tlsmgr(8)

## NAME
tlsmgr - Postfix TLS session cache and PRNG manager

## SYNOPSIS

```
tlsmgr [generic Postfix daemon options]
```

## DESCRIPTION

The tlsmgr(8) manages the Postfix TLS session caches. It stores and retrieves cache entries on request by smtpd(8) and smtp(8) processes, and periodically removes entries that have expired.

The tlsmgr(8) also manages the PRNG (pseudo random number generator) pool. It answers queries by the smtpd(8) and smtp(8) processes to seed their internal PRNG pools.

The tlsmgr(8)'s PRNG pool is initially seeded from an external source (EGD, /dev/urandom, or regular file). It is updated at configurable pseudo-random intervals with data from the external source. It is updated periodically with data from TLS session cache entries and with the time of day, and is updated with the time of day whenever a process requests tlsmgr(8) service.

The tlsmgr(8) saves the PRNG state to an exchange file periodically and when the process terminates, and reads the exchange file when initializing its PRNG.

## SECURITY

```

```

The tlsmgr(8) is not security-sensitive. The code that maintains the external and internal PRNG pools does not "trust" the data that it manipulates, and the code that maintains the TLS session cache does not touch the contents of the cached entries, except for seeding its internal PRNG pool.

The tlsmgr(8) can be run chrooted and with reduced privileges. At process startup it connects to the entropy source and exchange file, and creates or truncates the optional TLS session cache files.

With Postfix version 2.5 and later, the tlsmgr(8) no longer uses root privileges when opening cache files. These files should now be stored under the Postfix-owned data_directory. As a migration aid, an attempt to open a cache file under a non-Postfix directory is redirected to the Postfix-owned data_directory, and a warning is logged.

## DIAGNOSTICS

Problems and transactions are logged to syslogd(8) or postlogd(8).

## BUGS

There is no automatic means to limit the number of entries in the TLS session caches and/or the size of the TLS cache files.

## CONFIGURATION PARAMETERS

```

```

Changes to main.cf are not picked up automatically, because tlsmgr(8) is a persistent processes. Use the command "postfix reload" after a configuration change.

The text below provides only a parameter summary. See postconf(5) for more details including examples.

## TLS SESSION CACHE

```

```

lmtp_tls_loglevel (0)

The LMTP-specific version of the smtp_tls_loglevel configuration parameter.

lmtp_tls_session_cache_database (empty)

The LMTP-specific version of the smtp_tls_session_cache_database configuration parameter.

lmtp_tls_session_cache_timeout (3600s)

The LMTP-specific version of the smtp_tls_session_cache_timeout configuration parameter.

smtp_tls_loglevel (0)

Enable additional Postfix SMTP client logging of TLS activity.

smtp_tls_session_cache_database (empty)

Name of the file containing the optional Postfix SMTP client TLS session cache.

smtp_tls_session_cache_timeout (3600s)

The expiration time of Postfix SMTP client TLS session cache information.

smtpd_tls_loglevel (0)

Enable additional Postfix SMTP server logging of TLS activity.

smtpd_tls_session_cache_database (empty)

Name of the file containing the optional Postfix SMTP server TLS session cache.

smtpd_tls_session_cache_timeout (3600s)

The expiration time of Postfix SMTP server TLS session cache information.

## PSEUDO RANDOM NUMBER GENERATOR

```

```

tls_random_source (see 'postconf -d' output)

The external entropy source for the in-memory tlsmgr(8) pseudo random number generator (PRNG) pool.

tls_random_bytes (32)

The number of bytes that tlsmgr(8) reads from $tls_random_source when (re)seeding the in-memory pseudo random number generator (PRNG) pool.

tls_random_exchange_name (see 'postconf -d' output)

Name of the pseudo random number generator (PRNG) state file that is maintained by tlsmgr(8).

tls_random_prng_update_period (3600s)

The time between attempts by tlsmgr(8) to save the state of the pseudo random number generator (PRNG) to the file specified with $tls_random_exchange_name.

tls_random_reseed_period (3600s)

The maximal time between attempts by tlsmgr(8) to re-seed the in-memory pseudo random number generator (PRNG) pool from external sources.

## MISCELLANEOUS CONTROLS

```

```

config_directory (see 'postconf -d' output)

The default location of the Postfix main.cf and master.cf configuration files.

data_directory (see 'postconf -d' output)

The directory with Postfix-writable data files (for example: caches, pseudo-random numbers).

daemon_timeout (18000s)

How much time a Postfix daemon process may take to handle a request before it is terminated by a built-in watchdog timer.

process_id (read-only)

The process ID of a Postfix command or daemon process.

process_name (read-only)

The process name of a Postfix command or daemon process.

syslog_facility (mail)

The syslog facility of Postfix logging.

syslog_name (see 'postconf -d' output)

A prefix that is prepended to the process name in syslog records, so that, for example, "smtpd" becomes "prefix/smtpd".

Available in Postfix 3.3 and later:

service_name (read-only)

The master.cf service name of a Postfix daemon process.

## SEE ALSO

```
smtp(8), Postfix SMTP client
smtpd(8), Postfix SMTP server
postconf(5), configuration parameters
master(5), generic daemon options
master(8), process manager
postlogd(8), Postfix logging
syslogd(8), system logging
```

## README FILES

```

```

Use "postconf readme_directory" or "postconf html_directory" to locate this information.

```
TLS_README, Postfix TLS configuration and operation
```

## LICENSE

```

```

The Secure Mailer license must be distributed with this software.

## HISTORY

This service was introduced with Postfix version 2.2.

## AUTHOR(S)

```
Lutz Jaenicke
BTU Cottbus
Allgemeine Elektrotechnik
Universitaetsplatz 3-4
D-03044 Cottbus, Germany
Adapted by:
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
Wietse Venema
Google, Inc.
111 8th Avenue
New York, NY 10011, USA
```


tlsproxy

title: tlsproxy(8)

text:
# tlsproxy(8)

## NAME
tlsproxy - Postfix TLS proxy

## SYNOPSIS

```
tlsproxy [generic Postfix daemon options]
```

## DESCRIPTION

The tlsproxy(8) server implements a two-way TLS proxy. It is used by the postscreen(8) server to talk SMTP-over-TLS with remote SMTP clients that are not allowlisted (including clients whose allowlist status has expired), and by the smtp(8) client to support TLS connection reuse, but it should also work for non-SMTP protocols.

Although one tlsproxy(8) process can serve multiple sessions at the same time, it is a good idea to allow the number of processes to increase with load, so that the service remains responsive.

## PROTOCOL EXAMPLE

```

```

The example below concerns postscreen(8). However, the tlsproxy(8) server is agnostic of the application protocol, and the example is easily adapted to other applications.

After receiving a valid remote SMTP client STARTTLS command, the postscreen(8) server sends the remote SMTP client endpoint string, the requested role (server), and the requested timeout to tlsproxy(8). postscreen(8) then receives a "TLS available" indication from tlsproxy(8). If the TLS service is available, postscreen(8) sends the remote SMTP client file descriptor to tlsproxy(8), and sends the plaintext 220 greeting to the remote SMTP client. This triggers TLS negotiations between the remote SMTP client and tlsproxy(8). Upon completion of the TLS-level handshake, tlsproxy(8) translates between plaintext from/to postscreen(8) and ciphertext to/from the remote SMTP client.

## SECURITY

```

```

The tlsproxy(8) server is moderately security-sensitive. It talks to untrusted clients on the network. The process can be run chrooted at fixed low privilege.

## DIAGNOSTICS

Problems and transactions are logged to syslogd(8) or postlogd(8).

## CONFIGURATION PARAMETERS

```

```

Changes to main.cf are not picked up automatically, as tlsproxy(8) processes may run for a long time depending on mail server load. Use the command "postfix reload" to speed up a change.

The text below provides only a parameter summary. See postconf(5) for more details including examples.

## STARTTLS GLOBAL CONTROLS

```

```

The following settings are global and therefore cannot be overruled by information specified in a tlsproxy(8) client request.

tls_append_default_CA (no)

Append the system-supplied default Certification Authority certificates to the ones specified with *_tls_CApath or *_tls_CAfile.

tls_daemon_random_bytes (32)

The number of pseudo-random bytes that an smtp(8) or smtpd(8) process requests from the tlsmgr(8) server in order to seed its internal pseudo random number generator (PRNG).

tls_high_cipherlist (see 'postconf -d' output)

The OpenSSL cipherlist for "high" grade ciphers.

tls_medium_cipherlist (see 'postconf -d' output)

The OpenSSL cipherlist for "medium" or higher grade ciphers.

tls_null_cipherlist (eNULL:!aNULL)

The OpenSSL cipherlist for "NULL" grade ciphers that provide authentication without encryption.

tls_eecdh_strong_curve (prime256v1)

The elliptic curve used by the Postfix SMTP server for sensibly strong ephemeral ECDH key exchange.

tls_eecdh_ultra_curve (secp384r1)

The elliptic curve used by the Postfix SMTP server for maximally strong ephemeral ECDH key exchange.

tls_disable_workarounds (see 'postconf -d' output)

List or bit-mask of OpenSSL bug work-arounds to disable.

tls_preempt_cipherlist (no)

With SSLv3 and later, use the Postfix SMTP server's cipher preference order instead of the remote client's cipher preference order.

Available in Postfix version 2.8..3.7:

tls_low_cipherlist (see 'postconf -d' output)

The OpenSSL cipherlist for "low" or higher grade ciphers.

tls_export_cipherlist (see 'postconf -d' output)

The OpenSSL cipherlist for "export" or higher grade ciphers.

Available in Postfix version 2.9 and later:

tls_legacy_public_key_fingerprints (no)

A temporary migration aid for sites that use certificate public-key fingerprints with Postfix 2.9.0..2.9.5, which use an incorrect algorithm.

Available in Postfix version 2.11-3.1:

tls_dane_digest_agility (on)

Configure RFC7671 DANE TLSA digest algorithm agility.

tls_dane_trust_anchor_digest_enable (yes)

Enable support for RFC 6698 (DANE TLSA) DNS records that contain digests of trust-anchors with certificate usage "2".

Available in Postfix version 2.11 and later:

tlsmgr_service_name (tlsmgr)

The name of the tlsmgr(8) service entry in master.cf.

Available in Postfix version 3.0 and later:

tls_session_ticket_cipher (Postfix >= 3.0: aes-256-cbc, Postfix < 3.0: aes-128-cbc)

Algorithm used to encrypt RFC5077 TLS session tickets.

openssl_path (openssl)

The location of the OpenSSL command line program openssl(1).

Available in Postfix version 3.2 and later:

tls_eecdh_auto_curves (see 'postconf -d' output)

The prioritized list of elliptic curves supported by the Postfix SMTP client and server.

Available in Postfix version 3.4 and later:

tls_server_sni_maps (empty)

Optional lookup tables that map names received from remote SMTP clients via the TLS Server Name Indication (SNI) extension to the appropriate keys and certificate chains.

Available in Postfix 3.5, 3.4.6, 3.3.5, 3.2.10, 3.1.13 and later:

tls_fast_shutdown_enable (yes)

A workaround for implementations that hang Postfix while shutting down a TLS session, until Postfix times out.

Available in Postfix version 3.8 and later:

tls_ffdhe_auto_groups (see 'postconf -d' output)

The prioritized list of finite-field Diffie-Hellman ephemeral (FFDHE) key exchange groups supported by the Postfix SMTP client and server.

Available in Postfix 3.9, 3.8.1, 3.7.6, 3.6.10, 3.5.20 and later:

tls_config_file (default)

Optional configuration file with baseline OpenSSL settings.

tls_config_name (empty)

The application name passed by Postfix to OpenSSL library initialization functions.

## STARTTLS SERVER CONTROLS

```

```

These settings are clones of Postfix SMTP server settings. They allow tlsproxy(8) to load the same certificate and private key information as the Postfix SMTP server, before dropping privileges, so that the key files can be kept read-only for root. These settings can currently not be overruled by information in a tlsproxy(8) client request, but that limitation may be removed in a future version.

tlsproxy_tls_CAfile ($smtpd_tls_CAfile)

A file containing (PEM format) CA certificates of root CAs trusted to sign either remote SMTP client certificates or intermediate CA certificates.

tlsproxy_tls_CApath ($smtpd_tls_CApath)

A directory containing (PEM format) CA certificates of root CAs trusted to sign either remote SMTP client certificates or intermediate CA certificates.

tlsproxy_tls_always_issue_session_ids ($smtpd_tls_always_issue_session_ids)

Force the Postfix tlsproxy(8) server to issue a TLS session id, even when TLS session caching is turned off.

tlsproxy_tls_ask_ccert ($smtpd_tls_ask_ccert)

Ask a remote SMTP client for a client certificate.

tlsproxy_tls_ccert_verifydepth ($smtpd_tls_ccert_verifydepth)

The verification depth for remote SMTP client certificates.

tlsproxy_tls_cert_file ($smtpd_tls_cert_file)

File with the Postfix tlsproxy(8) server RSA certificate in PEM format.

tlsproxy_tls_ciphers ($smtpd_tls_ciphers)

The minimum TLS cipher grade that the Postfix tlsproxy(8) server will use with opportunistic TLS encryption.

tlsproxy_tls_dcert_file ($smtpd_tls_dcert_file)

File with the Postfix tlsproxy(8) server DSA certificate in PEM format.

tlsproxy_tls_dh1024_param_file ($smtpd_tls_dh1024_param_file)

File with DH parameters that the Postfix tlsproxy(8) server should use with non-export EDH ciphers.

tlsproxy_tls_dh512_param_file ($smtpd_tls_dh512_param_file)

File with DH parameters that the Postfix tlsproxy(8) server should use with export-grade EDH ciphers.

tlsproxy_tls_dkey_file ($smtpd_tls_dkey_file)

File with the Postfix tlsproxy(8) server DSA private key in PEM format.

tlsproxy_tls_eccert_file ($smtpd_tls_eccert_file)

File with the Postfix tlsproxy(8) server ECDSA certificate in PEM format.

tlsproxy_tls_eckey_file ($smtpd_tls_eckey_file)

File with the Postfix tlsproxy(8) server ECDSA private key in PEM format.

tlsproxy_tls_eecdh_grade ($smtpd_tls_eecdh_grade)

The Postfix tlsproxy(8) server security grade for ephemeral elliptic-curve Diffie-Hellman (EECDH) key exchange.

tlsproxy_tls_exclude_ciphers ($smtpd_tls_exclude_ciphers)

List of ciphers or cipher types to exclude from the tlsproxy(8) server cipher list at all TLS security levels.

tlsproxy_tls_fingerprint_digest ($smtpd_tls_fingerprint_digest)

The message digest algorithm to construct remote SMTP client-certificate fingerprints.

tlsproxy_tls_key_file ($smtpd_tls_key_file)

File with the Postfix tlsproxy(8) server RSA private key in PEM format.

tlsproxy_tls_loglevel ($smtpd_tls_loglevel)

Enable additional Postfix tlsproxy(8) server logging of TLS activity.

tlsproxy_tls_mandatory_ciphers ($smtpd_tls_mandatory_ciphers)

The minimum TLS cipher grade that the Postfix tlsproxy(8) server will use with mandatory TLS encryption.

tlsproxy_tls_mandatory_exclude_ciphers ($smtpd_tls_mandatory_exclude_ciphers)

Additional list of ciphers or cipher types to exclude from the tlsproxy(8) server cipher list at mandatory TLS security levels.

tlsproxy_tls_mandatory_protocols ($smtpd_tls_mandatory_protocols)

The SSL/TLS protocols accepted by the Postfix tlsproxy(8) server with mandatory TLS encryption.

tlsproxy_tls_protocols ($smtpd_tls_protocols)

List of TLS protocols that the Postfix tlsproxy(8) server will exclude or include with opportunistic TLS encryption.

tlsproxy_tls_req_ccert ($smtpd_tls_req_ccert)

With mandatory TLS encryption, require a trusted remote SMTP client certificate in order to allow TLS connections to proceed.

tlsproxy_tls_security_level ($smtpd_tls_security_level)

The SMTP TLS security level for the Postfix tlsproxy(8) server; when a non-empty value is specified, this overrides the obsolete parameters smtpd_use_tls and smtpd_enforce_tls.

tlsproxy_tls_chain_files ($smtpd_tls_chain_files)

Files with the Postfix tlsproxy(8) server keys and certificate chains in PEM format.

## STARTTLS CLIENT CONTROLS

```

```

These settings are clones of Postfix SMTP client settings. They allow tlsproxy(8) to load the same certificate and private key information as the Postfix SMTP client, before dropping privileges, so that the key files can be kept read-only for root. Some settings may be overruled by information in a tlsproxy(8) client request.

Available in Postfix version 3.4 and later:

tlsproxy_client_CAfile ($smtp_tls_CAfile)

A file containing CA certificates of root CAs trusted to sign either remote TLS server certificates or intermediate CA certificates.

tlsproxy_client_CApath ($smtp_tls_CApath)

Directory with PEM format Certification Authority certificates that the Postfix tlsproxy(8) client uses to verify a remote TLS server certificate.

tlsproxy_client_chain_files ($smtp_tls_chain_files)

Files with the Postfix tlsproxy(8) client keys and certificate chains in PEM format.

tlsproxy_client_cert_file ($smtp_tls_cert_file)

File with the Postfix tlsproxy(8) client RSA certificate in PEM format.

tlsproxy_client_key_file ($smtp_tls_key_file)

File with the Postfix tlsproxy(8) client RSA private key in PEM format.

tlsproxy_client_dcert_file ($smtp_tls_dcert_file)

File with the Postfix tlsproxy(8) client DSA certificate in PEM format.

tlsproxy_client_dkey_file ($smtp_tls_dkey_file)

File with the Postfix tlsproxy(8) client DSA private key in PEM format.

tlsproxy_client_eccert_file ($smtp_tls_eccert_file)

File with the Postfix tlsproxy(8) client ECDSA certificate in PEM format.

tlsproxy_client_eckey_file ($smtp_tls_eckey_file)

File with the Postfix tlsproxy(8) client ECDSA private key in PEM format.

tlsproxy_client_fingerprint_digest ($smtp_tls_fingerprint_digest)

The message digest algorithm used to construct remote TLS server certificate fingerprints.

tlsproxy_client_loglevel ($smtp_tls_loglevel)

Enable additional Postfix tlsproxy(8) client logging of TLS activity.

tlsproxy_client_loglevel_parameter (smtp_tls_loglevel)

The name of the parameter that provides the tlsproxy_client_loglevel value.

tlsproxy_client_scert_verifydepth ($smtp_tls_scert_verifydepth)

The verification depth for remote TLS server certificates.

tlsproxy_client_use_tls ($smtp_use_tls)

Opportunistic mode: use TLS when a remote server announces TLS support.

tlsproxy_client_enforce_tls ($smtp_enforce_tls)

Enforcement mode: require that SMTP servers use TLS encryption.

tlsproxy_client_per_site ($smtp_tls_per_site)

Optional lookup tables with the Postfix tlsproxy(8) client TLS usage policy by next-hop destination and by remote TLS server hostname.

Available in Postfix version 3.4-3.6:

tlsproxy_client_level ($smtp_tls_security_level)

The default TLS security level for the Postfix tlsproxy(8) client.

tlsproxy_client_policy ($smtp_tls_policy_maps)

Optional lookup tables with the Postfix tlsproxy(8) client TLS security policy by next-hop destination.

Available in Postfix version 3.7 and later:

tlsproxy_client_security_level ($smtp_tls_security_level)

The default TLS security level for the Postfix tlsproxy(8) client.

tlsproxy_client_policy_maps ($smtp_tls_policy_maps)

Optional lookup tables with the Postfix tlsproxy(8) client TLS security policy by next-hop destination.

## OBSOLETE STARTTLS SUPPORT CONTROLS

```

```

These parameters are supported for compatibility with smtpd(8) legacy parameters.

tlsproxy_use_tls ($smtpd_use_tls)

Opportunistic TLS: announce STARTTLS support to remote SMTP clients, but do not require that clients use TLS encryption.

tlsproxy_enforce_tls ($smtpd_enforce_tls)

Mandatory TLS: announce STARTTLS support to remote SMTP clients, and require that clients use TLS encryption.

tlsproxy_client_use_tls ($smtp_use_tls)

Opportunistic mode: use TLS when a remote server announces TLS support.

tlsproxy_client_enforce_tls ($smtp_enforce_tls)

Enforcement mode: require that SMTP servers use TLS encryption.

## RESOURCE CONTROLS

```

```

tlsproxy_watchdog_timeout (10s)

How much time a tlsproxy(8) process may take to process local or remote I/O before it is terminated by a built-in watchdog timer.

## MISCELLANEOUS CONTROLS

```

```

config_directory (see 'postconf -d' output)

The default location of the Postfix main.cf and master.cf configuration files.

process_id (read-only)

The process ID of a Postfix command or daemon process.

process_name (read-only)

The process name of a Postfix command or daemon process.

syslog_facility (mail)

The syslog facility of Postfix logging.

syslog_name (see 'postconf -d' output)

A prefix that is prepended to the process name in syslog records, so that, for example, "smtpd" becomes "prefix/smtpd".

Available in Postfix 3.3 and later:

service_name (read-only)

The master.cf service name of a Postfix daemon process.

## SEE ALSO

```
postscreen(8), Postfix zombie blocker
smtpd(8), Postfix SMTP server
postconf(5), configuration parameters
postlogd(8), Postfix logging
syslogd(8), system logging
```

## LICENSE

```

```

The Secure Mailer license must be distributed with this software.

## HISTORY

This service was introduced with Postfix version 2.8.

## AUTHOR(S)

```
Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA
Wietse Venema
Google, Inc.
111 8th Avenue
New York, NY 10011, USA
```


pgpool

title: pgpool(8)

summary: Pgpool\-II main server

text:
# pgpool(8)

## NAME
pgpool - Pgpool-II main server

## SYNOPSIS
pgpool [option...]

pgpool [option...] stop

pgpool [option...] reload

## DESCRIPTION
the Pgpool-II main server

## USAGES
pgpool runs in 3 modes: start, stop and reload. If none of stop or reload is given, it is assumed that "start" is specified.

## COMMON OPTIONS
These are common options for 3 modes.

-a hba_config_file

--hba-file=hba_config_file

Set the path to the pool_hba.conf configuration file. Mandatory if the file is placed other than the standard location.

-f config_file

--config-file=config_file

Set the path to the pgpool.conf configuration file. Mandatory if the file is placed other than the standard location.

-F pc_config_file

--pcp-file=pcp_config_file

Set the path to the pcp.conf configuration file. Mandatory if the file is placed other than the standard location.

-k key_file

--key-file=key_file

Set the path to the .pgpoolkey file. Mandatory if you use AES256 encrypted password and the file is placed other than the standard location and used.

-h

--help

Print help.

## STARTING PGPOOL-II MAIN SERVER
Here are options for the start mode.

-d

--debug

Run Pgpool-II in debug mode. Lots of debug messages are produced.

-n

--dont-detach

Don't run in daemon mode, does not detach control ttys.

-x

--debug-assertions

Turns on various assertion checks, This is a debugging aid.

-C

--clear-oidmaps

Clear query cache oidmaps when memqcache_method is memcached. If memqcache_method is shmem, Pgpool-II always discards oidmaps at the start-up time. So this option is not necessary.

-D

--discard-status

Discard pgpool_status file and do not restore previous status.

Caution

This option is testing purpose only for developers and you should not use it for other purposes. If pgpool_status is accidentally removed, Pgpool-II may go into split-brain (there are multiple primary servers exist).

## STOPPING PGPOOL-II MAIN SERVER
Here are options for the stop mode.

-m shutdown_mode

--mode=shutdown_mode

Stop Pgpool-II. shutdown_mode is either smart, fast or immediate. If smart is specified, Pgpool-II will wait for all clients are disconnected. If fast or immediate are specified, Pgpool-II immediately stops itself without waiting for all clients are disconnected. There's no difference between fast and immediate in the current implementation.

## RELOADING PGPOOL-II CONFIGURATION FILES
Reload configuration file of Pgpool-II. No specific options exist for reload mode. Common options are applicable.