Import postfix-2.10-20121019

Author: hyc

HISTORY

@@ -18012,3 +18012,49 @@ Apologies for any names omitted.
 	Bugfix: the postscreen_access_list feature was case-sensitive
 	in the first character of permit, reject, etc. Reported by
 	Francis Picabia. File: global/server_acl.c.
+
+20121009
+
+	Documentation: interaction between delay_warning_time,
+	notify_classes and delay_notice_recipient. File:
+	proto/postconf.proto.
+
+20101009
+
+	Human factors: log a warning that the postcat option -m
+	without -h or -b has no effect. File: postcat/postcat.c.
+
+20121010
+
+	Bugfix (introduced: Postfix 2.5): memory leak in program
+	initialization. Reported by Coverity. File: tls/tls_misc.c.
+
+	Bugfix (introduced: Postfix 2.3): memory leak in the unused
+	oqmgr program. Reported by Coverity. File: oqmgr/qmgr_message.c.
+
+20121011
+
+	Documentation: how to enable /etc/hosts multi-record lookups
+	with main.cf settings.  File: proto/LINUX_README.html.
+
+	Documentation: clarified the postscreen-tlsproxy interface.
+	File: tlsproxy/tlsproxy.c.
+
+20121012
+
+	Documentation: a simpler null-client example.  File:
+	proto/STANDARD_CONFIGURATION_README.html
+
+20120113
+
+	Cleanup: to compute the LDAP connection cache lookup key,
+	join the numeric fields with null, just like string fields.
+	Viktor Dukhovni. File: global/dict_ldap.c.
+
+20121015
+
+	Documentation: added section on regular-expression tables
+	to the aliases(5) manpage. File: proto/aliases.
+
+	Documentation: why "smtp_address_preference = any" is the
+	preferred setting. File: proto/postconf.proto.

README_FILES/LINUX_README

@@ -16,6 +16,12 @@ addresses:
         multi on
         ...
 
+Alternatively, specify the RESOLV_MULTI environment variable in main.cf:
+
+    /etc/postfix/main.cf:
+        import_environment = MAIL_CONFIG MAIL_DEBUG MAIL_LOGTAG TZ XAUTHORITY
+    DISPLAY LANG=C RESOLV_MULTI=on
+
 BBeerrkkeelleeyy DDBB iissssuueess
 
 If you can't compile Postfix because the file "db.h" isn't found, then you MUST

README_FILES/STANDARD_CONFIGURATION_README

@@ -63,32 +63,38 @@ the network, and it does not deliver any mail locally. A null client typically
 uses POP, IMAP or NFS for mailbox access.
 
 In this example we assume that the Internet domain name is "example.com" and
-that the machine is named "nullclient.example.com". As usual, the examples show
+that the machine is named "hostname.example.com". As usual, the examples show
 only parameters that are not left at their default settings.
 
     1 /etc/postfix/main.cf:
-    2     myorigin = $mydomain
-    3     relayhost = $mydomain
-    4     inet_interfaces = loopback-only
-    5     local_transport = error:local delivery is disabled
-    6
-    7 /etc/postfix/master.cf:
-    8     Comment out the local delivery agent entry
+    2     myhostname = hostname.example.com
+    3     myorigin = $mydomain
+    4     relayhost = $mydomain
+    5     inet_interfaces = loopback-only
+    6     mydestination =
 
 Translation:
 
-  * Line 2: Send mail as "[email protected]" (instead of
-    "[email protected]"), so that nothing ever has a reason to send
-    mail to "[email protected]".
+  * Line 2: Set myhostname to hostname.example.com, in case the machine name
+    isn't set to a fully-qualified domain name (use the command "postconf -
+    d myhostname" to find out what the machine name is).
+
+  * Line 2: The myhostname value also provides the default value for the
+    mydomain parameter (here, "mydomain = example.com").
+
+  * Line 3: Send mail as "[email protected]" (instead of
+    "[email protected]"), so that nothing ever has a reason to send
+    mail to "[email protected]".
 
-  * Line 3: Forward all mail to the mail server that is responsible for the
+  * Line 4: Forward all mail to the mail server that is responsible for the
     "example.com" domain. This prevents mail from getting stuck on the null
     client if it is turned off while some remote destination is unreachable.
+    Specify a real hostname here if your "example.com" domain has no MX record.
 
-  * Line 4: Do not accept mail from the network.
+  * Line 5: Do not accept mail from the network.
 
-  * Lines 5-8: Disable local mail delivery. All mail goes to the mail server as
-    specified in line 3.
+  * Line 6: Disable local mail delivery. All mail goes to the mail server as
+    specified in line 4.
 
 PPoossttffiixx oonn aa llooccaall nneettwwoorrkk
 

conf/aliases

@@ -56,9 +56,15 @@ decode:		root
 #        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
-#        suitable for the use as NIS maps.
+#        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 expres-
+#        sions. In this case, the lookups are done  in  a  slightly
+#        different way as described below under "REGULAR EXPRESSION
+#        TABLES".
 # 
 #        Users can control delivery of their own mail by setting up
 #        .forward files in their home directory.  Lines in per-user
@@ -143,6 +149,25 @@ decode:		root
 #        The local(8) delivery agent always folds the search string
 #        to lowercase before database lookup.
 # 
+# 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  regexp_table(5) or pcre_table(5). NOTE: these formats
+#        do not use ":" at the end of a pattern.
+# 
+#        Each regular expression is applied to  the  entire  search
+#        string.  Thus,  a  search string user+foo is not broken up
+#        into user and foo.
+# 
+#        Regular expressions are applied in the order as  specified
+#        in  the  table,  until  a regular expression is found that
+#        matches the search string.
+# 
+#        Lookup results are the same as with indexed file  lookups.
+#        For  security  reasons there is no support for $1, $2 etc.
+#        substring interpolation.
+# 
 # SECURITY
 #        The local(8) delivery agent disallows  regular  expression
 #        substitution  of $1 etc. in alias_maps, because that would

html/LINUX_README.html

@@ -35,6 +35,16 @@ <h2> Host lookup issues </h2>
 </pre>
 </blockquote>
 
+<p> Alternatively, specify the RESOLV_MULTI environment variable
+in <a href="postconf.5.html">main.cf</a>: </p>
+
+<blockquote>
+<pre>
+/etc/postfix/<a href="postconf.5.html">main.cf</a>:
+    <a href="postconf.5.html#import_environment">import_environment</a> = MAIL_CONFIG MAIL_DEBUG MAIL_LOGTAG TZ XAUTHORITY DISPLAY LANG=C RESOLV_MULTI=on
+</pre>
+</blockquote>
+
 <h2>Berkeley DB issues</h2>
 
 <p> If you can't compile Postfix because the file "db.h"

html/STANDARD_CONFIGURATION_README.html

@@ -102,40 +102,48 @@ <h2><a name="null_client">Postfix on a null client</a></h2>
 null client typically uses POP, IMAP or NFS for mailbox access. </p>
 
 <p> In this example we assume that the Internet domain name is
-"example.com" and that the machine is named "nullclient.example.com".
+"example.com" and that the machine is named "hostname.example.com".
 As usual, the examples show only parameters that are not left at
 their default settings. </p>
 
 <blockquote>
 <pre>
 1 /etc/postfix/<a href="postconf.5.html">main.cf</a>:
-2     <a href="postconf.5.html#myorigin">myorigin</a> = $<a href="postconf.5.html#mydomain">mydomain</a>
-3     <a href="postconf.5.html#relayhost">relayhost</a> = $<a href="postconf.5.html#mydomain">mydomain</a>
-4     <a href="postconf.5.html#inet_interfaces">inet_interfaces</a> = loopback-only
-5     <a href="postconf.5.html#local_transport">local_transport</a> = <a href="error.8.html">error</a>:local delivery is disabled
-6 
-7 /etc/postfix/<a href="master.5.html">master.cf</a>:
-8     Comment out the local delivery agent entry
+2     <a href="postconf.5.html#myhostname">myhostname</a> = hostname.example.com
+3     <a href="postconf.5.html#myorigin">myorigin</a> = $<a href="postconf.5.html#mydomain">mydomain</a>
+4     <a href="postconf.5.html#relayhost">relayhost</a> = $<a href="postconf.5.html#mydomain">mydomain</a>
+5     <a href="postconf.5.html#inet_interfaces">inet_interfaces</a> = loopback-only
+6     <a href="postconf.5.html#mydestination">mydestination</a> =
 </pre>
 </blockquote>
 
 <p> Translation: </p>
 
 <ul>
 
-<li> <p> Line 2: Send mail as "[email protected]" (instead of
-"[email protected]"), so that nothing ever has a reason
-to send mail to "[email protected]". </p>
+<li> <p> Line 2: Set <a href="postconf.5.html#myhostname">myhostname</a> to hostname.example.com, in case
+the machine name isn't set to a fully-qualified domain name (use
+the command "postconf -d <a href="postconf.5.html#myhostname">myhostname</a>" to find out what the machine
+name is).  </p>
+
+<li> <p> Line 2: The <a href="postconf.5.html#myhostname">myhostname</a> value also provides the default
+value for the <a href="postconf.5.html#mydomain">mydomain</a> parameter (here, "<a href="postconf.5.html#mydomain">mydomain</a> = example.com").
+</p>
+
+<li> <p> Line 3: Send mail as "[email protected]" (instead of
+"[email protected]"), so that nothing ever has a reason
+to send mail to "[email protected]". </p>
 
-<li> <p> Line 3: Forward all mail to the mail server that is
+<li> <p> Line 4: Forward all mail to the mail server that is
 responsible for the "example.com" domain. This prevents mail from
 getting stuck on the null client if it is turned off while some
-remote destination is unreachable. </p>
+remote destination is unreachable. Specify a real hostname
+here if your "example.com" domain has no MX record. </p>
 
-<li> <p> Line 4: Do not accept mail from the network. </p>
+<li> <p> Line 5: Do not accept mail from the network. </p>
 
-<li> <p> Lines 5-8: Disable local mail delivery. All mail goes to
-the mail server as specified in line 3.  </p>
+<li> <p> Line 6: Disable local mail delivery. All mail goes to
+the mail server as specified in line 4.  </p>
 
 </ul>
 

html/aliases.5.html

@@ -24,9 +24,15 @@
        <b>newaliases</b>  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
-       suitable for the use as NIS maps.
+       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 expres-
+       sions. In this case, the lookups are done  in  a  slightly
+       different way as described below under "REGULAR EXPRESSION
+       TABLES".
 
        Users can control delivery of their own mail by setting up
        <b>.forward</b> files in their home directory.  Lines in per-user
@@ -111,6 +117,25 @@
        The <a href="local.8.html">local(8)</a> delivery agent always folds the search string
        to lowercase before database lookup.
 
+<b>REGULAR EXPRESSION 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_table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre_table</b>(5)</a>. NOTE: these formats
+       do not use ":" at the end of a pattern.
+
+       Each regular expression is applied to  the  entire  search
+       string.  Thus,  a  search string <i>user+foo</i> is not broken up
+       into <i>user</i> and <i>foo</i>.
+
+       Regular expressions are applied in the order as  specified
+       in  the  table,  until  a regular expression is found that
+       matches the search string.
+
+       Lookup results are the same as with indexed file  lookups.
+       For  security  reasons there is no support for <b>$1</b>, <b>$2</b> etc.
+       substring interpolation.
+
 <b>SECURITY</b>
        The <a href="local.8.html"><b>local</b>(8)</a> delivery agent disallows  regular  expression
        substitution  of $1 etc. in <b><a href="postconf.5.html#alias_maps">alias_maps</a></b>, because that would

html/cleanup.8.html

@@ -438,8 +438,8 @@
               point when logging sub-second delay values.
 
        <b><a href="postconf.5.html#delay_warning_time">delay_warning_time</a> (0h)</b>
-              The time after which the sender receives  the  mes-
-              sage headers of mail that is still queued.
+              The time after which the sender receives a copy  of
+              the message headers of mail that is still queued.
 
        <b><a href="postconf.5.html#ipc_timeout">ipc_timeout</a> (3600s)</b>
               The time limit for sending or receiving information

html/mailq.1.html

@@ -443,8 +443,8 @@
               <a href="postalias.1.html"><b>postalias</b>(1)</a> and <a href="postmap.1.html"><b>postmap</b>(1)</a> commands.
 
        <b><a href="postconf.5.html#delay_warning_time">delay_warning_time</a> (0h)</b>
-              The  time  after which the sender receives the mes-
-              sage headers of mail that is still queued.
+              The  time after which the sender receives a copy of
+              the message headers of mail that is still queued.
 
        <b><a href="postconf.5.html#enable_errors_to">enable_errors_to</a> (no)</b>
               Report mail delivery errors to the  address  speci-

html/newaliases.1.html

@@ -443,8 +443,8 @@
               <a href="postalias.1.html"><b>postalias</b>(1)</a> and <a href="postmap.1.html"><b>postmap</b>(1)</a> commands.
 
        <b><a href="postconf.5.html#delay_warning_time">delay_warning_time</a> (0h)</b>
-              The  time  after which the sender receives the mes-
-              sage headers of mail that is still queued.
+              The  time after which the sender receives a copy of
+              the message headers of mail that is still queued.
 
        <b><a href="postconf.5.html#enable_errors_to">enable_errors_to</a> (no)</b>
               Report mail delivery errors to the  address  speci-

html/postconf.5.html

@@ -2516,7 +2516,7 @@ <h2> Postfix main.cf file format </h2>
 units.  </p>
 
 <p>
-This feature is enabled with the <a href="postconf.5.html#delay_warning_time">delay_warning_time</a> parameter.
+See also: <a href="postconf.5.html#delay_warning_time">delay_warning_time</a>, <a href="postconf.5.html#notify_classes">notify_classes</a>.
 </p>
 
 
@@ -2526,8 +2526,8 @@ <h2> Postfix main.cf file format </h2>
 (default: 0h)</b></DT><DD>
 
 <p>
-The time after which the sender receives the message headers of
-mail that is still queued.
+The time after which the sender receives a copy of the message
+headers of mail that is still queued.
 </p>
 
 <p>
@@ -2541,6 +2541,10 @@ <h2> Postfix main.cf file format </h2>
 The default time unit is h (hours).
 </p>
 
+<p>
+See also: <a href="postconf.5.html#delay_notice_recipient">delay_notice_recipient</a>, <a href="postconf.5.html#notify_classes">notify_classes</a>.
+</p>
+
 
 </DD>
 
@@ -6734,7 +6738,8 @@ <h2> Postfix main.cf file format </h2>
 
 <dt><b>delay</b></dt>
 
-<dd>Send the postmaster copies of the headers of delayed mail. The
+<dd>Send the postmaster copies of the headers of delayed mail (see
+<a href="postconf.5.html#delay_warning_time">delay_warning_time</a>). The
 notification is sent to the address specified with the
 <a href="postconf.5.html#delay_notice_recipient">delay_notice_recipient</a> configuration parameter (default: postmaster).
 </dd>
@@ -9209,6 +9214,21 @@ <h2> Postfix main.cf file format </h2>
 unless the <a href="postconf.5.html#inet_protocols">inet_protocols</a> setting enables both IPv4 and IPv6.
 With Postfix 2.8 the default is "ipv6".  </p>
 
+<p> Notes for mail delivery between sites that have both IPv4 and
+IPv6 connectivity: </p>
+
+<ul>
+
+<li> <p> The setting "<a href="postconf.5.html#smtp_address_preference">smtp_address_preference</a> = ipv6" is unsafe.
+It can fail to deliver mail when there is an outage that affects
+IPv6, while the destination is still reachable over IPv4. </p>
+
+<li> <p> The setting "<a href="postconf.5.html#smtp_address_preference">smtp_address_preference</a> = any" is safe. With
+this, mail will eventually be delivered even if there is an outage
+that affects IPv6 or IPv4, as long as it does not affect both. </p>
+
+</ul>
+
 <p> This feature is available in Postfix 2.8 and later.  </p>
 
 

html/sendmail.1.html

@@ -443,8 +443,8 @@
               <a href="postalias.1.html"><b>postalias</b>(1)</a> and <a href="postmap.1.html"><b>postmap</b>(1)</a> commands.
 
        <b><a href="postconf.5.html#delay_warning_time">delay_warning_time</a> (0h)</b>
-              The  time  after which the sender receives the mes-
-              sage headers of mail that is still queued.
+              The  time after which the sender receives a copy of
+              the message headers of mail that is still queued.
 
        <b><a href="postconf.5.html#enable_errors_to">enable_errors_to</a> (no)</b>
               Report mail delivery errors to the  address  speci-