postfix-3.4-20180203

postfix/HISTORY

@@ -23310,3 +23310,17 @@ Apologies for any names omitted.
 
 	Bugfix (introduced: 20180106): too many arguments for format
 	string. File: local/mailbox.c.
+
+20180128
+
+	Documentation: the tcp_table(5) manpage now documents the
+	absence of substring lookups. File: proto/tcp_table.
+
+20180203
+
+	Licence: in addition to the historical IBM Public License
+	1.0, this software is now also distributed with the more
+	recent Eclipse Public License 2.0. Recipients can choose
+	to take the software under the license of their choice.
+	Those who are more comfortable with the IPL can continue
+	with that license. File: LICENSE.

postfix/LICENSE

@@ -1,3 +1,290 @@
+LICENSE - SECURE MAILER
+
+This software is dual-licensed under both the Eclipse Public License
+version 2.0 and the IBM Public License version 1.0, for those who
+are more comfortable continuing with that license. Recipients can
+choose to take the software under the license of their choice.
+
+The remainder of this text contains a copy of each license.
+
+Eclipse Public License - v 2.0
+
+    THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE
+    PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION
+    OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+
+"Contribution" means:
+
+  a) in the case of the initial Contributor, the initial content
+     Distributed under this Agreement, and
+
+  b) in the case of each subsequent Contributor:
+     i) changes to the Program, and
+     ii) additions to the Program;
+  where such changes and/or additions to the Program originate from
+  and are Distributed by that particular Contributor. A Contribution
+  "originates" from a Contributor if it was added to the Program by
+  such Contributor itself or anyone acting on such Contributor's behalf.
+  Contributions do not include changes or additions to the Program that
+  are not Modified Works.
+
+"Contributor" means any person or entity that Distributes the Program.
+
+"Licensed Patents" mean patent claims licensable by a Contributor which
+are necessarily infringed by the use or sale of its Contribution alone
+or when combined with the Program.
+
+"Program" means the Contributions Distributed in accordance with this
+Agreement.
+
+"Recipient" means anyone who receives the Program under this Agreement
+or any Secondary License (as applicable), including Contributors.
+
+"Derivative Works" shall mean any work, whether in Source Code or other
+form, that is based on (or derived from) the Program and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship.
+
+"Modified Works" shall mean any work in Source Code or other form that
+results from an addition to, deletion from, or modification of the
+contents of the Program, including, for purposes of clarity any new file
+in Source Code form that contains any contents of the Program. Modified
+Works shall not include works that contain only declarations,
+interfaces, types, classes, structures, or files of the Program solely
+in each case in order to link to, bind by name, or subclass the Program
+or Modified Works thereof.
+
+"Distribute" means the acts of a) distributing or b) making available
+in any manner that enables the transfer of a copy.
+
+"Source Code" means the form of a Program preferred for making
+modifications, including but not limited to software source code,
+documentation source, and configuration files.
+
+"Secondary License" means either the GNU General Public License,
+Version 2.0, or any later versions of that license, including any
+exceptions or additional permissions as identified by the initial
+Contributor.
+
+2. GRANT OF RIGHTS
+
+  a) Subject to the terms of this Agreement, each Contributor hereby
+  grants Recipient a non-exclusive, worldwide, royalty-free copyright
+  license to reproduce, prepare Derivative Works of, publicly display,
+  publicly perform, Distribute and sublicense the Contribution of such
+  Contributor, if any, and such Derivative Works.
+
+  b) Subject to the terms of this Agreement, each Contributor hereby
+  grants Recipient a non-exclusive, worldwide, royalty-free patent
+  license under Licensed Patents to make, use, sell, offer to sell,
+  import and otherwise transfer the Contribution of such Contributor,
+  if any, in Source Code or other form. This patent license shall
+  apply to the combination of the Contribution and the Program if, at
+  the time the Contribution is added by the Contributor, such addition
+  of the Contribution causes such combination to be covered by the
+  Licensed Patents. The patent license shall not apply to any other
+  combinations which include the Contribution. No hardware per se is
+  licensed hereunder.
+
+  c) Recipient understands that although each Contributor grants the
+  licenses to its Contributions set forth herein, no assurances are
+  provided by any Contributor that the Program does not infringe the
+  patent or other intellectual property rights of any other entity.
+  Each Contributor disclaims any liability to Recipient for claims
+  brought by any other entity based on infringement of intellectual
+  property rights or otherwise. As a condition to exercising the
+  rights and licenses granted hereunder, each Recipient hereby
+  assumes sole responsibility to secure any other intellectual
+  property rights needed, if any. For example, if a third party
+  patent license is required to allow Recipient to Distribute the
+  Program, it is Recipient's responsibility to acquire that license
+  before distributing the Program.
+
+  d) Each Contributor represents that to its knowledge it has
+  sufficient copyright rights in its Contribution, if any, to grant
+  the copyright license set forth in this Agreement.
+
+  e) Notwithstanding the terms of any Secondary License, no
+  Contributor makes additional grants to any Recipient (other than
+  those set forth in this Agreement) as a result of such Recipient's
+  receipt of the Program under the terms of a Secondary License
+  (if permitted under the terms of Section 3).
+
+3. REQUIREMENTS
+
+3.1 If a Contributor Distributes the Program in any form, then:
+
+  a) the Program must also be made available as Source Code, in
+  accordance with section 3.2, and the Contributor must accompany
+  the Program with a statement that the Source Code for the Program
+  is available under this Agreement, and informs Recipients how to
+  obtain it in a reasonable manner on or through a medium customarily
+  used for software exchange; and
+
+  b) the Contributor may Distribute the Program under a license
+  different than this Agreement, provided that such license:
+     i) effectively disclaims on behalf of all other Contributors all
+     warranties and conditions, express and implied, including
+     warranties or conditions of title and non-infringement, and
+     implied warranties or conditions of merchantability and fitness
+     for a particular purpose;
+
+     ii) effectively excludes on behalf of all other Contributors all
+     liability for damages, including direct, indirect, special,
+     incidental and consequential damages, such as lost profits;
+
+     iii) does not attempt to limit or alter the recipients' rights
+     in the Source Code under section 3.2; and
+
+     iv) requires any subsequent distribution of the Program by any
+     party to be under a license that satisfies the requirements
+     of this section 3.
+
+3.2 When the Program is Distributed as Source Code:
+
+  a) it must be made available under this Agreement, or if the
+  Program (i) is combined with other material in a separate file or
+  files made available under a Secondary License, and (ii) the initial
+  Contributor attached to the Source Code the notice described in
+  Exhibit A of this Agreement, then the Program may be made available
+  under the terms of such Secondary Licenses, and
+
+  b) a copy of this Agreement must be included with each copy of
+  the Program.
+
+3.3 Contributors may not remove or alter any copyright, patent,
+trademark, attribution notices, disclaimers of warranty, or limitations
+of liability ("notices") contained within the Program from any copy of
+the Program which they Distribute, provided that Contributors may add
+their own appropriate notices.
+
+4. COMMERCIAL DISTRIBUTION
+
+Commercial distributors of software may accept certain responsibilities
+with respect to end users, business partners and the like. While this
+license is intended to facilitate the commercial use of the Program,
+the Contributor who includes the Program in a commercial product
+offering should do so in a manner which does not create potential
+liability for other Contributors. Therefore, if a Contributor includes
+the Program in a commercial product offering, such Contributor
+("Commercial Contributor") hereby agrees to defend and indemnify every
+other Contributor ("Indemnified Contributor") against any losses,
+damages and costs (collectively "Losses") arising from claims, lawsuits
+and other legal actions brought by a third party against the Indemnified
+Contributor to the extent caused by the acts or omissions of such
+Commercial Contributor in connection with its distribution of the Program
+in a commercial product offering. The obligations in this section do not
+apply to any claims or Losses relating to any actual or alleged
+intellectual property infringement. In order to qualify, an Indemnified
+Contributor must: a) promptly notify the Commercial Contributor in
+writing of such claim, and b) allow the Commercial Contributor to control,
+and cooperate with the Commercial Contributor in, the defense and any
+related settlement negotiations. The Indemnified Contributor may
+participate in any such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial
+product offering, Product X. That Contributor is then a Commercial
+Contributor. If that Commercial Contributor then makes performance
+claims, or offers warranties related to Product X, those performance
+claims and warranties are such Commercial Contributor's responsibility
+alone. Under this section, the Commercial Contributor would have to
+defend claims against the other Contributors related to those performance
+claims and warranties, and if a court requires any other Contributor to
+pay any damages as a result, the Commercial Contributor must pay
+those damages.
+
+5. NO WARRANTY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENT
+PERMITTED BY APPLICABLE LAW, THE PROGRAM IS PROVIDED ON AN "AS IS"
+BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
+IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF
+TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
+PURPOSE. Each Recipient is solely responsible for determining the
+appropriateness of using and distributing the Program and assumes all
+risks associated with its exercise of rights under this Agreement,
+including but not limited to the risks and costs of program errors,
+compliance with applicable laws, damage to or loss of data, programs
+or equipment, and unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENT
+PERMITTED BY APPLICABLE LAW, NEITHER RECIPIENT NOR ANY CONTRIBUTORS
+SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
+PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE
+EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+
+If any provision of this Agreement is invalid or unenforceable under
+applicable law, it shall not affect the validity or enforceability of
+the remainder of the terms of this Agreement, and without further
+action by the parties hereto, such provision shall be reformed to the
+minimum extent necessary to make such provision valid and enforceable.
+
+If Recipient institutes patent litigation against any entity
+(including a cross-claim or counterclaim in a lawsuit) alleging that the
+Program itself (excluding combinations of the Program with other software
+or hardware) infringes such Recipient's patent(s), then such Recipient's
+rights granted under Section 2(b) shall terminate as of the date such
+litigation is filed.
+
+All Recipient's rights under this Agreement shall terminate if it
+fails to comply with any of the material terms or conditions of this
+Agreement and does not cure such failure in a reasonable period of
+time after becoming aware of such noncompliance. If all Recipient's
+rights under this Agreement terminate, Recipient agrees to cease use
+and distribution of the Program as soon as reasonably practicable.
+However, Recipient's obligations under this Agreement and any licenses
+granted by Recipient relating to the Program shall continue and survive.
+
+Everyone is permitted to copy and distribute copies of this Agreement,
+but in order to avoid inconsistency the Agreement is copyrighted and
+may only be modified in the following manner. The Agreement Steward
+reserves the right to publish new versions (including revisions) of
+this Agreement from time to time. No one other than the Agreement
+Steward has the right to modify this Agreement. The Eclipse Foundation
+is the initial Agreement Steward. The Eclipse Foundation may assign the
+responsibility to serve as the Agreement Steward to a suitable separate
+entity. Each new version of the Agreement will be given a distinguishing
+version number. The Program (including Contributions) may always be
+Distributed subject to the version of the Agreement under which it was
+received. In addition, after a new version of the Agreement is published,
+Contributor may elect to Distribute the Program (including its
+Contributions) under the new version.
+
+Except as expressly stated in Sections 2(a) and 2(b) above, Recipient
+receives no rights or licenses to the intellectual property of any
+Contributor under this Agreement, whether expressly, by implication,
+estoppel or otherwise. All rights in the Program not expressly granted
+under this Agreement are reserved. Nothing in this Agreement is intended
+to be enforceable by any entity that is not a Contributor or Recipient.
+No third-party beneficiary rights are created under this Agreement.
+
+Exhibit A - Form of Secondary Licenses Notice
+
+"This Source Code may also be made available under the following 
+Secondary Licenses when the conditions for such availability set forth 
+in the Eclipse Public License, v. 2.0 are satisfied: {name license(s),
+version(s), and exceptions or additional permissions here}."
+
+  Simply including a copy of this Agreement, including this Exhibit A
+  is not sufficient to license the Source Code under Secondary Licenses.
+
+  If it is not possible or desirable to put the notice in a particular
+  file, then You may include the notice in a location (such as a LICENSE
+  file in a relevant directory) where a recipient would be likely to
+  look for such a notice.
+
+  You may add additional accurate notices of copyright ownership.
+
 IBM PUBLIC LICENSE VERSION 1.0 - SECURE MAILER
 
 THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM PUBLIC

postfix/RELEASE_NOTES

@@ -1,29 +1,26 @@
-This is the Postfix 3.3 (experimental) release.
+This is the Postfix 3.4 (experimental) release.
 
-The stable Postfix release is called postfix-3.2.x where 3=major
+The stable Postfix release is called postfix-3.3.x where 3=major
-release number, 2=minor release number, x=patchlevel.  The stable
+release number, 3=minor release number, x=patchlevel.  The stable
 release never changes except for patches that address bugs or
 emergencies. Patches change the patchlevel and the release date.
 
 New features are developed in snapshot releases. These are called
-postfix-3.3-yyyymmdd where yyyymmdd is the release date (yyyy=year,
+postfix-3.4-yyyymmdd where yyyymmdd is the release date (yyyy=year,
 mm=month, dd=day).  Patches are never issued for snapshot releases;
 instead, a new snapshot is released.
 
 The mail_release_date configuration parameter (format: yyyymmdd)
 specifies the release date of a stable release or snapshot release.
 
-If you upgrade from Postfix 3.1 or earlier, read RELEASE_NOTES-3.2
+If you upgrade from Postfix 3.2 or earlier, read RELEASE_NOTES-3.3
 before proceeding.
 
-Incompatible changes with snapshot 201800107
+License change
---------------------------------------------
+---------------
 
-This release changes the format of 'full name' information in
+This software is distributed with a dual license: in addition to the
-Postfix-generated From: headers, when a local program such as
+historical IBM Public License 1.0, it is now also distributed with the
-/bin/mail submits a message without From: header.
+more recent Eclipse Public License 2.0. Recipients can choose to take
-
+the software under the license of their choice. Those who are more
-Postfix-generated From: headers with 'full name' information are
+comfortable with the IPL can continue with that license.
-now formatted as "From: name <address>" by default. Specify
-"header_from_format = obsolete" to get the earlier form "From:
-address (name)". See the postconf(5) manpage for more details.

postfix/RELEASE_NOTES-3.3

@@ -0,0 +1,117 @@
+This is the Postfix 3.3 (stable) release.
+
+The stable Postfix release is called postfix-3.3.x where 3=major
+release number, 3=minor release number, x=patchlevel.  The stable
+release never changes except for patches that address bugs or
+emergencies. Patches change the patchlevel and the release date.
+
+New features are developed in snapshot releases. These are called
+postfix-3.4-yyyymmdd where yyyymmdd is the release date (yyyy=year,
+mm=month, dd=day).  Patches are never issued for snapshot releases;
+instead, a new snapshot is released.
+
+The mail_release_date configuration parameter (format: yyyymmdd)
+specifies the release date of a stable release or snapshot release.
+
+If you upgrade from Postfix 3.1 or earlier, read RELEASE_NOTES-3.2
+before proceeding.
+
+License change
+---------------
+
+This software is distributed with a dual license: in addition to the
+historical IBM Public License 1.0, it is now also distributed with the
+more recent Eclipse Public License 2.0. Recipients can choose to take
+the software under the license of their choice. Those who are more
+comfortable with the IPL can continue with that license.
+
+Major changes - compatibility safety net
+----------------------------------------
+
+[20180106] With compatibility_level < 1, the Postfix SMTP server
+now warns for mail that would be blocked by the Postfix 2.10
+smtpd_relay_restrictions feature. This extends the safety net for
+sites that upgrade from earlier Postfix versions (questions on the
+postfix-users list show a steady trickle). See COMPATIBILITY_README
+for details.
+
+Major changes - configuration
+-----------------------------
+
+[20170617] The postconf command warns about unknown parameter names
+in a Postfix database configuration file, specified as an absolute
+pathname.
+
+[20180113] New read-only service_name parameter that contains the
+master.cf service name. This parameter is set only in daemon
+processes. This allows, for example, setting the syslog_name in
+master.cf with "-o syslog_name=postfix/$service_name" for the
+"submission", "smtps", and "relay" services.
+
+Major changes - container support
+---------------------------------
+
+[20171218] Preliminary support to run Postfix in the foreground,
+with "postfix start-fg". This requires that multi-instance support
+is disabled.
+
+Major changes - database support
+---------------------------------
+
+[20170617] The postconf command warns about unknown parameter names
+in a Postfix database configuration file.
+
+[20171227] The pgsql_table(5) hosts parameter now supports the
+postgresql:// URI syntax. Contributed by Magosányi Árpád.
+
+Major changes - header format
+-----------------------------
+
+[20180010] This release changes the format of 'full name' information
+in Postfix-generated From: headers, when a local program such as
+/bin/mail submits a message without From: header.
+
+Postfix-generated From: headers with 'full name' information are
+now formatted as "From: name <address>" by default. Specify
+"header_from_format = obsolete" to get the earlier form "From:
+address (name)". See the postconf(5) manpage for more details.
+
+Major changes - invisible changes
+---------------------------------
+
+[20170617] Additional paranoia in the VSTRING implementation: a
+null byte after the end of vstring buffers so that C-style string
+operations won't scribble past the end; earlier detection of bad
+length and precision format string specifiers (this just improves
+error handling, as format strings cannot be specified externally).
+
+Major changes - milter support
+------------------------------
+
+[20170221] The Postfix Milter client no longer encloses single-letter
+macro names inside {}, even though this form is supported since
+Sendmail version 8.7.
+
+[20171223] Milter applications can now send RET and ENVID parameters
+in SMFIR_CHGFROM (change envelope sender) requests.
+
+Major changes - mixed IPv6/IPv4 support
+---------------------------------------
+
+[20170505] Workaround for mail delivery problems with destinations
+that announce primarily IPv6 MX addresses but that are unreachable
+over IPv6, when the smtp_address_limit eliminates most or all IPv4
+addresses. This includes the case that Postfix IPv6 support is
+turned on, but the local machine has no IPv6 connectivity.
+
+The Postfix SMTP client will now attempt to schedule similar numbers
+of IPv4 and IPv6 addresses. Specify "smtp_balance_mx_inet_protocols
+= no" to disable this workaround.
+
+Major changes - xclient
+-----------------------
+
+[20171218] The Postfix SMTP server now allows the XCLIENT command
+before STARTTLS when TLS is required. This is useful for servers
+that run behind a reverse proxy server such as nginx.
+

postfix/html/socketmap_table.5.html

@@ -27,8 +27,8 @@ SOCKETMAP_TABLE(5)                                          SOCKETMAP_TABLE(5)
 
 <b>PROTOCOL</b>
        Socketmaps use a simple protocol: the client sends one request, and the
-       server sends one reply.  Each request and reply are sent  as  one  net-
+       server sends one reply.  Each request and each reply are  sent  as  one
-       string object.
+       netstring object.
 
 <b>REQUEST FORMAT</b>
        The  socketmap  protocol supports only the lookup request.  The request

postfix/html/tcp_table.5.html

@@ -34,14 +34,17 @@ TCP_TABLE(5)                                                      TCP_TABLE(5)
        Send and receive operations must complete in 100 seconds.
 
 <b>REQUEST FORMAT</b>
-       Each request specifies a command, a lookup key, and possibly  a  lookup
+       The tcp_table protocol supports only the lookup request.   The  request
-       result.
+       has the following form:
 
        <b>get</b> SPACE <i>key</i> NEWLINE
               Look up data under the specified key.
 
-       <b>put</b> SPACE <i>key</i> SPACE <i>value</i> NEWLINE
+       Postfix  will  not  generate  partial  search keys such as domain names
-              This request is currently not implemented.
+       without one or more subdomains, network addresses without one  or  more
+       least-significant  octets,  or  email  addresses without the localpart,
+       address extension or domain portion. This behavior is also  found  with
+       <a href="cidr_table.5.html">cidr</a>:, <a href="pcre_table.5.html">pcre</a>:, and <a href="regexp_table.5.html">regexp</a>: tables.
 
 <b>REPLY FORMAT</b>
        Each  reply specifies a status code and text. Replies must be no longer
@@ -49,8 +52,7 @@ TCP_TABLE(5)                                                      TCP_TABLE(5)
 
        <b>500</b> SPACE <i>text</i> NEWLINE
               In case of a lookup request, the requested data does not  exist.
-              In  case  of  an  update request, the request was rejected.  The
+              The text describes the nature of the problem.
-              text describes the nature of the problem.
 
        <b>400</b> SPACE <i>text</i> NEWLINE
               This indicates an error condition. The text describes the nature
@@ -61,24 +63,24 @@ TCP_TABLE(5)                                                      TCP_TABLE(5)
               text contains an encoded version of the requested data.
 
 <b>ENCODING</b>
-       In request and reply parameters, the  character  %,  each  non-printing
+       In  request  and  reply  parameters, the character %, each non-printing
        character, and each whitespace character must be replaced by %XX, where
        XX is the corresponding ASCII hexadecimal character value. The hexadec-
        imal codes can be specified in any case (upper, lower, mixed).
 
-       The  Postfix  client always encodes a request.  The server may omit the
+       The Postfix client always encodes a request.  The server may  omit  the
-       encoding as long as the reply is guaranteed to not  contain  the  %  or
+       encoding  as  long  as  the reply is guaranteed to not contain the % or
        NEWLINE character.
 
 <b>SECURITY</b>
-       Do  not  use  TCP  lookup  tables  for security critical purposes.  The
+       Do not use TCP lookup  tables  for  security  critical  purposes.   The
        client-server connection is not protected and the server is not authen-
        ticated.
 
 <b>BUGS</b>
        Only the lookup method is currently implemented.
 
-       The  client  does  not  hang  up when the connection is idle for a long
+       The client does not hang up when the connection  is  idle  for  a  long
        time.
 
 <b>SEE ALSO</b>

postfix/man/man5/socketmap_table.5

@@ -33,7 +33,7 @@ socketmap client request (see "REQUEST FORMAT" below).
 .fi
 Socketmaps use a simple protocol: the client sends one
 request, and the server sends one reply.  Each request and
-reply are sent as one netstring object.
+each reply are sent as one netstring object.
 .SH "REQUEST FORMAT"
 .na
 .nf

postfix/man/man5/tcp_table.5

@@ -41,12 +41,17 @@ Send and receive operations must complete in 100 seconds.
 .nf
 .ad
 .fi
-Each request specifies a command, a lookup key, and possibly a
+The tcp_table protocol supports only the lookup request.
-lookup result.
+The request has the following form:
 .IP "\fBget\fR SPACE \fIkey\fR NEWLINE"
 Look up data under the specified key.
-.IP "\fBput\fR SPACE \fIkey\fR SPACE \fIvalue\fR NEWLINE"
+.PP
-This request is currently not implemented.
+Postfix will not generate partial search keys such as domain
+names without one or more subdomains, network addresses
+without one or more least\-significant octets, or email
+addresses without the localpart, address extension or domain
+portion. This behavior is also found with cidr:, pcre:, and
+regexp: tables.
 .SH "REPLY FORMAT"
 .na
 .nf
@@ -56,7 +61,6 @@ Each reply specifies a status code and text. Replies must be no
 longer than 4096 characters including the newline terminator.
 .IP "\fB500\fR SPACE \fItext\fR NEWLINE"
 In case of a lookup request, the requested data does not exist.
-In case of an update request, the request was rejected.
 The text describes the nature of the problem.
 .IP "\fB400\fR SPACE \fItext\fR NEWLINE"
 This indicates an error condition. The text describes the nature of

postfix/proto/socketmap_table

@@ -25,7 +25,7 @@
 # .fi
 #	Socketmaps use a simple protocol: the client sends one
 #	request, and the server sends one reply.  Each request and
-#	reply are sent as one netstring object.
+#	each reply are sent as one netstring object.
 # REQUEST FORMAT
 # .ad
 # .fi

postfix/proto/tcp_table

@@ -8,16 +8,16 @@
 #
 #	\fBpostmap -q - tcp:\fIhost:port\fB <\fIinputfile\fR
 # DESCRIPTION
-#       The Postfix mail system uses optional tables for address
+#	The Postfix mail system uses optional tables for address
-#       rewriting or mail routing. These tables are usually in
+#	rewriting or mail routing. These tables are usually in
-#       \fBdbm\fR or \fBdb\fR format. Alternatively, table lookups
+#	\fBdbm\fR or \fBdb\fR format. Alternatively, table lookups
-#       can be directed to a TCP server.
+#	can be directed to a TCP server.
 #
-#       To find out what types of lookup tables your Postfix system
+#	To find out what types of lookup tables your Postfix system
-#       supports use the "\fBpostconf -m\fR" command.
+#	supports use the "\fBpostconf -m\fR" command.
 #
-#       To test lookup tables, use the "\fBpostmap -q\fR" command as
+#	To test lookup tables, use the "\fBpostmap -q\fR" command as
-#       described in the SYNOPSIS above.
+#	described in the SYNOPSIS above.
 # PROTOCOL DESCRIPTION
 # .ad
 # .fi
@@ -31,12 +31,17 @@
 # REQUEST FORMAT
 # .ad
 # .fi
-#	Each request specifies a command, a lookup key, and possibly a
+#	The tcp_table protocol supports only the lookup request.
-#	lookup result.
+#	The request has the following form:
 # .IP "\fBget\fR SPACE \fIkey\fR NEWLINE"
 #	Look up data under the specified key.
-# .IP "\fBput\fR SPACE \fIkey\fR SPACE \fIvalue\fR NEWLINE"
+# .PP
-#	This request is currently not implemented.
+#	Postfix will not generate partial search keys such as domain
+#	names without one or more subdomains, network addresses
+#	without one or more least-significant octets, or email
+#	addresses without the localpart, address extension or domain
+#	portion. This behavior is also found with cidr:, pcre:, and
+#	regexp: tables.
 # REPLY FORMAT
 # .ad
 # .fi
@@ -44,7 +49,6 @@
 #	longer than 4096 characters including the newline terminator.
 # .IP "\fB500\fR SPACE \fItext\fR NEWLINE"
 #	In case of a lookup request, the requested data does not exist.
-#	In case of an update request, the request was rejected.
 #	The text describes the nature of the problem.
 # .IP "\fB400\fR SPACE \fItext\fR NEWLINE"
 #	This indicates an error condition. The text describes the nature of

postfix/src/global/mail_version.h

@@ -20,8 +20,8 @@
   * Patches change both the patchlevel and the release date. Snapshots have no
   * patchlevel; they change the release date only.
   */
-#define MAIL_RELEASE_DATE	"20180121"
+#define MAIL_RELEASE_DATE	"20180203"
-#define MAIL_VERSION_NUMBER	"3.3"
+#define MAIL_VERSION_NUMBER	"3.4"
 
 #ifdef SNAPSHOT
 #define MAIL_VERSION_DATE	"-" MAIL_RELEASE_DATE