From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] postfix: Update to version 3.10.1
Date: Sun, 02 Mar 2025 09:26:14 +0000 [thread overview]
Message-ID: <20250226181250.1470980-5-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250226181250.1470980-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 7019 bytes --]
- Update from version 3.9.1 to 3.10.1
- Update of rootfile not required
- Changelog
3.10.1
Bugfix (defect introduced: 20250210): a recent 'fix' for the default
smtp_tls_dane_insecure_mx_policy setting resulted in unnecessary 'dnssec_probe'
warnings, on systems that disable DNSSEC lookups (which is the default).
3.10.0
Changes that need a restart:
Internal protocol change: Postfix needs "postfix reload" (or "postfix stop"
and "postfix start") after upgrade, because of a change in the delivery
agent protocol. If this step is skipped, Postfix delivery agents will
log a warning:
unexpected attribute smtputf8 from xxx socket (expecting: sendopts)
where xxx is the delivery agent service name.
Changes in TLS support:
Forward compatibility: Support for OpenSSL 3.5 post-quantum cryptography.
To manage algorithm selection, OpenSSL introduces new TLS group syntax
that Postfix will not attempt to imitate. Instead, Postfix now allows
the tls_eecdh_auto_curves and tls_ffdhe_auto_groups parameter values to
have an empty value. When both are set empty, the algorithm selection
can be managed through OpenSSL configuration. For more, look for
"Post-quantum" in the postconf(5) manpage.
Support for the RFC 8689 "TLS-Required: no" message header to request
delivery of messages (such as TLSRPT summaries) even if the preferred
TLS security policy cannot be enforced. This limits the Postfix SMTP
client to "smtp_tls_security_level = may" which does not authenticate
server certificates and which allows falling back to plaintext.
Support for the REQUIRETLS SMTP service extension will evolve in Postfix 3.11.
Support for the TLSRPT protocol (defined in RFC 8460). With this, a domain
can publish a policy in DNS that requests daily summary reports for
successful and failed SMTP-over-TLS connections to that domain's MX
hosts. This supports both DANE (built-in) and MTA-STS (via an
smtp_tls_policy_maps plugin). The implementation uses a TLSRPT library
and reporting infrastructure that are maintained by sys4. For details,
see TLSRPT_README.
Miscellaneous changes:
Privacy: With "smtpd_hide_client_session = yes", the Postfix SMTP server
generates a Received: header without client session info. This setting
may be used with the MUA submission services (port 465 and 587).
Support for RFC 2047 encoding of non-ASCII "full name" information in
Postfix-generated From: message headers. Encoding non-ASCII full names
can avoid the need to use SMTPUTF8, and therefore can avoid
incompatibility with sites that do not support SMTPUTF8. See the
full_name_encoding_charset parameter description for details.
Database performance: When mysql: or pgsql: configuration specifies a
single host, assume that it is a load balancer and reconnect
immediately after a single failure, instead of failing all requests
for 60s.
Changes in logging:
The Postfix Milter implementation now logs the reason for a 'quarantine'
action, instead of "milter triggers HOLD action".
The SMTP server now logs the queue ID (or "NOQUEUE") when a connection
ends abnormally (timeout, lost connection, or too many errors), and
the cleanup server now logs "queueid: canceled" when a message
transaction is started but not completed. These changes simplify
logfile analysis.
Dovecot SASL client logging for "Invalid authentication mechanism" now
includes the name of that mechanism.
Postfix SMTP server 'reject' logging now shows the sasl_method,
sasl_username, and sasl_sender if available.
3.9.2
Forward compatibility: Support for OpenSSL 3.5 post-quantum cryptography.
To manage algorithm selection, OpenSSL introduces new TLS group syntax
that Postfix will not attempt to imitate. Instead, Postfix now allows
the tls_eecdh_auto_curves and tls_ffdhe_auto_groups parameter values
to have an empty value. When both are set empty, the algorithm
selection can be managed through OpenSSL configuration. Viktor Dukhovni.
Forward compatibility: ignore new queue file flag bits that may be used
with Postfix 3.10 and later. This is a safety in case a Postfix 3.10
upgrade needs to be rolled back, after the new TLS-Required feature
has been used.
Performance: when a mysql: or pgsql: configuration specifies a single
host, assume that it is a load balancer and reconnect immediately
after a single failure, instead of failing all requests for 60s.
Bugfix (defect introduced: Postfix 3.4, date 20181113): a server with
multiple TLS certificates could report, for a resumed TLS session, the
wrong server-signature and server-digest names in logging and
Received: message headers. Viktor Dukhovni.
Bugfix (defect introduced: Postfix 3.3, date 20180107) small memory leak
in the cleanup daemon when generating a "From: full-name " message
header. The impact is limited because the number of requests is
bounded by the "max_use" configuration parameter. Found during code
maintenance.
Bugfix (defect introduced: Postfix 3.0): the bounce daemon mangled a
non-ASCII address localpart in the "X-Postfix-Sender:" field of a
delivery status notification. It backslash-escaped each byte in a
multi-byte character. This behavior was implemented in Postfix 2.1 (no
support for UTF8 local-parts), but it became incorrect after SMTPUTF8
support was implemented in Postfix 3.0.
Bugfix (defect introduced: Postfix 3.6): Reverted the default
smtp_tls_dane_insecure_mx_policy setting to "dane" as of
Postfix 3.6.17, 3.7.13, 3.8.8, 3.9.2, and 3.10.0. By mistake the
default was dependent on the smtp_tls_security_level setting. Problem
reported by Ömer Güven.
Portability: added "include <sys_socket.h>" for a SUNOS5 workaround. Gary
R. Schmidt.
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/postfix | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/postfix b/lfs/postfix
index 2435f3c39..c9fe4cbd8 100644
--- a/lfs/postfix
+++ b/lfs/postfix
@@ -26,7 +26,7 @@ include Config
SUMMARY = A fast, secure, and flexible mailer
-VER = 3.9.1
+VER = 3.10.1
THISAPP = postfix-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = postfix
-PAK_VER = 46
+PAK_VER = 47
DEPS =
@@ -70,7 +70,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 78be7bf0f0d9e46429b40f98ddc98cac442cfdb404d77073346c973f3d0d4c52f299fc7f5d64bddaaf2db60dd234c52790f1efe4995faee8e2cd10c6f8e2096f
+$(DL_FILE)_BLAKE2 = ff2ff4a6fc61eb7f513124abc7a03f69b4c195967816a28a4708fbe7256e78959d499941747ef2fea7999bd2754e2e640e98e247a7870449cffb66ebf30ffee9
install : $(TARGET)
--
2.48.1
prev parent reply other threads:[~2025-03-02 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 9:26 [PATCH] btrfs-progs: Update to version 6.13 Adolf Belka
2025-03-02 9:26 ` [PATCH] pcre2: Update to version 10.45 Adolf Belka
2025-03-02 9:26 ` [PATCH] tshark: Update to version 4.4.5 Adolf Belka
2025-03-02 9:26 ` [PATCH] diffutils: Update to version 3.11 Adolf Belka
2025-03-02 9:26 ` [PATCH] zstd: Update to version 1.5.7 Adolf Belka
2025-03-02 9:26 ` [PATCH] which: Update to version 2.23 Adolf Belka
2025-03-02 9:26 ` [PATCH] libffi: Update to version 3.4.7 Adolf Belka
2025-03-02 9:26 ` [PATCH] xfsprogs: Update to version 6.13.0 Adolf Belka
2025-03-02 9:26 ` Adolf Belka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250226181250.1470980-5-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox