The frustration is real: your Zoho Mail app on Android delivers notifications perfectly for US and EU accounts, but the moment you switch to a UK-hosted account on zohomailcloud.co.uk, silence. No pings, no banners, no badges — just missed emails you only discover when you manually open the app.
You’re not imagining it, and you’re almost certainly not doing anything wrong.
This guide breaks down exactly why this happens, what you can do right now to stay on top of your inbox, and how to push Zoho toward a permanent fix. Whether you’re a business owner, IT admin, or power user managing a UK-region Zoho Mail account, this is the most complete resource available on this specific issue.
Originally reported in the Zoho community: Zoho Mail Android App problem
| Server | Push Notifications Working? |
|---|---|
zoho.com (US / Legacy) |
✅ Yes |
zohomail.eu (EU) |
✅ Yes |
zohomailcloud.co.uk (UK) |
❌ No |
The pattern here is the critical clue. When the same Android device, the same app version, and the same notification permissions produce working alerts for US and EU accounts — but not for a UK account — the variable is the server, not the device.
This is not a battery optimization problem. It’s not a permissions oversight. The root cause almost certainly lives at the infrastructure level, and understanding it will help you choose the right workaround while you wait for Zoho to resolve it.
Zoho Mail’s Android push notifications rely on Firebase Cloud Messaging (FCM) — Google’s service for delivering real-time alerts to Android devices. For FCM to work, Zoho’s backend servers must:
If the UK datacenter’s backend isn’t fully wired into this FCM pipeline — whether due to a missing API key, an incomplete server-side configuration, or a regional infrastructure build that hasn’t reached feature parity with US/EU deployments — your device never receives the push signal. The email arrives on the server; the notification simply never gets dispatched.
Regional server deployments are commonly rolled out incrementally. The UK zohomailcloud.co.uk infrastructure is a newer regional cluster, and it’s plausible that push notification routing hasn’t been fully commissioned on it yet.
The Zoho Mail Android app maintains internal mappings that associate server domains with push notification endpoints. The .co.uk domain suffix is structurally different from .com and .eu — and if the app’s push registration logic doesn’t correctly recognize zohomailcloud.co.uk as a valid endpoint for FCM token submission, the token registration silently fails. The app appears to work normally; it just never tells the UK server where to send your notifications.
Even if the app attempts registration, a network-level or API-level failure could mean the UK server backend never stores your device’s FCM token. Without a stored token, there is literally no address for Zoho’s UK servers to send a push notification to — regardless of how many emails arrive.
Some Zoho features are restricted on trial plans. While this is less likely to be the primary cause given the server-specific pattern, it’s worth noting that UK-region trial configurations could have an unintentional push notification restriction. If you’re on a paid plan and still experiencing this, this hypothesis can be ruled out.
While the underlying issue is almost certainly server-side and requires a Zoho engineering fix, these workarounds will keep you informed in the meantime.
What it does: Replaces real-time push with scheduled mail fetching — not instant, but reliable.
Steps:
Trade-off: Up to 15-minute delay on notifications; minor battery impact
Best for: Users who need a zero-configuration fix immediately
What it does: Clears any corrupted or misrouted token registration and forces the app to re-register with the UK server from scratch.
Steps:
Trade-off: May not resolve the issue if the root cause is server-side (the token re-registers but the server still can’t route it)
Best for: Ruling out a corrupted local token before escalating
What it does: Prevents Android’s power management from killing the FCM listener process in the background.
Important context: Given that US/EU notifications work on the same device, battery optimisation is unlikely to be the primary cause. However, it can compound the problem and is worth eliminating.
Steps:
Trade-off: Minimal — slight battery impact
Best for: OEM Android devices (Xiaomi, Samsung, OPPO) as a complementary fix
What it does: Bypasses the Zoho app’s broken push pathway entirely by using IMAP IDLE — a protocol that maintains a persistent server connection and delivers near-instant notifications through the third-party app’s own notification system.
Correct IMAP settings for UK/EU Zoho Mail accounts (zohomailcloud.co.uk):
| Setting | Value |
|---|---|
| Incoming (IMAP) Server | imappro.zoho.eu |
| IMAP Port | 993 |
| Security | SSL/TLS |
| Outgoing (SMTP) Server | smtp.zoho.eu |
| SMTP Port | 465 (SSL) or 587 (STARTTLS) |
| Username | Your full Zoho email address |
| Authentication | Password (or app-specific password if 2FA is enabled) |
⚠️ Important: For UK-region accounts (
zohomailcloud.co.uk), useimappro.zoho.eu— notimappro.zoho.com. The.euendpoint is the correct documented hostname for European and UK datacenter accounts. Using the.comendpoint may result in authentication failures or incorrect mailbox access.
Steps:
zohomailcloud.co.uk → Settings → Mail Accounts → [your account] → IMAP Access → ensure IMAP is enabledTrade-off: You lose Zoho-specific app features (Streams, integrated calendar, Zoho CRM sync)
Best for: Business users who cannot afford to miss emails and need a reliable solution until Zoho ships a fix
For full official IMAP configuration details, refer to Zoho’s IMAP documentation.
Before escalating to Zoho Support, run these diagnostics to build a clear evidence base.
zohomailcloud.co.uk via a browserIf your Android device doesn’t appear, or appears without notification permissions, this confirms an FCM token registration failure at the server level.
Per Zoho’s official Android notification documentation:
This is a known step that Zoho’s own support documentation highlights — the push toggle exists at both app-level and per-account level, and both must be enabled.
First-line support responses to notification issues are often generic. To get this escalated to the engineering team, you need to provide specific, technical information that makes it impossible to dismiss as a device configuration problem.
Submit to the Zoho Support Portal with the following:
Subject: Push Notification Failure — UK Server (zohomailcloud.co.uk) Only — Android
Device: [Manufacturer, Model, Android Version]
Zoho Mail App Version: [check Settings → About]
Issue: Push notifications not received for UK account (zohomailcloud.co.uk)
Confirmed working on SAME device:
- zoho.com (US) account: ✅ Notifications working
- zohomail.eu (EU) account: ✅ Notifications working
- zohomailcloud.co.uk (UK) account: ❌ No notifications
Steps already taken:
- Cleared app cache and data, re-logged in
- Verified Push Notifications toggle enabled (app-level and account-level)
- Excluded Zoho Mail from battery optimisation
- Tested on [stock Android / OEM device]
Request: Please escalate to Tier 2 / UK datacenter engineering team
for investigation of FCM push notification routing on zohomailcloud.co.uk
server cluster.
Key phrase to use: "This is server-specific, not device-specific — confirmed by identical settings producing working notifications on US and EU servers on the same device."
This framing makes it very difficult for support to close the ticket with generic device troubleshooting advice.
Determining whether this affects many UK users — or just a handful — directly influences how quickly Zoho prioritises a fix. Here’s how to contribute to that effort:
r/Zoho for "zohomailcloud.co.uk notifications" — upvote existing posts and add your device/version detailsThe more users who report this with consistent, specific details (UK server, Android, same-device US/EU working), the more likely it gets treated as a P1 infrastructure bug rather than an isolated user issue.
| Solution | Setup Effort | Effectiveness | Permanence | Best For |
|---|---|---|---|---|
| Background Polling | ⭐ Very Low | Medium (15-min delay) | Temporary | Anyone needing a quick fix |
| Clear App Data / Re-register | ⭐ Very Low | Low–Medium | Temporary | Ruling out local token corruption |
| Battery Optimisation Exclusion | ⭐ Very Low | Low (not root cause) | Permanent | OEM Android devices |
| Third-Party IMAP Client | ⭐⭐ Medium | High (near real-time) | Until Zoho fixes | Business users, power users |
| Zoho Support Escalation | ⭐⭐ Medium | High (permanent fix) | Permanent | Everyone — do this in parallel |
| Community Verification | ⭐ Very Low | Diagnostic | N/A | Accelerating Zoho’s fix timeline |
Recommended approach for business users: Implement the third-party IMAP client as your reliable interim solution, run the diagnostic steps to build evidence, and submit a detailed support ticket in parallel. These three actions give you immediate reliability while working toward a permanent resolution.
The zohomailcloud.co.uk infrastructure exists specifically to serve UK businesses with data residency requirements — keeping email data within UK/EU jurisdiction. This is a genuinely valuable feature for organisations subject to UK GDPR and data sovereignty requirements, which makes the push notification gap particularly frustrating: the very users who chose the UK server for compliance reasons are the ones being penalised by this bug.
If you’re evaluating Zoho Mail for your business more broadly, it remains one of the most capable and cost-effective business email platforms available — with deep integration across the Zoho One ecosystem, including CRM, Projects, Desk, and more. The UK server issue is a specific, fixable infrastructure problem — not a reflection of the platform’s overall quality.
For businesses already using Zoho Mail and looking to get more from the broader Zoho ecosystem, exploring Zoho Workplace — which bundles Mail, Cliq, Connect, Meeting, and more — is worth considering as your team scales.
zohomailcloud.co.uk cluster appears to have an FCM push notification routing gap not present on US or EU serversimappro.zoho.eu — not imappro.zoho.comIf you’re managing Zoho Mail as part of a broader Zoho deployment — or if you’re running into configuration challenges beyond this specific notification issue — the team at Creator Scripts specialises in Zoho implementation, configuration, and troubleshooting for businesses of all sizes.
Whether you need help with email infrastructure, Zoho One setup, or custom workflow automation, get in touch for a consultation — or explore the Creator Scripts blog for more Zoho guides, including:
Originally reported in the Zoho community: Zoho Mail Android App problem