Postmark
Postmark DMARC setup: DKIM, Return-Path and SPF alignment
Postmark DMARC setup: publish the DKIM TXT and the Return-Path CNAME so DKIM and SPF align, then add a DMARC record at p=none and read your reports.
Check your current setup:
How Postmark authenticates your mail
A Postmark DMARC setup needs three DNS records on your domain: a DKIM TXT record, a custom Return-Path CNAME and a DMARC TXT record. DMARC is a DNS policy that tells receivers what to do with mail that fails authentication. It passes when DKIM or SPF passes for a domain that aligns with your From address. In DMARC's default relaxed mode, aligned means both names share the same organizational domain.
Postmark starts signing mail from your domain after it verifies your DKIM record. DKIM is a signature that receivers check against a public key in your DNS.
By default, Postmark uses its own domain, pm.mtasv.net, as the Return-Path. That is the address that collects bounces, and it is the domain SPF checks. SPF passes there without any change on your side. But pm.mtasv.net does not match your From domain, so SPF does not align.
A custom Return-Path solves this. You point a subdomain of your domain at Postmark with a CNAME, and the Return-Path moves to your domain. You do not need include:spf.mtasv.net in your root SPF record for this, because that record is not the one SPF checks here.
Step 1: Add the domain
In Postmark, open Sender Signatures and click Add Domain. Then open DNS Settings next to the domain to see its records.
A Sender Signature confirms one address. Verifying the domain covers every address on it, and that verification needs the DKIM record below.
Step 2: Publish the DKIM record
Postmark creates a unique key for each domain. It shows a TXT record whose host is a timestamp followed by pm. Its API documentation uses 20131031155228pm._domainkey as an example.
Your host will be different. Copy the host and value from DNS Settings, create the TXT record, then click Verify in the DKIM section. Postmark says the record should show as verified within 48 hours. After that, you can confirm the published key with the DKIM checker, using the part of the host before ._domainkey as the selector.
Step 3: Add a custom Return-Path
Choose an unused Return-Path subdomain. Check its existing DNS first; a CNAME cannot share its name with TXT, MX or other data. Do not overwrite an active service. Then create the CNAME record:
- Host:
pm-bounces(the default; you can use another name if it matches in Postmark and in your DNS) - Value:
pm.mtasv.net
In the Return-Path section of DNS Settings, confirm the same name and click Verify. Bounces then use pm-bounces.example.com, which aligns with example.com in relaxed mode, DMARC’s default.
The CNAME sits on its own subdomain, so it does not touch the records on your root domain.
Step 4: Publish DMARC
Create a TXT record named _dmarc:
Use this starter value only if no DMARC policy exists at this name. Otherwise edit the existing record, preserving its p=, alignment settings and report addresses; add your monitored rua destination there. Never create a second policy record.
v=DMARC1; p=none; rua=mailto:dmarc@example.com
p=none states no preference about how receivers handle mail that fails, and it lets you collect reports while you monitor. Replace the address after mailto: with the reporting address from your DMARC Pulse panel. Receivers then send their aggregate reports, XML summaries of the mail they saw from your domain, to that address. If your domain already has a _dmarc record, edit it instead of creating a second one.
Once DKIM and the Return-Path are verified, Postmark should appear in your reports with both aligned.
Step 5: Check, then tighten the policy
Send a test and paste its headers into the email header analyzer. Look for dkim=pass, spf=pass with smtp.mailfrom showing pm-bounces.example.com (some receivers include the full address), and dmarc=pass.
Read the reports before you tighten anything. Postmark’s records only cover mail sent through Postmark, so every other service that sends as your domain has to authenticate on its own. Postmark’s DMARC guide suggests a few months of clean reports before p=quarantine. Move to p=reject only when legitimate mail keeps passing, because a stricter policy can block real mail from a sender you missed. Afterwards, the DMARC checker confirms what is published.
Common problems
- SPF passes but DMARC says it does not align.
smtp.mailfromstill showspm.mtasv.net, so the custom Return-Path is missing or unverified. If DKIM passes and aligns, DMARC still passes in the meantime. - DKIM will not verify. Some DNS hosts add your domain to the name you type, and the record lands on
20131031155228pm._domainkey.example.com.example.com. Enter only the part before your domain. Also remove leading or trailing spaces from the host and value. Postmark says some older DNS hosts limit TXT length and suggests asking them about string splitting. - Return-Path will not verify. Run
dig pm-bounces.example.com CNAME. The answer should bepm.mtasv.net. If you seepm.mtasv.net.example.com, your host appended the domain. Enter the value with a trailing dot:pm.mtasv.net. - Cloudflare proxy on the Return-Path CNAME. Postmark says the proxy can interfere with verification. Set the record to DNS only.
- Extra SPF at
pm-bounces. A CNAME cannot coexist with other data at the same name. Do not add SPF TXT there: Postmark’s CNAME target already supplies the SPF policy. Preserve an existing active service and choose a free name instead of overwriting it. aspf=sin your DMARC record. Postmark’s Return-Path subdomain cannot exactly match a parent From domain. Keep the policy and use passing DKIM withd=exactly matching From. Relaxingaspfis a deliberate domain-wide choice, not a required repair; DMARC needs only one passing aligned mechanism.- Bounces that mention your DMARC policy. Your policy is rejecting mail that has no aligned authentication. Postmark’s fix is to verify DKIM and add the custom Return-Path.
- Sending from a subdomain. Each subdomain is added to Postmark separately and gets its own DKIM and Return-Path records. To send fully authenticated mail from
mail.example.com, add and verify that subdomain as well. - Apple Private Email Relay. Postmark says this is the case where an SPF record is required, and it gives this value:
v=spf1 include:spf.mtasv.net ~all
Postmark's article does not say which DNS name takes this record. Apple requires an SPF TXT record on each domain you register for the relay, so publish it there. If that domain already has an SPF record, add include:spf.mtasv.net to it. A domain must not publish two SPF records.
- Older advice about
pct. Postmark’s DMARC guide describes ramping up with thepcttag. RFC 9989, the current DMARC standard, removed that tag, so tighten thepvalue in steps instead.