Hi,

I plan to host mail for 3 domains,

  mynet1.net
  mynet2.net
  mynet3.net

and have SSL certs for each domain.

I have 2 servers -- one hosted with StaticIPs facing the 'net, the other
behind a dynamic IP on my LAN.

the two MX for each of my mail domains point at the two static IPs on
the hosted server:

  A   mx1.mydomain.net 1.1.1.1      A   mx2.mydomain.net 2.2.2.2
  PTR 1.1.1.1 mx1.mydomain.net      PRT 2.2.2.2 mx2.mydomain.net

On my LAN server, with lots of RAM, disk & CPU, I hope to run 'full'
Zimbra, with all of its collaboration tools (calendar, contacts, etc).

On the hosted server (not a lot of RAM/CPU), I want to set up a
lightweight, low-maintenance Postfix to:
(1) listen at the two StaticIPs for all/only the three domains
(2) negotiate TLS/SSL correctly for each accepting domain
(3) virus & spam scan incoming mail from one set of rules
(4)
        (a) if the Zimbra server is accessible,
                deliver/forward accepted mail to Zimbra's postfix on my
                LAN for further processing and IMAP storage
        (b) if the Zimbra server is offline,
                store/queue the messages locally on the hosted server
                for later delivery a.s.a.p.

I've read most of the "Postfix: The Definitive Guide", and a bunch
online.  I'm still a bit green/confused, but I'm pretty sure all of the
pieces involved in this CAN be done.

My question is what's the 'best practice' way to do it all together?

In particular, for a start --

-- should I run ONE or TWO instances of postfix on the Hosted Server?
-- with my A/PTR records != the hosted mail domains, how do I ensure the
right TLS/SSL cert gets presented for a given domain?
-- how, exactly, do I setup the store/forward capability?  Custom
scripts? POP servers? other?

Some experience/guidance would be a big help!

DChil

Reply via email to