[ Sending-service guides ]

Authenticate email sent through Zoho Campaigns: configuration and verification

Configure the documented Zoho Campaigns sending route, preserve other mail services, and verify the delivered identities before accepting the change.

By the EmailAuth research team · 5 min read

[ Key points ]

  • Configure the documented Zoho Campaigns sending route, preserve other mail services, and verify the delivered identities before accepting the change.
  • Sender verification and domain authentication are separate gates.
On this page
  1. Scope and prerequisites
  2. Configure the documented route
  3. Product-specific risks
  4. Prove the route at the receiving end
  5. Diagnose failures without widening access
  6. Handover and recovery
  7. Confirm the provider boundary
  8. Work through a fictional diagnostic case
  9. Separate a passing message from enforcement readiness

Scope and prerequisites

This procedure concerns Zoho Campaigns marketing delivery. Treat it separately from Zoho Mail and other Zoho products. Own the sender mailbox, obtain access to the organization's authentication controls and identify the authoritative DNS operator before editing anything.

Configure the documented route

  • Step 1. Under Settings and Deliverability, use Manage Senders to add the sender address and complete its emailed verification.
  • Step 2. Open Domain Authentication, choose Setup for the domain and copy its SPF and DKIM records.
  • Step 3. Publish the supplied TXT values in authoritative DNS. Where an SPF record already exists, merge the required mechanism into that single policy rather than creating another record. The cited guide names include:zcsend.net; confirm the current account-issued value before changing a regional account.
  • Step 4. Return to Domain Authentication, Setup and Verify Domain. Inspect the reported error if validation fails. The guide gives a 24–48-hour DNS update window.
  • Step 5. Generate an approved test campaign using that sender and capture its delivered authentication identities.

Product-specific risks

Sender mailbox verification proves access to an address; it is not the same as passing domain authentication or DMARC. A campaign preview may not traverse the same route as an actual campaign, so document what type of test was sent. Keep a small approved seed list and record the exact sender selection. If DNS verification succeeds but the delivered From is not the expected domain, resolve the product configuration before widening distribution. Consent, unsubscribe behavior and list quality remain necessary even when authentication passes.

Prove the route at the receiving end

Use an approved external mailbox and save the complete raw message with its timestamp and message identifier. No live tenant test is claimed in this guide. The following is an acceptance worksheet to complete during implementation, not a record of observed results.

  • Evidence field: Visible From; What to record: Actual address and domain; Acceptance question: Is this the intended sender identity?
  • Evidence field: Envelope; What to record: Return-Path and receiver-reported SPF domain; Acceptance question: Which domain did SPF actually authenticate?
  • Evidence field: SPF; What to record: Trusted receiver result and evaluated identity; Acceptance question: Did it pass, and does that identity align?
  • Evidence field: DKIM; What to record: Every d= domain, s= selector and receiver result; Acceptance question: Does at least one passing signature align?
  • Evidence field: DMARC; What to record: Receiver result and applicable policy; Acceptance question: Does an aligned passing path exist?
  • Evidence field: Route; What to record: Product, account and message type; Acceptance question: Did the test use the production path?

DMARC needs at least one aligned, passing SPF or DKIM path. A passing signature from an unrelated service domain is not enough. Strict alignment requires exact domain equality; relaxed alignment uses the applicable organizational-domain relationship. Check the domain's actual alignment settings before declaring success. A subdomain is not an automatic strict match. SPF uses the SMTP identity, not the display name or Reply-To. Consult the alignment glossary when recording the decision.

Use Authentication-Results from the receiving system you trust, not a header supplied by an arbitrary sender. Capture all signatures rather than stopping at the first failure. For forwarded mail, compare a direct test with a forwarded copy: forwarding may change SPF evaluation or alter signed content. Do not diagnose those effects by adding the forwarder's address to your provider authorization.

Diagnose failures without widening access

Compare authoritative DNS with the exact configured record names first, then check recursive visibility and service validation. A wrong name, truncated key or conflicting CNAME is not fixed by waiting for caches. Keep only one SPF policy at an owner and check the ten DNS-lookup-term limit across evaluated includes and redirects before merging another sender. DKIM selectors belong to individual signing configurations; do not overwrite another application's record to force a validation result.

If authentication passes but delivery is poor, inspect the recipient response, reputation, content and sending permissions separately. DMARC pass does not promise acceptance or inbox placement. If neither path aligns, stop expansion and correct the actual sender configuration. Do not weaken the whole domain's DMARC policy to hide a single product failure.

Handover and recovery

Save the approved DNS diff, public lookup results, service status and redacted received-message worksheet with a named owner. Keep credentials and private keys out of tickets. On failure, pause the affected sending job or use a previously tested route under the service owner's control. Restore only the changed records that belong to this integration; keep public keys needed by in-flight messages. Retest after rollback, key rotation, domain migration or a change in outbound relay. Close the change only when the product owner and mail administrator can explain the observed identity chain.

Confirm the provider boundary

The current sender form permits up to five addresses in one addition, not a claim that five is the total account limit. If a verification email is missing, inspect filters and use Support rather than inventing domain ownership. Retiring a sender domain is a separate change: inventory scheduled campaigns and other uses before removing application configuration or DNS authorization.

Work through a fictional diagnostic case

Fictional written case only: CA-01 assumes news@club.example has completed its emailed sender verification, but the domain authentication screen still shows a missing DKIM record. No campaign original has been captured, so envelope and DKIM results are unknown. The campaign owner must obtain the correct account-issued record, complete domain verification and inspect a controlled final campaign. An address-verification email is not a campaign authentication test. No tenant, DNS, server command or message was exercised for this case.

Separate a passing message from enforcement readiness

RFC 9989 Section 7.4 requires valid DKIM for a domain publishing p=reject and cautions about indirect-mail interoperability. A single aligned SPF result does not by itself justify a reject-policy rollout. Review all legitimate routes and policy ownership separately from this provider setup.

[ Takeaway ]

Sender verification and domain authentication are separate gates.

[ By role ]

What this means for you

Choose your role for practical next steps.

IT / Mail Admin

Verify identities, not green badges

For Zoho Campaigns, keep product activation, DNS visibility and receiver results as separate evidence.

Next steps

  1. Capture current authoritative records before editing.
  2. Test each distinct sender and delivery route.
  3. Retain the public evidence and a narrow rollback plan.

CISO / SecOps

Limit delegated sending authority

The Zoho Campaigns integration should have a documented domain scope and accountable owner.

Next steps

  1. Review selector and envelope ownership before delegation.
  2. Exclude credentials and private keys from handover material.
  3. Require revalidation after channel or domain changes.

Founder / Non-technical

Protect the message that matters

Assign business ownership to the Zoho Campaigns route rather than treating DNS validation as project completion.

Next steps

  1. Name the critical message type and its sender.
  2. Approve a small representative test before broader sending.
  3. Keep an operational fallback and owner for failures.

[ FAQs ]

Frequently asked questions

Does clicking the sender verification email complete DNS setup?

No. Treat mailbox ownership, DNS validation and received-message authentication as three separate checks.

Can I add a second SPF record for Campaigns?

No. Retain one SPF policy at the owner and merge only the authorized mechanism, checking its lookup budget.

Is a preview sufficient for final acceptance?

Not by itself. Test the actual intended campaign route with approved seed recipients and retain the resulting raw message.

Can authentication replace unsubscribe and consent controls?

No. Authentication concerns domain authorization and alignment. Permission to send and recipient preference handling remain separate obligations.

What proves Zoho Campaigns mail passes DMARC?

A representative received message must have at least one passing SPF or DKIM identifier aligned with its visible From domain under the applicable alignment mode. Service verification alone is insufficient.

Can Zoho Campaigns authentication guarantee the inbox?

No. The recipient retains its own acceptance and filtering policy. Keep authentication results separate from placement and reputation evidence.

What should I save for a Zoho Campaigns handover?

Save the product route, approved DNS diff, verification status and redacted receiver evidence. Include the timestamp and sender identity, but exclude credentials and private keys.

When should the Zoho Campaigns route be retested?

Retest after a domain or selector change, relay migration, sending-channel change or rollback. Cover each distinct sender domain and representative message type.

[ Sources ]

Sources

  1. How to authenticate your domain - Online Help | Zoho Campaigns

    Sections Domain Authentication Steps

  2. dmarc

    Sections §4.4 · §5.3.5 · §7.4

  3. spf

    Sections §4.5 · §4.6.4

  4. dkim

    Sections §3.5 · §3.6.1 · §6.1

[ Glossary ]

Glossary

Alignment
The required relationship between the visible From domain and an authenticated SPF or DKIM domain.
Selector
The DKIM signature identifier that selects a DNS public key beneath the signing domain.
Return-Path
The delivered representation of the SMTP reverse-path, useful alongside receiver results when identifying the SPF domain.

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

Knowledge Base