Our step-by-step guide helps you quickly identify and resolve the most common problems preventing your emails from flowing smoothly. Get back to communicating fast.
When simple fixes fail, we help you understand the core mail components: SMTP (Sending), POP3/IMAP (Receiving), and DNS records. Dive into server logs for true root cause analysis.
When both sending and receiving stop, the situation feels more urgent. Communication comes to a halt, not partially, but completely. At that point, businesses are not just looking for a fix, they are trying to understand what failed underneath. An “i cannot send or receive mail service” issue rarely sits in one place. It could begin with server access, but quickly extends into authentication layers, domain records, firewall rules, or even account-level restrictions. One change, somewhere earlier, often triggers a chain reaction. What typically happens is teams focus on restoring one side first. Maybe sending starts working again. Or incoming emails resume. But unless the full path is checked, stability doesn’t last. The same disruption comes back, sometimes in a different form. In practice, email systems depend on consistency across multiple points. Hosting environment, DNS alignment, security filters, application integrations. Each piece has to agree with the other. Even a small mismatch can block the entire flow. So while the issue begins with a complete breakdown, the resolution usually expands beyond it. Businesses end up reviewing not just email, but how their underlying systems are structured and maintained. That’s where longer-term reliability starts to take shape.
Some teams reach out when everything stops at once. No emails going out, none coming in. Work pauses. Internal coordination gets messy very quickly. Others come after trying to resolve it step by step. Restarting services, checking accounts, making quick DNS edits. It works briefly. Then the silence returns. There are businesses heavily dependent on email for daily operations. Sales conversations, customer updates, vendor coordination. When both directions fail, the impact shows up immediately. We’ve also worked with teams during transitions. Platform shifts, hosting changes, new security layers being introduced. Email tends to be one of the first systems to reflect those changes, not always smoothly. In some cases, the setup has been running for years without review. No recent changes, yet things stop. That uncertainty is often harder than the issue itself. Different situations. Similar patterns underneath.
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.
