Control: tag -1 - unreproducible moreinfo
On 03.03.2026 21:56, Pirate Praveen wrote:
...
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.
Aha, this makes sense indeed - when you remove carefully added
configuration changes aimed to keep your system running, things
will break, unless you take care of them somehow. Maybe paying
attention to `ansible-playbook -CD` output after upgrade is a
good idea too.
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.
It's always a trade-off, - as I said, you're the only one who faced this
issue so far (it's been quite a number of upgrades since trixie is out).
For the rest of users, such NEWS entry would be a useless noise.
There's already quite some differences in postfix packaging in trixie
(removal of the postfix@- unit etc). I wanted to keep it as compact as
possible. Adding this change to NEWS didn't occur to me at all, though,
because it seemed like something which I solved by editing config.
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.
Yeah. When it's the same issue.
But doesn't matter anymore. That bug was not useful anyway, 17 years
after its been filed.
/mjt
