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

NAME
 virtual - Postfix virtual alias table format

SYNOPSIS
 postmap /etc/postfix/virtual

postmap -q "string" /etc/postfix/virtual

postmap -q - /etc/postfix/virtual &lt;inputfile

DESCRIPTION
 The optional <a href="virtual.5.html">virtual(5)</a> alias table rewrites recipient addresses for
 all local, all virtual, and all remote mail destinations. This is
 unlike the <a href="aliases.5.html">aliases(5)</a> table which is used only for <a href="local.8.html">local(8)</a> delivery.
 Virtual aliasing is recursive, and is implemented by the Postfix
 <a href="cleanup.8.html">cleanup(8)</a> daemon before mail is queued.

The main applications of virtual aliasing are:

o To redirect mail for one address to one or more addresses.

o To implement virtual alias domains where all addresses are
 aliased to addresses in other domains.

Virtual alias domains are not to be confused with the virtual
 mailbox domains that are implemented with the Postfix <a href="virtual.8.html">virtual(8)</a>
 mail delivery agent. With <a href="ADDRESS_CLASS_README.html#virtual_mailbox_class">virtual mailbox domains</a>, each recipi-
 ent address can have its own mailbox.

Virtual aliasing is applied only to recipient envelope addresses, and
 does not affect message headers. Use <a href="canonical.5.html">canonical(5)</a> mapping to rewrite
 header and envelope addresses in general.

Normally, the <a href="virtual.5.html">virtual(5)</a> alias table is specified as a text file that
 serves as input to the <a href="postmap.1.html">postmap(1)</a> command. The result, an indexed file
 in dbm or db format, is used for fast searching by the mail system.
 Execute the command "postmap /etc/postfix/virtual" to rebuild an
 indexed file after changing the corresponding text file.

When  the  table  is provided via other means such as NIS, LDAP or SQL,
       the same lookups are done as for ordinary indexed files.

Alternatively, the table can be provided as  a  regular-expression  map
       where  patterns  are  given  as  regular expressions, or lookups can be
       directed to TCP-based server. In those case, the lookups are done in  a
       slightly  different  way  as  described below under "REGULAR EXPRESSION
       TABLES" or "TCP-BASED TABLES".

CASE FOLDING
 The search string is folded to lowercase before database lookup. As of
 Postfix 2.3, the search string is not case folded with database types
 such as <a href="regexp_table.5.html">regexp</a>: or <a href="pcre_table.5.html">pcre</a>: whose lookup fields can match both upper and
 lower case.

TABLE FORMAT
 The input format for the <a href="postmap.1.html">postmap(1)</a> command is as follows:

pattern address, address, ...
 When pattern matches a mail address, replace it by the corre-
 sponding address.

blank lines and comments
              Empty lines and whitespace-only lines are ignored, as are  lines
              whose first non-whitespace character is a `#'.

multi-line text
              A  logical  line  starts  with  non-whitespace text. A line that
              starts with whitespace continues a logical line.

TABLE SEARCH ORDER
 With lookups from indexed files such as DB or DBM, or from networked
 tables such as NIS, LDAP or SQL, patterns are tried in the order as
 listed below:

user@domain address, address, ...
 Redirect mail for user@domain to address. This form has the
 highest precedence.

user address, address, ...
 Redirect mail for user@site to address when site is equal to
 $<a href="postconf.5.html#myorigin">myorigin</a>, when site is listed in $<a href="postconf.5.html#mydestination">mydestination</a>, or when it is
 listed in $<a href="postconf.5.html#inet_interfaces">inet_interfaces</a> or $<a href="postconf.5.html#proxy_interfaces">proxy_interfaces</a>.

This functionality overlaps with functionality of the local
 aliases(5) database. The difference is that <a href="virtual.5.html">virtual(5)</a> mapping
 can be applied to non-local addresses.

@domain address, address, ...
 Redirect mail for other users in domain to address. This form
 has the lowest precedence.

Note: @domain is a wild-card. With this form, the Postfix SMTP
 server accepts mail for any recipient in domain, regardless of
 whether that recipient exists. This may turn your mail system
 into a backscatter source: Postfix first accepts mail for
 non-existent recipients and then tries to return that mail as
 "undeliverable" to the often forged sender address.

RESULT ADDRESS REWRITING
 The lookup result is subject to address rewriting:

o When the result has the form @otherdomain, the result becomes
 the same user in otherdomain. This works only for the first
 address in a multi-address lookup result.

o When "<a href="postconf.5.html#append_at_myorigin">append_at_myorigin</a>=yes", append "@$<a href="postconf.5.html#myorigin">myorigin</a>" to addresses
 without "@domain".

o When "<a href="postconf.5.html#append_dot_mydomain">append_dot_mydomain</a>=yes", append ".$<a href="postconf.5.html#mydomain">mydomain</a>" to addresses
 without ".domain".

ADDRESS EXTENSION
 When a mail address localpart contains the optional recipient delimiter
 (e.g., user+foo@domain), the lookup order becomes: user+foo@domain,
 user@domain, user+foo, user, and @domain.

The <a href="postconf.5.html#propagate_unmatched_extensions">propagate_unmatched_extensions</a> parameter controls whether an
 unmatched address extension (+foo) is propagated to the result of table
 lookup.

VIRTUAL ALIAS DOMAINS
 Besides virtual aliases, the virtual alias table can also be used to
 implement <a href="ADDRESS_CLASS_README.html#virtual_alias_class">virtual alias domains</a>. With a virtual alias domain, all
 recipient addresses are aliased to addresses in other domains.

Virtual alias domains are not to be confused with the virtual mailbox
 domains that are implemented with the Postfix <a href="virtual.8.html">virtual(8)</a> mail delivery
 agent. With virtual mailbox domains, each recipient address can have
 its own mailbox.

With a <a href="ADDRESS_CLASS_README.html#virtual_alias_class">virtual alias domain</a>, the virtual domain has its own user name
 space. Local (i.e. non-virtual) usernames are not visible in a virtual
 alias domain. In particular, local <a href="aliases.5.html">aliases(5)</a> and local mailing lists
 are not visible as localname@virtual-alias.domain.

Support for a <a href="ADDRESS_CLASS_README.html#virtual_alias_class">virtual alias domain</a> looks like:

/etc/postfix/<a href="postconf.5.html">main.cf</a>:
 <a href="postconf.5.html#virtual_alias_maps">virtual_alias_maps</a> = <a href="DATABASE_README.html#types">hash</a>:/etc/postfix/virtual

Note: some systems use dbm databases instead of hash. See the output
 from "postconf -m" for available database types.

/etc/postfix/virtual:
 virtual-alias.domain anything (right-hand content does not matter)
 postmaster@virtual-alias.domain postmaster
 user1@virtual-alias.domain address1
 user2@virtual-alias.domain address2, address3

The virtual-alias.domain anything entry is required for a virtual alias
 domain. Without this entry, mail is rejected with "relay access
 denied", or bounces with "mail loops back to myself".

Do not specify <a href="ADDRESS_CLASS_README.html#virtual_alias_class">virtual alias domain</a> names in the <a href="postconf.5.html">main.cf</a> <a href="postconf.5.html#mydestination">mydestination</a>
 or <a href="postconf.5.html#relay_domains">relay_domains</a> configuration parameters.

With a <a href="ADDRESS_CLASS_README.html#virtual_alias_class">virtual alias domain</a>, the Postfix SMTP server accepts mail for
 known-user@virtual-alias.domain, and rejects mail for unknown-user@vir-
 tual-alias.domain as undeliverable.

Instead of specifying the virtual alias domain name via the <a href="postconf.5.html#virtual_alias_maps">vir</a>-
 <a href="postconf.5.html#virtual_alias_maps">tual_alias_maps</a> table, you may also specify it via the <a href="postconf.5.html">main.cf</a> <a href="postconf.5.html#virtual_alias_domains">vir-
 tual_alias_domains</a> configuration parameter. This latter parameter uses
 the same syntax as the <a href="postconf.5.html">main.cf</a> <a href="postconf.5.html#mydestination">mydestination</a> configuration parameter.

REGULAR EXPRESSION TABLES
 This section describes how the table lookups change when the table is
 given in the form of regular expressions. For a description of regular
 expression lookup table syntax, see <a href="regexp_table.5.html">regexp_table(5)</a> or <a href="pcre_table.5.html">pcre_table(5)</a>.

Each pattern is a regular expression that is applied to the entire
 address being looked up. Thus, user@domain mail addresses are not bro-
 ken up into their user and @domain constituent parts, nor is user+foo
 broken up into user and foo.

Patterns  are  applied  in the order as specified in the table, until a
       pattern is found that matches the search string.

Results are the same as with indexed file lookups, with the additional
 feature that parenthesized substrings from the pattern can be interpo-
 lated as $1, $2 and so on.

TCP-BASED TABLES
 This section describes how the table lookups change when lookups are
 directed to a TCP-based server. For a description of the TCP
 client/server lookup protocol, see <a href="tcp_table.5.html">tcp_table(5)</a>. This feature is not
 available up to and including Postfix version 2.4.

Each lookup operation uses the entire address once. Thus, user@domain
 mail addresses are not broken up into their user and @domain con-
 stituent parts, nor is user+foo broken up into user and foo.

Results are the same as with indexed file lookups.

BUGS
 The table format does not understand quoting conventions.

CONFIGURATION PARAMETERS
 The following <a href="postconf.5.html">main.cf</a> parameters are especially relevant to this topic.
 See the Postfix <a href="postconf.5.html">main.cf</a> file for syntax details and for default values.
 Use the "postfix reload" command after a configuration change.

<a href="postconf.5.html#virtual_alias_maps">virtual_alias_maps</a>
 List of virtual aliasing tables.

<a href="postconf.5.html#virtual_alias_domains">virtual_alias_domains</a>
 List of <a href="ADDRESS_CLASS_README.html#virtual_alias_class">virtual alias domains</a>. This uses the same syntax as the
 <a href="postconf.5.html#mydestination">mydestination</a> parameter.

<a href="postconf.5.html#propagate_unmatched_extensions">propagate_unmatched_extensions</a>
 A list of address rewriting or forwarding mechanisms that propa-
 gate an address extension from the original address to the
 result. Specify zero or more of canonical, virtual, alias, for-
 ward, include, or generic.

Other parameters of interest:

<a href="postconf.5.html#inet_interfaces">inet_interfaces</a>
 The network interface addresses that this system receives mail
 on. You need to stop and start Postfix when this parameter
 changes.

<a href="postconf.5.html#mydestination">mydestination</a>
 List of domains that this mail system considers local.

<a href="postconf.5.html#myorigin">myorigin</a>
 The domain that is appended to any address that does not have a
 domain.

<a href="postconf.5.html#owner_request_special">owner_request_special</a>
 Give special treatment to owner-xxx and xxx-request addresses.

<a href="postconf.5.html#proxy_interfaces">proxy_interfaces</a>
 Other interfaces that this machine receives mail on by way of a
 proxy agent or network address translator.

SEE ALSO
 <a href="cleanup.8.html">cleanup(8)</a>, canonicalize and enqueue mail
 <a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
 <a href="postconf.5.html">postconf(5)</a>, configuration parameters
 <a href="canonical.5.html">canonical(5)</a>, canonical address mapping

README FILES
 <a href="ADDRESS_REWRITING_README.html">ADDRESS_REWRITING_README</a>, address rewriting guide
 <a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
 <a href="VIRTUAL_README.html">VIRTUAL_README</a>, domain hosting guide

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

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

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