postfix: Update to version 3.9.1
Commit Message
- Update from version 3.9.0 to 3.9.1
- Update of rootfile not required
- Changelog
3.9.1
The mail_version configuration parameter did not have a three-number value
(3.9 instead of 3.9.0; it still had the two-number version from the
development releases postfix-3.9-yyyymmdd). This broke pathnames derived
from the mail_version value, such as shlib_directory. Problem reported by
Michael Orlitzky.
Bugfix (defect introduced: Postfix 2.9, date 20111218): with
"smtpd_sasl_auth_enable = no", the permit_sasl_authenticated feature
ignored information that was received with the XCLIENT LOGIN command, so
that the client was treated as unauthenticated. This was fixed by removing
an unnecessary test. Problem reported by Antonin Verrier.
Bugfix (defect introduced: postfix 3.0): the default master.cf syslog_name
setting for the relay service did not preserve multi-instance information,
which complicated logfile analysis. Found during a support discussion.
Bugfix (defect introduced: Postfix 2.3, date 20051222): file descriptor
leak after failure to connect to a Dovecot auth server. The impact is
limited because Dovecot auth failures are rare, there are limits on the
number of retries (one), on the number of errors per SMTP session
(smtpd_hard_error_limit), on the number of sessions per SMTP server
process (max_use), and on the number of file handles per process (managed
with sysctl). Found during code maintenance.
Bugfix (defect introduced: Postfix 3.4, date 20190121): the postsuper
command failed with "open logfile '/path/to/file': Permission denied" when
the maillog_file parameter specified a filename and Postfix was not
running. This was fixed by opening the maillog_file before dropping root
privileges. Found during code maintenance.
Bugfix (defect introduced Postfix 3.0). No autodetection of UTF8 text when
missing message headers were automatically added by Postfix (for example,
a From: header with UTF8 full name information from the password file).
This caused Postfix to send UTF8 in message headers without using the
SMTPUTF8 protocol. Problem reported by Michael Tokarev.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/postfix | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2024 IPFire Team <info@ipfire.org> #
+# Copyright (C) 2007-2025 IPFire Team <info@ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -26,7 +26,7 @@ include Config
SUMMARY = A fast, secure, and flexible mailer
-VER = 3.9.0
+VER = 3.9.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 = 45
+PAK_VER = 46
DEPS =
@@ -70,7 +70,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = e07a525d9cbea43d3ed11f3d672452cf94f88ca7bbaf3c3254bf5be4ef675a1797a5fff2444c0db60c6eb53e43734a388a91faed72bb2fb4e3e5a353535602b0
+$(DL_FILE)_BLAKE2 = 78be7bf0f0d9e46429b40f98ddc98cac442cfdb404d77073346c973f3d0d4c52f299fc7f5d64bddaaf2db60dd234c52790f1efe4995faee8e2cd10c6f8e2096f
install : $(TARGET)