On Wed, Feb 09, 2022 at 06:00:59PM +0530, Nitin N wrote: > On Wed, 9 Feb 2022, 4:44 pm Bastian Blank, <bastian+postfix-users= > postfix....@waldi.eu.org> wrote: > > > On Wed, Feb 09, 2022 at 12:45:21PM +0530, Nitin N wrote: > > > I checked out master_service_disable at here > > > <http://www.postfix.org/postconf.5.html#master_service_disable> but I > > > am a bit uncertain of how I should use it.
You're supposed to turn it off when ready: MULTI_INSTANCE_README: ... Setting up the "output" Postfix instance ... Then create the output instance: # postmulti -I postfix-out -G mta -e create ... The new instance will be created in a "disabled" state: /etc/postfix-out/main.cf # # ... "stock" main.cf settings ... # multi_instance_name = postfix-out queue_directory = /var/spool/postfix-out data_directory = /var/lib/postfix-out # multi_instance_enable = no master_service_disable = inet authorized_submit_users = Sice "postmulti" has no idea which IP addresses (if any) you'll want to assign to the new instance, and because at most one instance can use a given IP:port combination (and 0.0.0.0:port excludes all other uses of the port), new instances have all IP listeners disabled. After instructions to complete configuring the instance, including setting explicit "inet_interfaces", the documentation goes on to say: With the "output" configuration in place, enable and start the instance: 1 # postmulti -i postfix-out -x postconf -e \ ---> 2 "master_service_disable =" "authorized_submit_users = root" 3 # postmulti -i postfix-out -e enable 4 # postmulti -i postfix-out -p start > > Well. Did you understand what it does? > > Yes from the nullclient point of view yes I have understood as its > relaying and hence doesn't require services from its master.cf to be > started. > > I am not sure why if at all I should be disabling it in the main.cf of the > other instances. I haven't understood that part. Well, if you leave "inet" services disabled, naturally you get no TCP listeners running. -- Viktor.