Futchko, Rose:
> Good Afternoon. This is to confirm that the information located at
> http://www.postfix.org/MULTI_INSTANCE_README.html#quick is the right
> documentation to setup a multi-instance of Postfix within the following
> environment:
MULTI_INSTANCE_README describes multiple MTAs that run on the same
operating system instance.
However, you can apply the concepts of null client (no network
listener), service MTA instance, etc. equally well to MTAs running
on separate hosts.
So, you could have one null client on each host that handles local
submission by cron jobs etc., and the central server would also
have a service MTA instance that the others route their mail to.
Wietse
> A) 4 servers total, each one running a local POSTFIX instance.
> B) 3 of the servers will need to send mail from web applications (such
> as registration complete email response, request for new password, etc)
> to a central POSTFIX instance (all on the same subnet)
> C) 1 server is to be designated as a central Mail Transfer agent to the
> internet. This is for inbound and outbound mail. This server also
> supports a local copy of a mail list serve.
> D) All servers are on the same internal subnet.
>
> Server 1 (central mail transfer for web apps and mail list serve)
> POSTFIX conf currently is:
>
> alias_database = hash:/etc/aliases, hash:/etc/mailman/aliases alias_maps
> = hash:/etc/aliases, hash:/etc/mailman/aliases command_directory =
> /usr/sbin config_directory = /etc/postfix daemon_directory =
> /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level
> = 2 html_directory = no inet_protocols = all local_recipient_maps =
> unix:passwd.byname $alias_maps mailq_path = /usr/bin/mailq.postfix
> manpage_directory = /usr/share/man mydestination = $myhostname,
> list.$mydomain, localhost.$mydomain mydomain = informs.org myhostname =
> mail.informs.org myorigin = $myhostname newaliases_path =
> /usr/bin/newaliases.postfix readme_directory =
> /usr/share/doc/postfix-2.6.6/README_FILES
> recipient_delimiter = +
> sample_directory = /usr/share/doc/postfix-2.6.6/samples
> sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop
> smtpd_recipient_restrictions = permit_mynetworks
> reject_unauth_destination unknown_local_recipient_reject_code = 550
>
>
> Server 2-4 (web application email services) current postconf -n output.
> The desire is to send mail to the internet through Server 1 (MTA)
>
> alias_database = hash:/etc/aliases
> alias_maps = hash:/etc/aliases
> command_directory = /usr/sbin
> config_directory = /etc/postfix
> daemon_directory = /usr/libexec/postfix
> data_directory = /var/lib/postfix
> debug_peer_level = 2
> html_directory = no
> inet_interfaces = all
> inet_protocols = all
> mail_owner = postfix
> mailq_path = /usr/bin/mailq.postfix
> manpage_directory = /usr/share/man
> mydestination = $myhostname, localhost.$mydomain, localhost mydomain =
> or-exchange.com myhostname = mail.or-exchange.com myorigin = $mydomain
> newaliases_path = /usr/bin/newaliases.postfix queue_directory =
> /var/spool/postfix readme_directory =
> /usr/share/doc/postfix-2.6.6/README_FILES
> relayhost = mail.informs.org
> sample_directory = /usr/share/doc/postfix-2.6.6/samples
> sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop
> unknown_local_recipient_reject_code = 550
>
> Question(s):
> A) Is 'managing multiple postfix documentation on a single host' the
> correct way to achieve the central MTA from multiple hosts?
> B) If this is not the correct way, what is the recommended way to
> establish the central MTA to support multiple hosts? Each host will have
> its own POSTFIX install?
>
> Thank you,
> Rose
