1 1.1 tron <!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN" 2 1.1.1.4 christos "https://www.w3.org/TR/html4/loose.dtd"> 3 1.1 tron 4 1.1 tron <html> 5 1.1 tron 6 1.1 tron <head> 7 1.1 tron 8 1.1 tron <title>Postfix memcache client Howto</title> 9 1.1 tron 10 1.1.1.2 christos <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 11 1.1.1.3 christos <link rel='stylesheet' type='text/css' href='postfix-doc.css'> 12 1.1 tron 13 1.1 tron </head> 14 1.1 tron 15 1.1 tron <body> 16 1.1 tron 17 1.1 tron <h1><img src="postfix-logo.jpg" width="203" height="98" ALT="">Postfix memcache client Howto</h1> 18 1.1 tron 19 1.1 tron <hr> 20 1.1 tron 21 1.1 tron <h2>Introduction</h2> 22 1.1 tron 23 1.1 tron <p>The Postfix memcache client allows you to hook up Postfix to a 24 1.1 tron memcache server. The current implementation supports one memcache 25 1.1 tron server per Postfix table, with one optional Postfix database that 26 1.1 tron provides persistent backup. The Postfix memcache client supports 27 1.1 tron the lookup, update, delete and sequence operations. The sequence 28 1.1 tron (i.e. first/next) operation requires a backup database that supports 29 1.1 tron this operation. </p> 30 1.1 tron 31 1.1 tron <p> Typically, the Postfix memcache client is used to reduce query 32 1.1 tron load on a persistent database, but it may also be used to query a 33 1.1 tron memory-only database for low-value, easy-to-recreate, information 34 1.1 tron such as a reputation cache for postscreen(8), verify(8) or greylisting. 35 1.1 tron </p> 36 1.1 tron 37 1.1 tron <h2>Limitations</h2> 38 1.1 tron 39 1.1 tron <ul> 40 1.1 tron 41 1.1 tron <li> <p> The Postfix memcache client cannot be used for security-sensitive 42 1.1 tron tables such as <tt>alias_maps</tt> (these may contain "<tt>|command</tt>" 43 1.1 tron and "<tt>/file/name</tt>" destinations), or <tt>virtual_uid_maps</tt>, 44 1.1 tron <tt>virtual_gid_maps</tt> and <tt>virtual_mailbox_maps</tt> (these 45 1.1 tron specify UNIX process privileges or "<tt>/file/name</tt>" destinations). 46 1.1 tron Typically, a memcache database is writable by any process that can 47 1.1 tron talk to the memcache server; in contrast, security-sensitive tables 48 1.1 tron must never be writable by the unprivileged Postfix user. </p> 49 1.1 tron 50 1.1 tron <li> <p> The Postfix memcache client requires additional configuration 51 1.1 tron when used as postscreen(8) or verify(8) cache. For details see the 52 1.1 tron <tt>backup</tt> and <tt>ttl</tt> parameter discussions in the 53 1.1 tron memcache_table(5) manual page. </p> 54 1.1 tron 55 1.1 tron </ul> 56 1.1 tron 57 1.1 tron <h2>Building Postfix with memcache support</h2> 58 1.1 tron 59 1.1 tron <p>The Postfix memcache client has no external dependencies, 60 1.1 tron and is therefore built into Postfix by default. </p> 61 1.1 tron 62 1.1 tron <h2>Configuring memcache lookup tables</h2> 63 1.1 tron 64 1.1 tron <p> Configuration is described in the memcache_table(5) manpage. </p> 65 1.1 tron 66 1.1 tron <h2>Credits</h2> 67 1.1 tron 68 1.1 tron <p> The first memcache client for Postfix was written by Omar Kilani, 69 1.1 tron and was based on the libmemcache library. </p> 70 1.1 tron 71 1.1 tron <p> Wietse wrote the current memcache client from the ground up for 72 1.1 tron Postfix version 2.9. This implementation does not use libmemcache, 73 1.1 tron and bears no resemblance to earlier work. </p> 74 1.1 tron 75 1.1 tron </body> 76 1.1 tron 77 1.1 tron </html> 78
Indexes created Sat Jun 06 00:24:59 UTC 2026