Postmark domain verification applies when an application already sends through Postmark: the domain to verify is the exact one in its From address, and the proof is a message sent through that application’s Postmark route. The account check and the received-message check are separate: passing one does not mean you have passed the other.
I checked the Postmark setup instructions against Postmark’s documentation on 10 September 2026.
Confirm the sender and access
You need an active Postmark account permitted to send your test message, and you need to know which application route and intended From address you are verifying. The domain should be managed by an Account Owner or Account Admin, with the domain owner’s authorization and access to publish DNS records (Postmark: verifying DKIM, step 4). If any prerequisite is missing, stop here.
A Sender Signature approves an individual address, whereas domain verification authorizes addresses across that domain, so confirming a Sender Signature alone does not complete domain authentication (Postmark: address approval and domain authorization).
Before changing DNS records, record the DMARC policy that applies. Start at _dmarc under the exact From domain and determine any applicable parent policy as RFC 9989 section 4.10.1 describes. Check adkim and aspf: s selects strict alignment, r relaxed alignment, and an omitted mode defaults to relaxed (RFC 9989 section 4.7). The existing policy stays as it is while you add this sender.
Publish the account’s DKIM record
In Sender Signatures, choose Add Domain if the intended domain is not listed yet, then open its DNS Settings (Postmark: how to get your DKIM records). Keep that tab open beside your DNS editor.
| Setup item | DNS record | Name and value to use | Account checkpoint |
|---|---|---|---|
| DKIM | TXT | This domain’s displayed Hostname and complete Value Postmark: adding the record to your DNS | Run Verify and obtain verified status Postmark: verifying the setup |
| Optional custom Return-Path | CNAME | Displayed Hostname; displayed Value, documented as pm.mtasv.net Postmark: verifying custom Return-Path | Obtain verified Return-Path status Postmark: verifying custom Return-Path |
Check whether your DNS editor appends the zone name automatically: the full record name must match Postmark’s hostname without a duplicated suffix. Copy the complete public key from the account interface, never an example selector or truncated key (Postmark: adding the record to your DNS).
Save the TXT record, return to DNS Settings, and click Verify (Postmark: verifying the setup). Successful verification enables DKIM signing and domain-wide sending authorization (Postmark: verification and domain-wide sending). If the result reads Not Verified, investigate the discrepancy before continuing. Postmark documentation notes varying propagation windows, and waiting on its own does not confirm validation (Postmark: DKIM verification status, Postmark: domain verification status).
Do you need a custom Return-Path in Postmark?
Postmark’s default bounce domain is pm.mtasv.net (Postmark: what is the Return-Path?). Postmark manages SPF for that path, so adding include:spf.mtasv.net to your root-domain SPF record is neither required for it nor a replacement for the custom Return-Path CNAME (Postmark: default SPF and existing SPF records).
A custom bounce subdomain gives you another possible aligned authentication path. Strict alignment requires identical domains; relaxed alignment requires a shared Organizational Domain (RFC 9989 section 4.4). A passing, aligned DKIM signature can support DMARC on its own even when SPF is unaligned (RFC 9989 section 4.4.1).
If you configure this path, select an unused bounce hostname from DNS Settings. Publish the CNAME from the table; if you use a different supported alias, specify the same alias in Postmark’s Return-Path settings (Postmark: custom Return-Path setup). Provider documentation references both pm_bounces and pm-bounces, so use the specific hostname shown in your account (Postmark: custom Return-Path hostname, Postmark: why set a custom Return-Path?).
Do not add an SPF TXT or conflicting record at that exact CNAME name. If the name is already claimed, resolve the conflict with its owner or pick another supported alias (Postmark: CNAME and SPF at the same name). Confirm that the Return-Path is verified in the dashboard before relying on it (Postmark: verifying custom Return-Path).
If no applicable DMARC policy exists, the message cannot be counted as a DMARC pass (RFC 9989 section 5.3.2). In that case, pause this test while the domain owner prepares the broader DMARC rollout; the guide chapter on rolling out DMARC without breaking your email covers that work. That rollout needs working authentication (RFC 9989 section 5.1.4) and a destination that receives aggregate reports (RFC 9989 section 5.1.3). What remains is an owner-controlled initial monitoring policy such as p=none with the real report address (RFC 9989 section 5.1.4), covering author and Organizational Domains where they differ, and a process to review incoming data (RFC 9989 section 5.1.5). The sender inventory workflow establishes your sending scope. Return once these prerequisites are active; do not lower an existing policy to make this test pass.
Test the application route
Send one test message through your application to an external mailbox where you can get the original message source, and inspect the Authentication-Results produced by the receiving service you trust. If you cannot establish who produced the results, ask the receiving service to confirm them; until then, validation is incomplete (RFC 8601 section 1.2).
Record each result with its identity: dkim with header.d and the selector when supplied (RFC 8601 section 2.7.1), spf with smtp.mailfrom (RFC 8601 section 2.7.2), and dmarc with header.from (RFC 9989 section 9.1). Save a copy of the raw headers for troubleshooting or future reference.
The example that follows is synthetic; no message was sent for this article. Both cases use From: receipt@notify.example.com and an applicable policy of adkim=s; aspf=r. In Case A, the account verified the alias bounces. Assume that the receiver’s Organizational Domain discovery establishes example.com for both the From domain and the bounce domain, with no boundary between them; the shared suffix alone does not establish this (RFC 9989 section 4.10.2). In Case B, pm.mtasv.net belongs to a different Organizational Domain and no other passing, aligned DKIM signature exists.
| Receiver result | Case A | Case B |
|---|---|---|
| DKIM | dkim=pass header.d=notify.example.com | dkim=fail header.d=notify.example.com |
| SPF | spf=pass smtp.mailfrom=pm_bounces@bounces.notify.example.com | spf=pass smtp.mailfrom=pm_bounces@pm.mtasv.net |
| DMARC | dmarc=pass header.from=notify.example.com | dmarc=fail header.from=notify.example.com |
The bounce local-part shown here is illustrative. In Case A, DKIM matches exactly (satisfying strict alignment mode) and SPF shares the assumed Organizational Domain (satisfying relaxed mode), so both align under the stated modes (RFC 9989 section 4.4). In Case B, neither identity passes with alignment, causing DMARC to fail (RFC 9989 section 5.3.5). That failure points to the missing aligned path, not to a particular DNS defect.
Under strict SPF alignment (aspf=s), A’s bounces.notify.example.com would not align with notify.example.com because the domain strings differ (RFC 9989 section 4.4); however, its aligned DKIM signature would still satisfy DMARC on its own (RFC 9989 section 5.3.5). Likewise, if B’s DKIM result were pass, DMARC could pass despite the same unaligned SPF (RFC 9989 section 4.4.1).
When DKIM is Not Verified or the bounce domain is wrong
Pause rollout while any planned authentication path remains unverified. For Not Verified DKIM, compare the published record name and value against the Postmark dashboard: eliminate copying errors, remove trailing spaces, check for duplicated domain suffixes, and consult your DNS host if character length limits prevent you from publishing the complete value. Proxied Return-Path CNAMEs must be changed to DNS Only (Postmark: troubleshooting common DKIM issues).
If delivered messages continue to show the default bounce domain when you intended a custom Return-Path, compare the alias in Postmark with DNS (Postmark: custom Return-Path setup) and check its verification state (Postmark: verifying custom Return-Path). Correct the mismatch, reverify (Postmark: verifying custom Return-Path), then send a new test from your application and inspect the resulting headers (RFC 8601 section 2.1). If DNS entries match but DKIM continues to fail, save the original message and Postmark status for investigation; another DNS edit is not an established remedy.
If your organization requires strict SPF alignment, the subdomain example does not meet it; resolve that requirement separately and still check the DKIM result on its own. A passing test confirms authentication for that specific route and message, and even clean DMARC alignment does not promise inbox delivery (RFC 9989 section 1). For guidance on evaluating identities, see Compare DMARC authentication identities.
Frequently asked questions
Do I need to add include:spf.mtasv.net to my SPF record?
No. Postmark handles SPF on its own bounce domain rather than your apex zone. Adding include:spf.mtasv.net to your root SPF record is unnecessary and does not configure an aligned custom Return-Path.
Is a Sender Signature enough to authenticate my domain?
No. A Sender Signature only confirms sending permission for an individual email address. Domain verification signs outbound mail with DKIM for the whole domain and lets you send from any address at it.
Is a custom Return-Path required for DMARC to pass?
No. A custom bounce subdomain gives you another possible aligned authentication path, but a passing, aligned DKIM signature can support DMARC on its own even when SPF is unaligned.
Can a message pass DMARC if no DMARC policy exists?
No. A message cannot produce a DMARC pass without an applicable DMARC policy published in DNS. Publish at least a monitoring policy at _dmarc before attempting to validate DMARC alignment.
Why does Postmark show DKIM as Not Verified?
Compare the published name and value with the current account fields: correct copying errors or extra spaces, check for suffix duplication, and ask your DNS host for help if TXT length limits prevent you from publishing the complete value. A proxied Return-Path CNAME needs to be set to DNS Only.


