How Do I host some users on my old system and some on Zimbra?
Split users between Zimbra mail server and other mail server, some suggestions.
Check overall Zimbra system and service status quickly.
zmcontrol status
Use SNMP monitoring tools like Nagios or Zabbix to monitor Zimbra services, track system performance, and receive alerts for any issues or downtime.
Status & alerts
There are several third-party tools available that can help you monitor and maintain your Zimbra system. These tools provide additional features and functionality beyond what is available in the Zimbra web interface or command line interface. Some popular Zimbra monitoring tools include:
Web-based monitoring tool that provides real-time monitoring of email traffic, disk usage, and overall system health.
Commercial Zimbra version with advanced monitoring, reporting, and enterprise-level management features.
Provides access to Zimbra server status and performance data through SNMP for external monitoring tools.
Built-in alert system that notifies administrators about server issues, security threats, and performance problems in real-time.
Many businesses don’t start by thinking about systems like Zimbra. It usually comes up when something stops working, mail delays, login failures, or uncertainty around uptime. What typically happens is one issue leads to another. Monitoring becomes necessary, then access control, then backup, then overall infrastructure decisions. A simple need like checking the how-do-i-check-zimbra-status service often opens up larger questions. Where is the system hosted, who manages it, what happens if it goes down again. These are rarely isolated decisions. In practice, email systems sit close to core operations. Changes in hosting, security, or application layers tend to ripple through. Many teams end up exploring adjacent areas without planning to. That’s where having connected capabilities in place makes the process less reactive and more manageable over time.
Some teams come in when things are already stretched. Mail queues stuck, users waiting, internal pressure building. Others reach out earlier, quieter stage, just trying to avoid that situation. We’ve worked alongside internal IT teams, sometimes stepping in briefly, sometimes staying longer than expected. Different industries, different scales. Not always clean environments. There are cases where documentation didn’t exist. Or systems had been passed between vendors. It’s not unusual. A few clients prefer minimal involvement from our side. Others rely more heavily, especially during transitions. Both kinds of engagements tend to evolve. Long-term relationships don’t always start that way. Sometimes it begins with a single issue.
If your mail is crawling, the first thing you do isn't "refreshing the page"—it's hitting the CLI as the zimbra user. If mailboxd is showing as "Stopped" or "Starting," your web interface is dead. Most people panic here, but usually, it’s just a PID file that didn’t clear after a hard reboot. It costs ₹0 to fix, but if you let it sit, your ₹2 Lakh ($2,170) corporate communication flow is paralyzed. At JIL, we monitor these service states 24/7 so we can "Kick" the service before you even notice the lag.
Check the Postfix Queue. You can have "Green Lights" in the dashboard while 5,000 emails are sitting in the deferred queue because of a DNS timeout or an ISP block. Use /opt/zimbra/common/sbin/mailq to see the logjam. In 2026, if you aren't watching your MTA (Mail Transfer Agent) health, you're flying blind. A single rogue "Marketing Blast" from one user can clog the pipes for the entire company. We use custom alerts to sniff out these spikes before they trigger a "Server Busy" state.
Almost always. If your zimbra.log is filling up at 100MB a minute because of a "Logger" error, your disk I/O will spike, and the SOAP API will time out. This is where the "Status" check gets tricky. The service says "Running," but it’s too busy writing logs to actually serve your inbox. We scale our Zimbra builds on NVMe storage (roughly ₹4,500 or $49/mo extra for high-perf tiers) just to handle this overhead. If you're on legacy HDD, you’re just waiting for a crash.
Use zmdbstat. If your MySQL/MariaDB backend is lagging, your "Status" will look fine, but your Search Indexing will be broken. You’ll try to find an email from last Tuesday, and it won't show up. This "Ghosting" is a classic sign of a corrupted index. We run a monthly "re-index" on all high-volume accounts. It’s a background task that prevents that ₹80,000 ($868) "Data Recovery" nightmare later on.
That’s a DNS/Hostfile mismatch. If your /etc/hosts file doesn't perfectly match your zmhostname, the services can't "talk" to each other over the internal network. It’s a 10-second fix for a JIL engineer, but it can take down an entire ₹50 Lakh ($54,250) enterprise cluster if the "Internal Handshake" fails. Don't touch your server’s hostname unless you want to spend the next 6 hours in the "Emergency Console."
Fill out the form and our team will get back to you shortly. We are here to help you with your queries and support.
