From: Wietse Venema Date: Sat, 6 Jan 2018 05:00:00 +0000 (-0500) Subject: postfix-3.3-20180106 X-Git-Tag: v3.3.0-RC1~5 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fb55728de4e3de5b52e7c827869cb0536b0f44dd;p=thirdparty%2Fpostfix.git postfix-3.3-20180106 --- diff --git a/postfix/HISTORY b/postfix/HISTORY index 25d5fa870..0d863dd2f 100644 --- a/postfix/HISTORY +++ b/postfix/HISTORY @@ -23200,8 +23200,8 @@ Apologies for any names omitted. Workaround: reportedly, some res_query(3) implementation can return -1 with h_errno==0. Instead of terminating with - a panic, the DNS client now logs a warning and sets h_errno - to TRY_AGAIN. File: dns/dns_lookup.c. + a panic, the Postfix DNS client now logs a warning and sets + h_errno to TRY_AGAIN. File: dns/dns_lookup.c. Cleanup: allow XCLIENT before STARTTLS, when TLS is required. File: smtpd/smtpd.c. @@ -23238,3 +23238,23 @@ Apologies for any names omitted. Cleanup: added employer attributions for non-trivial changes after Wietse changed employers. + +20180106 + + Compatibility: with compatibility_level < 1, the 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). Files: proto/COMPATIBILITY_README.html, + global/mail_params[hc], smtpd/smtpd_check.c. + + Cleanup: reset compatibility_level warnings after 'postfix + reload'. This is relevant primarily for the master daemon. + File: global/mail_params.c. + + Cleanup: missing mailbox seek-to-end error check in the + local(8) delivery agent. File: local/mailbox.c. + + Cleanup: incorrect mailbox seek-to-end error message in the + virtual(8) delivery agent. File: virtual/mailbox.c. diff --git a/postfix/README_FILES/COMPATIBILITY_README b/postfix/README_FILES/COMPATIBILITY_README index 83d300cf4..20674ff6c 100644 --- a/postfix/README_FILES/COMPATIBILITY_README +++ b/postfix/README_FILES/COMPATIBILITY_README @@ -33,6 +33,9 @@ The following messages may be logged: * Using backwards-compatible default setting chroot=y + * Using backwards-compatible default setting smtpd_relay_restrictions = + (empty) + * Using backwards-compatible default setting mynetworks_style=subnet * Using backwards-compatible default setting relay_domains=$mydestination @@ -49,10 +52,14 @@ described at the end of this document. UUssiinngg bbaacckkwwaarrddss--ccoommppaattiibbllee ddeeffaauulltt sseettttiinngg aappppeenndd__ddoott__mmyyddoommaaiinn==yyeess -The append_dot_mydomain default value has changed from "yes" to "no". As long -as the append_dot_mydomain parameter is left at its implicit default value, and -the backwards-compatible default setting is turned on, Postfix may log one of -the following messages: +The append_dot_mydomain default value has changed from "yes" to "no". This +could result in unexpected non-delivery of email after Postfix is updated from +an older version. The backwards-compatibility safety net is designed to prevent +such surprises. + +As long as the append_dot_mydomain parameter is left at its implicit default +value, and the compatibility_level setting is less than 1, Postfix may log one +of the following messages: * Messages about missing "localhost" in mydestination or other address class: @@ -81,10 +88,16 @@ the following messages: UUssiinngg bbaacckkwwaarrddss--ccoommppaattiibbllee ddeeffaauulltt sseettttiinngg cchhrroooott==yy -The master.cf chroot default value has changed from "y" (yes) to "n" (no). As -long as a master.cf chroot field is left at its implicit default value, and the -backwards-compatible default setting is turned on, Postfix may log the -following message while it reads the master.cf file: +The master.cf chroot default value has changed from "y" (yes) to "n" (no). The +new default avoids the need for copies of system files under the Postfix queue +directory. However, sites with strict security requirements may want to keep +the chroot feature enabled after updating Postfix from an older version. The +backwards-compatibility safety net is designed allow the administrator to +choose if they want to keep the old behavior. + +As long as a master.cf chroot field is left at its implicit default value, and +the compatibility_level setting is less than 1, Postfix may log the following +message while it reads the master.cf file: postfix/master[27664]: /etc/postfix/master.cf: line 72: using backwards-compatible default setting chroot=y @@ -96,13 +109,45 @@ example, to update the chroot setting for the "smtp inet" service: # ppoossttccoonnff --FF ssmmttpp//iinneett//cchhrroooott==yy # ppoossttffiixx rreellooaadd +UUssiinngg bbaacckkwwaarrddss--ccoommppaattiibbllee ddeeffaauulltt sseettttiinngg ssmmttppdd__rreellaayy__rreessttrriiccttiioonnss == ((eemmppttyy)) + +The smtpd_relay_restrictions feature was introduced with Postfix version 2.10, +as a safety mechanism for configuration errors in smtpd_recipient_restrictions +that could make Postfix an open relay. + +The smtpd_relay_restrictions implicit default setting forbids mail to remote +destinations from clients that don't match permit_mynetworks or +permit_sasl_authenticated. This could result in unexpected 'Relay access +denied' errors after Postfix is updated from an older Postfix version. The +backwards-compatibility safety net is designed to prevent such surprises. + +When the compatibility_level less than 1, and the smtpd_relay_restrictions +parameter is left at its implicit default setting, Postfix may log the +following message: + + postfix/smtpd[38463]: using backwards-compatible default setting + "smtpd_relay_restrictions = (empty)" to avoid "Relay access + denied" error for recipient "user@example.com" from client + "host.example.net[10.0.0.2]" + +If this request should not be blocked, then the system administrator should +make the backwards-compatible setting "smtpd_relay_restrictions=" (i.e. empty) +permanent in main.cf: + + # ppoossttccoonnff ssmmttppdd__rreellaayy__rreessttrriiccttiioonnss== + # ppoossttffiixx rreellooaadd + UUssiinngg bbaacckkwwaarrddss--ccoommppaattiibbllee ddeeffaauulltt sseettttiinngg mmyynneettwwoorrkkss__ssttyyllee==ssuubbnneett The mynetworks_style default value has changed from "subnet" to "host". This -parameter is used to implement the "permit_mynetworks" feature. As long as the -mynetworks and mynetworks_style parameters are left at their implicit default -values, and the backwards-compatible default setting is turned on, the Postfix -SMTP server may log one of the following messages: +parameter is used to implement the "permit_mynetworks" feature. The change +could in unexpected 'access denied' errors after Postfix is updated from an +older version. The backwards-compatibility safety net is designed to prevent +such surprises. + +As long as the mynetworks and mynetworks_style parameters are left at their +implicit default values, and the compatibility_level setting is less than 2, +the Postfix SMTP server may log one of the following messages: postfix/smtpd[17375]: using backwards-compatible default setting mynetworks_style=subnet to permit request from client @@ -122,9 +167,13 @@ permanent in main.cf: UUssiinngg bbaacckkwwaarrddss--ccoommppaattiibbllee ddeeffaauulltt sseettttiinngg rreellaayy__ddoommaaiinnss==$$mmyyddeessttiinnaattiioonn The relay_domains default value has changed from "$mydestination" to the empty -value. As long as the relay_domains parameter is left at its implicit default -value, and the backwards-compatible default setting is turned on, Postfix may -log one of the following messages. +value. This could result in unexpected 'Relay access denied' errors or ETRN +errors after Postfix is updated from an older version. The backwards- +compatibility safety net is designed to prevent such surprises. + +As long as the relay_domains parameter is left at its implicit default value, +and the compatibility_level setting is less than 2, Postfix may log one of the +following messages. * Messages about accepting mail for a remote domain: @@ -163,14 +212,14 @@ UUssiinngg bbaacckkwwaarrddss--ccoommppaattiibbllee dd The smtputf8_enable default value has changed from "no" to "yes. With the new "yes" setting, the Postfix SMTP server rejects non-ASCII addresses from clients -that don't request SMTPUTF8 support. With the old "no" setting, Postfix will -accept such addresses, even if such addresses are not permitted by traditional -SMTP standards. +that don't request SMTPUTF8 support, after Postfix is updated from an older +version. The backwards-compatibility safety net is designed to prevent such +surprises. As long as the smtputf8_enable parameter is left at its implicit default value, -and the backwards-compatible default setting is turned on, Postfix logs a -warning each time an SMTP command uses a non-ASCII address localpart without -requesting SMTPUTF8 support: +and the compatibility_level setting is less than 1, Postfix logs a warning each +time an SMTP command uses a non-ASCII address localpart without requesting +SMTPUTF8 support: postfix/smtpd[27560]: using backwards-compatible default setting smtputf8_enable=no to accept non-ASCII sender address diff --git a/postfix/html/COMPATIBILITY_README.html b/postfix/html/COMPATIBILITY_README.html index 5772eb9a8..d527e1981 100644 --- a/postfix/html/COMPATIBILITY_README.html +++ b/postfix/html/COMPATIBILITY_README.html @@ -48,7 +48,7 @@ continuity of service. Based on this logging the system administrator can decide if any backwards-compatible settings need to be made permanent in main.cf or master.cf, before turning off the backwards-compatibility safety net as described at the -end of this document.

+end of this document.

The following messages may be logged:

@@ -60,6 +60,9 @@ default setting append_dot_mydomain=yes

  • Using backwards-compatible default setting chroot=y

    +

  • Using backwards-compatible +default setting smtpd_relay_restrictions = (empty)

    +

  • Using backwards-compatible default setting mynetworks_style=subnet

    @@ -79,15 +82,19 @@ sections that follow.

    When no more backwards-compatible settings need to be made permanent, the system administrator should turn off the backwards-compatibility safety net as described at the -end of this document.

    +end of this document.

    Using backwards-compatible default setting append_dot_mydomain=yes

    The append_dot_mydomain default value has changed from "yes" -to "no". As long as the append_dot_mydomain parameter is left at -its implicit default value, and the backwards-compatible default -setting is turned on, Postfix may log one of the following messages:

    +to "no". This could result in unexpected non-delivery of email after +Postfix is updated from an older version. The backwards-compatibility +safety net is designed to prevent such surprises.

    + +

    As long as the append_dot_mydomain parameter is left at +its implicit default value, and the compatibility_level setting is +less than 1, Postfix may log one of the following messages: