Zoho Mail admin: the three settings that go wrong after go-live

Zoho Mail admin for domains, retention and offboarding comes down to three habits. Keep your domain's mail records intact whenever DNS changes. Keep a copy of mail outside individual mailboxes with Email Journaling, and know how to search it. Remove a leaver only after their mail is captured and their devices have stopped syncing.

Zoho Mail admin is the organisation-level work done by the Super Admin and other administrators in the Admin Console and Control Panel. It is different from the settings each user changes for themselves. Admin work decides whether mail arrives at all, whether a record survives, and whether a former employee can still get in.

These three areas break after go-live for a simple reason. Nobody touches them during the build, and then a later change undoes the work. A web agency moves the name servers. Someone deletes an old domain. A manager asks for a leaver's account to be removed the same afternoon.

This guide takes each area in turn, with a worked example from Zoho's community forum, a table of the admin tools, and a leaver checklist you can copy. If you are still choosing a plan or a setup, the overview of Zoho Mail for UK businesses covers the product itself.

Domains: a name server change can stop every inbox at once

A name server change is the quickest way to break a working Zoho Mail domain. Name servers are the servers that answer for your domain's DNS. Whichever provider they point to must hold the records that route your mail to Zoho.

Worked example: redknox.ae

A thread on Zoho's community forum shows what happens. The domain redknox.ae was hosted on Zoho Mail. Its name servers were changed from ns1.etisalatdomains.ae (through ns4) to dns1.p04.nsone.net (through dns4).

The user then reported that all inboxes for the domain stopped working. The bounce showed SMTP status 421 with the diagnostic "Host not reachable". The last delivery attempt was dated 17 November 2023.

How to avoid the same failure

Treat any name server move as a mail change, even when the request is about the website. Before the switch, follow these steps:

Export or screenshot every DNS record at the current provider.
Recreate the mail records at the new provider before the name servers change.
Make the switch at a quiet time, not on a Friday afternoon.
Send test messages from an outside account straight after, and check they arrive.

Tell whoever manages your website or domain registrar about this rule. They often control the name servers, not the mail administrator.

Changing or removing a domain without stranding mail

A domain change in Zoho Mail needs planning, because users ask the same worried questions on the forum again and again. One user wanted to delete their domain, create a new one held with GoDaddy, keep the old domain's emails and redirect mail from old to new. Another asked whether their emails would still be there after deleting the previous domain and validating a new one, keeping the same users.

Two further threads show what goes wrong. A user on a free trial removed one domain and added another, then found test emails still going out from the old, removed domain. A different user could not remove mail hosting, which they needed to do before cancelling their domain.

A safer order for a domain change

Add and verify the new domain while the old one still works.
Check each user's sending address, and send a test from every mailbox.
Keep the old domain receiving until correspondents have moved to the new address.
Ask Zoho support in writing what happens to existing mail before you delete the old domain.

Check your plan before step one. A community post lists the free plan as single domain hosting, so running two domains side by side may need a paid plan.

Mail client server names to check after go-live

Mail clients on laptops and phones connect to Zoho through named servers, and those names must be current. Zoho has updated the SSL certificates for its POP, IMAP and SMTP servers: pop.zoho.com, imap.zoho.com and smtp.zoho.com. Zoho asks anyone still using mailpop.zoho.com as the POP server name to change it to pop.zoho.com in their mail client.

Client settings matter only if your plan allows client access. A community post lists the free plan as webmail access only, with up to 25 users, 5GB per user and a 25MB attachment limit. A user on the forum also mentions a 15-day free trial for evaluating Zoho Mail.

During your post-go-live check, list every device and app that connects to Zoho Mail. Note which server names each one uses. The same list becomes useful again later, when someone leaves and you need to know which devices still hold a copy of their mailbox.

A community post lists Zoho Mail's free plan at 25 users with 5 GB each, webmail access only: Free plan maximum users 25 users, Free plan storage 5 GB per user, Free plan attachment limit 25 MB per attachment — Source: help.zoho.com

Retention with Email Journaling: a second copy outside the mailbox

Email Journaling is the Zoho Mail feature that keeps your record of mail. It captures a copy of emails sent and received in your organisation and forwards it to a destination. Zoho describes the purpose as keeping a complete record for audits, legal reviews or internal investigations.

Journaling solves the core retention problem. A user's mailbox is one copy, and that user controls it. They can delete messages, and an admin can later remove the whole account. A journal copy sits elsewhere, so the record survives both.

Choices to make before you switch it on

The destination: an address the business controls, not a person's own mailbox.
Who can open the destination: as few people as the work allows.
How long the business needs to keep the copies, agreed with whoever owns compliance.
Who needs to be told: staff should know before journaling starts that a copy of their work mail is kept, why, for how long and who can see it. Tell staff in your staff privacy notice, and repeat it in your IT policy.
The paperwork: copying and searching staff mail counts as monitoring. Record your lawful basis and complete a data protection impact assessment before you switch it on.

Switch journaling on at go-live rather than when the first problem arrives. A journal copy only exists for mail that journaling has seen. If you start it the week a dispute begins, the months before are not in the record.

Finding mail later with Data Subject Requests and Spam Quarantine

Data Subject Requests (DSR) is the Zoho Mail Admin Console feature for finding mail after the event. It lets administrators search for email data, and export it, in response to legal investigations or compliance audits. Journaling keeps the record. DSR is how you search it when someone needs an answer.

Typical moments for a DSR search are easy to predict. A former employee's mail is needed for a customer dispute. An auditor asks for correspondence on a contract. A manager needs to know what a leaver told a supplier before they left.

Restrict DSR to the smallest group of admins you can. A search across all email is powerful, and the people who can run it should be named and few.

Spam Quarantine is the other Admin Console tool worth knowing here. When spam processing quarantines a message, it need not be blocked straight away. Spam Quarantine lets an admin review those messages. Check it when a user says an expected email never arrived, before you assume a domain fault.

Which Zoho Mail admin tool to use for which job

Five Zoho Mail admin features cover most retention and offboarding questions. They are easy to confuse because several of them touch the same messages. The table below sets out what each one does and when an admin reaches for it.

Feature	What it does	When an admin uses it
Email Journaling	Captures a copy of mail sent and received and forwards it to a destination	From go-live, to keep a record that outlives any mailbox
Data Subject Requests (DSR)	Searches and exports email data from the Admin Console	Legal investigations, compliance audits, a leaver's mail needed later
Email Recall	Takes sent emails back from recipients' inboxes inside your organisation	A message went to the wrong internal colleague
Spam Quarantine	Holds messages flagged by spam processing for review	An expected email never arrived
Inactive User Policy	Treats users with no login for more than 120 days as inactive	Reviewing dormant and leaver accounts

Note one limit. Email Recall works only inside your organisation, so it cannot pull back a message already delivered to a customer or supplier.

Offboarding a leaver in Zoho Mail: the order that loses nothing

Offboarding a leaver safely in Zoho Mail depends on the order of the steps, not on any single setting. Removing the user first is the mistake to avoid. Once the account is gone, any mail you did not capture goes with it.

Confirm journaling has been capturing the leaver's mail. If it has not, run a DSR search and export what the business must keep.
Agree who takes over the leaver's customers and suppliers, and tell those contacts the new address.
List the devices and apps that connect to the leaver's mailbox, and remove them.
Remove the user under Control Panel > User Details, the user list Zoho's own instructions use.
Remove the person from any other Zoho apps the team shares, such as Zoho Cliq for team messaging or Zoho Assist for remote support.

Step three matters more than it looks. Zoho counts logins through POP, IMAP and ActiveSync as activity. A phone still syncing the account keeps it looking active, and keeps mail flowing to that device.

When Svennis sets up Zoho Mail inside a Zoho One rollout, we switch on journaling and agree this leaver checklist before anyone leaves. The failure we see most often is a mailbox removed before anyone checked what had to be kept.

Remove a leaver in Zoho Mail only after their mail is captured and their devices are removed. What to do / Why it comes here. 1. Check journaling: Confirm the leaver's mail is captured, or run a DSR export / Mail not captured is lost with the account

The 120-day Inactive User Policy and dormant accounts

Zoho Mail's Inactive User Policy treats a user as inactive if they have not logged in for more than 120 days. Zoho has said it recently started implementing the policy. Logins through POP, IMAP and ActiveSync all count when Zoho tracks the period of inactivity.

The policy cuts both ways for an admin. A mailbox kept "just in case" after someone leaves, with nobody logging in, will cross the 120-day line. A leaver's account still synced to an old phone will not, because the phone's IMAP or ActiveSync logins keep resetting the clock.

So a dormant mailbox is a weak way to keep records. Read Zoho's current policy wording before you rely on any account that nobody uses. Journaling, with DSR to search it, is the record you control.

Run a short review each quarter. Pull the user list, mark anyone who has left or not logged in for months, and decide for each one: keep, hand over or remove. Small organisations often find a former employee or contractor still on the list, still syncing.

Closing a whole Zoho Mail organisation: the Super Admin sequence

Closing a Zoho Mail organisation that has your domain added follows a fixed sequence, and it must be done as the Super Admin. Zoho's community team sets out the steps in its guide on closing an account when you added your domain in Zoho Mail:

Log in as the Super Admin for your organisation.
Go to Control Panel > User Details and remove every user except the Super Admin.
Go to Domains and delete the domains you added.
Go to Dashboard > Delete Organization.
Go to accounts.zoho.com > Settings > Close Account.

The order explains a common complaint. One forum user could not remove mail hosting and so could not cancel their domain. Users and domains come off before the organisation itself.

Apply the offboarding rule to the whole organisation first. Before step two, make sure journaling copies and any DSR exports are stored outside Zoho Mail. Removing every user removes every mailbox the business has not already captured.

What this means for a UK company buying or auditing Zoho services

For a UK company, the practical point is to ask for evidence about each Zoho service separately. The facts on one listing do not transfer to another product.

The UK government's Digital Marketplace shows the kind of detail to look for. Zoho Corporation lists ManageEngine Log360 Cloud on the G-Cloud 15 framework, service ID 161601476274670. The listing states that ManageEngine is a division of Zoho. It gives the United Kingdom and the European Economic Area as data storage and processing locations.

The same G-Cloud listing for Log360 Cloud separates its assurances clearly. The listing gives ISO/IEC 27001 certification by BSI, dated 3 September 2025. The CSA STAR entry is a Level 1 self-assessment, which means Zoho assessed itself rather than being audited by an independent body.

All of that describes Log360 Cloud, a security monitoring service, not Zoho Mail. Log360 Cloud also needs an agent installed on a Windows machine to collect logs. If your auditors want sign-in records across systems as well as mailbox content, that is a separate purchase with its own checks. For Zoho Mail, ask the same questions directly: where mail is stored, and what independent certification covers it.

Next steps for your Zoho Mail admin this month

Four tasks put domains, retention and offboarding on a safe footing, and each takes an hour or two. Do them in this order:

Export every DNS record for your mail domain and store the copy where your web and IT contacts can find it.
Switch on Email Journaling to a destination the business controls, name who can open it, and tell staff in your privacy notice or IT policy that work mail is copied and kept.
Run one test DSR search on a single mailbox, so the first real request is not also the first attempt.
Write the five-step leaver checklist into your HR leaving process, with the Zoho Mail step owned by a named admin.

Then add a quarterly review of the user list against the 120-day Inactive User Policy. Pair it with a check of every device still syncing.

If you want help with the setup, start with the Zoho Mail service page, which explains how the product is configured for UK teams. If you are weighing outside help more generally, what a Zoho partner does sets out what to expect from one.

Sources

Looking for a Zoho partner in the UK? Svennis has been a Zoho Premium Partner since 2011, with more than 200 implementations delivered. See how we work as a UK Zoho Partner.

Zoho Mail admin: domains, retention and offboarding without losing mail