> On Mar 8, 2017, at 9:03 AM, Mario Theodoridis <mario.theodori...@regify.com>
> wrote:
>
> /usr/sbin/postfix set-permissions upgrade-configuration \
> config_directory=/etc/postfix \
> daemon_directory=/usr/libexec/postfix \
> command_directory=/usr/sbin \
> mail_owner=postfix \
> setgid_group=postdrop \
> manpage_directory=/usr/share/man \
> sample_directory=/usr/share/doc/postfix-2.6.6/samples \
> readme_directory=/usr/share/doc/postfix-2.6.6/README_FILES &> /dev/null
The problem is with the explicit "config_directory=/etc/postfix" setting.
This is used in combination with each instance, which results in the
default instance's files being edited instead of the files for the
instance in question.
I can reproduce the problem outcome you reported with Postfix 3.1.4
on FreeBSD.
# postmulti -e init
# postmulti -e create -I postfix-foo
# postfix set-permissions upgrade-configuration
"config_directory=/usr/local/etc/postfix"
# postmulti -l
postmulti: fatal: instance /usr/local/etc/postfix-foo,
queue_directory=/var/spool/postfix-foo conflicts with instance
/usr/local/etc/postfix, queue_directory=/var/spool/postfix-foo
This particular command does exactly what it is told, but probably
Postfix should have special logic to handle "config_directory" in
this and similar cases.
--
Viktor.
