From: Wietse Venema Date: Fri, 22 Oct 2021 05:00:00 +0000 (-0500) Subject: postfix-3.7-20211022 X-Git-Tag: v3.7.0-RC1~12 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6b8941f03ee386912dac2ad272dbb6e4bf674a6c;p=thirdparty%2Fpostfix.git postfix-3.7-20211022 --- diff --git a/postfix/HISTORY b/postfix/HISTORY index 0485b328c..470435702 100644 --- a/postfix/HISTORY +++ b/postfix/HISTORY @@ -25795,3 +25795,23 @@ Apologies for any names omitted. smtp/smtp.h, smtp/smtp_chat.c, smtp/smtp_params.c, smtpd/smtpd.c, smtpd/smtpd.h, smtpd/smtpd_chat.c, and test data. + +20211006 + + Documentation: http://tools.ietf.org/html/rfc[0-9]+ sometimes + does not redirect to the https site. Max-Julian Pogner. + Fixed by updating mantools/postlink and rebuilding the HTML + files that reference RFCs. + +20211016 + + Documentation: clarified the difference between private and + public services in master.cf. File: proto/master. + +20211022 + + Bugfix: the known_tcp_ports setting had no effect. Reported + by Peter. It also wasn't fully implemented. Files: + config_known_tcp_ports.c, mail_params.c, + posttls-finger/posttls-finger.c, smtp/smtp_connect.c, + util/find_inet.c, util/myaddrinfo.c. diff --git a/postfix/TODO b/postfix/TODO deleted file mode 100644 index 274bf9b40..000000000 --- a/postfix/TODO +++ /dev/null @@ -1,5 +0,0 @@ -Add a note to tlsproxy source why it does not enforce deadlines or -minimum data rates. Reason: tlsproxy relies on the plaintext client -to enforce their context-dependent deadlines and data rates. When -a plaintext client times out, it will close the tlsproxy connection, -and then tlsproxy will also hang up. diff --git a/postfix/WISHLIST b/postfix/WISHLIST index fb7f5d64e..a1e55e8ca 100644 --- a/postfix/WISHLIST +++ b/postfix/WISHLIST @@ -1,6 +1,11 @@ Wish list: - Add verp=+= to the qmgr "from=" logging. + Add a pointer to + http://mmogilvi.users.sourceforge.net/software/oauthbearer.html + in documentation or on-line howtos. + + Add verp=+= to the qmgr "from=" logging. This is already + implemented but not yet integrated. Need canonical Dovecot example that has virtual_mailbox_domains, (virtual_mailbox_maps or reject unverified_recipient), and diff --git a/postfix/html/BDAT_README.html b/postfix/html/BDAT_README.html index cb9775541..56532fc30 100644 --- a/postfix/html/BDAT_README.html +++ b/postfix/html/BDAT_README.html @@ -20,7 +20,7 @@ BDAT (CHUNKING) support

Overview

-

Postfix SMTP server supports RFC 3030 CHUNKING (the BDAT command) +

Postfix SMTP server supports RFC 3030 CHUNKING (the BDAT command) without BINARYMIME, in both smtpd(8) and postscreen(8). It is enabled by default.

@@ -155,7 +155,7 @@ signatures, so conversion would have to happen before signing.

Downsides of CHUNKING (BDAT) support

-

The RFC 3030 authors did not specify any limitations on how +

The RFC 3030 authors did not specify any limitations on how clients may pipeline commands (i.e. send commands without waiting for a server response). If a server announces PIPELINING support, like Postfix does, then a remote SMTP client can pipeline all @@ -167,10 +167,10 @@ behavior. If you require "rej then turn off Postfix's CHUNKING announcement as described above.

-

In RFC 4468, the authors write that a client may pipeline +

In RFC 4468, the authors write that a client may pipeline commands, and that after sending BURL LAST or BDAT LAST, a client must wait for the server's response. But as this text does not -appear in RFC 3030 which defines BDAT, is it a useless restriction +appear in RFC 3030 which defines BDAT, is it a useless restriction that Postfix will not enforce.

diff --git a/postfix/html/BUILTIN_FILTER_README.html b/postfix/html/BUILTIN_FILTER_README.html index fbe383ba3..74d138d47 100644 --- a/postfix/html/BUILTIN_FILTER_README.html +++ b/postfix/html/BUILTIN_FILTER_README.html @@ -222,9 +222,9 @@ header/body checks for mail to some domains only".

  • Header/body checks do not decode message headers or message body content. For example, if text in the message body is BASE64 -encoded (RFC 2045) then your regular expressions will have to match +encoded (RFC 2045) then your regular expressions will have to match the BASE64 encoded form. Likewise, message headers with encoded -non-ASCII characters (RFC 2047) need to be matched in their encoded +non-ASCII characters (RFC 2047) need to be matched in their encoded form.

  • Header/body checks cannot filter on a combination of diff --git a/postfix/html/DSN_README.html b/postfix/html/DSN_README.html index 0406d6065..ea50c09da 100644 --- a/postfix/html/DSN_README.html +++ b/postfix/html/DSN_README.html @@ -21,7 +21,7 @@ DSN Support

    Introduction

    Postfix version 2.3 introduces support for Delivery Status -Notifications as described in RFC 3464. This gives senders control +Notifications as described in RFC 3464. This gives senders control over successful and failed delivery notifications.

    Specifically, DSN support gives an email sender the ability to diff --git a/postfix/html/FORWARD_SECRECY_README.html b/postfix/html/FORWARD_SECRECY_README.html index 92622b422..fd685bd40 100644 --- a/postfix/html/FORWARD_SECRECY_README.html +++ b/postfix/html/FORWARD_SECRECY_README.html @@ -227,7 +227,7 @@ setting the main.cf parameter RFC 8031 to augment or replace the NIST curves tarnished +introduced in RFC 8031 to augment or replace the NIST curves tarnished by the Snowden revelations. Fortunately, TLS clients advertise their list of supported curves to the server so that servers can choose newer stronger curves when mutually supported. OpenSSL 1.0.2 diff --git a/postfix/html/IPV6_README.html b/postfix/html/IPV6_README.html index eb619e8b1..c1211e912 100644 --- a/postfix/html/IPV6_README.html +++ b/postfix/html/IPV6_README.html @@ -228,7 +228,7 @@ to the LMTP client.

  • The SMTP server now requires that IPv6 addresses in SMTP commands are specified as [ipv6:ipv6address], as -described in RFC 2821.

    +described in RFC 2821.

  • The IPv6 network address matching code was rewritten from the ground up, and is expected to be closer to the specification. diff --git a/postfix/html/LDAP_README.html b/postfix/html/LDAP_README.html index fae15b914..b4f938c13 100644 --- a/postfix/html/LDAP_README.html +++ b/postfix/html/LDAP_README.html @@ -199,7 +199,7 @@ server listening at port 389 on ldap.example.com. It will bind anonymously, search for any directory entries whose mailacceptinggeneralid attribute is "ldapuser", read the "maildrop" attributes of those found, and build a list of their maildrops, which will be treated -as RFC822 addresses to which the message will be delivered.

    +as RFC822 addresses to which the message will be delivered.

    Example: virtual domains/addresses

    @@ -592,10 +592,10 @@ contents, please include the applicable bits of some directory entries.

  • Prabhat K Singh: Wrote the initial Postfix LDAP lookups and connection caching. -
  • Keith Stevenson: RFC 2254 escaping in queries. +
  • Keith Stevenson: RFC 2254 escaping in queries.
  • Samuel Tardieu: Noticed that searches could include wildcards, prompting - the work on RFC 2254 escaping in queries. Spotted a bug + the work on RFC 2254 escaping in queries. Spotted a bug in binding.
  • Sami Haahtinen: Referral chasing and v3 support. diff --git a/postfix/html/MAILDROP_README.html b/postfix/html/MAILDROP_README.html index 24b3e63b4..aa2d7946a 100644 --- a/postfix/html/MAILDROP_README.html +++ b/postfix/html/MAILDROP_README.html @@ -85,7 +85,7 @@ becoming clogged with undeliverable messages. Specify an empty value ("virtual_mailbox_maps =") to disable this feature.

  • Lines 6 and 13-15 redirect mail for postmaster to the -local postmaster. RFC 821 requires that every domain has a postmaster +local postmaster. RFC 821 requires that every domain has a postmaster address.

    diff --git a/postfix/html/SASL_README.html b/postfix/html/SASL_README.html index 82407e7fa..c074c8c21 100644 --- a/postfix/html/SASL_README.html +++ b/postfix/html/SASL_README.html @@ -25,7 +25,7 @@ mail to remote destinations when the client's IP address is in the

    SMTP clients outside the SMTP server's network need a different way to get "same network" privileges. To address this need, Postfix -supports SASL authentication (RFC 4954, formerly RFC 2554). With +supports SASL authentication (RFC 4954, formerly RFC 2554). With this a remote SMTP client can authenticate to the Postfix SMTP server, and the Postfix SMTP client can authenticate to a remote SMTP server. Once a client is authenticated, a server can give it diff --git a/postfix/html/SMTPD_ACCESS_README.html b/postfix/html/SMTPD_ACCESS_README.html index 1ac3d57c2..53aa66d1d 100644 --- a/postfix/html/SMTPD_ACCESS_README.html +++ b/postfix/html/SMTPD_ACCESS_README.html @@ -145,7 +145,7 @@ no").