|
NAMEscache - Postfix shared connection cache serverSYNOPSISscache [generic Postfix daemon options] DESCRIPTIONThe scache(8) server maintains a shared multi-connection cache. This information can be used by, for example, Postfix SMTP clients or other Postfix delivery agents. 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 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 connections. The exact syntax of a logical destination or endpoint name is application dependent; the scache(8) server does not 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 scache(8) server is completely unaware of the details of that information. All information is stored with a finite time to live (ttl). The connection cache daemon terminates when no client is connected for max_idle time units. This server implements the following requests:
SECURITYThe scache(8) server is not security-sensitive. It does not talk to the network, and it does not talk to local users. The scache(8) server can run chrooted at fixed low privilege. The scache(8) server is not a trusted process. It must not be used to store information that is security sensitive. DIAGNOSTICSProblems and transactions are logged to syslogd(8) or postlogd(8). BUGSThe session cache cannot be shared among multiple machines. When a connection expires from the cache, it is closed without the appropriate protocol specific handshake. CONFIGURATION PARAMETERSChanges to main.cf are picked up automatically as scache(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. RESOURCE CONTROLS
MISCELLANEOUS CONTROLS
Available in Postfix 3.3 and later:
SEE ALSOsmtp(8), SMTP client postconf(5), configuration parameters master(8), process manager postlogd(8), Postfix logging syslogd(8), system logging README FILESUse "postconf readme_directory" or "postconf html_directory" to locate this information. CONNECTION_CACHE_README, Postfix connection cache LICENSEThe Secure Mailer license must be distributed with this software. HISTORYThis service was introduced with Postfix version 2.2. 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 Visit the GSP FreeBSD Man Page Interface. |