netinfo tables yes (contributed)
newaliases yes (main alias database only)
nis tables yes
-nis+ tables not yet
+nis+ tables yes
no <> in smtp yes (most common address forms)
pgsql tables yes (contributed)
pipeline option yes (server and client)
the SMTP client. File: smtp/smtp_connect.c.
Robustness: extra sanity checks. Files: util/dict_db.c,
- util/dict_dbm.c.
+ util/dict_dbm.c, dict_nis.c.
+
+20041030
+
+ Compatibility: "session cache" renamed to "connection cache"
+ to avoid confusion with the TLS session cache.
Open problems:
- Low: reject HELO with any domain name that this MTA is
- final destination for.
+ Low: reject HELO with any domain name or IP address that
+ this MTA is the final destination for.
Low: should the Delivered-To: test in local(8) be configurable?
and change the patchlevel and the release date. Patches are never
issued for snapshot releases.
+Incompatible changes with snapshot Postfix-2.2-20041030
+=======================================================
+
+The SMTP session cache is renamed to connection cache, to avoid
+confusion with the TLS session cache. Thus, all session_cache_mumble
+parameters are now called connection_cache_mumble.
+
Incompatible changes with snapshot Postfix-2.2-20041023
=======================================================
The NIS+ client by Geoff Gibbs is now part of the Postfix source
tree. Details are given in the nisplus_table(5) manual page.
-By default, Postfix no longer appends the its own domain to addresses
+By default, Postfix no longer appends its own domain to addresses
in message headers from remote clients. Thus, spam from poorly
written software no longer looks like it came from a local user.
(mostly) client commands that are invoked by users, and by
a larger number of services that run in the background.
- Postfix services run under control of the <a href="master.8.html"><b>master</b>(8)</a> pro-
- cess. The master.cf configuration file defines how a
+ Postfix services are implemented by daemon processes.
+ These run in the background under control of the <a href="master.8.html"><b>master</b>(8)</a>
+ process. The master.cf configuration file defines how a
client program connects to a service, and what daemon pro-
- gram runs when a service is requested. Most daemon pro-
+ gram runs when a service is requested. Most daemon pro-
cesses are short-lived and terminate after serving <b><a href="postconf.5.html#max_use">max_use</a></b>
clients, or after inactivity for <b><a href="postconf.5.html#max_idle">max_idle</a></b> or more units of
time.
- All daemons specified here must speak a Postfix-internal
+ All daemons specified here must speak a Postfix-internal
protocol. In order to execute non-Postfix software use the
- <a href="local.8.html"><b>local</b>(8)</a>, <a href="pipe.8.html"><b>pipe</b>(8)</a> or <a href="spawn.8.html"><b>spawn</b>(8)</a> services, or run the server
+ <a href="local.8.html"><b>local</b>(8)</a>, <a href="pipe.8.html"><b>pipe</b>(8)</a> or <a href="spawn.8.html"><b>spawn</b>(8)</a> services, or run the server
under control by <b>inetd</b>(8) or equivalent.
- Changes in master.cf requires that "<b>postfix reload</b>" be
- executed in order to reload the configuration.
+ After changing master.cf you must execute "<b>postfix reload</b>"
+ to reload the configuration.
<b>SYNTAX</b>
The general format of the master.cf file is as follows:
<b>o</b> Each logical line defines a single Postfix service.
- Each service is identified by its name and type as
- described below. When multiple lines specify the
- same service name and type, only the last one is
+ Each service is identified by its name and type as
+ described below. When multiple lines specify the
+ same service name and type, only the last one is
remembered. Otherwise, the order of master.cf ser-
vice definitions does not matter.
- <b>o</b> Empty lines and whitespace-only lines are ignored,
- as are lines whose first non-whitespace character
+ <b>o</b> Empty lines and whitespace-only lines are ignored,
+ as are lines whose first non-whitespace character
is a `#'.
- <b>o</b> A logical line starts with non-whitespace text. A
- line that starts with whitespace continues a logi-
+ <b>o</b> A logical line starts with non-whitespace text. A
+ line that starts with whitespace continues a logi-
cal line.
- Each logical line consists of eight fields separated by
- whitespace. These are described below in the order as
+ Each logical line consists of eight fields separated by
+ whitespace. These are described below in the order as
they appear in the master.cf file.
Where applicable a field of "-" requests that the built-in
- default value be used. For boolean fields specify "y" or
+ default value be used. For boolean fields specify "y" or
"n" to override the default value.
<b>Service name</b>
<b>Service type</b>
Specify one of the following service types:
- <b>inet</b> The service listens on a TCP/IP socket and
+ <b>inet</b> The service listens on a TCP/IP socket and
is therefore accessible via the network.
- The service name is specified as <i>host:port</i>,
+ The service name is specified as <i>host:port</i>,
denoting the host and port on which new con-
- nections should be accepted. The host part
- (and colon) may be omitted. Either host or
- port may be given in symbolic form (host or
+ nections should be accepted. The host part
+ (and colon) may be omitted. Either host or
+ port may be given in symbolic form (host or
service name) or in numeric form (IP address
or port number).
- Examples: a service name of <b>127.0.0.1:smtp</b>
- receives mail via the loopback interface
- only; and a service name of <b>10025</b> accepts
+ Examples: a service name of <b>127.0.0.1:smtp</b>
+ receives mail via the loopback interface
+ only; and a service name of <b>10025</b> accepts
connections on TCP port 10025 via all inter-
- faces
configured with the <b><a href="postconf.5.html#inet_interfaces">inet_interfaces</a></b>
+ faces
configured with the <b><a href="postconf.5.html#inet_interfaces">inet_interfaces</a></b>
parameter.
- <b>unix</b> The service listens on a UNIX-domain socket
+ <b>unix</b> The service listens on a UNIX-domain socket
and is accessible for local clients only.
- The service name is a pathname relative to
- the Postfix queue directory (pathname con-
- trolled with the <b><a href="postconf.5.html#queue_directory">queue_directory</a></b> configura-
+ The service name is a pathname relative to
+ the Postfix queue directory (pathname con-
+ trolled with the <b><a href="postconf.5.html#queue_directory">queue_directory</a></b> configura-
tion parameter in main.cf).
- On Solaris systems the <b>unix</b> type is imple-
+ On Solaris systems the <b>unix</b> type is imple-
mented with streams sockets.
- <b>fifo</b> The service listens on a FIFO (named pipe)
+ <b>fifo</b> The service listens on a FIFO (named pipe)
and is accessible for local clients only.
- The service name is a pathname relative to
- the Postfix queue directory (pathname con-
- trolled with the <b><a href="postconf.5.html#queue_directory">queue_directory</a></b> configura-
+ The service name is a pathname relative to
+ the Postfix queue directory (pathname con-
+ trolled with the <b><a href="postconf.5.html#queue_directory">queue_directory</a></b> configura-
tion parameter in main.cf).
<b>Private (default: y)</b>
- Whether or not access is restricted to the mail
- system. Internet (type <b>inet</b>) services can't be
+ Whether or not access is restricted to the mail
+ system. Internet (type <b>inet</b>) services can't be
private.
<b>Unprivileged (default: y)</b>
Whether the service runs with root privileges or as
- the owner of the Postfix system (the owner name is
+ the owner of the Postfix system (the owner name is
controlled by the <b><a href="postconf.5.html#mail_owner">mail_owner</a></b> configuration variable
in the main.cf file).
- The
<a href="local.8.html"><b>local</b>(8)</a>, <a href="pipe.8.html"><b>pipe</b>(8)</a>, <a href="spawn.8.html"><b>spawn</b>(8)</a>, and <a href="virtual.8.html"><b>virtual</b>(8)</a>
+ The
<a href="local.8.html"><b>local</b>(8)</a>, <a href="pipe.8.html"><b>pipe</b>(8)</a>, <a href="spawn.8.html"><b>spawn</b>(8)</a>, and <a href="virtual.8.html"><b>virtual</b>(8)</a>
daemons require privileges.
<b>Chroot (default: y)</b>
- Whether or not the service runs chrooted to the
+ Whether or not the service runs chrooted to the
mail queue directory (pathname is controlled by the
- <b><a href="postconf.5.html#queue_directory">queue_directory</a></b> configuration variable in the
+ <b><a href="postconf.5.html#queue_directory">queue_directory</a></b> configuration variable in the
main.cf file).
Chroot should not be used with the <a href="local.8.html"><b>local</b>(8)</a>,
- <a href="pipe.8.html"><b>pipe</b>(8)</a>
and <a href="spawn.8.html"><b>spawn</b>(8)</a> daemons. Although the <a href="proxymap.8.html"><b>prox-</b></a>
- <a href="proxymap.8.html"><b>ymap</b>(8)</a> server can run chrooted, doing so defeats
- most of the purpose of having that service in the
+ <a href="pipe.8.html"><b>pipe</b>(8)</a>
and <a href="spawn.8.html"><b>spawn</b>(8)</a> daemons. Although the <a href="proxymap.8.html"><b>prox-</b></a>
+ <a href="proxymap.8.html"><b>ymap</b>(8)</a> server can run chrooted, doing so defeats
+ most of the purpose of having that service in the
first place.
The files in the examples/chroot-setup subdirectory
- of the Postfix source archive describe how to set
- up a Postfix chroot environment for your type of
- machine, and <a href="BASIC_CONFIGURATION_README.html">BASIC_CONFIGURATION_README</a> discusses
+ of the Postfix source archive describe how to set
+ up a Postfix chroot environment for your type of
+ machine, and <a href="BASIC_CONFIGURATION_README.html">BASIC_CONFIGURATION_README</a> discusses
issues related to running daemons chrooted.
<b>Wakeup time (default: 0)</b>
- Automatically wake up the named service after the
- specified number of seconds. The wake up is imple-
- mented by connecting to the service and sending a
- wake up request. A ? at the end of the wake up
- time field requests that wake up events be sent
- only to services that are actually being used.
+ Automatically wake up the named service after the
+ specified number of seconds. The wake up is imple-
+ mented by connecting to the service and sending a
+ wake up request. A ? at the end of the wake up
+ time field requests that wake up events be sent
+ only to services that are actually being used.
Specify 0 for no automatic wake up.
The <a href="pickup.8.html"><b>pickup</b>(8)</a>, <a href="qmgr.8.html"><b>qmgr</b>(8)</a> and <a href="flush.8.html"><b>flush</b>(8)</a> daemons require
a wake up timer.
<b>Process limit (default: $<a href="postconf.5.html#default_process_limit">default_process_limit</a>)</b>
- The maximum number of processes that may execute
- this service simultaneously. Specify 0 for no pro-
+ The maximum number of processes that may execute
+ this service simultaneously. Specify 0 for no pro-
cess count limit.
NOTE: Some Postfix services must be configured as a
- single-process service (for example, <a href="qmgr.8.html"><b>qmgr</b>(8)</a>) and
- some services must be configured with no process
+ single-process service (for example, <a href="qmgr.8.html"><b>qmgr</b>(8)</a>) and
+ some services must be configured with no process
limit (for example, <a href="cleanup.8.html"><b>cleanup</b>(8)</a>). These limits must
not be changed.
<b>Command name + arguments</b>
- The command to be executed. Characters that are
- special to the shell such as ">" or "|" have no
- special meaning here, and quotes cannot be used to
+ The command to be executed. Characters that are
+ special to the shell such as ">" or "|" have no
+ special meaning here, and quotes cannot be used to
protect arguments containing whitespace.
- The command name is relative to the Postfix daemon
+ The command name is relative to the Postfix daemon
directory (pathname is controlled by the <b><a href="postconf.5.html#daemon_directory">dae</a>-</b>
<b><a href="postconf.5.html#daemon_directory">mon_directory</a></b> configuration variable).
- The command argument syntax for specific commands
- is specified in the respective daemon manual page.
+ The command argument syntax for specific commands
+ is specified in the respective daemon manual page.
- The following command-line options have the same
+ The following command-line options have the same
effect for all daemon programs:
- <b>-D</b> Run the daemon under control by the command
+ <b>-D</b> Run the daemon under control by the command
specified with the <b><a href="postconf.5.html#debugger_command">debugger_command</a></b> variable
in the main.cf configuration file. See
<a href="DEBUG_README.html">DEBUG_README</a> for hints and tips.
<b>-o</b> <i>name</i>=<i>value</i>
Override the named main.cf configuration
- parameter. The parameter value can refer to
+ parameter. The parameter value can refer to
other parameters as <i>$name</i> etc., just like in
main.cf. See <a href="postconf.5.html"><b>postconf</b>(5)</a> for syntax.
NOTE 1: do not specify whitespace around the
- "=". In parameter values, either avoid
+ "=". In parameter values, either avoid
whitespace altogether, use commas instead of
- spaces, or consider overrides like "-o
- name=$override_parameter" with $over-
+ spaces, or consider overrides like "-o
+ name=$override_parameter" with $over-
ride_parameter set in main.cf.
- NOTE 2: Over-zealous use of parameter over-
- rides makes the Postfix configuration hard
- to understand and maintain. At a certain
- point, it might be easier to configure mul-
- tiple instances of Postfix, instead of con-
+ NOTE 2: Over-zealous use of parameter over-
+ rides makes the Postfix configuration hard
+ to understand and maintain. At a certain
+ point, it might be easier to configure mul-
+ tiple instances of Postfix, instead of con-
figuring multiple personalities via mas-
ter.cf.
- <b>-v</b> Increase the verbose logging level. Specify
- multiple <b>-v</b> options to make a command more
- verbose.
+ <b>-v</b> Increase the verbose logging level. Specify
+ multiple <b>-v</b> options to make a Postfix daemon
+ process increasingly verbose.
<b>SEE ALSO</b>
<a href="master.8.html">master(8)</a>, process manager
<a href="DEBUG_README.html">DEBUG_README</a>, Postfix debugging
<b>LICENSE</b>
- The Secure Mailer license must be distributed with this
+ The Secure Mailer license must be distributed with this
software.
<b>AUTHOR(S)</b>
<DT><b><a name="session_cache_service">session_cache_service</a>
(default: scache)</b></DT><DD>
-<p> The name of the <a href="scache.8.html">scache(8)</a> session cache service. This service
+<p> The name of the <a href="scache.8.html">scache(8)</a> connection cache service. This service
maintains a limited pool of cached sessions. </p>
(default: 600s)</b></DT><DD>
<p> How frequently the <a href="scache.8.html">scache(8)</a> server logs usage statistics with
-session cache hit and miss rates for logical destinations and for
+connection cache hit and miss rates for logical destinations and for
physical endpoints. </p>
<DT><b><a name="session_cache_ttl_limit">session_cache_ttl_limit</a>
(default: 2s)</b></DT><DD>
-<p> The maximal time-to-live value that the session cache server
+<p> The maximal time-to-live value that the connection cache server
allows. Requests that specify a larger TTL will be stored with the
maximum allowed TTL. The purpose of this additional control is to
protect the infrastructure against careless people. The cache TTL
<DT><b><a name="smtp_connection_cache_on_demand">smtp_connection_cache_on_demand</a>
(default: yes)</b></DT><DD>
-<p> Temporarily enable SMTP session caching while a destination
+<p> Temporarily enable SMTP connection caching while a destination
has a high volume of mail in the <a href="QSHAPE_README.html#active_queue">active queue</a>. With SMTP connection
caching, a connection is not closed immediately after completion
of a mail transaction. Instead, the connection is kept open for
<DT><b><a name="smtp_connection_cache_reuse_limit">smtp_connection_cache_reuse_limit</a>
(default: 10)</b></DT><DD>
-<p> When SMTP session caching is enabled, the number of times that
+<p> When SMTP connection caching is enabled, the number of times that
an SMTP session is reused before it is closed.
</p>
<DT><b><a name="smtp_connection_cache_time_limit">smtp_connection_cache_time_limit</a>
(default: 2s)</b></DT><DD>
-<p> When SMTP session caching is enabled, the amount of time that
+<p> When SMTP connection caching is enabled, the amount of time that
an unused SMTP client socket is kept open before it is closed. Do
not specify larger values without permission from the remote sites.
</p>
<li> <a href="qmqpd.8.html">qmqpd(8)</a>, Postfix QMQP server
-<li> <a href="scache.8.html">scache(8)</a>, Postfix session cache manager
+<li> <a href="scache.8.html">scache(8)</a>, Postfix connection cache manager
<li> <a href="showq.8.html">showq(8)</a>, list Postfix mail queue
<a href="proxymap.8.html">proxymap(8)</a>, Postfix lookup table proxy server
<a href="qmgr.8.html">qmgr(8)</a>, Postfix queue manager
<a href="qmqpd.8.html">qmqpd(8)</a>, Postfix QMQP server
- <a href="scache.8.html">scache(8)</a>, Postfix session cache manager
+ <a href="scache.8.html">scache(8)</a>, Postfix connection cache manager
<a href="showq.8.html">showq(8)</a>, list Postfix mail queue
<a href="smtp.8.html">smtp(8)</a>, Postfix SMTP client
<a href="smtpd.8.html">smtpd(8)</a>, Postfix SMTP server
SCACHE(8) SCACHE(8)
<b>NAME</b>
- scache - Postfix session cache server
+ scache - Postfix connection cache server
<b>SYNOPSIS</b>
<b>scache</b> [generic Postfix daemon options]
<b>DESCRIPTION</b>
- The <b>scache</b> server maintains a shared multi-session cache.
- This information can be used by, for example, Postfix SMTP
- clients or other Postfix delivery agents.
+ The <b>scache</b> server maintains a shared multi-connection
+ cache. This information can be used by, for example, Post-
+ fix SMTP clients or other Postfix delivery agents.
- The session cache is organized into logical destination
- names, physical endpoint names, and sessions.
+ The connection cache is organized into logical destination
+ names, physical endpoint names, and connections.
As a specific example, logical SMTP destinations specify
(transport, domain, port), and physical SMTP endpoints
- specify (transport, IP address, port). An SMTP session
+ specify (transport, IP address, port). An SMTP connection
may be saved after a successful mail transaction.
In the general case, one logical destination may refer to
zero or more physical endpoints, one physical endpoint may
be referenced by zero or more logical destinations, and
- one endpoint may refer to zero or more sessions.
+ one endpoint may refer to zero or more connections.
The exact syntax of a logical destination or endpoint name
is application dependent; the <b>scache</b> service does not
- care. A session is stored as a file descriptor together
- with application-dependent information that is needed to
- re-activate a session object. Again, the <b>scache</b> service is
- completely unaware about the details of that information.
+ care. A connection is stored as a file descriptor
+ together with application-dependent information that is
+ needed to re-activate a connection object. Again, the
+ <b>scache</b> service is completely unaware about the details of
+ that information.
All information is stored with a finite time to live
- (ttl). The session cache daemon terminates when no client
- is connected for <b><a href="postconf.5.html#max_idle">max_idle</a></b> time units.
+ (ttl). The connection cache daemon terminates when no
+
client is connected for <b><a href="postconf.5.html#max_idle">max_idle</a></b> time units.
This server implements the following requests:
<b>save_endp</b> <i>ttl endpoint endpoint</i><b>_</b><i>properties file</i><b>_</b><i>descriptor</i>
- Save the specified file descriptor and session
+ Save the specified file descriptor and connection
property data under the specified endpoint name.
The endpoint properties are used by the client to
- re-activate a passivated session object.
+ re-activate a passivated connection object.
<b>find_endp</b> <i>endpoint</i>
Look up cached properties and a cached file
<b>save_dest</b> <i>ttl destination destination</i><b>_</b><i>properties endpoint</i>
Save the binding between a logical destination and
an endpoint under the destination name, together
- with destination specific session properties. The
- destination properties are used by the client to
- re-activate a passivated session object.
+ with destination specific connection properties.
+ The destination properties are used by the client
+ to re-activate a passivated connection object.
<b>find_dest</b> <i>destination</i>
Look up cached destination properties, cached end-
the specified logical destination.
<b>SECURITY</b>
- The session cache server is not security-sensitive. It
+ The connection cache server is not security-sensitive. It
does not talk to the network, and it does not talk to
local users. The scache server can run chrooted at fixed
low privilege.
- The session cache server is not a trusted process. It must
- not be used to store information that is security sensi-
- tive.
+ The connection cache server is not a trusted process. It
+ must not be used to store information that is security
+ sensitive.
<b>DIAGNOSTICS</b>
Problems and transactions are logged to <b>syslogd</b>(8).
<b>BUGS</b>
Sessions cannot be cached across multiple machines.
- When a session expires from the cache it is closed without
- protocol specific handshake.
+ When a connection expires from the cache it is closed
+ without protocol specific handshake.
<b>CONFIGURATION PARAMETERS</b>
Changes to <b>main.cf</b> are picked up automatically as
<a href="postconf.5.html">postconf(5)</a> for more details including examples.
<b>RESOURCE CONTROLS</b>
- <b><a href="postconf.5.html#session_cache_ttl_limit">session_cache_ttl_limit</a> (2s)</b>
- The maximal time-to-live value that the session
+ <b><a href="postconf.5.html#connection_cache_ttl_limit">connection_cache_ttl_limit</a> (2s)</b>
+ The maximal time-to-live value that the connection
cache server allows.
- <b><a href="postconf.5.html#session_cache_status_update_time">session_cache_status_update_time</a> (600s)</b>
+ <b><a href="postconf.5.html#connection_cache_status_update_time">connection_cache_status_update_time</a> (600s)</b>
How frequently the <a href="scache.8.html">scache(8)</a> server logs usage
- statistics with session cache hit and miss rates
+ statistics with connection cache hit and miss rates
for logical destinations and for physical end-
points.
client will try to deliver the mail to an alternate host.
After a successful mail transaction, a session may be
- saved to the <a href="scache.8.html"><b>scache(8)</a></b> session cache server, so that it
+ saved to the <a href="scache.8.html"><b>scache(8)</a></b> connection cache server, so that it
may be used by any SMTP client for a subsequent transac-
tion.
- By default, session caching is enabled temporarily for
+ By default, connection caching is enabled temporarily for
destinations that have a high volume of mail in the active
queue. Session caching can be enabled permanently for spe-
cific destinations.
and of other trouble.
<b>BUGS</b>
- SMTP session caching does not work with TLS. The necessary
- support for TLS object passivation and re-activation does
- not exist without closing the session, which defeats the
- purpose.
+ SMTP connection caching does not work with TLS. The neces-
+ sary support for TLS object passivation and re-activation
+ does not exist without closing the session, which defeats
+ the purpose.
- SMTP session caching assumes that SASL credentials are
+ SMTP connection caching assumes that SASL credentials are
valid for all destinations that map onto the same IP
- address and TCP port.
+ address and TCP port, and for all sender and recipient
+ addresses.
<b>CONFIGURATION PARAMETERS</b>
Changes to <b>main.cf</b> are picked up automatically, as <a href="smtp.8.html">smtp(8)</a>
- processes run for only a limited amount of time. Use the
+ processes run for only a limited amount of time. Use the
command "<b>postfix reload</b>" to speed up a change.
- The text below provides only a parameter summary. See
+ The text below provides only a parameter summary. See
<a href="postconf.5.html">postconf(5)</a> for more details including examples.
<b>COMPATIBILITY CONTROLS</b>
Never send EHLO at the start of an SMTP session.
<b><a href="postconf.5.html#smtp_defer_if_no_mx_address_found">smtp_defer_if_no_mx_address_found</a> (no)</b>
- Defer mail delivery when no MX record resolves to
+ Defer mail delivery when no MX record resolves to
an IP address.
<b><a href="postconf.5.html#smtp_line_length_limit">smtp_line_length_limit</a> (990)</b>
that Postfix will send via SMTP.
<b><a href="postconf.5.html#smtp_pix_workaround_delay_time">smtp_pix_workaround_delay_time</a> (10s)</b>
- How long the Postfix SMTP client pauses before
+ How long the Postfix SMTP client pauses before
sending ".<CR><LF>" in order to work around the PIX
firewall "<CR><LF>.<CR><LF>" bug.
<b><a href="postconf.5.html#smtp_pix_workaround_threshold_time">smtp_pix_workaround_threshold_time</a> (500s)</b>
- How long a message must be queued before the PIX
- firewall "<CR><LF>.<CR><LF>" bug workaround is
+ How long a message must be queued before the PIX
+ firewall "<CR><LF>.<CR><LF>" bug workaround is
turned on.
<b><a href="postconf.5.html#smtp_quote_rfc821_envelope">smtp_quote_rfc821_envelope</a> (yes)</b>
- Quote addresses in SMTP MAIL FROM and RCPT TO com-
+ Quote addresses in SMTP MAIL FROM and RCPT TO com-
mands as required by <a href="http://www.faqs.org/rfcs/rfc821.html">RFC 821</a>.
<b><a href="postconf.5.html#smtp_skip_5xx_greeting">smtp_skip_5xx_greeting</a> (yes)</b>
(go away, do not try again later).
<b><a href="postconf.5.html#smtp_skip_quit_response">smtp_skip_quit_response</a> (yes)</b>
- Do not wait for the response to the SMTP QUIT com-
+ Do not wait for the response to the SMTP QUIT com-
mand.
Available in Postfix version 2.0 and earlier:
Available in Postfix version 2.0 and later:
<b><a href="postconf.5.html#disable_mime_output_conversion">disable_mime_output_conversion</a> (no)</b>
- Disable the conversion of 8BITMIME format to 7BIT
+ Disable the conversion of 8BITMIME format to 7BIT
format.
<b><a href="postconf.5.html#mime_boundary_length_limit">mime_boundary_length_limit</a> (2048)</b>
Available in Postfix version 2.1 and later:
<b><a href="postconf.5.html#smtp_send_xforward_command">smtp_send_xforward_command</a> (no)</b>
- Send the non-standard XFORWARD command when the
- Postfix SMTP server EHLO response announces XFOR-
+ Send the non-standard XFORWARD command when the
+ Postfix SMTP server EHLO response announces XFOR-
WARD support.
<b>SASL AUTHENTICATION CONTROLS</b>
<b><a href="postconf.5.html#smtp_sasl_auth_enable">smtp_sasl_auth_enable</a> (no)</b>
- Enable SASL authentication in the Postfix SMTP
+ Enable SASL authentication in the Postfix SMTP
client.
<b><a href="postconf.5.html#smtp_sasl_password_maps">smtp_sasl_password_maps</a> (empty)</b>
- Optional SMTP client lookup tables with one user-
- name:password entry per remote hostname or domain.
+ Optional SMTP client lookup tables with one user-
+ name:password entry per remote hostname or domain.
<b><a href="postconf.5.html#smtp_sasl_security_options">smtp_sasl_security_options</a> (noplaintext, noanonymous)</b>
- What authentication mechanisms the Postfix SMTP
+ What authentication mechanisms the Postfix SMTP
client is allowed to use.
Available in Postfix version 2.2 and later:
<b><a href="postconf.5.html#smtp_sasl_mechanism_filter">smtp_sasl_mechanism_filter</a> (empty)</b>
- If non-empty, filters the SMTP server's list of
+ If non-empty, filters the SMTP server's list of
offered SASL mechanisms.
<b>RESOURCE AND RATE CONTROLS</b>
<b><a href="postconf.5.html#smtp_destination_concurrency_limit">smtp_destination_concurrency_limit</a> ($<a href="postconf.5.html#default_destination_concurrency_limit">default_destina</a>-</b>
<b><a href="postconf.5.html#default_destination_concurrency_limit">tion_concurrency_limit</a>)</b>
- The maximal number of parallel deliveries to the
- same destination via the smtp message delivery
+ The maximal number of parallel deliveries to the
+ same destination via the smtp message delivery
transport.
<b><a href="postconf.5.html#smtp_destination_recipient_limit">smtp_destination_recipient_limit</a> ($<a href="postconf.5.html#default_destination_recipient_limit">default_destina</a>-</b>
<b><a href="postconf.5.html#default_destination_recipient_limit">tion_recipient_limit</a>)</b>
- The maximal number of recipients per delivery via
+ The maximal number of recipients per delivery via
the smtp message delivery transport.
<b><a href="postconf.5.html#smtp_connect_timeout">smtp_connect_timeout</a> (30s)</b>
- The SMTP client time limit for completing a TCP
+ The SMTP client time limit for completing a TCP
connection, or zero (use the operating system
built-in time limit).
<b><a href="postconf.5.html#smtp_helo_timeout">smtp_helo_timeout</a> (300s)</b>
- The SMTP client time limit for sending the HELO or
- EHLO command, and for receiving the initial server
+ The SMTP client time limit for sending the HELO or
+ EHLO command, and for receiving the initial server
response.
<b><a href="postconf.5.html#smtp_xforward_timeout">smtp_xforward_timeout</a> (300s)</b>
command, and for receiving the server response.
<b><a href="postconf.5.html#smtp_mail_timeout">smtp_mail_timeout</a> (300s)</b>
- The SMTP client time limit for sending the MAIL
- FROM command, and for receiving the server
+ The SMTP client time limit for sending the MAIL
+ FROM command, and for receiving the server
response.
<b><a href="postconf.5.html#smtp_rcpt_timeout">smtp_rcpt_timeout</a> (300s)</b>
- The SMTP client time limit for sending the SMTP
- RCPT TO command, and for receiving the server
+ The SMTP client time limit for sending the SMTP
+ RCPT TO command, and for receiving the server
response.
<b><a href="postconf.5.html#smtp_data_init_timeout">smtp_data_init_timeout</a> (120s)</b>
- The SMTP client time limit for sending the SMTP
- DATA command, and for receiving the server
+ The SMTP client time limit for sending the SMTP
+ DATA command, and for receiving the server
response.
<b><a href="postconf.5.html#smtp_data_xfer_timeout">smtp_data_xfer_timeout</a> (180s)</b>
- The SMTP client time limit for sending the SMTP
+ The SMTP client time limit for sending the SMTP
message content.
<b><a href="postconf.5.html#smtp_data_done_timeout">smtp_data_done_timeout</a> (600s)</b>
- The SMTP client time limit for sending the SMTP
+ The SMTP client time limit for sending the SMTP
".", and for receiving the server response.
<b><a href="postconf.5.html#smtp_quit_timeout">smtp_quit_timeout</a> (300s)</b>
- The SMTP client time limit for sending the QUIT
+ The SMTP client time limit for sending the QUIT
command, and for receiving the server response.
Available in Postfix version 2.1 and later:
lookups, or zero (no limit).
<b><a href="postconf.5.html#smtp_mx_session_limit">smtp_mx_session_limit</a> (2)</b>
- The maximal number of SMTP sessions per delivery
- request before giving up or delivering to a fall-
+ The maximal number of SMTP sessions per delivery
+ request before giving up or delivering to a fall-
back relay host, or zero (no limit).
<b><a href="postconf.5.html#smtp_rset_timeout">smtp_rset_timeout</a> (20s)</b>
- The SMTP client time limit for sending the RSET
+ The SMTP client time limit for sending the RSET
command, and for receiving the server response.
Available in Postfix version 2.2 and later:
<b><a href="postconf.5.html#smtp_connection_cache_destinations">smtp_connection_cache_destinations</a> (empty)</b>
- Permanently enable SMTP connection caching for the
+ Permanently enable SMTP connection caching for the
specified destinations.
<b><a href="postconf.5.html#smtp_connection_cache_on_demand">smtp_connection_cache_on_demand</a> (yes)</b>
- Temporarily enable SMTP session caching while a
+ Temporarily enable SMTP connection caching while a
destination has a high volume of mail in the active
queue.
<b><a href="postconf.5.html#smtp_connection_cache_reuse_limit">smtp_connection_cache_reuse_limit</a> (10)</b>
- When SMTP session caching is enabled, the number of
- times that an SMTP session is reused before it is
- closed.
+ When SMTP connection caching is enabled, the number
+ of times that an SMTP session is reused before it
+ is closed.
<b><a href="postconf.5.html#smtp_connection_cache_time_limit">smtp_connection_cache_time_limit</a> (2s)</b>
- When SMTP session caching is enabled, the amount of
- time that an unused SMTP client socket is kept open
- before it is closed.
+ When SMTP connection caching is enabled, the amount
+ of time that an unused SMTP client socket is kept
+ open before it is closed.
<b>TROUBLE SHOOTING CONTROLS</b>
<b><a href="postconf.5.html#debug_peer_level">debug_peer_level</a> (2)</b>
- The increment in verbose logging level when a
- remote client or server matches a pattern in the
+ The increment in verbose logging level when a
+ remote client or server matches a pattern in the
<a href="postconf.5.html#debug_peer_list">debug_peer_list</a> parameter.
<b><a href="postconf.5.html#debug_peer_list">debug_peer_list</a> (empty)</b>
- Optional list of remote client or server hostname
- or network address patterns that cause the verbose
- logging level to increase by the amount specified
+ Optional list of remote client or server hostname
+ or network address patterns that cause the verbose
+ logging level to increase by the amount specified
in $<a href="postconf.5.html#debug_peer_level">debug_peer_level</a>.
<b><a href="postconf.5.html#error_notice_recipient">error_notice_recipient</a> (postmaster)</b>
- The recipient of postmaster notifications about
- mail delivery problems that are caused by policy,
+ The recipient of postmaster notifications about
+ mail delivery problems that are caused by policy,
resource, software or protocol errors.
<b><a href="postconf.5.html#notify_classes">notify_classes</a> (resource, software)</b>
- The list of error classes that are reported to the
+ The list of error classes that are reported to the
postmaster.
<b>MISCELLANEOUS CONTROLS</b>
<b><a href="postconf.5.html#best_mx_transport">best_mx_transport</a> (empty)</b>
- Where the Postfix SMTP client should deliver mail
+ Where the Postfix SMTP client should deliver mail
when it detects a "mail loops back to myself" error
condition.
<b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b>
- The default location of the Postfix main.cf and
+ The default location of the Postfix main.cf and
master.cf configuration files.
<b><a href="postconf.5.html#daemon_timeout">daemon_timeout</a> (18000s)</b>
- How much time a Postfix daemon process may take to
- handle a request before it is terminated by a
+ How much time a Postfix daemon process may take to
+ handle a request before it is terminated by a
built-in watchdog timer.
<b><a href="postconf.5.html#disable_dns_lookups">disable_dns_lookups</a> (no)</b>
- Disable DNS lookups in the Postfix SMTP and LMTP
+ Disable DNS lookups in the Postfix SMTP and LMTP
clients.
<b><a href="postconf.5.html#fallback_relay">fallback_relay</a> (empty)</b>
- Optional list of relay hosts for SMTP destinations
+ Optional list of relay hosts for SMTP destinations
that can't be found or that are unreachable.
<b><a href="postconf.5.html#inet_interfaces">inet_interfaces</a> (all)</b>
over an internal communication channel.
<b><a href="postconf.5.html#max_idle">max_idle</a> (100s)</b>
- The maximum amount of time that an idle Postfix
- daemon process waits for the next service request
+ The maximum amount of time that an idle Postfix
+ daemon process waits for the next service request
before exiting.
<b><a href="postconf.5.html#max_use">max_use</a> (100)</b>
- The maximal number of connection requests before a
+ The maximal number of connection requests before a
Postfix daemon process terminates.
<b><a href="postconf.5.html#process_id">process_id</a> (read-only)</b>
- The process ID of a Postfix command or daemon pro-
+ The process ID of a Postfix command or daemon pro-
cess.
<b><a href="postconf.5.html#process_name">process_name</a> (read-only)</b>
- The process name of a Postfix command or daemon
+ The process name of a Postfix command or daemon
process.
<b><a href="postconf.5.html#proxy_interfaces">proxy_interfaces</a> (empty)</b>
The network interface addresses that this mail sys-
- tem receives mail on by way of a proxy or network
+ tem receives mail on by way of a proxy or network
address translation unit.
<b><a href="postconf.5.html#smtp_bind_address">smtp_bind_address</a> (empty)</b>
client should bind to when making a connection.
<b><a href="postconf.5.html#smtp_helo_name">smtp_helo_name</a> ($<a href="postconf.5.html#myhostname">myhostname</a>)</b>
- The hostname to send in the SMTP EHLO or HELO com-
+ The hostname to send in the SMTP EHLO or HELO com-
mand.
<b><a href="postconf.5.html#smtp_host_lookup">smtp_host_lookup</a> (dns)</b>
- What mechanisms when the SMTP client uses to look
+ What mechanisms when the SMTP client uses to look
up a host's IP address.
<b><a href="postconf.5.html#smtp_randomize_addresses">smtp_randomize_addresses</a> (yes)</b>
- Randomize the order of equal-preference MX host
+ Randomize the order of equal-preference MX host
addresses.
<b><a href="postconf.5.html#syslog_facility">syslog_facility</a> (mail)</b>
The syslog facility of Postfix logging.
<b><a href="postconf.5.html#syslog_name">syslog_name</a> (postfix)</b>
- The mail system name that is prepended to the pro-
+ The mail system name that is prepended to the pro-
cess name in syslog records, so that "smtpd"
becomes, for example, "postfix/smtpd".
<b>SEE ALSO</b>
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
<a href="bounce.8.html">bounce(8)</a>, delivery status reports
- <a href="scache.8.html">scache(8)</a>, session cache server
+ <a href="scache.8.html">scache(8)</a>, connection cache server
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
<a href="master.8.html">master(8)</a>, process manager
syslogd(8), system logging
<a href="SASL_README.html">SASL_README</a>, Postfix SASL howto
<b>LICENSE</b>
- The Secure Mailer license must be distributed with this
+ The Secure Mailer license must be distributed with this
software.
<b>AUTHOR(S)</b>
proxymap(8), Postfix lookup table proxy server
qmgr(8), Postfix queue manager
qmqpd(8), Postfix QMQP server
-scache(8), Postfix session cache manager
+scache(8), Postfix connection cache manager
showq(8), list Postfix mail queue
smtp(8), Postfix SMTP client
smtpd(8), Postfix SMTP server
(mostly) client commands that are invoked by users, and by
a larger number of services that run in the background.
-Postfix services run under control of the \fBmaster\fR(8)
+Postfix services are implemented by daemon processes. These
+run in the background under control of the \fBmaster\fR(8)
process. The master.cf configuration file defines how a
client program connects to a service, and what daemon
program runs when a service is requested. Most daemon
\fBlocal\fR(8), \fBpipe\fR(8) or \fBspawn\fR(8) services, or
run the server under control by \fBinetd\fR(8) or equivalent.
.PP
-Changes in master.cf requires that "\fBpostfix reload\fR" be
-executed in order to reload the configuration.
+After changing master.cf you must execute "\fBpostfix reload\fR"
+to reload the configuration.
.SH "SYNTAX"
.na
.nf
personalities via master.cf.
.IP \fB-v\fR
Increase the verbose logging level. Specify multiple \fB-v\fR
-options to make a command more verbose.
+options to make a Postfix daemon process increasingly verbose.
.SH "SEE ALSO"
.na
.nf
Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks).
The default time unit is s (seconds).
.SH session_cache_service (default: scache)
-The name of the scache(8) session cache service. This service
+The name of the scache(8) connection cache service. This service
maintains a limited pool of cached sessions.
.SH session_cache_status_update_time (default: 600s)
How frequently the scache(8) server logs usage statistics with
-session cache hit and miss rates for logical destinations and for
+connection cache hit and miss rates for logical destinations and for
physical endpoints.
.SH session_cache_ttl_limit (default: 2s)
-The maximal time-to-live value that the session cache server
+The maximal time-to-live value that the connection cache server
allows. Requests that specify a larger TTL will be stored with the
maximum allowed TTL. The purpose of this additional control is to
protect the infrastructure against careless people. The cache TTL
.PP
This feature is available in Postfix 2.2 and later.
.SH smtp_connection_cache_on_demand (default: yes)
-Temporarily enable SMTP session caching while a destination
+Temporarily enable SMTP connection caching while a destination
has a high volume of mail in the active queue. With SMTP connection
caching, a connection is not closed immediately after completion
of a mail transaction. Instead, the connection is kept open for
.PP
This feature is available in Postfix 2.2 and later.
.SH smtp_connection_cache_reuse_limit (default: 10)
-When SMTP session caching is enabled, the number of times that
+When SMTP connection caching is enabled, the number of times that
an SMTP session is reused before it is closed.
.PP
This feature is available in Postfix 2.2 and later.
.SH smtp_connection_cache_time_limit (default: 2s)
-When SMTP session caching is enabled, the amount of time that
+When SMTP connection caching is enabled, the amount of time that
an unused SMTP client socket is kept open before it is closed. Do
not specify larger values without permission from the remote sites.
.PP
.SH NAME
scache
\-
-Postfix session cache server
+Postfix connection cache server
.SH "SYNOPSIS"
.na
.nf
.SH DESCRIPTION
.ad
.fi
-The \fBscache\fR server maintains a shared multi-session
+The \fBscache\fR server maintains a shared multi-connection
cache. This information can be used by, for example, Postfix
SMTP clients or other Postfix delivery agents.
-The session cache is organized into logical destination
-names, physical endpoint names, and sessions.
+The connection cache is organized into logical destination
+names, physical endpoint names, and connections.
As a specific example, logical SMTP destinations specify
(transport, domain, port), and physical SMTP endpoints
-specify (transport, IP address, port). An SMTP session
+specify (transport, IP address, port). An SMTP connection
may be saved after a successful mail transaction.
In the general case, one logical destination may refer to
zero or more physical endpoints, one physical endpoint may
be referenced by zero or more logical destinations, and
-one endpoint may refer to zero or more sessions.
+one endpoint may refer to zero or more connections.
The exact syntax of a logical destination or endpoint name
is application dependent; the \fBscache\fR service does
-not care. A session is stored as a file descriptor together
+not care. A connection is stored as a file descriptor together
with application-dependent information that is needed to
-re-activate a session object. Again, the \fBscache\fR
+re-activate a connection object. Again, the \fBscache\fR
service is completely unaware about the details of that
information.
All information is stored with a finite time to live (ttl).
-The session cache daemon terminates when no client is
+The connection cache daemon terminates when no client is
connected for \fBmax_idle\fR time units.
This server implements the following requests:
.IP "\fBsave_endp\fI ttl endpoint endpoint_properties file_descriptor\fR"
-Save the specified file descriptor and session property data
+Save the specified file descriptor and connection property data
under the specified endpoint name. The endpoint properties
-are used by the client to re-activate a passivated session
+are used by the client to re-activate a passivated connection
object.
.IP "\fBfind_endp\fI endpoint\fR"
Look up cached properties and a cached file descriptor for the
.IP "\fBsave_dest\fI ttl destination destination_properties endpoint\fR"
Save the binding between a logical destination and an
endpoint under the destination name, together with destination
-specific session properties. The destination properties
-are used by the client to re-activate a passivated session
+specific connection properties. The destination properties
+are used by the client to re-activate a passivated connection
object.
.IP "\fBfind_dest\fI destination\fR"
Look up cached destination properties, cached endpoint properties,
.nf
.ad
.fi
-The session cache server is not security-sensitive. It does not
+The connection cache server is not security-sensitive. It does not
talk to the network, and it does not talk to local users.
The scache server can run chrooted at fixed low privilege.
-The session cache server is not a trusted process. It must
+The connection cache server is not a trusted process. It must
not be used to store information that is security sensitive.
.SH DIAGNOSTICS
.ad
.fi
Sessions cannot be cached across multiple machines.
-When a session expires from the cache it is closed without
+When a connection expires from the cache it is closed without
protocol specific handshake.
.SH "CONFIGURATION PARAMETERS"
.na
.nf
.ad
.fi
-.IP "\fBsession_cache_ttl_limit (2s)\fR"
-The maximal time-to-live value that the session cache server
+.IP "\fBconnection_cache_ttl_limit (2s)\fR"
+The maximal time-to-live value that the connection cache server
allows.
-.IP "\fBsession_cache_status_update_time (600s)\fR"
+.IP "\fBconnection_cache_status_update_time (600s)\fR"
How frequently the scache(8) server logs usage statistics with
-session cache hit and miss rates for logical destinations and for
+connection cache hit and miss rates for logical destinations and for
physical endpoints.
.SH "MISCELLANEOUS CONTROLS"
.na
deliver the mail to an alternate host.
After a successful mail transaction, a session may be saved
-to the \fBscache(8)\fR session cache server, so that it
+to the \fBscache(8)\fR connection cache server, so that it
may be used by any SMTP client for a subsequent transaction.
-By default, session caching is enabled temporarily for
+By default, connection caching is enabled temporarily for
destinations that have a high volume of mail in the active
queue. Session caching can be enabled permanently for
specific destinations.
.SH BUGS
.ad
.fi
-SMTP session caching does not work with TLS. The necessary
+SMTP connection caching does not work with TLS. The necessary
support for TLS object passivation and re-activation does not
exist without closing the session, which defeats the purpose.
-SMTP session caching assumes that SASL credentials are valid for
-all destinations that map onto the same IP address and TCP port.
+SMTP connection caching assumes that SASL credentials are valid for
+all destinations that map onto the same IP address and TCP port,
+and for all sender and recipient addresses.
.SH "CONFIGURATION PARAMETERS"
.na
.nf
Permanently enable SMTP connection caching for the specified
destinations.
.IP "\fBsmtp_connection_cache_on_demand (yes)\fR"
-Temporarily enable SMTP session caching while a destination
+Temporarily enable SMTP connection caching while a destination
has a high volume of mail in the active queue.
.IP "\fBsmtp_connection_cache_reuse_limit (10)\fR"
-When SMTP session caching is enabled, the number of times that
+When SMTP connection caching is enabled, the number of times that
an SMTP session is reused before it is closed.
.IP "\fBsmtp_connection_cache_time_limit (2s)\fR"
-When SMTP session caching is enabled, the amount of time that
+When SMTP connection caching is enabled, the amount of time that
an unused SMTP client socket is kept open before it is closed.
.SH "TROUBLE SHOOTING CONTROLS"
.na
.nf
qmgr(8), queue manager
bounce(8), delivery status reports
-scache(8), session cache server
+scache(8), connection cache server
postconf(5), configuration parameters
master(8), process manager
syslogd(8), system logging
s;\bservice_throttle_time\b;<a href="postconf.5.html#service_throttle_time">$&</a>;g;
s;\bsetgid_group\b;<a href="postconf.5.html#setgid_group">$&</a>;g;
- s;\bsession_cache_service\b;<a href="postconf.5.html#session_cache_service">$&</a>;g;
- s;\bsession_cache_status_update_time\b;<a href="postconf.5.html#session_cache_status_update_time">$&</a>;g;
- s;\bsession_cache_ttl_limit\b;<a href="postconf.5.html#session_cache_ttl_limit">$&</a>;g;
+ s;\bconnection_cache_service\b;<a href="postconf.5.html#connection_cache_service">$&</a>;g;
+ s;\bconnection_cache_status_update_time\b;<a href="postconf.5.html#connection_cache_status_update_time">$&</a>;g;
+ s;\bconnection_cache_ttl_limit\b;<a href="postconf.5.html#connection_cache_ttl_limit">$&</a>;g;
s;\bshow_user_unknown_table_name\b;<a href="postconf.5.html#show_user_unknown_table_name">$&</a>;g;
s;\bshowq_service_name\b;<a href="postconf.5.html#showq_service_name">$&</a>;g;
# (mostly) client commands that are invoked by users, and by
# a larger number of services that run in the background.
#
-# Postfix services run under control of the \fBmaster\fR(8)
+# Postfix services are implemented by daemon processes. These
+# run in the background under control of the \fBmaster\fR(8)
# process. The master.cf configuration file defines how a
# client program connects to a service, and what daemon
# program runs when a service is requested. Most daemon
# \fBlocal\fR(8), \fBpipe\fR(8) or \fBspawn\fR(8) services, or
# run the server under control by \fBinetd\fR(8) or equivalent.
# .PP
-# Changes in master.cf requires that "\fBpostfix reload\fR" be
-# executed in order to reload the configuration.
+# After changing master.cf you must execute "\fBpostfix reload\fR"
+# to reload the configuration.
# SYNTAX
# .ad
# .fi
# personalities via master.cf.
# .IP \fB-v\fR
# Increase the verbose logging level. Specify multiple \fB-v\fR
-# options to make a command more verbose.
+# options to make a Postfix daemon process increasingly verbose.
# SEE ALSO
# master(8), process manager
# postconf(5), configuration parameters
%PARAM smtp_connection_cache_time_limit 2s
-<p> When SMTP session caching is enabled, the amount of time that
+<p> When SMTP connection caching is enabled, the amount of time that
an unused SMTP client socket is kept open before it is closed. Do
not specify larger values without permission from the remote sites.
</p>
%PARAM smtp_connection_cache_reuse_limit 10
-<p> When SMTP session caching is enabled, the number of times that
+<p> When SMTP connection caching is enabled, the number of times that
an SMTP session is reused before it is closed.
</p>
%PARAM smtp_connection_cache_on_demand yes
-<p> Temporarily enable SMTP session caching while a destination
+<p> Temporarily enable SMTP connection caching while a destination
has a high volume of mail in the active queue. With SMTP connection
caching, a connection is not closed immediately after completion
of a mail transaction. Instead, the connection is kept open for
%PARAM session_cache_service scache
-<p> The name of the scache(8) session cache service. This service
+<p> The name of the scache(8) connection cache service. This service
maintains a limited pool of cached sessions. </p>
%PARAM session_cache_ttl_limit 2s
-<p> The maximal time-to-live value that the session cache server
+<p> The maximal time-to-live value that the connection cache server
allows. Requests that specify a larger TTL will be stored with the
maximum allowed TTL. The purpose of this additional control is to
protect the infrastructure against careless people. The cache TTL
%PARAM session_cache_status_update_time 600s
<p> How frequently the scache(8) server logs usage statistics with
-session cache hit and miss rates for logical destinations and for
+connection cache hit and miss rates for logical destinations and for
physical endpoints. </p>
%PARAM remote_header_rewrite_domain
/*
* Session cache service.
*/
-#define VAR_SCACHE_SERVICE "session_cache_service"
+#define VAR_SCACHE_SERVICE "connection_cache_service"
#define DEF_SCACHE_SERVICE "scache"
extern char *var_scache_service;
-#define VAR_SCACHE_TTL_LIM "session_cache_ttl_limit"
+#define VAR_SCACHE_TTL_LIM "connection_cache_ttl_limit"
#define DEF_SCACHE_TTL_LIM "2s"
extern int var_scache_ttl_lim;
-#define VAR_SCACHE_STAT_TIME "session_cache_status_update_time"
+#define VAR_SCACHE_STAT_TIME "connection_cache_status_update_time"
#define DEF_SCACHE_STAT_TIME "600s"
extern int var_scache_stat_time;
* Patches change the patchlevel and the release date. Snapshots change the
* release date only.
*/
-#define MAIL_RELEASE_DATE "20041023"
+#define MAIL_RELEASE_DATE "20041030"
#define MAIL_VERSION_NUMBER "2.2"
#define VAR_MAIL_VERSION "mail_version"
/* proxymap(8), Postfix lookup table proxy server
/* qmgr(8), Postfix queue manager
/* qmqpd(8), Postfix QMQP server
-/* scache(8), Postfix session cache manager
+/* scache(8), Postfix connection cache manager
/* showq(8), list Postfix mail queue
/* smtp(8), Postfix SMTP client
/* smtpd(8), Postfix SMTP server
/* NAME
/* scache 8
/* SUMMARY
-/* Postfix session cache server
+/* Postfix connection cache server
/* SYNOPSIS
/* \fBscache\fR [generic Postfix daemon options]
/* DESCRIPTION
-/* The \fBscache\fR server maintains a shared multi-session
+/* The \fBscache\fR server maintains a shared multi-connection
/* cache. This information can be used by, for example, Postfix
/* SMTP clients or other Postfix delivery agents.
/*
-/* The session cache is organized into logical destination
-/* names, physical endpoint names, and sessions.
+/* The connection cache is organized into logical destination
+/* names, physical endpoint names, and connections.
/*
/* As a specific example, logical SMTP destinations specify
/* (transport, domain, port), and physical SMTP endpoints
-/* specify (transport, IP address, port). An SMTP session
+/* specify (transport, IP address, port). An SMTP connection
/* may be saved after a successful mail transaction.
/*
/* In the general case, one logical destination may refer to
/* zero or more physical endpoints, one physical endpoint may
/* be referenced by zero or more logical destinations, and
-/* one endpoint may refer to zero or more sessions.
+/* one endpoint may refer to zero or more connections.
/*
/* The exact syntax of a logical destination or endpoint name
/* is application dependent; the \fBscache\fR service does
-/* not care. A session is stored as a file descriptor together
+/* not care. A connection is stored as a file descriptor together
/* with application-dependent information that is needed to
-/* re-activate a session object. Again, the \fBscache\fR
+/* re-activate a connection object. Again, the \fBscache\fR
/* service is completely unaware about the details of that
/* information.
/*
/* All information is stored with a finite time to live (ttl).
-/* The session cache daemon terminates when no client is
+/* The connection cache daemon terminates when no client is
/* connected for \fBmax_idle\fR time units.
/*
/* This server implements the following requests:
/* .IP "\fBsave_endp\fI ttl endpoint endpoint_properties file_descriptor\fR"
-/* Save the specified file descriptor and session property data
+/* Save the specified file descriptor and connection property data
/* under the specified endpoint name. The endpoint properties
-/* are used by the client to re-activate a passivated session
+/* are used by the client to re-activate a passivated connection
/* object.
/* .IP "\fBfind_endp\fI endpoint\fR"
/* Look up cached properties and a cached file descriptor for the
/* .IP "\fBsave_dest\fI ttl destination destination_properties endpoint\fR"
/* Save the binding between a logical destination and an
/* endpoint under the destination name, together with destination
-/* specific session properties. The destination properties
-/* are used by the client to re-activate a passivated session
+/* specific connection properties. The destination properties
+/* are used by the client to re-activate a passivated connection
/* object.
/* .IP "\fBfind_dest\fI destination\fR"
/* Look up cached destination properties, cached endpoint properties,
/* SECURITY
/* .ad
/* .fi
-/* The session cache server is not security-sensitive. It does not
+/* The connection cache server is not security-sensitive. It does not
/* talk to the network, and it does not talk to local users.
/* The scache server can run chrooted at fixed low privilege.
/*
-/* The session cache server is not a trusted process. It must
+/* The connection cache server is not a trusted process. It must
/* not be used to store information that is security sensitive.
/* DIAGNOSTICS
/* Problems and transactions are logged to \fBsyslogd\fR(8).
/* BUGS
/* Sessions cannot be cached across multiple machines.
/*
-/* When a session expires from the cache it is closed without
+/* When a connection expires from the cache it is closed without
/* protocol specific handshake.
/* CONFIGURATION PARAMETERS
/* .ad
/* RESOURCE CONTROLS
/* .ad
/* .fi
-/* .IP "\fBsession_cache_ttl_limit (2s)\fR"
-/* The maximal time-to-live value that the session cache server
+/* .IP "\fBconnection_cache_ttl_limit (2s)\fR"
+/* The maximal time-to-live value that the connection cache server
/* allows.
-/* .IP "\fBsession_cache_status_update_time (600s)\fR"
+/* .IP "\fBconnection_cache_status_update_time (600s)\fR"
/* How frequently the scache(8) server logs usage statistics with
-/* session cache hit and miss rates for logical destinations and for
+/* connection cache hit and miss rates for logical destinations and for
/* physical endpoints.
/* MISCELLANEOUS CONTROLS
/* .ad
}
}
-/* scache_find_endp_service - protocol to find session for endpoint */
+/* scache_find_endp_service - protocol to find connection for endpoint */
static void scache_find_endp_service(VSTREAM *client_stream)
{
}
}
-/* scache_find_dest_service - protocol to find session for destination */
+/* scache_find_dest_service - protocol to find connection for destination */
static void scache_find_dest_service(VSTREAM *client_stream)
{
scache_endp_hits = scache_endp_miss = 0;
}
if (scache_dest_count || scache_endp_count || scache_sess_count) {
- msg_info("statistics: max simultaneous domains=%d addresses=%d sessions=%d",
+ msg_info("statistics: max simultaneous domains=%d addresses=%d connection=%d",
scache_dest_count, scache_endp_count, scache_sess_count);
scache_dest_count = 0;
scache_endp_count = 0;
/* to a recoverable error condition, the SMTP client will try to
/* deliver the mail to an alternate host.
/*
-/* After a successful mail transaction, a session may be saved
-/* to the \fBscache(8)\fR session cache server, so that it
+/* After a successful mail transaction, a connection may be saved
+/* to the \fBscache(8)\fR connection cache server, so that it
/* may be used by any SMTP client for a subsequent transaction.
/*
-/* By default, session caching is enabled temporarily for
+/* By default, connection caching is enabled temporarily for
/* destinations that have a high volume of mail in the active
/* queue. Session caching can be enabled permanently for
/* specific destinations.
/* the postmaster is notified of bounces, protocol problems, and of
/* other trouble.
/* BUGS
-/* SMTP session caching does not work with TLS. The necessary
+/* SMTP connection caching does not work with TLS. The necessary
/* support for TLS object passivation and re-activation does not
/* exist without closing the session, which defeats the purpose.
/*
-/* SMTP session caching assumes that SASL credentials are valid for
+/* SMTP connection caching assumes that SASL credentials are valid for
/* all destinations that map onto the same IP address and TCP port.
/* CONFIGURATION PARAMETERS
/* .ad
/* Permanently enable SMTP connection caching for the specified
/* destinations.
/* .IP "\fBsmtp_connection_cache_on_demand (yes)\fR"
-/* Temporarily enable SMTP session caching while a destination
+/* Temporarily enable SMTP connection caching while a destination
/* has a high volume of mail in the active queue.
/* .IP "\fBsmtp_connection_cache_reuse_limit (10)\fR"
-/* When SMTP session caching is enabled, the number of times that
+/* When SMTP connection caching is enabled, the number of times that
/* an SMTP session is reused before it is closed.
/* .IP "\fBsmtp_connection_cache_time_limit (2s)\fR"
-/* When SMTP session caching is enabled, the amount of time that
+/* When SMTP connection caching is enabled, the amount of time that
/* an unused SMTP client socket is kept open before it is closed.
/* TROUBLE SHOOTING CONTROLS
/* .ad
/* SEE ALSO
/* qmgr(8), queue manager
/* bounce(8), delivery status reports
-/* scache(8), session cache server
+/* scache(8), connection cache server
/* postconf(5), configuration parameters
/* master(8), process manager
/* syslogd(8), system logging
projects / thirdparty / postfix.git / commitdiff
