include:spf.mtasv.net lists Postmark’s sending servers. Postmark stopped asking for it in 2017: its mail carries Postmark’s own return-path, so SPF checks Postmark’s domain. In Postmark’s words, adding the include “will do nothing for you because it will be for your root domain which is not used in your Return Path”. For SPF that aligns, set up the custom return-path CNAME instead.
v=spf1 a mx include:spf.mtasv.net ~all
| Belongs to | Postmark — transactional and broadcast streams |
| Needed on your domain? | No — SPF checks a different domain for its mail, not this record on yours |
What it costs, and is it in your record?
We measure include:spf.mtasv.net as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Postmark’s is there and what it costs.
What it covers
All mail sent through Postmark, transactional and broadcast.
Do you need it?
No. Postmark’s default return-path is pm_bounces@pm.mtasv.net, and “the Return-Path of all emails sent through Postmark already includes our outbound sending IPs and SPF record”. It is “no longer required to include Postmark in your own custom SPF record”.
For SPF alignment with DMARC, add the custom return-path: pm-bounces.yourdomain.com as a CNAME to pm.mtasv.net. That name then carries Postmark’s SPF record, so no include is needed on any name.
Common mistakes
- Adding the include instead of the CNAME: “The effect will not be the same.”
- Putting an SPF TXT record on the return-path subdomain — a name with a CNAME can have no other records.
- DMARC with aspf=s: the custom return-path is always a subdomain, so it can never match strictly.
Includes it replaced
Postmark asked for include:spf.mtasv.net until its domain-authentication update of October 2017, which replaced it with the return-path CNAME.
Setting up Postmark: SPF, DKIM and DMARC together →
Questions
Is it harmful to keep include:spf.mtasv.net?
It costs one of your 10 lookups and does nothing for Postmark’s mail. If nothing else sends from Postmark’s servers as your domain, it can go.
Sources
Checked on 26 September 2026 against these official sources:
- How do I set up SPF for Postmark? — postmarkapp.com
- Why is it not required to include Postmark in our own custom SPF record? — postmarkapp.com
- How do I add a custom return-path? — postmarkapp.com
- Why we no longer ask for SPF records — postmarkapp.com