Using Zoho as your SMTP Provider

SMTP (Simple Mail Transfer Protocol) is what reliably delivers email sent from the platform. Using Zoho Mail's SMTP server can help ensure smooth, consistent delivery for your outbound messages.

This guide covers the outgoing server settings for both personal Zoho accounts and domain-based organization accounts, plus a few common configuration gotchas.

If you also need incoming mail settings, see Zoho's Zoho Mail IMAP Server Details.

Outgoing server settings for personal email users

For personal accounts with an address like username@zoho.com, use these settings:

Setting | Value

Outgoing Server Name | smtp.zoho.com

Port | 465 with SSL — or — 587 with TLS

Require Authentication | Yes

Learn more about Why Can't I Use My Free Email Address As The SMTP?

Outgoing server settings for domain-based organizations

For organization accounts with a domain-based address like you@yourdomain.com, use these settings:

Setting | Value

Outgoing Server Name | smtppro.zoho.com

Port | 465 with SSL — or — 587 with TLS

Require Authentication | Yes

Username | Your Zoho username or full Zoho Mail address ( you@yourdomain.com )

Email Address | Your Zoho Mail address ( you@yourdomain.com )

Password | Your Zoho account password (an app-specific password is required if two-factor authentication is enabled)

If two-factor authentication is enabled on your Zoho account, you'll need to generate an application-specific password and use that in the password field instead of your regular Zoho password.

Frequently Asked Questions

Before you begin

“Using Zoho as your SMTP Provider” is part of the Marketing → Email Marketing area in Adaptive AI. Build templates, broadcasts, campaigns, and performance reporting. Email configuration affects deliverability, reputation, consent, and reporting. Test the exact sender, content, links, and recipient state before sending to a real audience. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Confirm the sending domain or provider is connected, authenticated, and approved for the From address you plan to use.
• Verify the audience has appropriate consent and exclude unsubscribed, bounced, suppressed, or otherwise restricted recipients.
• Prepare a small internal test segment with multiple mailbox providers and complete contact fields for merge-value testing.
• Review the subject, preview text, sender name, reply-to address, links, fallback values, and required business identification.
• Check whether the email is part of a campaign, workflow, course, invoice, or system notification so you test the correct sending path.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Send to the internal test segment and confirm each mailbox receives the message from the intended sender without broken merge values.
2. 2Open the message on desktop and mobile, then test every link, image, button, reply path, and unsubscribe control.
3. 3Review delivery logs for accepted, delivered, bounced, blocked, complained, opened, and clicked events where available.
4. 4Confirm replies return to the correct inbox and that the related contact conversation or workflow updates as intended.
5. 5Only expand the audience after the test content, recipient filters, timing, and tracking behavior are all correct.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Check domain authentication, provider status, From-address alignment, and sending limits when messages are rejected or never leave the queue.
• Review suppression, bounce, complaint, unsubscribe, and invalid-domain status for a recipient-specific delivery failure.
• Use the email log and provider response rather than repeated test sends to identify the exact rejection or deferral reason.
• Confirm merge fields have fallback values and that the test contact contains the data expected by the template.
• Compare campaign or workflow scheduling, account time zone, smart-send rules, and quiet hours when delivery is delayed.

Best practices

• Send relevant content to well-defined segments and avoid sudden volume increases that can damage domain reputation.
• Use one recognizable sender identity, working reply path, accurate subject, and clear unsubscribe option in marketing messages.
• Remove chronically invalid addresses and investigate complaint or bounce spikes before sending the next campaign.
• Keep templates focused, accessible, mobile-readable, and free of unnecessary tracking or image weight.
• Record major sender, domain, audience, and automation changes so deliverability shifts can be traced to a specific event.