chroot in master.cf should not depend on default values

[jahlives]

• Modoboa: 1.15.0
• installer used: Yes

looks to me that there is a potential issue with postfix depending on OS used and Postfix version. Postfix 2.10 has a default value for chroot YES whereas postfix from 3 onwards uses default NO (see postfix manpage).
The master.cf does not specify a value for chroot so default is used. The problem arises if the OS does not properly setup the chroot environment. We were affected on Centos7.
Our name resolution did not work at all. After setting chroot to NO (n) in master.cf the resolution worked.
Found that the chroot-update script from centos has issues described here and therefore does not copy all necessary files (mostly libfiles) into the chroot dir.

imho the master.cf configuration should always specify a value for chroot of a service and not depend on default values which may change at any update

[tonioo]

@jahlives Maybe adding an option to the installer could be a good solution? (either to chroot or not)

[jahlives]

@tonioo think an installer option should do it (make it default to no). Maybe as a plus: verify that chroot environment is okay, although could be hard to determine that from outside of postfix