----- Message from Simon Wilson <si...@simonandkate.net> ---------
Date: Fri, 19 Mar 2021 13:40:11 +1000
From: Simon Wilson <si...@simonandkate.net>
Reply-To: si...@simonandkate.net
Subject: upgrade 2.10 - 3.3 config compatibility
To: postfix-users@postfix.org
I have a well established 2.10 Postfix instance on 2.10 (CentOS7)
which is to be migrated to a new machine running Postfix 3.3 (on
RHEL8).
I've been reading http://www.postfix.org/COMPATIBILITY_README.html,
and from what I can see the backward compatibility issues I may run
into are (with existing config from 2.10)
- append_dot_mydomain (not explicitly set on 2.10, i.e. implicitly "yes")
- chroot (explicitly set to n on 2.10 in master.cf)
- smtpd_relay_restrictions (explicitly set to empty on 2.10)
- mynetworks_style (not explicitly set on 2.10, i.e. implicitly "subnet")
- relay_domains (not explicitly set on 2.10, i.e. implicitly
"$mydestination")
To re-use the existing configuration I'm thinking I need to:
1. explicitly set append_dot_mydomain to yes
2. explicitly set mynetworks_style to subnet (2.10 config =
"mynetworks = 127.0.0.0/8, 192.168.1.0/24")
3. explicitly set relay_domains=$mydestination
If I do those should I explicitly set compatibility_level, or would
it not be needed because I have addressed the compatibility issues?
And are there any other 'gotchas' to be aware of with this upgrade?
Thank you kindly.
Simon
---- End message from Simon Wilson <si...@simonandkate.net> -----
Ok, I migrated the config from the 2.10 server, and added new specific
configuration items for:
append_dot_mydomain = yes
mynetworks_style = subnet
relay_domains = $mydestination
With those set, all services in master.cf explicitly chroot=n, and
compatibility_level set to 99, I migrated onto Postfix 3.3. I had a
few minor hiccups with other bits (like a typo trying to run the spf
policy) but the Postfix part of the migration has swung straight over
and not missed a beat.
Thanks
Simon.
--
Simon Wilson
M: 0400 12 11 16
