Connect Postmark to SiteOps
Ask senders which service most reliably reaches the inbox and Postmark's name comes up first. Its whole reputation rests on strictness: new accounts are reviewed, every sender is verified, and inboxes trust mail from it precisely because of that gatekeeping.
That trust is what you are borrowing here. The emails SiteOps drafts and you approve take Postmark's route out — sent from your address, with the sent, opened and clicked counts flowing back into the dashboard.
Postmark organises sending into servers, and each server has its own API token — that token is what you paste into SiteOps. Before it can send, Postmark also wants proof the from address is yours: a quick sender signature, or a full domain verification. The setup below walks both roads.
Set it up, step by step
0 of 7 done
- Sender signatures
- Add domain or signature
- Servers
- Message streams
- Servers
- API Tokens
The server token's journey — from the API Tokens tab to one SiteOps field - Settings
- Postmark
- Save
Let an agent do it
If you go the domain verification road, an agent with access to your DNS can add the DKIM and Return-Path records for you.
Add Postmark's domain verification records to my DNS.
1. I am verifying <my sending domain> in Postmark. Its verification screen shows two records — here they are exactly as displayed: a DKIM TXT record (host like <timestamp>._domainkey.<my domain>, value <the DKIM value>) and a Return-Path CNAME (host pm-bounces, target <the CNAME target Postmark shows>).
2. Open the DNS zone for the domain at <my DNS host> and add both records with the exact type, host and value. Keep Postmark's full DKIM host, timestamp prefix included — do not shorten it.
3. Check both: dig TXT <dkim host> +short and dig CNAME pm-bounces.<my domain> +short.
4. Tell me when they resolve so I can press Verify in Postmark.Creating the account, Postmark's approval review, pressing Verify and copying the server token into SiteOps stay with you.
If something does not work
- Postmark rejected my from address
- The address is not verified. Either add it as a sender signature and click the confirmation link Postmark sends, or verify the whole domain — then make sure the from address in SiteOps settings matches what you verified, exactly.
- The token saved but my emails still sit as drafts
- The from address is the missing half. Open the Email section in SiteOps settings and set the sender name and address. The draft's note says exactly which half the gate is waiting on.
- I can only send to my own domain
- Your account is still in Postmark's review period — every new account starts that way. Check the request-approval banner in the Postmark dashboard, answer what they ask, and full sending unlocks once approved.
- Why does Postmark have two kinds of streams?
- Deliverability. Receipts and password resets earn a near-perfect reputation; newsletters live a riskier life. Keeping them on separate streams means a rough newsletter never makes your receipts land in spam. SiteOps mail is the newsletter kind — keep it on a broadcast stream.
- I connected both Postmark and Resend — which one sends?
- The one named in the 'Sends go through' picker in SiteOps Settings — an explicit choice, never a guess. Both can stay connected; only the picked provider sends, and switching takes one click in the Email section.