Bug 46895 - Postfix version compatibility level
Postfix version compatibility level
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Mail
UCS 4.3
Other Linux
: P5 minor (vote)
: UCS 4.4-7-errata
Assigned To: Toni Röhmeyer
Tobias Wenzel
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-26 14:04 CEST by Moritz Bunkus
Modified: 2021-01-06 16:53 CET (History)
5 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Bunkus 2018-04-26 14:04:55 CEST
Hey,

Postfix on UCS 4.3 emits a warning about backwards compatibility when its configuration is reloaded:

$ postfix reload
postfix: Postfix is running with backwards-compatible default settings
postfix: See http://www.postfix.org/COMPATIBILITY_README.html for details
postfix: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"
postfix/postfix-script: refreshing the Postfix mail system

As far as I can see the default settings used by UCS aren't affected by bumping the compatibility_level setting to 2 (and if they are those settings should be made explicit by adding them to the configuration). Therefore "compatibility_level=2" should probably be added to the main.cf templates.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2018-04-26 14:44:23 CEST
From Bug 45963c1:

> Postfix 3 has a "Backwards-Compatibility Safety Net" 
> (http://www.postfix.org/COMPATIBILITY_README.html) which is activated.
> All listed configuration options are now set explicitly, but the compatibility 
> mode has not been deactivated, because users might set custom options in their 
> main.cf.local file.
> If a customer wishes, the compatibility-mode can be deactivated with 
> "compatibility_level=3" in main.cf.local.

I think, with UCS 4.3-1, we can change the default to compat level 3.
Comment 2 Toni Röhmeyer univentionstaff 2020-09-10 12:07:50 CEST
I checked again the default settings on compatibility_level 2 and 3.
It still seems that they are unaffected by the change.

So I set the default compatibility_level=3 in the main.cf templates.


commit 1d274d0ea2937b75134f2509cde78be77a7de67a
Bug #46895: set compatibility_level=3

on branch troehmey/bug46895_postfix_compatibility_level.
Comment 3 Tobias Wenzel univentionstaff 2020-11-30 09:23:23 CET
QA → All OK → Reopen for merge and build

Thanks for the fix, this was getting annoying :)
Comment 4 Toni Röhmeyer univentionstaff 2020-12-09 12:04:38 CET
Merged to 4.4-7 with:

4d83f2691a Bug #46895: added yaml
2e7a84762a Bug #46895: added changelog entry
baf65a6b46 Bug #46895: Merge branch 'troehmey/bug46895_postfix_compatibility_level_v2' into 4.4-7
465fde1ee6 Bug #46895: set compatibility_level=3

(I created a new branch troehmey/bug46895_postfix_compatibility_level_v2 which was up to date with 4.4-7 and cherry picked the commit from comment #2 in order to avoid merge conflicts.)


Successful build:

Package: univention-mail-postfix
Version: 13.0.4-2A~4.4.0.202012091157
Branch: ucs_4.4-0
Scope: errata4.4-7
Comment 5 Tobias Wenzel univentionstaff 2020-12-09 15:55:54 CET
QA → All OK → VERIFY

Yaml → OK
Changelog → I added a "Bug #46895" in the changelog → OK
Merge → OK
Comment 6 Florian Best univentionstaff 2020-12-09 23:09:55 CET
REOPEN: no merge request for UCS 5 is done
REOPEN: no target milestone is set
Comment 7 Toni Röhmeyer univentionstaff 2020-12-15 09:30:26 CET
Target milestone has been set.

Merge request (from a new branch "troehmey/bug46895-ucs5") for UCS5 is here:
https://git.knut.univention.de/univention/ucs/-/merge_requests/52