From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] postfix: Update to version 3.10.4
Date: Tue, 26 Aug 2025 20:49:00 +0200 [thread overview]
Message-ID: <20250826184904.6229-19-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250826184904.6229-1-adolf.belka@ipfire.org>
- Update from version 3.10.2 to 3.10.4
- Update of rootfile not required
- Changelog
3.10.4
Fixes for postscreen(8):
Bugfix (defect introduced: postfix-2.2, date 20050203): after detecting a
lookup table change, and after starting a new postscreen process, the old
postscreen process logged an ENOTSOCK error while attempting to accept a
connection on a socket that it was no longer listening on. This error was
introduced first in the multi_server skeleton code, and was five years later
duplicated in the event_server skeleton that was created for postscreen.
Problem reported by Florian Piekert.
Bugfix (defect introduced: Postfix 2.8, date 20101230): after detecting a cache
table change and before starting a new postscreen process, the old postscreen
process did not close the postscreen_cache_map, and therefore kept an
exclusive lock that could prevent a new postscreen process from starting.
Problem reported by Florian Piekert.
Fixes for tlsproxy(8):
Bugfix (defect introduced: Postfix 3.7): incorrect backwards compatible support
for the legacy configuration parameters tlsproxy_client_level and
tlsproxy_client_policy. This disabled the tlsproxy TLS client role when a
legacy parameter was set (instead of the newer tlsproxy_client_security_level
or tlsproxy_client_policy_maps). Reported by John Doe, diagnosed by Viktor
Dukhovni.
Bugfix (defect introduced: Postfix 3.4): with the TLS client role disabled by
configuration, the tlsproxy daemon dereferenced a null pointer while handling
a tlsproxy client request. Reported by John Doe.
Reducing process churn: Postfix daemons no longer automatically restart after a
btree:, dbm:, hash:, lmdb:, or sdbm: table file modification time change, when
they opened that table for writing.
Portability: deleted an <openssl/engine.h> build dependency, because the feature
is being removed from OpenSSL, and Postfix no longer needs it.
Cleanup: with "tls_required_enable = yes", the Postfix SMTP client will no longer
maintain TLSRPT statistics for messages that contain a "TLS-Required: no"
header. This can prevent TLSRPT notifications for TLSRPT notifications.
Bugfix (defect introduced: Postfix 3.6, date 20200710): Postfix TLS client code
logged "Untrusted TLS connection" (wrong) instead of "Trusted TLS connection"
(right), for a new or resumed TLS session, when a server offered a trusted
(valid PKI trust chain) certificate that did not match the expected server name
pattern. Fix by Viktor Dukhovni.
3.10.3
This release fixes defects that were introduced in Postfix 3.10. These were
fixed first in the Postfix 3.11 unstable release.
The defects exist only with the default configuration "tls_required_enable = yes".
Bugfix (defect introduced: Postfix-3.10, date 20250117): include the
current TLS security level in the SMTP connection cache lookup key for
lookups by next-hop destination, to avoid reusing the same SMTP
connection when sending messages with and without a "TLS-Required: no"
header. Likewise, include the current TLS security level in the TLS
session lookup key, to avoid reusing the same TLS session info when
sending messages with and without a "TLS-Required: no" header.
Bugfix (defect introduced: Postfix-3.10, date 20250117): the Postfix SMTP
client attempted to look up TLSA records even with "TLS-Required: no".
This could result in unnecessary failures. Fix by Viktor Dukhovni &
Wietse.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/postfix | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/postfix b/lfs/postfix
index 5dd1a3c98..2bc0174d1 100644
--- a/lfs/postfix
+++ b/lfs/postfix
@@ -26,7 +26,7 @@ include Config
SUMMARY = A fast, secure, and flexible mailer
-VER = 3.10.2
+VER = 3.10.4
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 = 48
+PAK_VER = 49
DEPS =
@@ -72,7 +72,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = b75fec52e837d43e0fa5d6ede3f44ccc62144133a2c433f536c566362b20a6a9b8a8cbf8e11f64d84fa751311cc9451158cda0edc212a0e45a9097530f41cea4
+$(DL_FILE)_BLAKE2 = e0a9b3dbd858e9b2bacb137b886ef35a89220caf91da5bcb90de5fd3df7285645deaff6e58f571cdc75966098cf13190b0315690c270b9f3ed69a21e63d2d3ab
install : $(TARGET)
--
2.51.0
next prev parent reply other threads:[~2025-08-26 18:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 18:48 [PATCH] btrfs-progs: Update to version 6.16 Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship btrfs-progs Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship gdbm Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship harfbuzz Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship hwdata Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship libinih Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship lsof Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship nano Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship sudo Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship whois Adolf Belka
2025-08-26 18:48 ` [PATCH] fping: Update to version 5.4 Adolf Belka
2025-08-26 18:48 ` [PATCH] gdbm: Update to version 1.26 Adolf Belka
2025-08-26 18:48 ` [PATCH] git: Update to version 2.51.0 Adolf Belka
2025-08-26 18:48 ` [PATCH] harfbuzz: Update to version 11.4.3 Adolf Belka
2025-08-26 18:48 ` [PATCH] hwdata: Update to version 0.398 Adolf Belka
2025-08-26 18:48 ` [PATCH] libinih: Update to version 61 Adolf Belka
2025-08-26 18:48 ` [PATCH] lsof: Update to version 4.99.5 Adolf Belka
2025-08-26 18:48 ` [PATCH] nano: Update to version 8.6 Adolf Belka
2025-08-26 18:49 ` Adolf Belka [this message]
2025-08-26 18:49 ` [PATCH] rpcbind: Update to version 1.2.8 Adolf Belka
2025-08-26 18:49 ` [PATCH] sudo: Update to version 1.9.17p2 Adolf Belka
2025-08-26 18:49 ` [PATCH] whois: Update to version 5.6.4 Adolf Belka
2025-08-26 18:49 ` [PATCH] wsdd: Update to version 0.9 Adolf Belka
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=20250826184904.6229-19-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