A company has two office locations in different cities. The first location has around 2000 mailboxes on Zimbra with a Multiserver setup of one Proxy/LDAP/MTA and two Mailbox/MTA server. I think this a standard setup that many users here familiar with. The second location has around 500 mailboxes on Exchange and they will move to Zimbra (one Domain, like @example.com).
Create the accounts on the Zimbra setup in the first location
- Easy to implement
- second location has only 10 MBit connection to the Internet -> bad user experience
Add Zimbra server in second locations with Proxy/MTA/LDAP/Mailbox on it (all mails to and from external accounts will be routed via 10 MBit/s to the MTA server of location one (this is the main MX-Server in the DNS), all mails to other Zimbra-User will be either delivered locally or through 10 MBit/s to the Zimbra setup in location one. There is a VPN between the two office locations).
- good performance for users in the second locations
- saved bandwidth
- more administration work
- more sophisticated setup
What do you think? I have seen a similar setup in a blog post from Mozilla (especially the last image). The users in the second office will connect to there Zimbra server with a different URL (first location mail.example.com (reachable from internal and external networks), second location mail.ber.example.com (from network of second location directly, from any other network (external or first location) they are going to mail.example.com proxy and will be routed via Zimbra proxy to the mailbox server in the second location through the VPN). The difference between my idea and the setup from Mozilla is: I want only one point of Internet connection (first location). All incoming/outgoing mails and also all external access to Web Client will be going to first location and if needed redirected to mailbox server in the second location accessble via mail.example.com and mail.ber.example.com.
Thanks for your replies,