front-end (satic IP) --> zimbra (dynamic IP) possible?

[sjorge]

Hi

I wonder if it's possible to do something like:

[main server]
ip = static
services:
- httpd
- ftp
- ...

[zimbra server]
ip = dynamic, behind router so NAT
services:
- zimbra


incomming:
main (postfix) --> *@example.org,*@example.com --> zimbra (which handles spam, mailboxes,...)

outgoing:
zimbra --> main

Is this possible? if so how does this work DNS wise?

currently I have example.org has a MX pointing to mail.example.org.
(which currently resolves to the same IP as Example Web Page)

so I want to point mail.example.org to my zimbra server at the office (via cname to my dyndns account).

Will this work? what do I need to do at the zimbra end config and dns wise?

I want the mail to be buffered on the main server incase the one in the office goes down and send once it's back.

I know I'm asking a lot here but the information i can find seems to say it's possible but it's very very confusing.

I haven't done any install yet for the zimbra server.
It will either be a chroot on my gentoo server or a domU on out main server.

So I'm open for sugestions even on which distro to use.

Thanks in advance for any help info.

some extra information:
So far i've used kerio mail server but my companies license is expiring and it's way to expensive we have around 8 active users.

I've no prior experience with zimbra or postfix.

[uxbod]

Welcome to the forums

As your ZCS server will be behind a firewall/router on NAT then you will need to setup a Wiki :: Split DNS architecture.

[Tripple]

Originally Posted by sjorge

[main server]
ip = static
services:
- httpd
- ftp
- ...

[zimbra server]
ip = dynamic, behind router so NAT
services:
- zimbra

incomming:
main (postfix) --> *@example.org,*@example.com --> zimbra (which handles spam, mailboxes,...)

outgoing:
zimbra --> main

How does your network setup looks like?
Do you have a static IP on the WAN side and servers on the LAN side?
Is your webserver with static IP in the same location as your Zimbra server?

[uxbod]

[zimbra server]
ip = dynamic, behind router so NAT
services:
- zimbra

so the OP will need to have a Split DNS as mentioned in my original post.

[Tripple]

Originally Posted by uxbod

so the OP will need to have a Split DNS as mentioned in my original post.

I'm behind a NAT. It works for me without split DNS. All I have to do is forward port 25 and 443 to the Zimbra server. I'm receiving mail so I guess this works fine.

This setup is receiving mail for years but Zimbra is new to me. I'm using it for about 2 weeks now.

[sjorge]

@usbox: Split DNS seems to be a step in the right direction.
I'll read the entire article tomorrow once I'm fresh again

@Tripple:
main server is a VPS that's located in germany. (and has a static IP)
zimbra server will be a local server in the LAN, the WAN side at the office sadly doesn't have a static IP. It changes every... 24-48h.

so all mail shall be passing through the VPS and should be cache in case the zimbra server is offline (it shouldn't but you never know).

But I want to do the webmail, spam filtering etc on the zimbra server.

The split DNS should solve the problems of being NAT but from skim reading the article it doesn't seem to make it so that mail is first buffered at the main server for safety.

Hopefully I'm not trying to bite of more than I can chew.

[Tripple]

To my knowledge, it's not recommended to use a mailserver on a dynamic IP.

Long time ago I was using the same configuration. I used Fetchmail to get mail to my local server.

[sjorge]

That's exactly why I want a lightweight postfix on the main server with a static IP to be the one exposed. So it will appear as a static server.

Sort of like a PO box, in this case the main server. And have an internal secretary (the local zimbra server) redistribute it internally, collect the mail and drop it off at the PO box again so the postman can pick it up.

Sorry for using crappy terminology but it's easiest to describe what I want like this.

[Tripple]

Did you take a look at Fetchmail?

[sjorge]

Yes, that seems to solve part of the problem.

Now I just need to configure postfix on the main server. Hopefully I'll get this working seem to have most info I need now! Thanks.