Zimbra Mp -
The most common scenario is moving from a working Zimbra Single-Server to a full Zimbra MP infrastructure. This is known as "expanding your system."
High-level steps:
Pro Tip: For large migrations, use zmprov scripting and schedule moves during off-hours, as moving a 50GB mailbox can take time.
If a physical server melts down, only a fraction of your users are affected. And because LDAP is replicated and mail stores can be rebuilt from redundant storage or backups, the recovery is surgical rather than catastrophic. zimbra mp
Symptoms: Emails stuck in deferred queue on MTA server.
Root Cause: MTA cannot connect to the correct mailbox node (firewall, or DNS resolution failure).
Solution:
Check /var/log/zimbra.log on MTA. Look for Host not found or Connection refused. Ensure mailbox nodes are resolvable from MTA and that port 7025 (LMTP) is open.
Zimbra MP refers to the Multi-Server edition of Zimbra Collaboration (formerly Zimbra Network Edition). Unlike the Single-Server installation, where all services (Mailbox, MTA, LDAP, Proxy) run on one machine, Zimbra MP distributes these roles across multiple physical or virtual servers.
The "MP" designation explicitly indicates a deployment strategy designed for: The most common scenario is moving from a
To put it simply: if your organization has more than 500 users or cannot tolerate unexpected downtime, you need Zimbra MP.
A standard Zimbra MP deployment consists of several distinct server roles. Understanding each is critical to mastering the architecture.
Zimbra MP transforms a capable groupware platform into an enterprise-grade collaboration backbone. Yes, it’s more complex than single-server — but the gains in uptime, performance, and scalability are worth the effort. Pro Tip: For large migrations, use zmprov scripting
Start small (2 LDAP + 2 mailbox + 1 proxy/mta), document everything, and test failover scenarios before going live.
The proxy layer is what makes modern Zimbra MP seamless. Proxies handle both HTTP/HTTPS (webmail) and IMAP/POP/SMTP traffic. The proxy intelligently routes requests to the correct mailbox node without users ever needing to know which physical server houses their data.
For organizations evaluating Zimbra MP: