[ Sending-service guides ]

Authenticate email sent through Zoho Assist: configuration and verification

Configure the documented Zoho Assist 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 Assist sending route, preserve other mail services, and verify the delivered identities before accepting the change.
  • Verification in another Zoho service does not complete Assist setup.
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

Zoho Assist supports company-domain sending through its email domain verification flow. This guide covers that product's DKIM setup, not every Zoho application. The Assist administrator needs access to Email Configuration and a DNS owner who can publish the generated public key. Verifying a domain in another Zoho service should not be treated as completion here.

Configure the documented route

  • Step 1. Open Settings, General, Email Configuration in Zoho Assist. Select Domain verification and Add & Verify New Domain.
  • Step 2. Enter the domain part of the intended company sender address and choose Generate Key. Save the returned hostname and value in the change request, checking that the domain is the one actually used for sending.
  • Step 3. In the authoritative DNS manager, create a TXT record with that hostname and the complete supplied value. The documentation's example hostname is an illustration, not a selector you should reuse when the account gives a different one.
  • Step 4. Check how the DNS provider treats a fully qualified name. If it automatically adds the zone name, enter only the relative label needed to obtain the exact final hostname.
  • Step 5. Return to the Domain Verification screen and choose Verify Now. Assist says verification time depends on the record TTL and can take a few hours. A positive status confirms the service found its record; it is not a recipient inbox guarantee.
  • Step 6. Trigger the relevant Assist notification from the intended company address to an approved external test mailbox. Collect the message after all outbound handling and inspect the DKIM signing domain.
  • Step 7. Record the notification type, tenant and sender identity. Repeat for a different domain rather than assuming all technicians and templates share the same authenticated identity.

Product-specific risks

If the TXT entry is present but Assist cannot verify it, compare the full name and complete key against the current generated values. Multiple TXT records at the same DKIM selector, accidental domain duplication and changes made at an inactive DNS host all deserve attention. The cited Assist procedure specifies DKIM, not a universal Assist SPF include or a custom Return-Path recipe. Do not add speculative DNS values to make a checklist appear complete. Authentication can improve trust but cannot ensure inbox placement.

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 public source does not establish a universal selector, rotation overlap schedule, sender-address entitlement or custom-envelope recipe. Keep those questions with Assist Support when applicable; do not infer them from another Zoho product. Its inbox-placement language is an oversimplification: valid signing does not override the receiver’s filtering decisions.

Work through a fictional diagnostic case

Fictional written case only: ZA-01 assumes shop.example is verified in a different Zoho application, but Assist has not verified its generated key for notifications from support@shop.example. No received Assist signature or envelope result is known. The Assist owner must complete this product’s domain workflow and collect a controlled notification; the other application’s green status cannot close the Assist evidence row. 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 ]

Verification in another Zoho service does not complete Assist setup.

[ By role ]

What this means for you

Choose your role for practical next steps.

IT / Mail Admin

Verify identities, not green badges

For Zoho Assist, 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 Assist 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 Assist 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

Where is domain verification in Assist?

The documented path is Settings, General, Email Configuration, then Domain verification and Add & Verify New Domain.

Should I reuse zoho._domainkey from an example?

Use the exact generated hostname from your Assist account. The example does not override the account-specific value.

Do I need an Assist SPF include?

The cited Assist flow documents DKIM. It does not establish a universal SPF include for this route; verify the actual envelope before proposing an SPF change.

Does Verify Now guarantee inbox delivery?

No. It confirms the configuration check. A receiver still evaluates alignment, reputation, content and its own filtering policy.

What proves Zoho Assist 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 Assist 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 Assist 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 Assist 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. Email Domain Verification

    Sections Add domain name · Add TXT record · Verify domain ownership

  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