Gecko [ www.ctm-euromeuble.fr ]

Name	Size	Permission	Date
ADDRESS_CLASS_README.html	13.12 KB	-rw-r--r--	2020-02-16 20:59
ADDRESS_REWRITING_README.html	51.57 KB	-rw-r--r--	2020-02-16 20:59
ADDRESS_VERIFICATION_README.html	29.08 KB	-rw-r--r--	2020-02-16 20:59
BACKSCATTER_README.html	14.58 KB	-rw-r--r--	2020-02-16 20:59
BASIC_CONFIGURATION_README.html	28.25 KB	-rw-r--r--	2020-02-16 20:59
BUILTIN_FILTER_README.html	19.44 KB	-rw-r--r--	2020-02-16 20:59
CDB_README.html	4.01 KB	-rw-r--r--	2020-02-16 20:59
COMPATIBILITY_README.html	12.47 KB	-rw-r--r--	2020-02-16 20:59
CONNECTION_CACHE_README.html	12.02 KB	-rw-r--r--	2020-02-16 20:59
CONTENT_INSPECTION_README.html	3.57 KB	-rw-r--r--	2020-02-16 20:59
DATABASE_README.html	20.07 KB	-rw-r--r--	2020-02-16 20:59
DB_README.html	8.32 KB	-rw-r--r--	2020-02-16 20:59
DEBUG_README.html	20.59 KB	-rw-r--r--	2020-02-16 20:59
DSN_README.html	5.14 KB	-rw-r--r--	2020-02-16 20:59
ETRN_README.html	13.83 KB	-rw-r--r--	2020-02-16 20:59
FILTER_README.html	38.25 KB	-rw-r--r--	2020-02-16 20:59
FORWARD_SECRECY_README.html	29.03 KB	-rw-r--r--	2020-02-16 20:59
INSTALL.html	58.1 KB	-rw-r--r--	2020-02-16 20:59
IPV6_README.html	14.29 KB	-rw-r--r--	2020-02-16 20:59
LDAP_README.html	23.62 KB	-rw-r--r--	2020-02-16 20:59
LINUX_README.html	2.71 KB	-rw-r--r--	2020-02-16 20:59
LMDB_README.html	14.61 KB	-rw-r--r--	2020-02-16 20:59
LOCAL_RECIPIENT_README.html	7.71 KB	-rw-r--r--	2020-02-16 20:59
MAILDROP_README.html	6.99 KB	-rw-r--r--	2020-02-16 20:59
MEMCACHE_README.html	2.85 KB	-rw-r--r--	2020-02-16 20:59
MILTER_README.html	33.84 KB	-rw-r--r--	2020-02-16 20:59
MULTI_INSTANCE_README.html	54.29 KB	-rw-r--r--	2020-02-16 20:59
MYSQL_README.html	6.54 KB	-rw-r--r--	2020-02-16 20:59
NFS_README.html	5.19 KB	-rw-r--r--	2020-02-16 20:59
OVERVIEW.html	33.49 KB	-rw-r--r--	2020-02-16 20:59
PACKAGE_README.html	5.49 KB	-rw-r--r--	2020-02-16 20:59
PCRE_README.html	3.97 KB	-rw-r--r--	2020-02-16 20:59
PGSQL_README.html	5.86 KB	-rw-r--r--	2020-02-16 20:59
POSTSCREEN_README.html	52.75 KB	-rw-r--r--	2020-02-16 20:59
QSHAPE_README.html	46.6 KB	-rw-r--r--	2020-02-16 20:59
RESTRICTION_CLASS_README.html	9.08 KB	-rw-r--r--	2020-02-16 20:59
SASL_README.html	69.85 KB	-rw-r--r--	2020-02-16 20:59
SCHEDULER_README.html	72.05 KB	-rw-r--r--	2020-02-16 20:59
SMTPD_ACCESS_README.html	21.38 KB	-rw-r--r--	2020-02-16 20:59
SMTPD_POLICY_README.html	32.2 KB	-rw-r--r--	2020-02-16 20:59
SMTPD_PROXY_README.html	16.09 KB	-rw-r--r--	2020-02-16 20:59
SMTPUTF8_README.html	13.81 KB	-rw-r--r--	2020-02-16 20:59
SOHO_README.html	16.35 KB	-rw-r--r--	2020-02-16 20:59
SQLITE_README.html	3.53 KB	-rw-r--r--	2020-02-16 20:59
STANDARD_CONFIGURATION_README.html	33.36 KB	-rw-r--r--	2020-02-16 20:59
STRESS_README.html	24.34 KB	-rw-r--r--	2020-02-16 20:59
TLS_LEGACY_README.html	64.9 KB	-rw-r--r--	2020-02-16 20:59
TLS_README.html	141.53 KB	-rw-r--r--	2020-02-16 20:59
TUNING_README.html	29.65 KB	-rw-r--r--	2020-02-16 20:59
UUCP_README.html	6.37 KB	-rw-r--r--	2020-02-16 20:59
VERP_README.html	9.36 KB	-rw-r--r--	2020-02-16 20:59
VIRTUAL_README.html	29.75 KB	-rw-r--r--	2020-02-16 20:59
XCLIENT_README.html	8.35 KB	-rw-r--r--	2020-02-16 20:59
XFORWARD_README.html	8.08 KB	-rw-r--r--	2020-02-16 20:59
access.5.html	23.14 KB	-rw-r--r--	2020-02-16 20:59
aliases.5.html	10.73 KB	-rw-r--r--	2020-02-16 20:59
anvil.8.html	10.36 KB	-rw-r--r--	2020-02-16 20:59
bounce.5.html	9.61 KB	-rw-r--r--	2020-02-16 20:59
bounce.8.html	9.51 KB	-rw-r--r--	2020-02-16 20:59
canonical.5.html	14.12 KB	-rw-r--r--	2020-02-16 20:59
cidr_table.5.html	4.65 KB	-rw-r--r--	2020-02-16 20:59
cleanup.8.html	27.79 KB	-rw-r--r--	2020-02-16 20:59
defer.8.html	9.51 KB	-rw-r--r--	2020-02-16 20:59
discard.8.html	5.99 KB	-rw-r--r--	2020-02-16 20:59
dnsblog.8.html	4.42 KB	-rw-r--r--	2020-02-16 20:59
error.8.html	6.65 KB	-rw-r--r--	2020-02-16 20:59
flush.8.html	8.43 KB	-rw-r--r--	2020-02-16 20:59
generic.5.html	11.6 KB	-rw-r--r--	2020-02-16 20:59
header_checks.5.html	25.89 KB	-rw-r--r--	2020-02-16 20:59
index.html	4.52 KB	-rw-r--r--	2020-02-16 20:59
ldap_table.5.html	36.07 KB	-rw-r--r--	2020-02-16 20:59
lmdb_table.5.html	5.41 KB	-rw-r--r--	2020-02-16 20:59
lmtp.8.html	50.41 KB	-rw-r--r--	2020-02-16 20:59
local.8.html	36.49 KB	-rw-r--r--	2020-02-16 20:59
mailq.1.html	23.52 KB	-rw-r--r--	2020-02-16 20:59
master.5.html	13.86 KB	-rw-r--r--	2020-02-16 20:59
master.8.html	10.41 KB	-rw-r--r--	2020-02-16 20:59
memcache_table.5.html	12.07 KB	-rw-r--r--	2020-02-16 20:59
mysql_table.5.html	16.72 KB	-rw-r--r--	2020-02-16 20:59
newaliases.1.html	23.52 KB	-rw-r--r--	2020-02-16 20:59
nisplus_table.5.html	3.51 KB	-rw-r--r--	2020-02-16 20:59
oqmgr.8.html	22.08 KB	-rw-r--r--	2020-02-16 20:59
pcre_table.5.html	9.94 KB	-rw-r--r--	2020-02-16 20:59
pgsql_table.5.html	16 KB	-rw-r--r--	2020-02-16 20:59
pickup.8.html	5.83 KB	-rw-r--r--	2020-02-16 20:59
pipe.8.html	24.79 KB	-rw-r--r--	2020-02-16 20:59
postalias.1.html	12.17 KB	-rw-r--r--	2020-02-16 20:59
postcat.1.html	3.91 KB	-rw-r--r--	2020-02-16 20:59
postconf.1.html	29.45 KB	-rw-r--r--	2020-02-16 20:59
postconf.5.html	715.88 KB	-rw-r--r--	2020-02-16 20:59
postdrop.1.html	5.83 KB	-rw-r--r--	2020-02-16 20:59
postfix-logo.jpg	3.58 KB	-rw-r--r--	2020-02-16 20:59
postfix-manuals.html	7.27 KB	-rw-r--r--	2020-02-16 20:59
postfix-power.png	5.26 KB	-rw-r--r--	2020-02-16 20:59
postfix-tls.1.html	14.53 KB	-rw-r--r--	2020-02-16 20:59
postfix-wrapper.5.html	15.48 KB	-rw-r--r--	2020-02-16 20:59
postfix.1.html	21.65 KB	-rw-r--r--	2020-02-16 20:59
postkick.1.html	3.7 KB	-rw-r--r--	2020-02-16 20:59
postlock.1.html	4.89 KB	-rw-r--r--	2020-02-16 20:59
postlog.1.html	3.9 KB	-rw-r--r--	2020-02-16 20:59
postmap.1.html	15.17 KB	-rw-r--r--	2020-02-16 20:59
postmulti.1.html	23.16 KB	-rw-r--r--	2020-02-16 20:59
postqueue.1.html	12.01 KB	-rw-r--r--	2020-02-16 20:59
postscreen.8.html	28.23 KB	-rw-r--r--	2020-02-16 20:59
postsuper.1.html	14.22 KB	-rw-r--r--	2020-02-16 20:59
posttls-finger.1.html	18.53 KB	-rw-r--r--	2020-02-16 20:59
proxymap.8.html	11.34 KB	-rw-r--r--	2020-02-16 20:59
qmgr.8.html	26.61 KB	-rw-r--r--	2020-02-16 20:59
qmqp-sink.1.html	2.36 KB	-rw-r--r--	2020-02-16 20:59
qmqp-source.1.html	3.88 KB	-rw-r--r--	2020-02-16 20:59
qmqpd.8.html	8.78 KB	-rw-r--r--	2020-02-16 20:59
qshape.1.html	7.33 KB	-rw-r--r--	2020-02-16 20:59
regexp_table.5.html	7.89 KB	-rw-r--r--	2020-02-16 20:59
relocated.5.html	7.96 KB	-rw-r--r--	2020-02-16 20:59
scache.8.html	7.5 KB	-rw-r--r--	2020-02-16 20:59
sendmail.1.html	23.52 KB	-rw-r--r--	2020-02-16 20:59
showq.8.html	5.55 KB	-rw-r--r--	2020-02-16 20:59
smtp-sink.1.html	13.2 KB	-rw-r--r--	2020-02-16 20:59
smtp-source.1.html	5.55 KB	-rw-r--r--	2020-02-16 20:59
smtp.8.html	50.41 KB	-rw-r--r--	2020-02-16 20:59
smtpd.8.html	79.32 KB	-rw-r--r--	2020-02-16 20:59
socketmap_table.5.html	4.36 KB	-rw-r--r--	2020-02-16 20:59
spawn.8.html	7.16 KB	-rw-r--r--	2020-02-16 20:59
sqlite_table.5.html	13.42 KB	-rw-r--r--	2020-02-16 20:59
tcp_table.5.html	4.31 KB	-rw-r--r--	2020-02-16 20:59
tlsmgr.8.html	9.85 KB	-rw-r--r--	2020-02-16 20:59
tlsproxy.8.html	14.63 KB	-rw-r--r--	2020-02-16 20:59
trace.8.html	9.51 KB	-rw-r--r--	2020-02-16 20:59
transport.5.html	14.87 KB	-rw-r--r--	2020-02-16 20:59
trivial-rewrite.8.html	19.13 KB	-rw-r--r--	2020-02-16 20:59
verify.8.html	12.06 KB	-rw-r--r--	2020-02-16 20:59
virtual.5.html	15.06 KB	-rw-r--r--	2020-02-16 20:59
virtual.8.html	16.9 KB	-rw-r--r--	2020-02-16 20:59

Rename

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"
 "http://www.w3.org/TR/html4/loose.dtd">
<html> <head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<title> Postfix manual - memcache_table(5) </title>
</head> <body> <pre>
MEMCACHE_TABLE(5) MEMCACHE_TABLE(5)

NAME
 memcache_table - Postfix memcache client configuration

SYNOPSIS
 postmap -q "string" <a href="memcache_table.5.html">memcache</a>:/etc/postfix/filename

postmap -q - <a href="memcache_table.5.html">memcache</a>:/etc/postfix/filename &lt;inputfile

DESCRIPTION
 The Postfix mail system uses optional tables for address rewriting or
 mail routing. These tables are usually in dbm or db format.

Alternatively, lookup tables can be specified as memcache instances.
 To use memcache lookups, define a memcache source as a lookup table in
 <a href="postconf.5.html">main.cf</a>, for example:

<a href="postconf.5.html#virtual_alias_maps">virtual_alias_maps</a> = <a href="memcache_table.5.html">memcache</a>:/etc/postfix/memcache-aliases.cf

The file /etc/postfix/memcache-aliases.cf has the same format as the
 Postfix <a href="postconf.5.html">main.cf</a> file, and specifies the parameters described below.

The  Postfix  memcache  client  supports the lookup, update, delete and
       sequence (first/next) operations. The  sequence  operation  requires  a
       backup database that supports the operation.

MEMCACHE MAIN PARAMETERS
 memcache (default: inet:localhost:11211)
 The memcache server (note: singular) that Postfix will try to
 connect to. For a TCP server specify "inet:" followed by a
 hostname or address, ":", and a port name or number. Specify an
 IPv6 address inside "[]". For a UNIX-domain server specify
 "unix:" followed by the socket pathname. Examples:

memcache = inet:memcache.example.com:11211
                  memcache = inet:127.0.0.1:11211
                  memcache = inet:[fc00:8d00:189::3]:11211
                  memcache = unix:/path/to/socket

NOTE: to access a UNIX-domain socket with the <a href="proxymap.8.html">proxymap(8)</a>
 server, the socket must be accessible by the unprivileged post-
 fix user.

backup (default: undefined)
 An optional Postfix database that provides persistent backup for
 the memcache database. The Postfix memcache client will update
 the memcache database whenever it looks up or changes informa-
 tion in the persistent database. Specify a Postfix "<a href="DATABASE_README.html">type:table</a>"
 database. Examples:

# Non-shared postscreen cache.
 backup = <a href="DATABASE_README.html#types">btree</a>:/var/lib/postfix/<a href="postconf.5.html#postscreen_cache_map">postscreen_cache_map</a>

# Shared postscreen cache for processes on the same host.
 backup = <a href="proxymap.8.html">proxy</a>:<a href="DATABASE_README.html#types">btree</a>:/var/lib/postfix/<a href="postconf.5.html#postscreen_cache_map">postscreen_cache_map</a>

Access to remote proxymap servers is under development.

NOTE 1: When sharing a persistent <a href="postscreen.8.html">postscreen(8)</a> or <a href="verify.8.html">verify(8)</a>
 cache, disable automatic cache cleanup (set
 *_cache_cleanup_interval = 0) except with one Postfix instance
 that will be responsible for cache cleanup.

NOTE 2: When multiple tables share the same memcache database,
 each table should use the key_format feature (see below) to
 prepend its own unique string to the lookup key. Otherwise,
 automatic <a href="postscreen.8.html">postscreen(8)</a> or <a href="verify.8.html">verify(8)</a> cache cleanup may not work.

NOTE 3: When the backup database is accessed with "<a href="proxymap.8.html">proxy</a>:"
 lookups, the full backup database name (including the "<a href="proxymap.8.html">proxy</a>:"
 prefix) must be specified in the proxymap server's
 <a href="postconf.5.html#proxy_read_maps">proxy_read_maps</a> or <a href="postconf.5.html#proxy_write_maps">proxy_write_maps</a> setting (depending on
 whether the access is read-only or read-write).

flags (default: 0)
 Optional flags that should be stored along with a memcache
 update. The flags are ignored when looking up information.

ttl (default: 3600)
 The expiration time in seconds of memcache updates.

NOTE 1: When using a memcache table as <a href="postscreen.8.html">postscreen(8)</a> or <a href="verify.8.html">ver-</a>
 <a href="verify.8.html">ify(8)</a> cache without persistent backup, specify a zero
 *_cache_cleanup_interval value with all Postfix instances that
 use the memcache, and specify the largest <a href="postscreen.8.html">postscreen(8)</a> *_ttl
 value or <a href="verify.8.html">verify(8)</a> *_expire_time value as the memcache table's
 ttl value.

NOTE 2: According to memcache protocol  documentation,  a  value
              greater  than  30 days (2592000 seconds) specifies absolute UNIX
              time. Smaller values are relative to the time of the update.

MEMCACHE KEY PARAMETERS
 key_format (default: %s)
 Format of the lookup and update keys that the Postfix memcache
 client sends to the memcache server. By default, these are the
 same as the lookup and update keys that the memcache client
 receives from Postfix applications.

NOTE 1: The key_format feature is not used for backup database
 requests.

NOTE 2: When multiple tables share the same memcache database,
 each table should prepend its own unique string to the lookup
 key. Otherwise, automatic <a href="postscreen.8.html">postscreen(8)</a> or <a href="verify.8.html">verify(8)</a> cache
 cleanup may not work.

Examples:

key_format = aliases:%s
                  key_format = verify:%s
                  key_format = postscreen:%s

The key_format parameter supports the following '%' expansions:

%% This is replaced by a literal '%' character.

%s This is replaced by the memcache client input key.

%u When the input key is an address of the form user@domain,
 %u is replaced by the SQL quoted local part of the
 address. Otherwise, %u is replaced by the entire search
 string. If the localpart is empty, a lookup is silently
 suppressed and returns no results (an update is skipped
 with a warning).

%d When the input key is an address of the form user@domain,
 %d is replaced by the domain part of the address. Other-
 wise, a lookup is silently suppressed and returns no
 results (an update is skipped with a warning).

%[SUD] The upper-case equivalents of the above expansions behave
 in the key_format parameter identically to their
 lower-case counter-parts.

%[1-9] The patterns %1, %2, ... %9 are replaced by the corre-
 sponding most significant component of the input key's
 domain. If the input key is user@mail.example.com, then
 %1 is com, %2 is example and %3 is mail. If the input key
 is unqualified or does not have enough domain components
 to satisfy all the specified patterns, a lookup is
 silently suppressed and returns no results (an update is
 skipped with a warning).

domain (default: no domain list)
 This feature can significantly reduce database server load.
 Specify a list of domain names, paths to files, or "<a href="DATABASE_README.html">type:table</a>"
 databases. When specified, only fully qualified search keys
 with a *non-empty* localpart and a matching domain are eligible
 for lookup or update: bare 'user' lookups, bare domain lookups
 and "@domain" lookups are silently skipped (updates are skipped
 with a warning). Example:

domain = example.com, <a href="DATABASE_README.html#types">hash</a>:/etc/postfix/searchdomains

MEMCACHE ERROR CONTROLS
 data_size_limit (default: 10240)
 The maximal memcache reply data length in bytes.

line_size_limit (default: 1024)
 The maximal memcache reply line length in bytes.

max_try (default: 2)
 The number of times to try a memcache command before giving up.
 The memcache client does not retry a command when the memcache
 server accepts no connection.

retry_pause (default: 1)
 The time in seconds before retrying a failed memcache command.

timeout (default: 2)
 The time limit for sending a memcache command and for receiving
 a memcache reply.

BUGS
 The Postfix memcache client cannot be used for security-sensitive
 tables such as <a href="postconf.5.html#alias_maps">alias_maps</a> (these may contain "|command and "/file/name"
 destinations), or <a href="postconf.5.html#virtual_uid_maps">virtual_uid_maps</a>, <a href="postconf.5.html#virtual_gid_maps">virtual_gid_maps</a> and <a href="postconf.5.html#virtual_mailbox_maps">virtual_mail</a>-
 <a href="postconf.5.html#virtual_mailbox_maps">box_maps</a> (these specify UNIX process privileges or "/file/name" desti-
 nations). In a typical deployment a memcache database is writable by
 any process that can talk to the memcache server; in contrast, secu-
 rity-sensitive tables must never be writable by the unprivileged Post-
 fix user.

The Postfix memcache client requires additional configuration when used
 as <a href="postscreen.8.html">postscreen(8)</a> or <a href="verify.8.html">verify(8)</a> cache. For details see the backup and
 ttl parameter discussions in the MEMCACHE MAIN PARAMETERS section
 above.

SEE ALSO
 <a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
 <a href="postconf.5.html">postconf(5)</a>, configuration parameters

README FILES
 <a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
 <a href="MEMCACHE_README.html">MEMCACHE_README</a>, Postfix memcache client guide

LICENSE
 The Secure Mailer license must be distributed with this software.

HISTORY
 Memcache support was introduced with Postfix version 2.9.

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

MEMCACHE_TABLE(5)
</pre> </body> </html>