|PGSQL_TABLE(5)||File Formats Manual||PGSQL_TABLE(5)|
pgsql_table - Postfix PostgreSQL client configuration
postmap -q "string" pgsql:/etc/postfix/filename postmap -q - pgsql:/etc/postfix/filename <inputfile
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 PostgreSQL databases. In order to use PostgreSQL lookups, define a PostgreSQL source as a lookup table in main.cf, for example:
alias_maps = pgsql:/etc/pgsql-aliases.cf
The file /etc/postfix/pgsql-aliases.cf has the same format as the Postfix main.cf file, and can specify the parameters described below.
When using SQL to store lists such as $mynetworks, $mydestination, $relay_domains, $local_recipient_maps, etc., it is important to understand that the table must store each list member as a separate key. The table lookup verifies the *existence* of the key. See "Postfix lists versus tables" in the DATABASE_README document for a discussion.
Do NOT create tables that return the full list of domains in $mydestination or $relay_domains etc., or IP addresses in $mynetworks.
DO create tables with each matching item as a key and with an arbitrary value. With SQL databases it is not uncommon to return the key itself or a constant value.
hosts = host1.some.domain host2.some.domain:port hosts = unix:/file/name
The hosts are tried in random order, with all connections over UNIX domain sockets being tried before those over TCP. The connections are automatically closed after being idle for about 1 minute, and are re-opened as necessary.
NOTE: the unix: and inet: prefixes are accepted for backwards compatibility reasons, but are actually ignored. The PostgreSQL client library will always try to connect to an UNIX socket if the name starts with a slash, and will try a TCP connection otherwise.
user = someone password = some_password
dbname = customer_database
query = SELECT replacement FROM aliases WHERE mailbox = '%s'
This parameter supports the following '%' expansions:
The precedence of this parameter has changed with Postfix 2.2, in prior releases the precedence was, from highest to lowest, select_function, query, select_field, ...
With Postfix 2.2 the query parameter has highest precedence, see COMPATIBILITY above.
NOTE: DO NOT put quotes around the query parameter.
The default value %s specifies that each result value should be used as is.
This parameter is available with Postfix 2.2 and later.
NOTE: DO NOT put quotes around the result format!
domain = postfix.org, hash:/etc/postfix/searchdomains
It is best not to use SQL to store the domains eligible for SQL lookups.
This parameter is available with Postfix 2.2 and later.
NOTE: DO NOT define this parameter for local(8) aliases, because the input keys are always unqualified.
For compatibility with other Postfix lookup tables, PostgreSQL parameters can also be defined in main.cf. In order to do that, specify as PostgreSQL source a name that doesn't begin with a slash or a dot. The PostgreSQL parameters will then be accessible as the name you've given the source in its definition, an underscore, and the name of the parameter. For example, if the map is specified as "pgsql:pgsqlname", the parameter "hosts" would be defined in main.cf as "pgsqlname_hosts".
Note: with this form, the passwords for the PostgreSQL sources are written in main.cf, which is normally world-readable. Support for this form will be removed in a future Postfix version.
This section describes query interfaces that are deprecated as of Postfix 2.2. Please migrate to the new query interface as the old interfaces are slated to be phased out.
select_function = my_lookup_user_alias
This is equivalent to:
query = SELECT my_lookup_user_alias('%s')
This parameter overrides the legacy table-related fields (described below). With Postfix versions prior to 2.2, it also overrides the query parameter. Starting with Postfix 2.2, the query parameter has highest precedence, and the select_function parameter is deprecated.
The following parameters (with lower precedence than the select_function interface described above) can be used to build the SQL select statement as follows:
SELECT [select_field] FROM [table] WHERE [where_field] = '%s' [additional_conditions]
The specifier %s is replaced with each lookup by the lookup key and is escaped so if it contains single quotes or other odd characters, it will not cause a parse error, or worse, a security problem.
Starting with Postfix 2.2, this interface is obsoleted by the more general query interface described above. If higher precedence the query or select_function parameters described above are defined, the parameters described here are ignored.
select_field = forw_addr
table = mxaliases
where_field = alias
additional_conditions = AND status = 'paid'
postmap(1), Postfix lookup table manager postconf(5), configuration parameters ldap_table(5), LDAP lookup tables mysql_table(5), MySQL lookup tables sqlite_table(5), SQLite lookup tables
Use "postconf readme_directory" or "postconf html_directory" to locate this information.
DATABASE_README, Postfix lookup table overview PGSQL_README, Postfix PostgreSQL client guide
The Secure Mailer license must be distributed with this software.
PgSQL support was introduced with Postfix version 2.1.
Based on the MySQL client by: Scott Cotton, Joshua Marcus IC Group, Inc. Ported to PostgreSQL by: Aaron Sethman Further enhanced by: Liviu Daia Institute of Mathematics of the Romanian Academy P.O. BOX 1-764 RO-014700 Bucharest, ROMANIA