diff --git a/postfix/HISTORY b/postfix/HISTORY index 67d718529..5bb2b8157 100644 --- a/postfix/HISTORY +++ b/postfix/HISTORY @@ -19209,3 +19209,10 @@ Apologies for any names omitted. Workaround: increased the 5s connection timeout to 30s. Viktor Dukhovni. File: posttls-finger/posttls-finger.c. + +20131121 + + Documentation: new socketmap_table(5) and lmdb_table(5) + manpages. Files: mantools/postlink, conf/postfix-files, + html/Makefile.in, man/Makefile.in, proto/DATABASE_README.html, + postconf/postconf.c, proto/socketmap_table, proto/lmdb_table. diff --git a/postfix/README_FILES/DATABASE_README b/postfix/README_FILES/DATABASE_README index 629135c63..d08559902 100644 --- a/postfix/README_FILES/DATABASE_README +++ b/postfix/README_FILES/DATABASE_README @@ -195,10 +195,11 @@ To find out what database types your Postfix system supports, use the "ppooss (CIDR) patterns. The table format is described in cidr_table(5). ddbbmm An indexed file type based on hashing. This is available only on - systems with support for DBM databases. Database files are created with - the postmap(1) or postalias(1) command. The lookup table name as used - in "dbm:table" is the database file name without the ".dir" or ".pag" - suffix. + systems with support for DBM databases. Public database files are + created with the postmap(1) or postalias(1) command, and private + databases are maintained by Postfix daemons. The lookup table name as + used in "dbm:table" is the database file name without the ".dir" or + ".pag" suffix. eennvviirroonn The UNIX process environment array. The lookup key is the variable name. The lookup table name in "environ:table" is ignored. @@ -207,79 +208,80 @@ To find out what database types your Postfix system supports, use the "ppooss for logging only. This table exists to simplify Postfix error tests. hhaasshh An indexed file type based on hashing. This is available only on - systems with support for Berkeley DB databases. Database files are - created with the postmap(1) or postalias(1) command. The database name - as used in "hash:table" is the database file name without the ".db" - suffix. + systems with support for Berkeley DB databases. Public database files + are created with the postmap(1) or postalias(1) command, and private + databases are maintained by Postfix daemons. The database name as used + in "hash:table" is the database file name without the ".db" suffix. iinntteerrnnaall A non-shared, in-memory hash table. Its content are lost when a process terminates. - llmmddbb (unsupported) - The OpenLDAP LMDB database (a memory-mapped, persistent file). Database - files are created with the postmap(1) or postalias(1) command. The - database name as used in "lmdb:table" is the database file name without - the ".lmdb" suffix. + llmmddbb + OpenLDAP LMDB database (a memory-mapped. This is available only on + systems with support for LMDB databases. Public database files are + created with the postmap(1) or postalias(1) command, and private + databases are maintained by Postfix daemons. The database name as used + in "lmdb:table" is the database file name without the ".lmdb" suffix. + See lmdb_table(5) for details. llddaapp (read-only) - Perform lookups using the LDAP protocol. Configuration details are - given in the ldap_table(5). + LDAP database client. Configuration details are given in the ldap_table + (5). mmeemmccaacchhee - Perform memcache database lookups or updates. Configuration details are - given in memcache_table(5). + Memcache database client. Configuration details are given in + memcache_table(5). mmyyssqqll (read-only) - Perform MySQL database lookups. Configuration details are given in - mysql_table(5). + MySQL database client. Configuration details are given in mysql_table + (5). nneettiinnffoo (read-only) - Perform Netinfo database lookups. + Netinfo database client. nniiss (read-only) - Perform NIS database lookups. + NIS database client. nniisspplluuss (read-only) - Perform NIS+ database lookups. Configuration details are given in - nisplus_table(5). + NIS+ database client. Configuration details are given in nisplus_table + (5). ppccrree (read-only) A lookup table based on Perl Compatible Regular Expressions. The file format is described in pcre_table(5). The lookup table name as used in "pcre:table" is the name of the regular expression file. ppggssqqll (read-only) - Perform PostgreSQL database lookups. Configuration details are given in + PostgreSQL database client. Configuration details are given in pgsql_table(5). pprrooxxyy - Access information via the Postfix proxymap(8) service. The lookup - table name syntax is "proxy:type:table". + Postfix proxymap(8) client for shared access to Postfix databases. The + lookup table name syntax is "proxy:type:table". rreeggeexxpp (read-only) A lookup table based on regular expressions. The file format is described in regexp_table(5). The lookup table name as used in "regexp: table" is the name of the regular expression file. ssddbbmm An indexed file type based on hashing. This is available only on - systems with support for SDBM databases. Database files are created - with the postmap(1) or postalias(1) command. The lookup table name as + systems with support for SDBM databases. Public database files are + created with the postmap(1) or postalias(1) command, and private + databases are maintained by Postfix daemons. The lookup table name as used in "sdbm:table" is the database file name without the ".dir" or ".pag" suffix. ssoocckkeettmmaapp (read-only) - Query a Sendmail-style socketmap server. The name of the table - specifies iinneett:host:port:socketmap-name for a TCP-based server, or - uunniixx:pathname:socketmap-name for a UNIX-domain server. In both cases - socketmap-name is the name of the socketmap. + Sendmail-style socketmap client. The name of the table is either iinneett: + host:port:name for a TCP/IP server, or uunniixx:pathname:name for a UNIX- + domain server. See socketmap_table(5) for details. ssqqlliittee (read-only) - Perform SQLite database lookups. Configuration details are given in - sqlite_table(5). + SQLite database. Configuration details are given in sqlite_table(5). ssttaattiicc (read-only) - Always returns its lookup table name as lookup result. For example, the - lookup table "static:foobar" always returns the string "foobar" as + A table that always returns its name as the lookup result. For example, + the lookup table "static:foobar" always returns the string "foobar" as lookup result. ttccpp - Access information through a TCP/IP server. The protocol is described - in tcp_table(5). The lookup table name is "tcp:host:port" where "host" - specifies a symbolic hostname or a numeric IP address, and "port" - specifies a symbolic service name or a numeric port number. + TCP/IP client. The protocol is described in tcp_table(5). The lookup + table name is "tcp:host:port" where "host" specifies a symbolic + hostname or a numeric IP address, and "port" specifies a symbolic + service name or a numeric port number. tteexxtthhaasshh (read-only) - This produces similar results as hash: files, except that you don't - have to run the postmap(1) command before you can use the file, and - that texthash: does not detect changes after the file is read. The + A table that produces similar results as hash: files, except that you + don't have to run the postmap(1) command before you can use the file, + and that texthash: does not detect changes after the file is read. The lookup table name is "texthash:filename", where the file name is taken literally; no suffix is appended. uunniixx (read-only) - A limited way to query the UNIX authentication database. The following + A limited view of the UNIX authentication database. The following tables are implemented: uunniixx::ppaasssswwdd..bbyynnaammee The table is the UNIX password database. The key is a login name. diff --git a/postfix/conf/postfix-files b/postfix/conf/postfix-files index 90ef9575a..2da438efc 100644 --- a/postfix/conf/postfix-files +++ b/postfix/conf/postfix-files @@ -165,9 +165,11 @@ $manpage_directory/man5/generics.5:f:root:-:644:o $manpage_directory/man5/generic.5:f:root:-:644 $manpage_directory/man5/header_checks.5:f:root:-:644 $manpage_directory/man5/ldap_table.5:f:root:-:644 +$manpage_directory/man5/lmdb_table.5:f:root:-:644 $manpage_directory/man5/master.5:f:root:-:644 $manpage_directory/man5/memcache_table.5:f:root:-:644 $manpage_directory/man5/mysql_table.5:f:root:-:644 +$manpage_directory/man5/socketmap_table.5:f:root:-:644 $manpage_directory/man5/sqlite_table.5:f:root:-:644 $manpage_directory/man5/nisplus_table.5:f:root:-:644 $manpage_directory/man5/pcre_table.5:f:root:-:644 diff --git a/postfix/html/DATABASE_README.html b/postfix/html/DATABASE_README.html index f7a6ef73a..eec6d13f5 100644 --- a/postfix/html/DATABASE_README.html +++ b/postfix/html/DATABASE_README.html @@ -286,10 +286,11 @@ Routing (CIDR) patterns. The table format is described in postmap(1) or postalias(1) command. The lookup -table name as used in "dbm:table" is the database file name without -the ".dir" or ".pag" suffix. +on systems with support for DBM databases. Public database files +are created with the postmap(1) or postalias(1) command, and private +databases are maintained by Postfix daemons. The lookup table name +as used in "dbm:table" is the database file name without the ".dir" +or ".pag" suffix.
environ
@@ -306,50 +307,53 @@ error tests.
hash
An indexed file type based on hashing. This is available only -on systems with support for Berkeley DB databases. Database files are -created with the postmap(1) or postalias(1) command. The database +on systems with support for Berkeley DB databases. Public database +files are created with the postmap(1) or postalias(1) command, and +private databases are maintained by Postfix daemons. The database name as used in "hash:table" is the database file name without the -".db" suffix.
+".db" suffix.
internal
A non-shared, in-memory hash table. Its content are lost when a process terminates.
-
lmdb (unsupported)
+
lmdb
-
The OpenLDAP LMDB database (a memory-mapped, persistent file). -Database files are created with the postmap(1) or postalias(1) -command. The database name as used in "lmdb:table" is the database -file name without the ".lmdb" suffix. +
OpenLDAP LMDB database (a memory-mapped. This is available +only on systems with support for LMDB databases. Public database +files are created with the postmap(1) or postalias(1) command, and +private databases are maintained by Postfix daemons. The database +name as used in "lmdb:table" is the database file name without the +".lmdb" suffix. See lmdb_table(5) for details.
ldap (read-only)
-
Perform lookups using the LDAP protocol. Configuration details -are given in the ldap_table(5).
+
LDAP database client. Configuration details are given in the +ldap_table(5).
memcache
-
Perform memcache database lookups or updates. Configuration -details are given in memcache_table(5).
+
Memcache database client. Configuration details are given in +memcache_table(5).
mysql (read-only)
-
Perform MySQL database lookups. Configuration details are given -in mysql_table(5).
+
MySQL database client. Configuration details are given in +mysql_table(5).
netinfo (read-only)
-
Perform Netinfo database lookups.
+
Netinfo database client.
nis (read-only)
-
Perform NIS database lookups.
+
NIS database client.
nisplus (read-only)
-
Perform NIS+ database lookups. Configuration details are given -in nisplus_table(5).
+
NIS+ database client. Configuration details are given in +nisplus_table(5).
pcre (read-only)
@@ -360,13 +364,14 @@ file.
pgsql (read-only)
-
Perform PostgreSQL database lookups. Configuration details -are given in pgsql_table(5).
+
PostgreSQL database client. Configuration details are given +in pgsql_table(5).
proxy
-
Access information via the Postfix proxymap(8) service. The -lookup table name syntax is "proxy:type:table".
+
Postfix proxymap(8) client for shared access to Postfix +databases. The lookup table name syntax is "proxy:type:table". +
regexp (read-only)
@@ -377,52 +382,49 @@ is described in regexp_table(5). The lookup ta
sdbm
An indexed file type based on hashing. This is available only -on systems with support for SDBM databases. Database files are -created with the postmap(1) or postalias(1) command. The lookup -table name as used in "sdbm:table" is the database file name without -the ".dir" or ".pag" suffix.
+on systems with support for SDBM databases. Public database files +are created with the postmap(1) or postalias(1) command, and private +databases are maintained by Postfix daemons. The lookup table name +as used in "sdbm:table" is the database file name without the ".dir" +or ".pag" suffix.
socketmap (read-only)
-
Query a Sendmail-style socketmap server. The name of the table -specifies inet:host:port:socketmap-name -for a TCP-based server, or -unix:pathname:socketmap-name for a UNIX-domain -server. In both cases socketmap-name is the name of the -socketmap.
+
Sendmail-style socketmap client. The name of the table is +either inet:host:port:name for a TCP/IP +server, or unix:pathname:name for a UNIX-domain +server. See socketmap_table(5) for details.
sqlite (read-only)
-
Perform SQLite database lookups. Configuration details are given -in sqlite_table(5).
+
SQLite database. Configuration details are given in sqlite_table(5). +
static (read-only)
-
Always returns its lookup table name as lookup result. For -example, the lookup table "static:foobar" always returns the string -"foobar" as lookup result.
+
A table that always returns its name as the lookup result. +For example, the lookup table "static:foobar" always returns the +string "foobar" as lookup result.
tcp
-
Access information through a TCP/IP server. The protocol is -described in tcp_table(5). The lookup table name is "tcp:host:port" -where "host" specifies a symbolic hostname or a numeric IP address, -and "port" specifies a symbolic service name or a numeric port -number. -
+
TCP/IP client. The protocol is described in tcp_table(5). The +lookup table name is "tcp:host:port" where "host" specifies a +symbolic hostname or a numeric IP address, and "port" specifies a +symbolic service name or a numeric port number.
texthash (read-only)
-
This produces similar results as hash: files, except that you -don't have to run the postmap(1) command before you can use the -file, and that texthash: does not detect changes after the file is -read. The lookup table name is "texthash:filename", where the file -name is taken literally; no suffix is appended.
+
A table that produces similar results as hash: files, except +that you don't have to run the postmap(1) command before you can +use the file, and that texthash: does not detect changes after the +file is read. The lookup table name is "texthash:filename", where +the file name is taken literally; no suffix is appended.
unix (read-only)
-
A limited way to query the UNIX authentication database. The -following tables are implemented: +
A limited view of the UNIX authentication database. The following +tables are implemented:
diff --git a/postfix/html/LMDB_README.html b/postfix/html/LMDB_README.html index a607b5235..9f7c64c2a 100644 --- a/postfix/html/LMDB_README.html +++ b/postfix/html/LMDB_README.html @@ -177,7 +177,7 @@ errors.

-
Problem:

The "postmap lmdb:filename" command +

Problem:

The "postmap lmdb:filename" command fails with an MDB_TXN_FULL error. This problem does not exist with other Postfix databases.

@@ -199,7 +199,7 @@ resolved by increasing the database size.