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 - sqlite_table(5) </title>
</head> <body> <pre>
SQLITE_TABLE(5) SQLITE_TABLE(5)

NAME
 sqlite_table - Postfix SQLite configuration

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

postmap -q - <a href="sqlite_table.5.html">sqlite</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 SQLite databases. In
 order to use SQLite lookups, define an SQLite source as a lookup table
 in <a href="postconf.5.html">main.cf</a>, for example:
 <a href="postconf.5.html#alias_maps">alias_maps</a> = <a href="sqlite_table.5.html">sqlite</a>:/etc/sqlite-aliases.cf

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

BACKWARDS COMPATIBILITY
 For compatibility with other Postfix lookup tables, SQLite parameters
 can also be defined in <a href="postconf.5.html">main.cf</a>. In order to do that, specify as SQLite
 source a name that doesn't begin with a slash or a dot. The SQLite
 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 "<a href="sqlite_table.5.html">sqlite</a>:sqlitename", the parameter
 "query" below would be defined in <a href="postconf.5.html">main.cf</a> as "sqlitename_query".

Normally, the SQL query is specified via a single query parameter
 (described in more detail below). When this parameter is not specified
 in the map definition, Postfix reverts to an older interface, with the
 SQL query constructed from the select_field, table, where_field and
 additional_conditions parameters. The old interface will be gradually
 phased out. To migrate to the new interface set:

query = SELECT [select_field]
 FROM [table]
 WHERE [where_field] = '%s'
 [additional_conditions]

Insert the value, not the name, of each legacy parameter. Note that the
 additional_conditions parameter is optional and if not empty, will
 always start with AND.

LIST MEMBERSHIP
 When using SQL to store lists such as $<a href="postconf.5.html#mynetworks">mynetworks</a>, $<a href="postconf.5.html#mydestination">mydestination</a>,
 $<a href="postconf.5.html#relay_domains">relay_domains</a>, $<a href="postconf.5.html#local_recipient_maps">local_recipient_maps</a>, etc., it is important to under-
 stand 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 <a href="DATABASE_README.html">DATABASE_README</a> document for a discussion.

Do NOT create tables that return the full list of domains in $<a href="postconf.5.html#mydestination">mydesti</a>-
 <a href="postconf.5.html#mydestination">nation</a> or $<a href="postconf.5.html#relay_domains">relay_domains</a> etc., or IP addresses in $<a href="postconf.5.html#mynetworks">mynetworks</a>.

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.

SQLITE PARAMETERS
 dbpath The SQLite database file location. Example:
 dbpath = customer_database

query The SQL query template used to search the database, where %s is
 a substitute for the address Postfix is trying to resolve, e.g.
 query = SELECT replacement FROM aliases WHERE mailbox = '%s'

This parameter supports the following '%' expansions:

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

%s This is replaced by the input key. SQL quoting is used
 to make sure that the input key does not add unexpected
 metacharacters.

%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, the query is sup-
 pressed and returns no results.

%d When the input key is an address of the form user@domain,
 %d is replaced by the SQL quoted domain part of the
 address. Otherwise, the query is suppressed and returns
 no results.

%[SUD] The upper-case equivalents of the above expansions behave
 in the query parameter identically to their lower-case
 counter-parts. With the result_format parameter (see
 below), they expand the input key rather than the result
 value.

%[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, the query is sup-
 pressed and returns no results.

The domain parameter described below limits the input keys to
 addresses in matching domains. When the domain parameter is
 non-empty, SQL queries for unqualified addresses or addresses in
 non-matching domains are suppressed and return no results.

This parameter is available with Postfix 2.2. In prior releases
 the SQL query was built from the separate parameters:
 select_field, table, where_field and additional_conditions. The
 mapping from the old parameters to the equivalent query is:

SELECT [select_field]
 FROM [table]
 WHERE [where_field] = '%s'
 [additional_conditions]

The '%s' in the WHERE clause expands to the escaped search
 string. With Postfix 2.2 these legacy parameters are used if
 the query parameter is not specified.

NOTE: DO NOT put quotes around the query parameter.

result_format (default: %s)
 Format template applied to result attributes. Most commonly used
 to append (or prepend) text to the result. This parameter sup-
 ports the following '%' expansions:

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

%s This is replaced by the value of the result attribute.
 When result is empty it is skipped.

%u When the result attribute value is an address of the form
 user@domain, %u is replaced by the local part of the
 address. When the result has an empty localpart it is
 skipped.

%d When a result attribute value is an address of the form
 user@domain, %d is replaced by the domain part of the
 attribute value. When the result is unqualified it is
 skipped.

%[SUD1-9]
 The upper-case and decimal digit expansions interpolate
 the parts of the input key rather than the result. Their
 behavior is identical to that described with query, and
 in fact because the input key is known in advance,
 queries whose key does not contain all the information
 specified in the result template are suppressed and
 return no results.

For example, using "result_format = <a href="smtp.8.html">smtp</a>:[%s]" allows one to use
 a mailHost attribute as the basis of a <a href="transport.5.html">transport(5)</a> table. After
 applying the result format, multiple values are concatenated as
 comma separated strings. The expansion_limit and parameter
 explained below allows one to restrict the number of values in
 the result, which is especially useful for maps that must return
 at most one value.

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 (default: no domain list)
 This is a list of domain names, paths to files, or dictionaries.
 When specified, only fully qualified search keys with a
 *non-empty* localpart and a matching domain are eligible for
 lookup: 'user' lookups, bare domain lookups and "@domain"
 lookups are not performed. This can significantly reduce the
 query load on the SQLite server.
 domain = postfix.org, <a href="DATABASE_README.html#types">hash</a>:/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 <a href="local.8.html">local(8)</a> aliases, because
 the input keys are always unqualified.

expansion_limit (default: 0)
 A limit on the total number of result elements returned (as a
 comma separated list) by a lookup against the map. A setting of
 zero disables the limit. Lookups fail with a temporary error if
 the limit is exceeded. Setting the limit to 1 ensures that
 lookups do not return multiple values.

OBSOLETE QUERY INTERFACE
 This section describes an interface that is deprecated as of Postfix
 2.2. It is replaced by the more general query interface described
 above. If the query parameter is defined, the legacy parameters
 described here ignored. Please migrate to the new interface as the
 legacy interface may be removed in a future release.

The  following  parameters  can  be  used  to fill in a SELECT template
       statement of the form:

SELECT [select_field]
 FROM [table]
 WHERE [where_field] = '%s'
 [additional_conditions]

The specifier %s is replaced by the search string, 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.

select_field
 The SQL "select" parameter. Example:
 select_field = forw_addr

table The SQL "select .. from" table name. Example:
 table = mxaliases

where_field
 The SQL "select .. where" parameter. Example:
 where_field = alias

additional_conditions
 Additional conditions to the SQL query. Example:
 additional_conditions = AND status = 'paid'

SEE ALSO
 <a href="postmap.1.html">postmap(1)</a>, Postfix lookup table maintenance
 <a href="postconf.5.html">postconf(5)</a>, configuration parameters
 <a href="ldap_table.5.html">ldap_table(5)</a>, LDAP lookup tables
 <a href="mysql_table.5.html">mysql_table(5)</a>, MySQL lookup tables
 <a href="pgsql_table.5.html">pgsql_table(5)</a>, PostgreSQL lookup tables

README FILES
 <a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
 <a href="SQLITE_README.html">SQLITE_README</a>, Postfix SQLITE howto

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

HISTORY
 SQLite support was introduced with Postfix version 2.8.

AUTHOR(S)
 Original implementation by:
 Axel Steiner

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