diff --git a/postfix/HISTORY b/postfix/HISTORY index 209aa5cb3..fb2f94b1e 100644 --- a/postfix/HISTORY +++ b/postfix/HISTORY @@ -4445,3 +4445,53 @@ Apologies for any names omitted. Cleanup: changed prototype of internal function that did not return a useful result. File: src/util/vstream_popen.c. + +20001110 + + Workaround: the Debian post install script passes an open + file descriptor into the master server and waits forever. + Reported by Lamont Jones. File: master/master.c. + +20001114 + + Compatibility: added sendmail -G (gateway submission) option + for compatibility with the sendmail rmail command. Requested + by David Gilbert, Velocet Communications. + +20001116 + + Documentation: added MAILER-DAEMON to the list of sample + masquerade_exceptions settings in conf/sample-rewrite.cf. + Suggested by Karl O. Pinc, pop.artic.edu. + + Performance: the slow start (gradually increase number of + parallel connections to the same site) was too gentle and + Postfix would back off too quickly. Files: qmgr/qmgr_queue.c + and nqmgr/qmgr_queue.c. Yup, changed the same code, again. + We now allow for a margin above the actual concurrency, + with the size of the initial destination concurrency. + + Bugfix: the recipient home directory test broke mailbox_transport + support for non-UNIX recipients. File: local/recipient.c. + +20001117 + + Robustness: additional integrity tests for the nqmgr by + Patrik Rak. File: nqmgr/qmgr_message.c. + +20001118 + + Bugfix: the new LDAP client code did not work properly if + the new ldap_domain parameter was not specified. LaMont + Jones, HP. File: util/dict_ldap.c. + + Feature: the soft_bounce safety net is extended to the SMTP + server. With "soft_bounce = yes", The SMTP server changes + all 5xx (reject) replies into 4xx (try again) replies. + + Documentation: the virtual(5) man page now documents both + Postfix-style virtual domains and Sendmail-style virtual + domains, including their interaction with local usernames, + aliases and mailing lists. Hopefully, this ends some of + the confusion surrounding virtual domain support. Updated + several FAQ entries concerning virtual domain support. diff --git a/postfix/SASL_README b/postfix/SASL_README index 271487961..537337715 100644 --- a/postfix/SASL_README +++ b/postfix/SASL_README @@ -45,6 +45,10 @@ from: IMPORTANT: if you install the Cyrus SASL libraries as per the default, you will have to symlink /usr/lib/sasl -> /usr/local/lib/sasl. +Reportedly, Microsoft Internet Explorer version 5 requires the +non-standard SASL LOGIN authentication method. To enable this +authentication method, specify ``./configure --enable-login''. + Building Postfix with SASL authentication support ================================================= diff --git a/postfix/conf/aliases b/postfix/conf/aliases index cdf06c1fb..6ef99b3ff 100644 --- a/postfix/conf/aliases +++ b/postfix/conf/aliases @@ -43,16 +43,17 @@ decode: root # # DESCRIPTION # The aliases file provides a system-wide mechanism to redi- -# rect mail for local recipients. +# rect mail for local recipients. The redirections are pro- +# cessed by the Postfix local(8) delivery agent. # -# The file serves as input to the postalias(1) command. The -# result, an indexed file in dbm or db format, is used for -# fast lookup by the mail system. Execute the command -# newaliases in order to rebuild the indexed file after +# The file serves as input to the postalias(1) command. The +# result, an indexed file in dbm or db format, is used for +# fast lookup by the mail system. Execute the command +# newaliases in order to rebuild the indexed file after # changing the Postfix alias database. # -# The input and output file formats are expected to be com- -# patible with Sendmail version 8, and are expected to be +# The input and output file formats are expected to be com- +# patible with Sendmail version 8, and are expected to be # suitable for the use as NIS maps. # # Users can control delivery of their own mail by setting up @@ -66,57 +67,56 @@ decode: root # # name: value1, value2, ... # -# o Lines that begin with whitespace continue the pre- +# o Lines that begin with whitespace continue the pre- # vious line. # -# o Blank lines are ignored, as are lines beginning +# o Blank lines are ignored, as are lines beginning # with `#'. # -# The name is a local address (no domain part). Use double -# quotes when the name contains any special characters such -# as whitespace, `#', `:', or `@'. The name is folded to +# The name is a local address (no domain part). Use double +# quotes when the name contains any special characters such +# as whitespace, `#', `:', or `@'. The name is folded to # lowercase, in order to make database lookups case insensi- # tive. # # In addition, when an alias exists for owner-name, delivery -# diagnostics are directed to that address, instead of to +# diagnostics are directed to that address, instead of to # the originator. This is typically used to direct delivery -# errors to the owner of a mailing list, who is in a better -# position to deal with mailing list delivery problems than +# errors to the owner of a mailing list, who is in a better +# position to deal with mailing list delivery problems than # the originator of the undelivered mail. # # The value contains one or more of the following: # -# address -# Mail is forwarded to address, which is compatible -# # 1 # # ALIASES(5) ALIASES(5) # +# address +# Mail is forwarded to address, which is compatible # with the RFC 822 standard. # # /file/name -# Mail is appended to /file/name. See local(8) for -# details of delivery to file. Delivery is not lim- -# ited to regular files. For example, to dispose of +# Mail is appended to /file/name. See local(8) for +# details of delivery to file. Delivery is not lim- +# ited to regular files. For example, to dispose of # unwanted mail, deflect it to /dev/null. # # |command -# Mail is piped into command. Commands that contain -# special characters, such as whitespace, should be -# enclosed between double quotes. See local(8) for +# Mail is piped into command. Commands that contain +# special characters, such as whitespace, should be +# enclosed between double quotes. See local(8) for # details of delivery to command. # # When the command fails, a limited amount of command -# output is mailed back to the sender. The file -# /usr/include/sysexits.h defines the expected exit -# status codes. For example, use |"exit 67" to simu- -# late a "user unknown" error, and |"exit 0" to +# output is mailed back to the sender. The file +# /usr/include/sysexits.h defines the expected exit +# status codes. For example, use |"exit 67" to simu- +# late a "user unknown" error, and |"exit 0" to # implement an expensive black hole. # # :include:/file/name -# Mail is sent to the destinations listed in the +# Mail is sent to the destinations listed in the # named file. Lines in :include: files have the same # syntax as the right-hand side of alias entries. # @@ -128,37 +128,37 @@ decode: root # # ADDRESS EXTENSION # When alias database search fails, and the recipient local- -# part contains the optional recipient delimiter (e.g., -# user+foo), the search is repeated for the unextended +# part contains the optional recipient delimiter (e.g., +# user+foo), the search is repeated for the unextended # address (e.g., user). # # CONFIGURATION PARAMETERS -# The following main.cf parameters are especially relevant -# to this topic. See the Postfix main.cf file for syntax -# details and for default values. Use the postfix reload +# The following main.cf parameters are especially relevant +# to this topic. See the Postfix main.cf file for syntax +# details and for default values. Use the postfix reload # command after a configuration change. # # alias_maps # List of alias databases. # # allow_mail_to_commands -# Restrict the usage of mail delivery to external -# command. -# -# allow_mail_to_files # Restrict the usage of mail delivery to external -# file. +# command. # # 2 # # ALIASES(5) ALIASES(5) # +# allow_mail_to_files +# Restrict the usage of mail delivery to external +# file. +# # owner_request_special # Give special treatment to owner-xxx and xxx-request # addresses. # # recipient_delimiter -# Delimiter that separates recipients from address +# Delimiter that separates recipients from address # extensions. # # STANDARDS @@ -169,7 +169,7 @@ decode: root # postalias(1) alias database management # # LICENSE -# The Secure Mailer license must be distributed with this +# The Secure Mailer license must be distributed with this # software. # # AUTHOR(S) diff --git a/postfix/conf/canonical b/postfix/conf/canonical index c00227c29..6be24c040 100644 --- a/postfix/conf/canonical +++ b/postfix/conf/canonical @@ -8,50 +8,51 @@ # postmap /etc/postfix/canonical # # DESCRIPTION -# The optional canonical file specifies an address mapping +# The optional canonical table specifies an address mapping # for local and non-local addresses. The mapping is used by # the cleanup(8) daemon. The address mapping is recursive. # -# Normally, the file serves as input to the postmap(1) com- -# mand. 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/canonical in order to rebuild -# the indexed file after changing the canonical table. +# Normally, the canonical table is specified as a text file +# that serves as input to the postmap(1) 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/canonical in order to rebuild the +# indexed file after changing the text file. # -# When the table is provided via other means such as NIS, -# LDAP or SQL, the same lookups are done as for ordinary +# 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- +# 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 +# sions. In that case, the lookups are done in a slightly # different way as described below. # -# The canonical mapping affects both message header +# The canonical mapping affects both message header # addresses (i.e. addresses that appear inside messages) and -# message envelope addresses (for example, the addresses -# that are used in SMTP protocol commands). Think Sendmail +# message envelope addresses (for example, the addresses +# that are used in SMTP protocol commands). Think Sendmail # rule set S3, if you like. # -# Typically, one would use the canonical table to replace -# login names by Firstname.Lastname, or to clean up +# Typically, one would use the canonical table to replace +# login names by Firstname.Lastname, or to clean up # addresses produced by legacy mail systems. # -# The canonical mapping is not to be confused with virtual +# The canonical mapping is not to be confused with virtual # domain support. Use the virtual(5) map for that purpose. # -# The canonical mapping is not to be confused with local +# The canonical mapping is not to be confused with local # aliasing. Use the aliases(5) map for that purpose. # # TABLE FORMAT # The format of the canonical table is as follows: # # blanks and comments -# Blank lines are ignored, as are lines beginning +# Blank lines are ignored, as are lines beginning # with `#'. # # leading whitespace -# Lines that begin with whitespace continue the pre- +# Lines that begin with whitespace continue the pre- # vious line. # # 1 @@ -59,78 +60,78 @@ # CANONICAL(5) CANONICAL(5) # # pattern result -# When pattern matches a mail address, replace it by +# When pattern matches a mail address, replace it by # the corresponding result. # # With lookups from indexed files such as DB or DBM, or from -# networked tables such as NIS, LDAP or SQL, patterns are +# networked tables such as NIS, LDAP or SQL, patterns are # tried in the order as listed below: # # user@domain address -# user@domain is replaced by address. This form has +# user@domain is replaced by address. This form has # the highest precedence. # -# This form useful to clean up addresses produced by -# legacy mail systems. It can also be used to pro- -# duce Firstname.Lastname style addresses, but see +# This form useful to clean up addresses produced by +# legacy mail systems. It can also be used to pro- +# duce Firstname.Lastname style addresses, but see # below for a simpler solution. # # user address # user@site is replaced by address when site is equal -# to $myorigin, when site is listed in $mydestina- +# to $myorigin, when site is listed in $mydestina- # tion, or when it is listed in $inet_interfaces. # -# This form is useful for replacing login names by +# This form is useful for replacing login names by # Firstname.Lastname. # # @domain address -# Every address in domain is replaced by address. +# Every address in domain is replaced by address. # This form has the lowest precedence. # -# In all the above forms, when address has the form @other- +# In all the above forms, when address has the form @other- # domain, the result is the same user in otherdomain. # # ADDRESS EXTENSION -# When table lookup fails, and the address localpart con- -# tains the optional recipient delimiter (e.g., -# user+foo@domain), the search is repeated for the unex- -# tended address (e.g. user@domain), and the unmatched +# When table lookup fails, and the address localpart con- +# tains the optional recipient delimiter (e.g., +# user+foo@domain), the search is repeated for the unex- +# tended address (e.g. user@domain), and the unmatched # extension is propagated to the result of table lookup. The # matching order is: user+foo@domain, user@domain, user+foo, # user, and @domain. # # REGULAR EXPRESSION TABLES -# This section describes how the table lookups change when +# 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, +# a description of regular expression lookup table syntax, # see regexp_table(5) or pcre_table(5). # -# Each pattern is a regular expression that is applied to +# Each pattern is a regular expression that is applied to # the entire address being looked up. Thus, user@domain mail -# addresses are not broken up into their user and @domain +# addresses are not broken 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 +# Patterns are applied in the order as specified in the # # 2 # # CANONICAL(5) CANONICAL(5) # -# table, until a pattern is found that matches the search +# 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 $1, $2 and so on. +# Results are the same as with normal indexed file lookups, +# with the additional feature that parenthesized substrings +# from the pattern can be interpolated as $1, $2 and so on. # # BUGS -# The table format does not understand quoting conventions. +# The table format does not understand quoting conventions. # # CONFIGURATION PARAMETERS -# The following main.cf parameters are especially relevant -# to this topic. See the Postfix main.cf file for syntax -# details and for default values. Use the postfix reload +# The following main.cf parameters are especially relevant +# to this topic. See the Postfix main.cf file for syntax +# details and for default values. Use the postfix reload # command after a configuration change. # # canonical_maps @@ -147,19 +148,19 @@ # Other parameters of interest: # # inet_interfaces -# The network interface addresses that this system +# The network interface addresses that this system # receives mail on. # # masquerade_domains -# List of domains that hide their subdomain struc- +# List of domains that hide their subdomain struc- # ture. # # masquerade_exceptions -# List of user names that are not subject to address +# List of user names that are not subject to address # masquerading. # # mydestination -# List of domains that this mail system considers +# List of domains that this mail system considers # local. # # myorigin @@ -182,7 +183,7 @@ # regexp_table(5) format of POSIX regular expression tables # # LICENSE -# The Secure Mailer license must be distributed with this +# The Secure Mailer license must be distributed with this # software. # # AUTHOR(S) diff --git a/postfix/conf/sample-rewrite.cf b/postfix/conf/sample-rewrite.cf index 5b5f3a584..b4073fb4b 100644 --- a/postfix/conf/sample-rewrite.cf +++ b/postfix/conf/sample-rewrite.cf @@ -40,6 +40,7 @@ masquerade_domains = # # By default, address masquerading makes no exceptions. # +#masquerade_exceptions = root,mailer-daemon #masquerade_exceptions = root masquerade_exceptions = diff --git a/postfix/conf/virtual b/postfix/conf/virtual index 591f146ac..28066d981 100644 --- a/postfix/conf/virtual +++ b/postfix/conf/virtual @@ -8,45 +8,103 @@ # postmap /etc/postfix/virtual # # DESCRIPTION -# The optional virtual table specifies redirections for -# local and non-local recipients or domains. The redirec- -# tions are used by the cleanup(8) daemon. The redirections -# are recursive. +# The optional virtual table specifies address redirections +# for local and non-local recipients or domains. The redi- +# rections are used by the cleanup(8) daemon. The redirec- +# tions are recursive. # -# The virtual redirection is applied only to the recipient -# envelope address, and does not affect message headers. +# The virtual redirection is applied only to recipient enve- +# lope addresses, and does not affect message headers. # Think Sendmail rule set S0, if you like. Use canonical(5) # mapping to rewrite header and envelope addresses in gen- # eral. # -# Normally, the file serves as input to the postmap(1) com- -# mand. 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 in order to rebuild -# the indexed file after changing the virtual table. +# Normally, the virtual table is specified as a text file +# that serves as input to the postmap(1) 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 in order to rebuild the +# indexed file after changing the text file. # -# When the table is provided via other means such as NIS, -# LDAP or SQL, the same lookups are done as for ordinary +# 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- +# 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 +# sions. In that case, the lookups are done in a slightly # different way as described below. # -# TABLE FORMAT -# Typical support for a virtual domain looks like the fol- -# lowing: +# POSTFIX-STYLE VIRTUAL DOMAINS +# 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 aliases(5) and mailing lists +# are not visible in a Postfix-style virtual domain. # +# Use a Sendmail-style virtual domain (see below) if local +# usernames, aliases(5) or mailing lists should be visible +# in that virtual domain. +# +# Support for a Postfix-style virtual domain looks like: +# +# /etc/postfix/virtual: # virtual.domain anything (right-hand content does not matter) # postmaster@virtual.domain postmaster # user1@virtual.domain address1 # user2@virtual.domain address2, address3 # -# With this, the SMTP server accepts mail for virtual.domain -# and rejects mail for unknown@virtual.domain as undeliver- +# The virtual.domain anything entry is required for a +# +# 1 +# +# VIRTUAL(5) VIRTUAL(5) +# +# Postfix-style virtual domain. +# +# Do not list the virtual domain in the main.cf mydestina- +# tion configuration parameter. Such an entry is required +# only for a Sendmail-style virtual domain. +# +# With a Postfix-style virtual domain, the Postfix SMTP +# server accepts mail for known-user@virtual.domain and +# rejects mail for unknown-user@virtual.domain as undeliver- # able. # +# SENDMAIL-STYLE VIRTUAL DOMAINS +# 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 +# in a Sendmail-style virtual domain. +# +# Use a Postfix-style virtual domain (see above) if local +# usernames, aliases(5) or mailing lists should not be visi- +# ble in that virtual domain. +# +# Support for a Sendmail-style virtual domain looks like: +# +# /etc/postfix/main.cf: +# mydestination = $myhostname localhost.$mydomain $mydomain +# virtual.domain +# +# /etc/postfix/virtual: +# user1@virtual.domain address1 +# user2@virtual.domain address2, address3 +# +# The main.cf mydestination entry is required for a Send- +# mail-style virtual domain. +# +# Do not specify a virtual.domain whatever entry in the vir- +# tual table. Such an entry is required only with a Postfix- +# style virtual domain. +# +# With a Sendmail-style virtual domain, the Postfix local +# delivery agent delivers mail for an unknown user@vir- +# tual.domain 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. +# +# TABLE FORMAT # The format of the virtual table is as follows, mappings # being tried in the order as listed in this manual page: # @@ -54,13 +112,14 @@ # Blank lines are ignored, as are lines beginning # with `#'. # -# 1 +# leading whitespace +# Lines that begin with whitespace continue the +# +# 2 # # VIRTUAL(5) VIRTUAL(5) # -# leading whitespace -# Lines that begin with whitespace continue the pre- -# vious line. +# previous line. # # pattern result # When pattern matches a mail address, replace it by @@ -113,11 +172,12 @@ # constituent parts, nor is user+foo broken up into user and # foo. # -# 2 +# Patterns are applied in the order as specified in the +# +# 3 # # VIRTUAL(5) VIRTUAL(5) # -# Patterns are applied in the order as specified in the # table, until a pattern is found that matches the search # string. # @@ -170,5 +230,5 @@ # P.O. Box 704 # Yorktown Heights, NY 10598, USA # -# 3 +# 4 # diff --git a/postfix/html/aliases.5.html b/postfix/html/aliases.5.html index 146d267f1..a5ddb2163 100644 --- a/postfix/html/aliases.5.html +++ b/postfix/html/aliases.5.html @@ -13,16 +13,17 @@ ALIASES(5) ALIASES(5) DESCRIPTION The aliases file provides a system-wide mechanism to redi- - rect mail for local recipients. + rect mail for local recipients. The redirections are pro- + cessed by the Postfix local(8) delivery agent. - The file serves as input to the postalias(1) command. The - result, an indexed file in dbm or db format, is used for - fast lookup by the mail system. Execute the command - newaliases in order to rebuild the indexed file after + The file serves as input to the postalias(1) command. The + result, an indexed file in dbm or db format, is used for + fast lookup by the mail system. Execute the command + newaliases in order to rebuild the indexed file after changing the Postfix alias database. - The input and output file formats are expected to be com- - patible with Sendmail version 8, and are expected to be + The input and output file formats are expected to be com- + patible with Sendmail version 8, and are expected to be suitable for the use as NIS maps. Users can control delivery of their own mail by setting up @@ -36,29 +37,28 @@ ALIASES(5) ALIASES(5) name: value1, value2, ... - o Lines that begin with whitespace continue the pre- + o Lines that begin with whitespace continue the pre- vious line. - o Blank lines are ignored, as are lines beginning + o Blank lines are ignored, as are lines beginning with `#'. - The name is a local address (no domain part). Use double - quotes when the name contains any special characters such - as whitespace, `#', `:', or `@'. The name is folded to + The name is a local address (no domain part). Use double + quotes when the name contains any special characters such + as whitespace, `#', `:', or `@'. The name is folded to lowercase, in order to make database lookups case insensi- tive. In addition, when an alias exists for owner-name, delivery - diagnostics are directed to that address, instead of to + diagnostics are directed to that address, instead of to the originator. This is typically used to direct delivery - errors to the owner of a mailing list, who is in a better - position to deal with mailing list delivery problems than + errors to the owner of a mailing list, who is in a better + position to deal with mailing list delivery problems than the originator of the undelivered mail. The value contains one or more of the following: - address - Mail is forwarded to address, which is compatible + @@ -71,29 +71,31 @@ ALIASES(5) ALIASES(5) ALIASES(5) ALIASES(5) + address + Mail is forwarded to address, which is compatible with the RFC 822 standard. /file/name - Mail is appended to /file/name. See local(8) for - details of delivery to file. Delivery is not lim- - ited to regular files. For example, to dispose of + Mail is appended to /file/name. See local(8) for + details of delivery to file. Delivery is not lim- + ited to regular files. For example, to dispose of unwanted mail, deflect it to /dev/null. |command - Mail is piped into command. Commands that contain - special characters, such as whitespace, should be - enclosed between double quotes. See local(8) for + Mail is piped into command. Commands that contain + special characters, such as whitespace, should be + enclosed between double quotes. See local(8) for details of delivery to command. When the command fails, a limited amount of command - output is mailed back to the sender. The file - /usr/include/sysexits.h defines the expected exit - status codes. For example, use |"exit 67" to simu- - late a "user unknown" error, and |"exit 0" to + output is mailed back to the sender. The file + /usr/include/sysexits.h defines the expected exit + status codes. For example, use |"exit 67" to simu- + late a "user unknown" error, and |"exit 0" to implement an expensive black hole. :include:/file/name - Mail is sent to the destinations listed in the + Mail is sent to the destinations listed in the named file. Lines in :include: files have the same syntax as the right-hand side of alias entries. @@ -105,26 +107,24 @@ ALIASES(5) ALIASES(5) ADDRESS EXTENSION When alias database search fails, and the recipient local- - part contains the optional recipient delimiter (e.g., - user+foo), the search is repeated for the unextended + part contains the optional recipient delimiter (e.g., + user+foo), the search is repeated for the unextended address (e.g., user). CONFIGURATION PARAMETERS - The following main.cf parameters are especially relevant - to this topic. See the Postfix main.cf file for syntax - details and for default values. Use the postfix reload + The following main.cf parameters are especially relevant + to this topic. See the Postfix main.cf file for syntax + details and for default values. Use the postfix reload command after a configuration change. alias_maps List of alias databases. allow_mail_to_commands - Restrict the usage of mail delivery to external + Restrict the usage of mail delivery to external command. - allow_mail_to_files - Restrict the usage of mail delivery to external - file. + @@ -137,12 +137,16 @@ ALIASES(5) ALIASES(5) ALIASES(5) ALIASES(5) + allow_mail_to_files + Restrict the usage of mail delivery to external + file. + owner_request_special Give special treatment to owner-xxx and xxx-request addresses. recipient_delimiter - Delimiter that separates recipients from address + Delimiter that separates recipients from address extensions. STANDARDS @@ -153,7 +157,7 @@ ALIASES(5) ALIASES(5) postalias(1) alias database management LICENSE - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. AUTHOR(S) @@ -185,10 +189,6 @@ ALIASES(5) ALIASES(5) - - - - diff --git a/postfix/html/canonical.5.html b/postfix/html/canonical.5.html index 664326072..aedf50526 100644 --- a/postfix/html/canonical.5.html +++ b/postfix/html/canonical.5.html @@ -12,56 +12,56 @@ CANONICAL(5) CANONICAL(5) postmap /etc/postfix/canonical DESCRIPTION - The optional canonical file specifies an address mapping + The optional canonical table specifies an address mapping for local and non-local addresses. The mapping is used by the cleanup(8) daemon. The address mapping is recursive. - Normally, the file serves as input to the postmap(1) com- - mand. 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/canonical in order to rebuild - the indexed file after changing the canonical table. + Normally, the canonical table is specified as a text file + that serves as input to the postmap(1) 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/canonical in order to rebuild the + indexed file after changing the text file. - When the table is provided via other means such as NIS, - LDAP or SQL, the same lookups are done as for ordinary + 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- + 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 + sions. In that case, the lookups are done in a slightly different way as described below. - The canonical mapping affects both message header + The canonical mapping affects both message header addresses (i.e. addresses that appear inside messages) and - message envelope addresses (for example, the addresses - that are used in SMTP protocol commands). Think Sendmail + message envelope addresses (for example, the addresses + that are used in SMTP protocol commands). Think Sendmail rule set S3, if you like. - Typically, one would use the canonical table to replace - login names by Firstname.Lastname, or to clean up + Typically, one would use the canonical table to replace + login names by Firstname.Lastname, or to clean up addresses produced by legacy mail systems. - The canonical mapping is not to be confused with virtual + The canonical mapping is not to be confused with virtual domain support. Use the virtual(5) map for that purpose. - The canonical mapping is not to be confused with local + The canonical mapping is not to be confused with local aliasing. Use the aliases(5) map for that purpose. TABLE FORMAT The format of the canonical table is as follows: blanks and comments - Blank lines are ignored, as are lines beginning + Blank lines are ignored, as are lines beginning with `#'. leading whitespace - Lines that begin with whitespace continue the pre- + Lines that begin with whitespace continue the pre- vious line. - 1 @@ -72,59 +72,59 @@ CANONICAL(5) CANONICAL(5) pattern result - When pattern matches a mail address, replace it by + When pattern matches a mail address, replace it by the corresponding result. With lookups from indexed files such as DB or DBM, or from - networked tables such as NIS, LDAP or SQL, patterns are + networked tables such as NIS, LDAP or SQL, patterns are tried in the order as listed below: user@domain address - user@domain is replaced by address. This form has + user@domain is replaced by address. This form has the highest precedence. - This form useful to clean up addresses produced by - legacy mail systems. It can also be used to pro- - duce Firstname.Lastname style addresses, but see + This form useful to clean up addresses produced by + legacy mail systems. It can also be used to pro- + duce Firstname.Lastname style addresses, but see below for a simpler solution. user address user@site is replaced by address when site is equal - to $myorigin, when site is listed in $mydestina- + to $myorigin, when site is listed in $mydestina- tion, or when it is listed in $inet_interfaces. - This form is useful for replacing login names by + This form is useful for replacing login names by Firstname.Lastname. @domain address - Every address in domain is replaced by address. + Every address in domain is replaced by address. This form has the lowest precedence. - In all the above forms, when address has the form @other- + In all the above forms, when address has the form @other- domain, the result is the same user in otherdomain. ADDRESS EXTENSION - When table lookup fails, and the address localpart con- - tains the optional recipient delimiter (e.g., - user+foo@domain), the search is repeated for the unex- - tended address (e.g. user@domain), and the unmatched + When table lookup fails, and the address localpart con- + tains the optional recipient delimiter (e.g., + user+foo@domain), the search is repeated for the unex- + tended address (e.g. user@domain), and the unmatched extension is propagated to the result of table lookup. The matching order is: user+foo@domain, user@domain, user+foo, user, and @domain. REGULAR EXPRESSION TABLES - This section describes how the table lookups change when + 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, + a description of regular expression lookup table syntax, see regexp_table(5) or pcre_table(5). - Each pattern is a regular expression that is applied to + Each pattern is a regular expression that is applied to the entire address being looked up. Thus, user@domain mail - addresses are not broken up into their user and @domain + addresses are not broken 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 + Patterns are applied in the order as specified in the @@ -137,20 +137,20 @@ CANONICAL(5) CANONICAL(5) CANONICAL(5) CANONICAL(5) - table, until a pattern is found that matches the search + 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 $1, $2 and so on. + Results are the same as with normal indexed file lookups, + with the additional feature that parenthesized substrings + from the pattern can be interpolated as $1, $2 and so on. BUGS - The table format does not understand quoting conventions. + The table format does not understand quoting conventions. CONFIGURATION PARAMETERS - The following main.cf parameters are especially relevant - to this topic. See the Postfix main.cf file for syntax - details and for default values. Use the postfix reload + The following main.cf parameters are especially relevant + to this topic. See the Postfix main.cf file for syntax + details and for default values. Use the postfix reload command after a configuration change. canonical_maps @@ -167,19 +167,19 @@ CANONICAL(5) CANONICAL(5) Other parameters of interest: inet_interfaces - The network interface addresses that this system + The network interface addresses that this system receives mail on. masquerade_domains - List of domains that hide their subdomain struc- + List of domains that hide their subdomain struc- ture. masquerade_exceptions - List of user names that are not subject to address + List of user names that are not subject to address masquerading. mydestination - List of domains that this mail system considers + List of domains that this mail system considers local. myorigin @@ -209,7 +209,7 @@ CANONICAL(5) CANONICAL(5) regexp_table(5) format of POSIX regular expression tables LICENSE - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. AUTHOR(S) diff --git a/postfix/html/faq.html b/postfix/html/faq.html index 2433606ad..db0cfd95b 100644 --- a/postfix/html/faq.html +++ b/postfix/html/faq.html @@ -128,7 +128,7 @@ addresses
  • Relaying mail for mobile users -
  • Postfix refuses mail for virtual +
  • Postfix refuses mail for virtual domains with "relay access denied"
  • Restricting what users can send mail to off-site destinations @@ -155,6 +155,8 @@ domains with "relay access denied"
  • Root's mail is delivered to nobody +
  • What does "biff_notify: Connection refused" mean? +
  • Postfix accepts mail for non-existing local users
  • Delivering some users locally while @@ -190,27 +192,24 @@ distribution list
  • Postfix ignores the owner-list alias +
  • Commands and mailing lists don't work in Postfix virtual maps +

    Virtual domains