# SPF record for Postmark

URL: https://iblockspam.com/spf/postmark
Last updated: 2026-10-09

Include: None needed
Where it goes: Not needed (optional pm-bounces CNAME)
DNS lookups: 0 on your domain

You don't need to add Postmark to your SPF record. Postmark says mail sent through it always passes SPF, because the default Return-Path (pm_bounces@pm.mtasv.net) uses Postmark's own SPF record. To make SPF align with your domain for DMARC, add a custom Return-Path: a CNAME such as pm-bounces.example.com pointing to pm.mtasv.net.

## Example records

- Optional custom Return-Path (CNAME, not TXT) (CNAME, host pm-bounces): `pm.mtasv.net`
- Your main domain on Microsoft 365 stays as it is (TXT, host @): `v=spf1 include:spf.protection.outlook.com -all`
- Your main domain on Google Workspace stays as it is (TXT, host @): `v=spf1 include:_spf.google.com ~all`

## Notes

- Either DKIM or SPF alignment is enough to pass DMARC, so DKIM alone covers Postmark mail.
- Postmark's custom Return-Path is always a subdomain, so keep `aspf=r` (relaxed, the default) in your DMARC record. With `aspf=s`, Postmark mail can't pass DMARC through SPF.

## How to add it

- Set up DKIM for your sending domain in Postmark first: Postmark calls it the standard for email authentication.
- If you want SPF alignment too, add a CNAME record `pm-bounces` (the default label) pointing to `pm.mtasv.net`.
- In Postmark, open Signatures, choose DNS Settings for your domain and enter the Return-Path you created.
- Leave your main domain's SPF record unchanged.

## DKIM and DMARC

Postmark recommends DKIM as the main way to authenticate. With DKIM on your domain and an optional `pm-bounces` Return-Path, Postmark mail passes DMARC through both checks. Keep SPF alignment relaxed in your [DMARC record](https://iblockspam.com/blog/dmarc-record-examples).

## Common mistakes

- Adding a Postmark include to your root SPF record. Postmark says it is no longer required; it only spends lookups.
- Setting `aspf=s` in DMARC while relying on Postmark's Return-Path for SPF alignment.

**Q: Do I need to add Postmark to my SPF record?**
No. Postmark says it is no longer required: receivers check SPF on the Return-Path domain, and Postmark's default Return-Path already uses its own SPF record. Your main domain's record stays as it is.

**Q: How do I make Postmark mail pass DMARC with SPF?**
Add a custom Return-Path: a CNAME such as `pm-bounces.example.com` pointing to `pm.mtasv.net`, then enter it under Signatures, DNS Settings. SPF then aligns with your From domain under relaxed alignment.

**Q: Can I use aspf=s in DMARC with Postmark?**
Not if you need SPF alignment. Postmark's custom Return-Path is always a subdomain of your domain, so it can only align under relaxed SPF alignment (`aspf=r`, the default). DKIM alignment is unaffected.

Sources:
- Postmark Support: How do I set up SPF for Postmark?: https://postmarkapp.com/support/article/1092-how-do-i-set-up-spf-for-postmark
- Postmark Support: How do I add a custom Return-Path?: https://postmarkapp.com/support/article/910-adding-a-custom-return-path-domain

---

Source: iBlockSpam, https://iblockspam.com/spf/postmark (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt