Skip to content
SpoofKiller
Provider setup guides

DMARC for Postmark: DKIM and Return-Path Alignment

Make Postmark mail pass DMARC with a DKIM record and a custom Return-Path that aligns with your domain.

Reading time
6 min read
Last updated
Updated
Gloved hands sorting envelopes into a wooden pigeonhole rack on a purple background.
Transactional mail is sorted by what it can prove. Two DNS records decide which pigeonhole yours lands in.
In this guideShow 7 sections

Your password-reset emails are the most punctual employees you have. They work nights. They never ask for a raise. And if you send them through Postmark without finishing the DNS setup, they go out the door carrying somebody else’s identification. The mail arrives, usually. But when a receiver asks the DMARC question, which is “does anything authenticated here actually belong to the domain in the From line?”, the honest answer is a shrug.

Fixing this takes two DNS records and about ten minutes. One record gives Postmark a DKIM key under your name. The other gives your bounces a home address on your own domain. This guide walks through both, explains why each one matters, and shows how to prove the work is done before you tighten your policy.

What Postmark sends before you touch DNS

DMARC has one rule and it is stricter than it sounds. A message passes if SPF or DKIM passes and the domain that passed matches the domain your reader sees in the From header. Passing is not enough. The pass has to be yours. If that distinction is new, our explanation of DMARC alignment covers it in full.

Out of the box, a Postmark message from receipts@example.com has two identities that are not yours:

  • The Return-Path (the envelope sender, where bounces go) sits on a Postmark-owned domain. SPF is checked against that domain, so SPF passes, for Postmark.
  • The DKIM signature may be signed with a Postmark domain in the d= tag until you verify your own. That signature is valid. It is also about somebody else.

Two passes, zero alignment, one DMARC failure. Under p=none you will never notice. Under p=quarantine or p=reject your receipts go to spam or nowhere, which customers tend to notice on your behalf.

Step 1: Publish the Postmark DKIM record

In Postmark, open Sender Signatures and choose the Domains tab. Add your domain, or open it if it is already there, and look at its DNS settings. Postmark shows you a DKIM record: a TXT record whose hostname is a selector ending in pm, followed by ._domainkey.

Type:   TXT
Host:   20260114093012pm._domainkey.example.com
Value:  k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB...

That selector is an illustration. Yours will be different, and so will the key. Copy both the hostname and the value exactly from the Postmark dashboard. Do not retype them, and do not borrow them from a blog post, including this one.

Three things go wrong here, and they are always the same three:

  • The doubled domain. Many DNS hosts append your zone name automatically. Enter the full hostname and you publish …pm._domainkey.example.com.example.com, a record no one will ever look up. If your host appends, enter only the part before your domain.
  • The truncated key. A copy that loses the last few characters produces a key that looks fine and verifies nothing.
  • The helpful quotation marks. Some DNS panels add quotes for you. Add your own as well and the record now contains literal quote characters.

Once the record is live, press Postmark’s verify button, then check it independently. Paste the selector into the DKIM record checker and confirm that a public key comes back and that it is not empty. If nothing comes back, the DNS propagation checker will tell you whether the record is missing or merely slow.

With this one record in place, Postmark signs your mail with d=example.com. DKIM now aligns, and DMARC can pass on DKIM alone. You could stop here. You should not.

Step 2: Set a custom Return-Path

DKIM is a signature on the message, and signatures can break. A gateway rewrites a link, a mailing list adds a footer, and the hash no longer matches. When that happens you want a second aligned identity to catch the message. That is the custom Return-Path.

In the same DNS settings screen, Postmark asks for a CNAME record. The conventional hostname is pm-bounces, and it points to Postmark’s bounce domain:

Type:   CNAME
Host:   pm-bounces.example.com
Value:  pm.mtasv.net

Again, confirm both sides against what your dashboard shows. After you verify it, Postmark uses pm-bounces.example.com as the envelope sender. Receivers evaluate SPF against that name, follow the CNAME, and find Postmark’s SPF record, which authorizes Postmark’s servers. SPF passes, and this time the domain that passed is a subdomain of yours.

One record signs the letter. The other puts your return address on the envelope. DMARC needs only one of them to hold, which is the best argument for having both.

If your DNS lives at Cloudflare, set this CNAME to “DNS only.” A proxied record answers with Cloudflare’s addresses instead of Postmark’s name, and the Return-Path stops verifying. The Cloudflare DNS guide has the details.

Do you need Postmark in your SPF record?

Usually not, and this surprises people. SPF is checked against the envelope sender, not the From header. Once your Return-Path is pm-bounces.example.com, the SPF lookup happens at that name, where the CNAME hands it to Postmark. The SPF record at your root domain is never consulted for Postmark mail.

This is good news, because the root record has a budget of ten DNS lookups and every include spends some of it. If an old tutorial had you add a Postmark include years ago, check what your record costs today with the SPF checker. Before deleting anything, confirm in your reports that Postmark mail really is using the custom Return-Path. The guide to common SPF errors explains what happens when the budget runs out.

A warning about strict alignment

By default DMARC uses relaxed alignment: pm-bounces.example.com and example.com share an organizational domain, so they match. If your DMARC record contains aspf=s, alignment is strict, and the two names must be identical. They are not, so SPF alignment fails for every Postmark message.

DKIM is unaffected as long as you send from the exact domain you verified. But send from billing@mail.example.com while signing as example.com under adkim=s, and that fails too. Unless you have a specific reason for strict mode, leave both tags out and let the defaults do their job.

Step 3: Publish DMARC and read the reports

If you have no DMARC record yet, start with one that only watches. The DMARC record generator will build it, and the DMARC configuration guide explains each tag.

Host:   _dmarc.example.com
Value:  v=DMARC1; p=none; rua=mailto:reports@example.com

Within a day or two, receivers that participate in DMARC reporting begin sending aggregate reports. Look for the rows whose sending IPs belong to Postmark. A healthy row shows DKIM passing with your domain and SPF passing with pm-bounces.example.com, both aligned. Raw reports are XML, written for machines by machines; you can upload one to the DMARC report analyzer to read it as a table, or let SpoofKiller’s DMARC monitoring collect and sort them for you.

For a faster check, send yourself a message and paste its headers into the email header analyzer. You are looking for dkim=pass with your domain, spf=pass with your bounce subdomain, and dmarc=pass.

More than one stream, server, or domain

Postmark verifies DKIM and Return-Path per domain, not per server or message stream. Transactional and broadcast streams sending from the same domain share the same two records. A second sending domain needs its own pair. So does a subdomain if you add it to Postmark as a separate domain.

One trap deserves a sentence. Verifying a single sender address by clicking a confirmation email proves you can read that inbox. It does not publish DKIM for your domain. If your account has only confirmed addresses and no verified domain, your mail is not aligned yet.

And Postmark is rarely the only thing sending as you. Your mailbox provider, your CRM, and the invoicing tool someone signed up for in 2021 all need the same treatment before enforcement. The staged plan for reaching p=reject covers the whole inventory.

FAQ

Questions about DMARC for Postmark

Short answers to what readers ask next. If yours is missing, write to us and a person will reply.

Ask a question

Free, no obligation

Want a second pair of eyes on your records?

Send us your domain. We will look at its DMARC, SPF, and DKIM setup and write back, in plain English, with what we found and what to fix first.

  • A person reads your records, not a script
  • Specific fixes, in order of importance
  • No sales sequence afterward

We use your details to reply. Nothing else.

Reading about it is the slow way.

Run the free check and see your own domain's DMARC, SPF, and DKIM in the time it took to read this paragraph. No account, no card.