Zoho Email Warm Up: Free Plan API and IMAP Setup

You can warm up Zoho Mail on the free plan through the Zoho Mail API, or on Mail Lite and higher through IMAP. If you skip DNS, region matching, or a slow ramp, good mailboxes can still land in spam. This guide gives the setup path, DNS checks, and safe sending numbers.

The main Zoho difference is access method. Many warm-up guides assume every mailbox has IMAP, but Zoho’s free plan needs a different path. If you are still comparing tools, start with this free email warm-up overview, then use the Zoho-specific setup below.

Which Zoho warm-up path works?

There are two practical ways to warm up Zoho Mail.

Use the Zoho Mail API if you are on the free plan. Use IMAP if you are on Mail Lite or a higher plan with IMAP access. Do not force an IMAP setup on a mailbox where IMAP is not enabled. It can fail even when the password is correct.

Zoho also uses regional data centres. Your account may live on a Zoho domain such as zoho.com, zoho.eu, zoho.in, or zoho.com.au. The exact list can change, so check Zoho’s current account-server and data-centre documentation when you connect.

Keep the data centre consistent. If your Zoho account is in the EU, do not generate an OAuth code from a US Zoho account URL. If your mailbox is in India, do not use EU server details. A region mismatch often looks like a bad password, expired token, or permission error.

BobWork Email Warm-up supports Zoho Mail API through a Self Client code, including the Zoho free plan. It also supports Zoho over IMAP on Mail Lite and higher. By default your Zoho mailboxes warm in the shared network; switch the account to Private pool and they warm only with your own mailboxes.

What Zoho email warm up numbers work?

Warm-up creates ordinary mailbox activity before you increase outbound sending. It does not repair a broken domain. It also does not override spam complaints, poor lists, missing DNS, or bad copy.

Use conservative numbers for Zoho. New domains need more time than established domains. If you send to Gmail recipients, follow Google’s sender guidance: keep spam complaints under 0.1%, and never at or above 0.3%. Google documents this in its email sender guidelines.

BobWork’s default engine starts at 3 emails per day, adds 2 per day, and caps at 30 unless you edit the mailbox cap. Sends are spread between 09:00 and 18:00 in the mailbox’s own time zone, with randomness every 15 minutes.

That timing matters. Fixed sending patterns are not normal human behavior.

The engine also favors peers on different domains or providers twice as often. About 40% of received warm-up mail gets a reply, and threads stop after 3 messages. The content is plain text office talk with no links or images.

If you want the day-by-day version, use this email warm-up timeline before setting campaign targets.

Which DNS records matter?

Do DNS before warm-up. Warm-up cannot compensate for missing SPF, DKIM, or DMARC. Zoho sends mail for your domain, so receiving servers need proof that Zoho is allowed to send.

You need three records.

SPF says which mail servers can send for your domain. DKIM signs each message with a cryptographic signature. DMARC tells receivers what to do when SPF or DKIM fails, and where to send reports if you configure reporting.

For Zoho, SPF usually includes Zoho’s sending include. Do not copy an old record blindly. Open Zoho’s own SPF instructions for your account and publish the value it gives you. Zoho documents domain authentication in its SPF and DKIM setup guidance.

DKIM is the record people often miss. Zoho commonly uses the selector zmail. That means the host name can look like this:

zmail._domainkey.yourdomain.com

The value is a long TXT record generated inside Zoho. Do not invent it. Copy it from Zoho Admin Console.

In Zoho Mail Admin Console, open your domain settings, then look for email authentication or DKIM. Zoho menu labels can vary by interface and plan, so use the current Zoho screen as the source of truth. Publish the selector, host name, and TXT value shown there.

DMARC can begin in monitoring mode:

_dmarc.yourdomain.com TXT "v=DMARC1; p=none"

A monitoring policy lets you test alignment without rejecting mail. Move to a stricter policy only when you understand every legitimate sender for the domain.

BobWork checks SPF, DKIM, and DMARC daily through DNS. For DKIM discovery, it checks common selectors including zmail and zoho. That helps with Zoho because a valid DKIM record may exist under a selector your tool did not try.

How do you connect by API?

Use this path for the free Zoho Mail plan.

The API method uses Zoho’s OAuth flow through a Self Client code. In practice, you generate a short-lived code inside Zoho API Console, then paste it into the warm-up tool. The tool exchanges it for the access it needs.

Read Zoho’s current OAuth flow in the Zoho API OAuth documentation before troubleshooting tokens. OAuth behavior, token lifetime, and account-server URLs can depend on your region.

Test the mailbox first

Log in to Zoho Mail as the mailbox owner. Send one normal email to another inbox you control. Reply to it. Confirm you can send and receive without warm-up software.

If this fails, fix Zoho first. Warm-up software cannot repair a suspended account, unverified domain, or blocked sender.

Match the data centre

Look at the Zoho URL used when you are signed in. Check the data-centre selector in your warm-up tool, if it has one. Keep those two aligned.

If your account is on a European Zoho data centre, use the European Zoho account server when generating authorization. If your account is on another regional data centre, use that region. Do not mix regions during OAuth.

Generate the Self Client code

Open Zoho API Console. Create or use a Self Client. Generate a grant code using the scope shown by your warm-up tool.

Do not guess the scope. Too little access causes permission errors. Too much access is unnecessary. A good tool should tell you exactly which scope it needs.

Paste the code into the warm-up setup before it expires. If you wait too long, generate a new code instead of reusing the old one.

Verify limited mailbox access

After connection, check that the tool can send and receive its own warm-up messages. It should not need to read personal mail.

BobWork only touches warm-up mail carrying its own hidden header. For Zoho API senders, it can also recognize a known warm-up subject. Real mail is never read, moved, or answered.

That distinction matters. A warm-up tool should not become a general mailbox reader.

How do you connect by IMAP?

Use IMAP if your Zoho plan supports it and you prefer a mail-client style connection.

Zoho documents IMAP access in its IMAP configuration guide. Check the current server names, ports, and regional differences there. Do not rely on a copied server from another Zoho region.

Typical secure mail-client settings use IMAP for receiving and SMTP for sending. IMAP normally uses SSL on port 993. SMTP submission commonly uses port 465 with SSL or port 587 with TLS. Confirm Zoho’s current setting for your account before saving.

Enable IMAP in Zoho

Open Zoho Mail settings for the mailbox. Find the mail account settings, then IMAP access. Enable IMAP if your plan allows it.

If you cannot see IMAP, your plan may not support it. On the free plan, use the API path instead of trying random server combinations.

Create an app password

If your Zoho account uses multi-factor authentication, you may need an application-specific password for IMAP and SMTP. Generate it from Zoho account security settings, then paste it into the warm-up tool.

Do not use your primary password if Zoho asks for an app password. Do not reuse the same app password across unrelated tools.

Test both directions

An IMAP connection only proves the tool can read the receiving inbox. SMTP must also work for sending.

Send one test warm-up message, then check the receiving inbox. If sending fails, review SMTP host, port, encryption, username, and password. If receiving fails, review IMAP host, port, encryption, and whether IMAP is enabled.

How should you ramp sending?

After the mailbox connects, resist the urge to raise volume immediately.

A new Zoho mailbox with a custom domain should behave like a normal work inbox first. It should send small numbers of messages, receive replies, and avoid identical daily patterns. It should also show working authentication before campaigns begin.

The default BobWork ramp handles this: 3 emails per day, then +2 per day, capped at 30. Weekends run at 30%. A pair of mailboxes never writes to each other twice within 3 hours.

You can edit the cap per mailbox, up to 100. That does not mean you should. For outreach, a lower warm-up cap plus steady campaign volume is usually safer than a high artificial warm-up number.

Keep warm-up running during outbound campaigns at 10–15 emails per day. Keep real outreach around 30–50 emails per mailbox per day. If you need more total sending, add mailboxes and domains rather than forcing one Zoho mailbox to carry the load.

Check Zoho’s current sending limits for your plan before campaigns. Provider limits are ceilings, not recommended cold-outreach targets.

Your first campaign should be smaller than your target volume. Send to a clean, relevant list. Avoid link-heavy templates, image-only messages, URL shorteners, and misleading subject lines. These are common reasons mail goes to spam, even when DNS is correct. This spam troubleshooting guide covers the usual causes.

If you manage several inboxes, define the rollout before you send. This outbound sending strategy helps you add capacity without turning one mailbox into the bottleneck.

What should you check first?

Use this checklist before the first outreach campaign. It catches most Zoho warm-up failures.

Do not skip the normal test email. It is the fastest way to separate a Zoho account problem from a warm-up configuration problem.

What breaks Zoho warm-up?

Most Zoho warm-up problems fall into five groups.

The first is a plan mismatch. You are trying to use IMAP on a mailbox where IMAP is not available. Use the API path on the free plan.

The second is a data-centre mismatch. The mailbox belongs to one Zoho region, but the authorization or server settings belong to another. Recreate the token or connection using the correct region.

The third is missing DKIM. SPF alone is not enough. Publish the Zoho DKIM record, wait for DNS propagation, and verify inside Zoho. If your selector is zmail, make sure the host name includes zmail._domainkey.

The fourth is a sudden volume jump. Going from a quiet mailbox to aggressive outreach is risky. Slow down, keep warm-up active, and let replies accumulate.

The fifth is poor list or content quality. Warm-up cannot protect you from irrelevant recipients, scraped lists, spam complaints, or deceptive copy. If replies are low and complaints rise, fix the campaign before blaming Zoho.

In BobWork, spam rate means the share of a sender’s warm-up mail that receiving mailboxes found in Spam over 7 days. That is measured directly inside receiving mailboxes, not through third-party seed lists. Health scores show Healthy at 85 or above, Watch from 60 to 84, At risk below 60, and Blocked when login or permission fails.

If a warm-up email lands in Spam, BobWork moves only its own warm-up mail to Inbox, marks it read, labels it Warm-up, and archives it after 24 hours. It does not rescue real mail or answer real threads.

Warm-up is not a one-time switch. Keep it running quietly while the mailbox sends real campaigns.

For an existing Zoho domain, use at least 14 days before normal outreach. For a new domain, use 3–4 weeks. During campaigns, keep warm-up around 10–15 emails per day and avoid large changes in real sending volume.

Watch the trend more than one bad message. One spam landing can happen. A rising 7-day spam rate means the mailbox, domain, list, or content needs attention.

If you want a free setup for Zoho, start with BobWork Email Warm-up. Use the Zoho Mail API for the free plan, or IMAP on Mail Lite and higher. Add your mailboxes (at least 2 if you switch the account to a private pool), confirm SPF, zmail DKIM, and DMARC, then let the ramp run before you push outbound volume.

Frequently asked questions