64beefdf8e
Accepting request 1328660 from server:mail
Ana Guerrero2026-01-23 16:31:48 +00:00
d226bdcd77
Accepting request 1328660 from server:mail
Ana Guerrero2026-01-23 16:31:48 +00:00
e9b9e10966
- also drop " -s " from the CCARGS to prevent stripping there - also drop " -s " from the CCARGS to prevent stripping there
Marcus Rueckert2026-01-22 11:10:32 +00:00
c1cf3ad407
- also drop " -s " from the CCARGS to prevent stripping there - also drop " -s " from the CCARGS to prevent stripping there
Marcus Rueckert2026-01-22 11:10:32 +00:00
98e8e29d85
- Don't fail strip on non-existing files (easy hack to fix 32bit builds).
Dominique Leuenberger2026-01-21 07:51:19 +00:00
efa27a0044
- fix (bsc#1256462) [Build 12.10] openQA test fails in mta: Failed to start postfix.service Remove postfix set-permisson from all spaces - Strip binaries
Peter Varkoly2026-01-20 20:23:32 +00:00
fb8d0d55dd
- fix (bsc#1256462) [Build 12.10] openQA test fails in mta: Failed to start postfix.service Remove postfix set-permisson from all spaces - Strip binaries
Peter Varkoly2026-01-20 20:23:32 +00:00
970adada74
Add README.md Remove postfix set-permissions to avoid security issues.
Peter Varkoly2026-01-15 18:56:10 +01:00
f412734954
Accepting request 1327227 from server:mail
Ana Guerrero2026-01-14 15:19:28 +00:00
78d8198753
Accepting request 1327227 from server:mail
Ana Guerrero2026-01-14 15:19:28 +00:00
fe62243a9c
- fix (bsc#1256462) [Build 12.10] openQA test fails in mta: Failed to start postfix.service Put postfix set-permisson into %post
Peter Varkoly2026-01-14 14:39:02 +00:00
933be084e3
- fix (bsc#1256462) [Build 12.10] openQA test fails in mta: Failed to start postfix.service Put postfix set-permisson into %post
Peter Varkoly2026-01-14 14:39:02 +00:00
c80ebd392c
- fix (bsc#1256462) [Build 12.10] openQA test fails in mta: Failed to start postfix.service Put postfix set-permisson into %post
Peter Varkoly2026-01-13 21:57:16 +00:00
2bfcd4faf0
- fix (bsc#1256462) [Build 12.10] openQA test fails in mta: Failed to start postfix.service Put postfix set-permisson into %post
Peter Varkoly2026-01-13 21:57:16 +00:00
0ef40347d7
- fix (bsc#1256462) [Build 12.10] openQA test fails in mta: Failed to start postfix.service Put postfix set-permisson into %post
Peter Varkoly2026-01-13 20:29:20 +00:00
5a4ab1d1fb
- fix (bsc#1256462) [Build 12.10] openQA test fails in mta: Failed to start postfix.service Put postfix set-permisson into %post
Peter Varkoly2026-01-13 20:29:20 +00:00
7570232dd5
- (jsc#PED-14859) Fix packages for Immutable Mode - postfix
Peter Varkoly2025-12-21 20:53:52 +00:00
811af81a5d
- (jsc#PED-14859) Fix packages for Immutable Mode - postfix
Peter Varkoly2025-12-21 20:53:52 +00:00
75cccd4aa2
- Put /etc/permissions.d/postfix.paranoid into the postfix-SUSE.tar.gz
Peter Varkoly2025-12-14 18:47:38 +00:00
aac4c2d1c3
- Put /etc/permissions.d/postfix.paranoid into the postfix-SUSE.tar.gz
Peter Varkoly2025-12-14 18:47:38 +00:00
586fe82787
- fix postfix-SUSE.tar.gz, postfix.service: correct path for postalias from /sbin/postalias to /usr/sbin/postalias
Peter Varkoly2025-12-14 18:30:47 +00:00
45c87c725f
Accepting request 1322209 from home:jsjhb:branches:server:mail
Peter Varkoly2025-12-14 18:30:47 +00:00
70205cb7cb
- update to 3.10.7 * This patch addresses build errors on recent Linux distributions. With the patch, Postfix builds will run the compiler with a backwards compatibility option that is supported by Gcc and Clang. For other compilers, an error message provides hints.
Peter Varkoly2025-12-11 11:28:06 +00:00
11cfe0e42f
Accepting request 1322077 from home:adkorte:branches:server:mail
Peter Varkoly2025-12-11 11:28:06 +00:00
7e07dc866e
- Add /var/spool/mail to the permissions.d drop-in. This directory used to be whitelisted globally in the permissions package but an update for the exim mail server changed that (bsc#1254597 bsc#1240755). - Reintroduce permissions.d/postfix-paranoid drop-in that was removed in r534.
Peter Varkoly2025-12-10 16:00:17 +00:00
d666620037
Accepting request 1321984 from home:wfrisch:branches:server:mail
Peter Varkoly2025-12-10 16:00:17 +00:00
a137672f6f
- postfix is unable to send mail by default (bsc#1253775) o Clean up the package * Get rid of config.postfix script to avoid unintentional changes of the configuration. The sysconfig files mail and postfix were removed also. * Deliver the original main.cf and master.cf * Remove a lot of deprecated stuff from the package. * Remove the ExecStartPre scripts to maintain the postmaps and the chroot environment. * A new ExecStartPre script manages the default alias map which is part of the default configuration of postfix. /sbin/postalias /etc/aliases * Do not use the permissions framework. A new ExecStartPre script takes care of the right permissions: /usr/sbin/postfix set-permissions * Remove mkpostfixcert
Peter Varkoly2025-12-08 10:58:57 +00:00
b125830120
Accepting request 1321316 from home:varkoly:branches:server:mail
Peter Varkoly2025-12-08 10:58:57 +00:00
f53a873cf3
Accepting request 1320355 from server:mail
Ana Guerrero2025-11-28 15:50:43 +00:00
e4dadb5000
Accepting request 1320355 from server:mail
Ana Guerrero2025-11-28 15:50:43 +00:00
c2aec40fd6
Accepting request 1320246 from home:adkorte:branches:server:mail
Peter Varkoly2025-11-27 15:56:38 +00:00
b6d140c55b
- update to 3.10.6 * Bugfix (defect introduced: Postfix 3.10, date: 20250117). Symptom: warning messages that smtp_tls_wrappermode requires "smtp_tls_security_level = encrypt". Root cause: support for "TLS-Required: no" broke client-side TLS wrappermode support, by downgrading a connection to TLS security level 'may'. The fix changes the downgrade level for wrappermode connections to 'encrypt'. Rationale: by design, TLS can be optional only for connections that use STARTTLS. The downgrade to unauthenticated 'encrypt' allows a sender to avoid an email delivery problem. Problem reported by Joshua Tyler Cochran. * New logging: the Postfix SMTP client will log a warning when an MX hostname does not match STS policy MX patterns, with "smtp_tls_enforce_sts_mx_patterns = yes" in Postfix, and with TLSRPT support enabled in a TLS policy plugin. It will log a successful match only when verbose logging is enabled. * Bugfix (defect introduced: Postfix 3.10, date: 20240902): SMTP client null pointer crash when an STS policy plugin sends no policy_string or no mx_pattern attributes. This can happen only during tests with a fake STS plugin. * Bugfix (defect introduced: Postfix 2.9, date: 20120307): segfault when a duplicate parameter name is given to "postconf -X" or "postconf -#'. * Documentation: removed incorrect text from the parameter description for smtp_cname_overrides_servername. File: proto/postconf.proto. - update to 3.10.6 * Bugfix (defect introduced: Postfix 3.10, date: 20250117). Symptom: warning messages that smtp_tls_wrappermode requires "smtp_tls_security_level = encrypt". Root cause: support for "TLS-Required: no" broke client-side TLS wrappermode support, by downgrading a connection to TLS security level 'may'. The fix changes the downgrade level for wrappermode connections to 'encrypt'. Rationale: by design, TLS can be optional only for connections that use STARTTLS. The downgrade to unauthenticated 'encrypt' allows a sender to avoid an email delivery problem. Problem reported by Joshua Tyler Cochran. * New logging: the Postfix SMTP client will log a warning when an MX hostname does not match STS policy MX patterns, with "smtp_tls_enforce_sts_mx_patterns = yes" in Postfix, and with TLSRPT support enabled in a TLS policy plugin. It will log a successful match only when verbose logging is enabled. * Bugfix (defect introduced: Postfix 3.10, date: 20240902): SMTP client null pointer crash when an STS policy plugin sends no policy_string or no mx_pattern attributes. This can happen only during tests with a fake STS plugin. * Bugfix (defect introduced: Postfix 2.9, date: 20120307): segfault when a duplicate parameter name is given to "postconf -X" or "postconf -#'. * Documentation: removed incorrect text from the parameter description for smtp_cname_overrides_servername. File: proto/postconf.proto.
Peter Varkoly2025-11-27 15:56:38 +00:00
04a2d27eb3
Accepting request 1319697 from server:mail
Ana Guerrero2025-11-25 14:52:00 +00:00
5a7ffca241
Accepting request 1319697 from server:mail
Ana Guerrero2025-11-25 14:52:00 +00:00
649c913733
Accepting request 1317429 from home:adkorte:branches:server:mail
Peter Varkoly2025-11-24 10:11:12 +00:00
c996d2b3fa
- update to 3.10.5 * Workaround for an interface mis-match between the Postfix SMTP client and MTA-STS policy plugins. * The existing behavior is to connect to any MX host listed in DNS, and to match the server certificate against any STS policy MX host pattern. * The corrected behavior is to connect to an MX host only if its name matches any STS policy MX host pattern, and to match the server certificate against the MX hostname. The corrected behavior must be enabled in two places: in Postfix with a new parameter "smtp_tls_enforce_sts_mx_patterns" (default: "yes") and in an MTA-STS plugin by enabling TLSRPT support, so that the plugin forwards STS policy attributes to Postfix. This works even if Postfix TLSRPT support is disabled at build time or at runtime. * TLSRPT Workaround: when a TLSRPT policy-type value is "no-policy-found", pretend that the TLSRPT policy domain value is equal to the recipient domain. This ignores that different policy types (TLSA, STS) use different policy domains. But this is what Microsoft does, and therefore, what other tools expect. * Bugfix (defect introduced: Postfix 3.0): the Postfix SMTP client's connection reuse logic did not distinguish between sessions that require SMTPUTF8 support, and sessions that do not. The solution is 1) to store sessions with different SMTPUTF8 requirements under distinct connection cache storage keys, and 2) to not cache a connection when SMTPUTF8 is required but the server does not support that feature. * Bugfix (defect introduced: Postfix 3.0, date 20140731): the smtpd 'disconnect' command statistics did not count commands with "bad syntax" and "bad UTF-8 syntax" errors. * Bugfix: the August 2025 patch broke DBM library support which is still needed on Solaris; and the same change could result in warnings with "database X is older than source file Y". * Postfix 3.11 forward compatibility: to avoid ugly warnings when Postfix 3.11 is rolled back to an older version, allow a preliminary 'size' record in maildrop queue files created with Postfix 3.11 or later. * Bugfix (defect introduced: Postfix 3.8, date 20220128): non-reproducible build, because the 'postconf -e' output order for new main.cf entries was no longer deterministic. Problem reported by Oleksandr Natalenko, diagnosis by Eray Aslan. * To make builds predictable, add missing meta_directory and shlib_directory settings to the stock main.cf file. Problem diagnosed by Eray Aslan. * Bugfix (defect introduced: Postfix 3.9, date 20230517): posttls-finger(1) logged an incorrectly-formatted port number. Viktor Dukhovni. - rebase postfix-bdb-main.cf.patch - adapt rpmlint o dir-or-file-outside-snapshot
Peter Varkoly2025-11-24 10:11:12 +00:00
dc948e18ca
Accepting request 1302032 from server:mail
Ana Guerrero2025-09-01 15:16:44 +00:00
6e9f9fb39d
Accepting request 1302032 from server:mail
Ana Guerrero2025-09-01 15:16:44 +00:00
807e89e8cb
Accepting request 1300344 from home:adkorte:branches:server:mail
Peter Varkoly2025-08-30 17:43:47 +00:00
0f4d618a6b
Accepting request 1300344 from home:adkorte:branches:server:mail
Peter Varkoly2025-08-30 17:43:47 +00:00
cd36f2a29e
Accepting request 1297328 from home:adkorte:branches:server:mail
Peter Varkoly2025-08-07 18:51:15 +00:00
682d6d2595
- update to 3.10.3 * 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.
Peter Varkoly2025-08-07 18:51:15 +00:00
9daebae2dc
Accepting request 1282030 from server:mail
Ana Guerrero2025-06-03 15:51:10 +00:00
Dominique Leuenberger
Peter Varkoly
Ana Guerrero
OBS User buildservice-autocommit
Marcus Rueckert