Overview
What you need depends on how you send mail with JetEmail:
The dashboard lists the exact names and values for your domain. Use those values; the examples below use
yourdomain.com — replace with your real domain.
SMTP: “Allow any domain”
If you use SMTP with allow any domain, you are only required to publish SPF for each sending domain. TXT record (typically at@ / root of the domain, or as your DNS host instructs):
Dashboard: domain verification records
When you add and verify a domain in the dashboard, JetEmail shows a fixed set of records. Add all of them in DNS. Names use your domain (e.g.yourdomain.com instead of noc.network in the examples below).
SPF
(Exact host may match what the dashboard displays for your provider.)
Return path (bounce domain)
The subdomain is not always
em12345 — JetEmail assigns a unique em… hostname per domain (e.g. em21157). Copy the exact name from your dashboard.
DKIM
DMARC
p=none is the minimum policy that satisfies verification. A stricter policy also passes — for example p=quarantine or p=reject — as long as DMARC is valid. See our DMARC guide if you want to tighten policy later.
After you publish DNS
- DNS can take a few minutes to propagate.
- The dashboard shows Verified next to each record when it’s correct.
- If something stays unverified, double-check hostnames (some panels append the domain automatically — avoid doubling
.yourdomain.com).
Why it matters
- SPF — Authorizes JetEmail to send for your domain.
- Return-path CNAME — Aligns bounces and infrastructure with our sending setup.
- DKIM — Cryptographic signing for your messages.
- DMARC — Policy and alignment on top of SPF/DKIM.