Postmark names each DKIM key after the moment it was made, followed by pm — 20131031155228pm, say — and publishes it as a TXT record. A new key gets a new name, so rotating means adding a record, not changing one.
| Whose | Postmark — transactional email |
| Selector | <date and time>pm |
| Published as | A TXT with the key, at a name made of the date and time the key was made, then pm |
| Key | 1024-bit RSA |
| Rotation | By hand, which Postmark recommends every three months: Sender Signatures → DNS Settings → Generate New |
| Before you set it up | Gmail shows “via pm.mtasv.net”, Postmark’s return-path domain |
| Where to find it | Sender Signatures → the domain → DNS Settings |
| Can it go? | An old key once the new one verifies — Postmark says when it is safe, and suggests waiting a few days. |
Is Postmark’s key on your domain?
Postmark makes a selector for each account. Enter a domain and the selector it gave you — or paste the DKIM-Signature header of a message it sent — and we check the key, and name every other key the domain publishes.
The records
What Postmark asks you to publish, with its own values in place of the placeholders:
20240101123456pm._domainkey.example.com TXT k=rsa; p=<public key>
Common mistakes
- A doubled domain in the name: …pm._domainkey.example.com.example.com.
Setting up Postmark from scratch? Its SPF, DKIM and DMARC records, and a check of all three.
Questions
Postmark shows a different selector from the one in my DNS. Which is right?
Both, for a while: after a rotation the new key has a new name, and the old record can go once Postmark says it is safe to remove.
Sources
Checked on 27 September 2026 against these official sources:
- How do I set up DKIM for Postmark? — postmarkapp.com
- How often should I generate/rotate a new DKIM key? — postmarkapp.com
- Domains API — Postmark Developer Documentation — postmarkapp.com