Univention Bugzilla – Bug 45963
postfix main.cf and init script needs to be adjusted for UCS 4.3
Last modified: 2018-06-04 08:29:43 CEST
In UCS 4.3 postfix doesn't start because the old init script and the old main.cf is used - which is incompatible with the new version. All mail tests are failing therefore because port 25 is closed.
Fixed a test: 3adf67eb: handle not-returning openssl call Package: ucs-test Version: 8.0.7-2A~4.3.0.201801021618 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. 7ddb47aa: adapt configuration and init script to stretch c625a0dd: changelog 114bddc3: update copyright univention-mail-postfix 12.0.0-3A~4.3.0.201801021556
[4.3-0 871e5bda15] Bug #45963: add missing UCR declaration univention-mail-postfix 12.0.0-4A~4.3.0.201801021805
Apparently the Postfix config parser doesn't support comments behind values. c626d1e5: fix config c19454bf: changelog univention-mail-postfix 12.0.0-5A~4.3.0.201801030919
Apparently the init script checks the master.cf if it needs to maintain the chroot environment, and the backwards compatibility settings make "-" to "y". I set it to be explicitly "y" (partially reverting 7ddb47aa), so when a user would set the compatibility mode to "3" to get rid of the warning message, he will not end up with an unmaintained chroot. IMHO we should either disable all use of the chroot or configure all daemons to run there. 2ad1197e: force init script to maintain chroot environment univention-mail-postfix 12.0.0-6A~4.3.0.201801041244
Why have you set "mynetworks_style"? This option is only used to determine the default value of "mynetworks", but "mynetworks" is always set via the UCR template. So there is currently no change in behaviour → OK for me. root@master:~# postconf compatibility_level postconf: warning: compatibility_level: unknown parameter root@master:~# lsb_release -r Release: 4.2-3 errata284 root@master:~# postconf compatibility_level compatibility_level = 0 root@master:~# lsb_release -r Release: 4.3-0 errata0 OK: code change ??: functional test OK: release notes/changelog ??: did a small change to a ucs-test script → wait for jenkins results Fixed some UCR variable descriptions: Package: univention-mail-postfix Version: 12.0.0-13A~4.3.0.201802252224 Branch: ucs_4.3-0
(In reply to Sönke Schwardt-Krummrich from comment #5) > Why have you set "mynetworks_style"? This option is only used to determine > the default value of "mynetworks", but "mynetworks" is always set via the > UCR template. So there is currently no change in behaviour > → OK for me. Yes - it doesn't change anything of us now. But my intention was to have two things: * Make changes of configuration defaults explicit (or at least documented). * To get rid of all compatibility warnings. To achieve the latter, the first must be done: the settings that got its defaults changed must be set explicitly.
Commit "[4.3-0 ce9701a8b7] Bug #45984: don't disable connection caching on postfix' amavis port" was accidentally labeled for Bug #45984, though it was meant for this bug and should have been named "enable chroot'ing of scache service". The packages changelog was modified to reflect this with commit [4.3-0 4cbbf0a884]. Actually there was confusion as well, so another commit fixes it (no package rebuild though): [4.3-0 f4fddc0889] Bug #45963: fix changelog entry
(In reply to Sönke Schwardt-Krummrich from comment #5) > OK: code change > ??: functional test > OK: release notes/changelog > ??: did a small change to a ucs-test script → wait for jenkins results OK: functional test OK: test scripts (In reply to Daniel Tröder from comment #6) > Yes - it doesn't change anything of us now. But my intention was to have two > things: > * Make changes of configuration defaults explicit (or at least documented). > * To get rid of all compatibility warnings. > To achieve the latter, the first must be done: the settings that got its > defaults changed must be set explicitly. → OK → VERIFIED
UCS 4.3 has been released: https://docs.software-univention.de/release-notes-4.3-0-en.html https://docs.software-univention.de/release-notes-4.3-0-de.html If this error occurs again, please use "Clone This Bug".