On 3/4/26 12:17 AM, Michael Tokarev wrote:
I verified upgrades from various different versions of postfix package, and the upgrade definitely adds this configuration item. A lot of users with cyrus sasl upgraded their systems flawlessly. Just yesterday I upgraded another bookworm system to trixie, including postfix, and the procedure added cyrus_sasl_config_path = /etc/postfix/sasl to main.cf, even if I don't use cyrus or sasl in general. So this should be something on your system which breaks this workaround.
I maintain main.cf as a template in ansible. So I need to make this change manually to the configuration file. This would be the case for people using configuration management tools like ansible.
After postfix was updated, I have applied the main.cf in my ansible templates which removed this entry. I later found it out by comparing the postconf output on a freshly installed system.
Please find out what's different on your system. Which was the version of postfix you're upgrading from? There's definitely no reason to add news entries saying upgrade will break your system if it doesn't happen for everyone else.
As I said, it will break anyone using a configuration management system like ansible as they need to make this change in their template configuration as well. So I think it deserves a mention in the NEWS file.
Also, it's a bad habit to hijack an old bug report which talks about a version which were many debian releases ago - it's unlikely to be the same issue.
I have seen people recommending to check existing issues and comment on them rather than opening new issues.
Thanks, /mjt
OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
