Postmark sends with its own Return-Path, so it does not need to be in your SPF record at all — Postmark says so itself. What it needs is its DKIM key published as a TXT record, and, to make SPF align for DMARC as well, a custom Return-Path CNAME on a subdomain of yours.
| SPF | Not needed on your domain |
| DKIM | TXT at <date>pm._domainkey |
| Bounce domain | pm.mtasv.net, or pm-bounces.<your domain> |
| Set up in | Postmark → Sender Signatures → your domain → DNS Settings |
Is your domain set up for Postmark?
We read your SPF record, look for Postmark’s DKIM key and check DMARC. Nothing is stored.
SPF for Postmark
Postmark: “It is no longer required to include Postmark in your own custom SPF record.” Its Return-Path already carries Postmark’s sending servers, and your root domain is not used as the Return-Path, so include:spf.mtasv.net there does nothing.
For SPF alignment, add a custom Return-Path: a CNAME pm-bounces.yourdomain.com → pm.mtasv.net. SPF then passes for a subdomain of yours, which aligns under DMARC’s relaxed default.
DKIM for Postmark
In Postmark, open Sender Signatures → your domain → DNS Settings. The DKIM record’s name is a timestamp followed by pm, unique to your account; the key is 1024-bit.
Until DKIM is verified, Postmark signs with its own domain and Gmail shows your mail “via pm.mtasv.net”.
When you rotate the key, Postmark creates a pending record and keeps signing with the old key until the new one verifies.
| Name | Type | Value |
|---|---|---|
<YYYYMMDDhhmmss>pm._domainkey | TXT | k=rsa; p=<key from Postmark> |
pm-bounces | CNAME | pm.mtasv.net |
The exact values come from Postmark; copy them from there. Placeholders are in angle brackets.
Bounce domain and DMARC
With DKIM verified, Postmark mail passes DMARC on DKIM. With the pm-bounces Return-Path too, it passes on SPF as well. Without either, it fails DMARC once your policy is enforced.
No DMARC record yet? Start with one that only reports, read the reports for a couple of weeks, then tighten it: build it with the DMARC generator.
Common mistakes
- Adding include:spf.mtasv.net to the root SPF record and expecting SPF to align — it cannot.
- DNS hosts that append the domain, producing …pm._domainkey.yourdomain.com.yourdomain.com; enter the host without the domain.
- On Cloudflare the pm-bounces CNAME must be DNS only (grey cloud), or it will not verify.
- The pm-bounces subdomain must not already have other records.
Questions
Why is my DKIM selector a long number?
Postmark names each key by the time it was created, followed by pm. Copy it from DNS Settings; it is different for every account and changes when the key rotates.
Sources
Checked against Postmark’s own documentation on 25 September 2026:
- How do I set up SPF for Postmark? — postmarkapp.com
- How do I add a custom return-path? — postmarkapp.com
- How do I set up DKIM for Postmark? — postmarkapp.com