>
> Check the multi_instance name setting in themain.cf file of the
> affected instance.
>
> Was this instance created from scratch with postmulti, or was this
> imported as an already existing instance?
>
> I do not recall why the instance name is needed, that was designed
> in 2009.
>
> Wietse
Wietse Venema:
> Laura Smith:
> > I'm on Postfix 3.4.10 and the following is driving me nuts:
>
> Wietse:
> > > You're running some commands with sudo and some without. Because
> > > of that, environment variables and command aliases may differ.
> > >
> > > In particular:
> > >
> > > PATH determin
Laura Smith:
> I'm on Postfix 3.4.10 and the following is driving me nuts:
Wietse:
> > You're running some commands with sudo and some without. Because
> > of that, environment variables and command aliases may differ.
> >
> > In particular:
> >
> > PATH determines where the postmulti command is f
e running some commands with sudo and some without. Because
> of that, environment variables and command aliases may differ.
>
> In particular:
>
> PATH determines where the postmulti command is found.
>
> MAIL_CONFIG determines what main.cf file it will use.
>
> and
Wietse
> $ sudo postmulti -i postfix-authrelay -p reload
> postmulti: fatal: No matching instances
>
> $ sudo postmulti -i postfix-inetgen -p reload
> postfix-inetgen/postfix-script: refreshing the Postfix mail system
>
> $ sudo postmulti -g mta -p reload
> postfix-inetgen/po
ay -p reload
postmulti: fatal: No matching instances
$ sudo postmulti -i postfix-inetgen -p reload
postfix-inetgen/postfix-script: refreshing the Postfix mail system
$ sudo postmulti -g mta -p reload
postfix-inetgen/postfix-script: refreshing the Postfix mail system
Am I missing somemthing stu
