Fix guide

How to Fix DMARC Alignment for Postmark

Postmark makes alignment easy: add their bounce CNAME + DKIM TXT — two moves, done.

Why Postmark trips DMARC

You skipped sender signatures — Postmark can’t line up DKIM or bounce-path SPF with your From: domain until those records exist. That’s alignment in a nutshell.

Exact DNS records

pm-bounces.yourdomain.com → CNAME → (target from Postmark) DKIM TXT at host shown in Postmark (e.g. pm._domainkey or similar)

Step-by-step fix

Step 1 Postmark → Sender Signatures → your domain
Step 2 Copy the DKIM TXT record Postmark provides
Step 3 Add Return-Path CNAME (e.g. pm-bounces) for bounce domain
Step 4 Add records at your DNS provider
Step 5 Wait for green verification in Postmark
Step 6 Confirm DKIM and SPF alignment with DNS Preflight

Run your domain through DNS Preflight

Open DNS Preflight →

FAQ

What are the Postmark DMARC alignment steps?

Add DKIM TXT and Return-Path CNAME from Postmark's Sender Signatures, verify in Postmark, then confirm with DNS Preflight.

Why is Postmark easier than other ESPs for alignment?

Postmark uses a small, clear set of DNS records and strong documentation — typically DKIM TXT plus one bounce CNAME.

How do I verify Postmark DNS?

Postmark dashboard shows verification status. DNS Preflight can confirm public DKIM and SPF records.

Can I get both SPF and DKIM alignment with Postmark?

Yes — the Return-Path CNAME enables SPF alignment; DKIM TXT enables DKIM alignment.

Does Postmark support DMARC p=reject?

Yes when alignment passes — monitor reports when tightening policy.