Postmark: verify your domain
What this guide is for
Postmark sends your transactional emails. Domain verification relies on a DKIM key (required) and a Return-Path CNAME (optional but strongly recommended) that aligns SPF with your domain for DMARC.
Expected records
| Type | Name (host) | Value |
|---|---|---|
| TXT (DKIM) | <timestamp>pm._domainkey (e.g. 20231012153021pm._domainkey) |
public key provided by Postmark (k=rsa; p=...) |
| CNAME (Return-Path) | pm-bounces |
pm.mtasv.net |
| TXT (DMARC) | _dmarc |
v=DMARC1; p=none; rua=mailto:[email protected] |
- The DKIM selector is unique to your domain (a timestamp followed by
pm): copy the name and value shown by Postmark. - The
pm-bouncesname is a default. You can choose another one, as long as it is identical in Postmark and in your DNS. - With the custom Return-Path, SPF is evaluated on
pm-bounces.example.com: no include is needed in your root domain's SPF record.
Steps in Postmark
- In Postmark, open Sender Signatures and add your domain (Add Domain).
- Postmark shows the DKIM record and the Return-Path CNAME. Create them at your DNS host.
- Return to Postmark and click Verify next to each record. Postmark also rechecks DKIM every five minutes; validation can take up to 48 hours.
Cloudflare: turn off the proxy (orange cloud) on the Return-Path CNAME, otherwise Postmark cannot verify it.
Check the setup
- In Postmark, DKIM and Return-Path should both be verified.
- Send a test email to Gmail and check for
DKIM: PASSwith your domain, andSPF: PASSwithpm-bounces.example.com. - Run a new scan in this tool. The Postmark selector contains a timestamp: it is recognized if it is among the scanned selectors.
DMARC
Publish a single TXT record at _dmarc.<your domain>, starting with monitoring:
v=DMARC1; p=none; rua=mailto:[email protected]
DMARC compares the Return-Path domain with your From domain: without a custom Return-Path, SPF alignment fails and only DKIM can make DMARC pass. Read the reports for a few weeks, then move gradually to p=quarantine and p=reject.