diff options
| author | itojun <itojun@NetBSD.org> | 2001-03-13 17:45:02 +0000 |
|---|---|---|
| committer | itojun <itojun@NetBSD.org> | 2001-03-13 17:45:02 +0000 |
| commit | 173b2f6655e38657f15bb57fe26dc23e8d054d4e (patch) | |
| tree | 04af30df8438e7c54ceb4e5f4bf0dff83788ce54 /gnu/dist/postfix/html/virtual.5.html | |
| parent | c7871f80bf97592f2ca4dd16d6d7708bec2c33a2 (diff) | |
postfix release-20010228
Diffstat (limited to 'gnu/dist/postfix/html/virtual.5.html')
| -rw-r--r-- | gnu/dist/postfix/html/virtual.5.html | 256 |
1 files changed, 161 insertions, 95 deletions
diff --git a/gnu/dist/postfix/html/virtual.5.html b/gnu/dist/postfix/html/virtual.5.html index 91f57e9b7bd..720d763b6ae 100644 --- a/gnu/dist/postfix/html/virtual.5.html +++ b/gnu/dist/postfix/html/virtual.5.html @@ -12,53 +12,53 @@ VIRTUAL(5) VIRTUAL(5) <b>postmap</b> <b>/etc/postfix/virtual</b> <b>DESCRIPTION</b> - The optional <b>virtual</b> table specifies redirections for - local and non-local recipients or domains. The redirec- - tions are used by the <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon. The redirections - are recursive. + The optional <b>virtual</b> table specifies address redirections + for local and non-local recipients or domains. The redi- + rections are used by the <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon. The redirec- + tions are recursive. - The <b>virtual</b> redirection is applied only to the recipient - envelope address, and does not affect message headers. + The <b>virtual</b> redirection is applied only to recipient enve- + lope addresses, and does not affect message headers. Think Sendmail rule set <b>S0</b>, if you like. Use <a href="canonical.5.html"><b>canonical</b>(5)</a> mapping to rewrite header and envelope addresses in gen- eral. - The file serves as input to the <a href="postmap.1.html"><b>postmap</b>(1)</a> command. The - result, an indexed file in <b>dbm</b> or <b>db</b> format, is used for - fast searching by the mail system. After an update it may - take a minute or so before the change becomes visible. - Issue a <b>postfix</b> <b>reload</b> command to eliminate the delay. + Normally, the <b>virtual</b> table is specified as a text file + that serves as input to the <a href="postmap.1.html"><b>postmap</b>(1)</a> command. The + result, an indexed file in <b>dbm</b> or <b>db</b> format, is used for + fast searching by the mail system. Execute the command + <b>postmap</b> <b>/etc/postfix/virtual</b> in order to rebuild the + indexed file after changing the text file. - Typical support for a virtual domain looks like the fol- - lowing: + When the table is provided via other means such as NIS, + LDAP or SQL, the same lookups are done as for ordinary + indexed files. - <i>virtual.domain</i> <i>anything</i> (right-hand content does not matter) - <i>user1@virtual.domain</i> <i>address1</i> - <i>user2@virtual.domain</i> <i>address2,</i> <i>address3</i> + Alternatively, the table can be provided as a regular- + expression map where patterns are given as regular expres- + sions. In that case, the lookups are done in a slightly + different way as described below. - With this, the SMTP server accepts mail for <i>virtual.domain</i> - and rejects mail for <i>unknown</i>@<i>virtual.domain</i> as undeliver- - able. +<b>POSTFIX-STYLE</b> <b>VIRTUAL</b> <b>DOMAINS</b> + With a Postfix-style virtual domain, the virtual domain + has its own user name space. Local (i.e. non-virtual) + usernames are not visible in a Postfix-style virtual + domain. In particular, local <a href="aliases.5.html"><b>aliases</b>(5)</a> and mailing lists + are not visible as <i>localname@virtual.domain</i>. - The format of the virtual table is as follows, mappings - being tried in the order as listed in this manual page: - - blanks and comments - Blank lines are ignored, as are lines beginning - with `#'. + Use a Sendmail-style virtual domain (see below) if local + usernames, <a href="aliases.5.html"><b>aliases</b>(5)</a> or mailing lists should be visible + as <i>localname@virtual.domain</i>. - <i>user</i>@<i>domain</i> <i>address,</i> <i>address,</i> <i>...</i> - Mail for <i>user</i>@<i>domain</i> is redirected to <i>address</i>. - This form has the highest precedence. + Support for a Postfix-style virtual domain looks like: - <i>user</i> <i>address,</i> <i>address,</i> <i>...</i> - Mail for <i>user</i>@<i>site</i> is redirected to <i>address</i> when - <i>site</i> is equal to $<b>myorigin</b>, when <i>site</i> is listed in - $mydestination, or when it is listed in - $<i>inet_interfaces</i>. + /etc/postfix/virtual: + <i>virtual.domain</i> <i>anything</i> (right-hand content does not matter) + <i>postmaster@virtual.domain</i> <i>postmaster</i> + <i>user1@virtual.domain</i> <i>address1</i> + <i>user2@virtual.domain</i> <i>address2,</i> <i>address3</i> - This functionality overlaps with functionality of - the local <i>alias</i>(5) database. The difference is that + The <i>virtual.domain</i> <i>anything</i> entry is required for a @@ -71,60 +71,60 @@ VIRTUAL(5) VIRTUAL(5) VIRTUAL(5) VIRTUAL(5) - <b>virtual</b> mapping can be applied to non-local - addresses. + Postfix-style virtual domain. - @<i>domain</i> <i>address,</i> <i>address,</i> <i>...</i> - Mail for any user in <i>domain</i> is redirected to - <i>address</i>. This form has the lowest precedence. + Do not list a Postfix-style virtual domain in the <b>main.cf</b> + <b>mydestination</b> configuration parameter. Such an entry is + required only for a Sendmail-style virtual domain. - In all the above forms, when <i>address</i> has the form @<i>other-</i> - <i>domain</i>, the result is the same user in <i>otherdomain</i>. This - works for the first address in the expansion only. + With a Postfix-style virtual domain, the Postfix SMTP + server accepts mail for <i>known-user@virtual.domain</i> and + rejects mail for <i>unknown-user</i>@<i>virtual.domain</i> as undeliver- + able. -<b>ADDRESS</b> <b>EXTENSION</b> - When the search fails, and the address localpart contains - the optional recipient delimiter (e.g., <i>user+foo</i>@<i>domain</i>), - the search is repeated for the unextended address (e.g. - <i>user</i>@<i>domain</i>), and the unmatched address extension is prop- - agated to the result of expansion. The matching order is: - <i>user+foo</i>@<i>domain</i>, <i>user</i>@<i>domain</i>, <i>user+foo</i>, <i>user</i>, and @<i>domain</i>. +<b>SENDMAIL-STYLE</b> <b>VIRTUAL</b> <b>DOMAINS</b> + With a Sendmail-style virtual domain, every local (i.e. + non-virtual) username is visible in the virtual domain. In + particular, every local alias and mailing list is visible + as <i>localname@virtual.domain</i>. -<b>BUGS</b> - The table format does not understand quoting conventions. + Use a Postfix-style virtual domain (see above) if local + usernames, <a href="aliases.5.html"><b>aliases</b>(5)</a> or mailing lists should not be visi- + ble as <i>localname@virtual.domain</i>. -<b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this topic. See the Postfix <b>main.cf</b> file for syntax - details and for default values. Use the <b>postfix</b> <b>reload</b> - command after a configuration change. + Support for a Sendmail-style virtual domain looks like: - <b>virtual</b><i>_</i><b>maps</b> - List of virtual mapping tables. + /etc/postfix/main.cf: + mydestination = $myhostname localhost.$mydomain $mydomain + <i>virtual.domain</i> - Other parameters of interest: + /etc/postfix/virtual: + <i>user1@virtual.domain</i> <i>address1</i> + <i>user2@virtual.domain</i> <i>address2,</i> <i>address3</i> - <b>inet</b><i>_</i><b>interfaces</b> - The network interface addresses that this system - receives mail on. + The <b>main.cf</b> <b>mydestination</b> entry is required for a Send- + mail-style virtual domain. - <b>mydestination</b> - List of domains that this mail system considers - local. + Do not specify a <i>virtual.domain</i> <i>whatever</i> virtual map entry + for a Sendmail-style virtual domain. Such an entry is + required only with a Postfix-style virtual domain. - <b>myorigin</b> - The domain that is appended to locally-posted mail. + With a Sendmail-style virtual domain, the Postfix local + delivery agent delivers mail for an unknown <i>user</i>@<i>vir-</i> + <i>tual.domain</i> to a local (i.e. non-virtual) user that has + the same name; if no such recipient exists, the Postfix + local delivery agent bounces the mail to the sender. - <b>owner</b><i>_</i><b>request</b><i>_</i><b>special</b> - Give special treatment to <b>owner-</b><i>xxx</i> and <i>xxx</i><b>-request</b> - addresses. +<b>TABLE</b> <b>FORMAT</b> + The format of the virtual table is as follows, mappings + being tried in the order as listed in this manual page: -<b>SEE</b> <b>ALSO</b> - <a href="cleanup.8.html">cleanup(8)</a> canonicalize and enqueue mail - <a href="postmap.1.html">postmap(1)</a> create mapping table + blanks and comments + Blank lines are ignored, as are lines beginning + with `#'. -<b>LICENSE</b> - The Secure Mailer license must be distributed with this + leading whitespace + Lines that begin with whitespace continue the @@ -137,64 +137,130 @@ VIRTUAL(5) VIRTUAL(5) VIRTUAL(5) VIRTUAL(5) - software. - -<b>AUTHOR(S)</b> - Wietse Venema - IBM T.J. Watson Research - P.O. Box 704 - Yorktown Heights, NY 10598, USA - - - - - - - - - - - + previous line. + <i>pattern</i> <i>result</i> + When <i>pattern</i> matches a mail address, replace it by + the corresponding <i>result</i>. + 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: + <i>user</i>@<i>domain</i> <i>address,</i> <i>address,</i> <i>...</i> + Mail for <i>user</i>@<i>domain</i> is redirected to <i>address</i>. + This form has the highest precedence. + <i>user</i> <i>address,</i> <i>address,</i> <i>...</i> + Mail for <i>user</i>@<i>site</i> is redirected to <i>address</i> when + <i>site</i> is equal to $<b>myorigin</b>, when <i>site</i> is listed in + $mydestination, or when it is listed in + $<i>inet_interfaces</i>. + This functionality overlaps with functionality of + the local <i>alias</i>(5) database. The difference is that + <b>virtual</b> mapping can be applied to non-local + addresses. + @<i>domain</i> <i>address,</i> <i>address,</i> <i>...</i> + Mail for any user in <i>domain</i> is redirected to + <i>address</i>. This form has the lowest precedence. + In all the above forms, when <i>address</i> has the form @<i>other-</i> + <i>domain</i>, the result is the same user in <i>otherdomain</i>. This + works for the first address in the expansion only. +<b>ADDRESS</b> <b>EXTENSION</b> + When the search fails, and the address localpart contains + the optional recipient delimiter (e.g., <i>user+foo</i>@<i>domain</i>), + the search is repeated for the unextended address (e.g. + <i>user</i>@<i>domain</i>), and the unmatched address extension is prop- + agated to the result of expansion. The matching order is: + <i>user+foo</i>@<i>domain</i>, <i>user</i>@<i>domain</i>, <i>user+foo</i>, <i>user</i>, and @<i>domain</i>. +<b>REGULAR</b> <b>EXPRESSION</b> <b>TABLES</b> + 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"><b>regexp</b><i>_</i><b>table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre</b><i>_</i><b>table</b>(5)</a>. + Each pattern is a regular expression that is applied to + the entire address being looked up. Thus, <i>user@domain</i> mail + addresses are not broken up into their <i>user</i> and <i>@domain</i> + constituent parts, nor is <i>user+foo</i> broken up into <i>user</i> and + <i>foo</i>. + Patterns are applied in the order as specified in the + 3 +VIRTUAL(5) VIRTUAL(5) + table, until a pattern is found that matches the search + string. + Results are the same as with normal indexed file lookups, + with the additional feature that parenthesized substrings + from the pattern can be interpolated as <b>$1</b>, <b>$2</b> and so on. +<b>BUGS</b> + The table format does not understand quoting conventions. +<b>CONFIGURATION</b> <b>PARAMETERS</b> + The following <b>main.cf</b> parameters are especially relevant + to this topic. See the Postfix <b>main.cf</b> file for syntax + details and for default values. Use the <b>postfix</b> <b>reload</b> + command after a configuration change. + <b>virtual</b><i>_</i><b>maps</b> + List of virtual mapping tables. + Other parameters of interest: + <b>inet</b><i>_</i><b>interfaces</b> + The network interface addresses that this system + receives mail on. + <b>mydestination</b> + List of domains that this mail system considers + local. + <b>myorigin</b> + The domain that is appended to locally-posted mail. + <b>owner</b><i>_</i><b>request</b><i>_</i><b>special</b> + Give special treatment to <b>owner-</b><i>xxx</i> and <i>xxx</i><b>-request</b> + addresses. +<b>SEE</b> <b>ALSO</b> + <a href="cleanup.8.html">cleanup(8)</a> canonicalize and enqueue mail + <a href="postmap.1.html">postmap(1)</a> create mapping table + <a href="pcre_table.5.html">pcre_table(5)</a> format of PCRE tables + <a href="regexp_table.5.html">regexp_table(5)</a> format of POSIX regular expression tables +<b>LICENSE</b> + The Secure Mailer license must be distributed with this + software. +<b>AUTHOR(S)</b> + Wietse Venema + IBM T.J. Watson Research + P.O. Box 704 + Yorktown Heights, NY 10598, USA - 3 + 4 </pre> </body> </html> |
