It was a Monday morning. One of our sales guys walks up and says his Outlook stopped pulling emails from Zoho. Fine, happens. I remoted in, looked at the account settings — everything looked right. Port 993, SSL enabled, imap.zoho.in as the server. Textbook. And it still wasn't working. The connection would just time out, no useful error, nothing actionable. Just Outlook sitting there spinning like it had all the time in the world.

I've seen this a hundred times now. The frustrating part isn't even that it breaks — it's that Zoho's own help docs send you in circles. They'll tell you to check your port settings, you check them, they're fine, and you're back to square one. What nobody tells you upfront is that IMAP failures on Zoho are almost never about the port. It's almost always either the wrong server address for your region, a missing app password, or IMAP not being enabled at the account level. One of those three. Every time.

So I started keeping notes. Every time this came up for someone on our team or I saw it in a support thread, I wrote down what actually fixed it. This post is that list. No fluff, just the stuff that works.

Table of Contents

• Why Zoho Mail IMAP Fails (The Real Reasons)
• Step 1 — Verify IMAP Is Actually Enabled in Zoho
• Step 2 — Use the Right Server Address for Your Region
• Step 3 — Generate and Use an App-Specific Password
• Step 4 — Exact Settings for Outlook, iPhone, and Gmail
• Common Mistakes That Keep Breaking This

Why Zoho Mail IMAP Fails (The Real Reasons)

Here's the thing — when IMAP stops working on Zoho, people immediately go to the email client and start changing ports. Understandable instinct. Wrong move. The client settings are rarely the problem.

Zoho runs on different data centers depending on where your organization was set up. If you're in India, your mail server is imap.zoho.in. If you're on a global account, it's imap.zoho.com. Using the wrong one gives you a connection timeout that looks exactly like a port problem. Maddening.

On top of that, Zoho requires you to explicitly enable IMAP access per user. It's not on by default for everyone. And if your organization has two-factor authentication turned on — which it should — your regular password flat out won't work for IMAP. You need an app-specific password. This one trips up even experienced users because the error message just says "authentication failed," not "hey, you need an app password."

Step 1 — Verify IMAP Is Actually Enabled in Zoho

Log into Zoho Mail directly at mail.zoho.in or mail.zoho.com. Go to Settings (gear icon, top right) then click Mail Accounts in the left sidebar. Select your account, then look for the IMAP Access section.

There should be a toggle. If it's off, turn it on. Save. Done. Sounds too simple, right? You'd be surprised how often this is the whole problem. I've had users spend two hours on port configurations when IMAP was just disabled.

If you're an admin managing this for others, you can check this for all users under the Admin Console at mail.zoho.in/adminconsole — go to Email Settings and look at the IMAP/POP configuration under mail access policies.

Step 2 — Use the Right Server Address for Your Region

This is the one that gets people most often. Here are the correct server addresses:

For India (.in accounts):

IMAP Server: imap.zoho.in
Port: 993
Security: SSL/TLS

SMTP Server: smtp.zoho.in
Port: 465
Security: SSL/TLS

For Global accounts (.com):

IMAP Server: imap.zoho.com
Port: 993
Security: SSL/TLS

SMTP Server: smtp.zoho.com
Port: 465
Security: SSL/TLS

How do you know which one you're on? Log into your Zoho Mail and check the URL. If it shows mail.zoho.in, you're on the India data center. Use the .in servers. If it's mail.zoho.com, use the .com ones. Simple test, easy to miss.

Step 3 — Generate and Use an App-Specific Password

If your Zoho account has two-factor authentication enabled, stop right here. Your regular password will not work for IMAP. It will fail every single time, and the error won't tell you why clearly. You need to generate an app password.

Here's how: Go to accounts.zoho.in (or accounts.zoho.com), click on your profile, then go to Security. Scroll down to App Passwords. Click Generate New Password, give it a name like "Outlook" or "iPhone Mail", and copy the password it gives you. Use that in your email client instead of your regular password.

One thing worth knowing — that app password is shown once. If you lose it, you have to generate a new one. I always paste it somewhere temporarily before setting it up in the client.

Step 4 — Exact Settings for Outlook, iPhone, and Gmail

Outlook 2016 / Outlook 365: Go to File > Add Account, choose Manual setup, pick IMAP. Incoming server: imap.zoho.in, port 993, encryption SSL. Outgoing: smtp.zoho.in, port 465, SSL. Username is your full email address. Password is your app password if 2FA is on.

iPhone (iOS Mail app): Go to Settings > Mail > Accounts > Add Account > Other > Add Mail Account. Fill in your name, email, and app password. On the next screen, pick IMAP. Use imap.zoho.in for incoming, smtp.zoho.in for outgoing. Both on port 993/465 with SSL. iPhone sometimes auto-detects wrong settings so always double-check after setup under Account > Advanced.

Gmail (via Settings > Check mail from other accounts): This uses POP3, not IMAP. Use pop.zoho.in, port 995, SSL enabled. Same app password applies. Honestly, I find this setup finicky and would only recommend it if someone specifically needs Gmail as their front-end.

Common Mistakes That Keep Breaking This

Using port 143 instead of 993. Port 143 is unencrypted IMAP. It might work on some networks, but most corporate firewalls block it and Zoho strongly prefers 993. Just use 993 with SSL and don't think about it.

Using your regular password when 2FA is on. Already covered this but I'll say it again because it causes so much confusion. Authentication failed does not mean your password is wrong. It means Zoho won't accept a regular password for IMAP when 2FA is active.

Mixing up .in and .com servers. This gives you a timeout, not an auth error, so people assume it's a network problem and start blaming their ISP or firewall. Check the URL of your webmail first.

Not saving the IMAP toggle in Zoho settings. There's a save button. Easy to click the toggle and then navigate away without saving. The toggle will look like it's on but it reverts. Hit save, then refresh the page to confirm.

Leaving the outgoing server authentication unchecked in Outlook. Outlook has a checkbox under More Settings > Outgoing Server that says "My outgoing server requires authentication." Make sure that's checked or you'll connect fine for incoming but sending will fail.

Look, none of this is complicated once you know what to look for. But Zoho's interface buries some of these settings and the error messages don't exactly point you in the right direction. Hope this saves you the hour I wasted the first time I ran into it. If you're still stuck after all this, check whether your organization's admin has restricted IMAP access at the domain level — that's a separate setting in the admin console and overrides everything at the user level.