DextelDocs

Connect Postmark

Fast transactional delivery. Unsigned webhooks (the private URL token authenticates them) and an inbound message stream.

Where this lives in Dextel

Agency: Agency → Integrations → Email Service (outbound only). Sub-account: Settings → Integrations → Email Integration (outbound + inbound). The modal shows the exact webhook URLs to paste into Postmark; this page explains what to do with them.

Prerequisites

  • A Postmark account and a domain you control (you'll add DNS records).
  • Owner or admin access to the Dextel agency or sub-account.
  • Credentials you'll enter in Dextel: Server API token, Message stream (optional).

1. Create the API credentials

  1. Open your Server → API Tokens → Create token.
  2. Use a Server token (Account tokens can't send).
  3. Paste it into Dextel. Leave Message stream blank unless you use a custom one.

Postmark docs: API keys

2. Verify your sending domain

  1. Open Sender Signatures → Domains → Add Domain.
  2. Add the DKIM TXT record and the Return-Path CNAME (pm-bounces → pm.mtasv.net).
  3. Click Verify next to each record.
  4. In Server → Message Streams → Default Transactional Stream → Settings, turn on open and link tracking.

Then in Dextel enter a From email on that domain (for example hello@yourdomain.com) and a From name, and click Validate & Connect. Dextel checks the credentials against Postmark before saving.

Postmark docs: domains

3. Delivery events

Delivered, opened, clicked, bounced and spam events feed the Email Event workflow trigger and automatically unsubscribe contacts after a hard bounce or complaint. Copy the Webhook URL from the Delivery events tab in Dextel, then:

  1. Open Server → Message Streams → Default Transactional Stream → Webhooks → Add webhook.
  2. Paste <your delivery-events webhook URL> as the Webhook URL.
  3. Tick Delivery, Bounce, Spam Complaint, Open and Click, then Save.
  4. Keep the URL private — Postmark doesn't sign webhooks, the token inside the URL is what authenticates them.
This provider does not sign its webhooks. The webhook URL Dextel gives you contains a private token that authenticates each post — never share the URL.

Use Send a test email in the same tab to confirm outbound works; the events pill turns green once the first event arrives.

Postmark docs: webhooks

4. Inbound email (sub-accounts only)

Inbound turns contact replies into Inbox conversations and fires the Contact Replied — Email trigger. Mail is received at your saved From address, so when a contact hits Reply the message comes back through Postmark to Dextel. The MX record routes all mail for that domain to Postmark: if you already receive mail on the domain, send from an address on a subdomain (for example hello@mail.yourdomain.com).

DNS records

TypeHostValuePriority
MXyourdomain.cominbound.postmarkapp.com10

Steps

  1. Add an MX record for yourdomain.com pointing to inbound.postmarkapp.com (priority 10).
  2. Open Server → Message Streams → Default Inbound Stream → Settings.
  3. Set Inbound domain forwarding to yourdomain.com and the Webhook to <your inbound webhook URL>, Save, then Check DNS.
  4. Send a test email to your From address.

Limits

  • Inbound messages over 35 MB are rejected.

Postmark docs: inbound

Troubleshooting

  • "Inactive recipient" — Postmark suppresses addresses that hard-bounced; reactivate them under Suppressions.
  • Sends work but no events — the webhook must be on the same message stream you send from.
  • Still stuck? Compare with another provider on the Email Providers overview.