Authenticate your sending domain so emails to customers come from your address
(e.g. [email protected]) and aren't flagged as spam.
Pick a subdomain you control (e.g. mail.acmepest.com). Using a subdomain
keeps your reputation isolated from your primary domain. The "from" name is what
customers see in their inbox.
https://, no trailing slash. A subdomain like mail. is recommended.
Add these two records to 's DNS. Once propagated,
click Refresh status below — Postmark usually verifies within a few minutes.
| Purpose | Type | Hostname | Value | Status |
|---|---|---|---|---|
DMARC is the third email-auth layer. Without it, receivers like Gmail trust your mail less over time — even when DKIM and SPF pass. Publishing a policy starts in monitoring mode (no enforcement), and you get daily reports about who's sending as your domain.
| Type | Hostname | Value | Status |
|---|---|---|---|
DMARC tells receivers (Gmail, Yahoo, Microsoft) what to do when a message claims to be from your domain but can't prove it through SPF or DKIM. Without DMARC, that policy gap is left to the receiver's guess — which trends toward "trust less" over time.
The record above uses p=none, which means "don't reject anything, just send me reports."
Once you've watched the reports for a couple weeks and confirmed all legit mail is passing, you can
ratchet up to p=quarantine (sends spoofed mail to spam) or p=reject (bounces it
outright).
Reports go to . Make sure that mailbox
exists. They arrive as zipped XML files daily; tools like
dmarcian
or
Postmark's free DMARC monitor
parse them into a readable dashboard.
Sends a test email to your account address (). Works in stub mode too — useful for checking the integration end-to-end before DNS finishes propagating.