Zimbra Collaboration Suite 7.0
Zimbra Collaboration Suite 7.0
Administrator's Guide
Open Source Edition


Product Overview > Example of a Typical Multi-Server Configuration

Example of a Typical Multi-Server Configuration
The exact configuration for each deployment is highly dependent on variables including the number of mailboxes, mailbox quotas, performance requirements, existing network infrastructure, IT policies, security methodologies, spam filtering requirements, and so forth.
Figure  shows a typical configuration with incoming traffic and user connection. Alternate ways of configuring at many points within the network are possible.
Typical Configuration with Incoming Traffic and User Connections
Explanation of Figure  follows:
 
An external user connecting to the messaging server also goes through a firewall to the second load balancer.
The designated Zimbra MTA server looks up the addressee’s directory information from the Zimbra LDAP replica server.
After obtaining the user’s information from the Zimbra LDAP server, the MTA server sends the mail to the appropriate Zimbra server.
Internal end-user connections are made directly to any Zimbra server which then obtains the user’s directory information from Zimbra LDAP and redirects the user as needed.