Insights:Business Email SPF/DKIM/DMARC Configuration: Steps and Common Mistakes
Step 1: SPF
Add a TXT record to the domain DNS:
v=spf1 include:mail-service-spf-domain -all
Key points:
- A domain can have only one SPF record.
- Include all mail sending sources.
- Do not exceed 10 DNS lookups.
- Monitor first; switch to
-allonce you confirm no漏.
Verify:
dig TXT example.com
Step 2: DKIM
Generate keys in the email service provider admin panel and write the public key to DNS:
selector._domainkey.example.com TXT "v=DKIM1; k=rsa; p=..."
Key points:
- The selector must match the actual sending config.
- Use the key length required by the provider.
- When rotating keys, keep the old record active for a while.
- Multiple sending sources may have separate DKIM records.
Step 3: DMARC
_dmarc.example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
Policy progression:
p=none: Monitor only, collect reports.p=quarantine: Failed messages are sent to spam.p=reject: Reject failed messages.
Do not skip the monitoring period and go straight to reject.
Common Mistakes
- Multiple SPF records — recipient cannot determine which to apply.
- Forgot to include a marketing platform or overseas sending service in SPF.
- Wrong DKIM selector, so the signature does not match.
- No DMARC report address — issues go unseen.
- Applying reject immediately also blocks legitimate mail.
- Configured only the root domain and ignored subdomains and sending domains.
- No post-configuration test; you only find out when customers complain.
Rollout Pace
| Phase | Action | Observation |
|---|---|---|
| Week 1 | SPF + DKIM | Normal send/receive, bounces |
| Weeks 2–4 | DMARC p=none | Report sources |
| Weeks 5–8 | p=quarantine | Misclassifications and missing configs |
| After stabilizing | p=reject | Ongoing monitoring |
Checklist
- Send a test email from an external mailbox and check the authentication result.
- Use an email-testing tool to verify whether SPF / DKIM / DMARC pass.
- Check subdomains and marketing platforms.
- Keep a report inbox and review it regularly.
- Record all configuration changes.
Boundaries
Correct configuration lowers the chance of forgery and landing in spam, but it cannot guarantee delivery to the inbox. Content quality, sending frequency, recipient-side policies, and domain reputation all affect the outcome.
Related Articles: