Email-in with Postmark
Step-by-step configuration for Postmark Inbound.
Postmark is what we recommend for inbound mail — high deliverability, good parsing, reasonable pricing.
What you'll set up
- A Postmark Inbound server.
- An inbound address pointing at Postmark's MX.
- A webhook on that server pointing at Nura24.
Step 1 — Create a Postmark Inbound server
- Sign in to Postmark.
- Servers → Add server.
- Name it (e.g. "Nura24 Inbound").
- Pick "Inbound" mode.
You get an inbound address that looks like <random>@inbound.postmarkapp.com. You can also configure a custom inbound domain — see step 3 if you want tickets@inbox.acme.com instead.
Step 2 — Configure the webhook
In the new server's Settings → Webhooks:
- Inbound Webhook URL:
https://api.nura24.com/email/inbound?secret=<your-platform-secret> - (Or use a custom header — Postmark supports basic auth on the webhook URL; use that to pass the secret if you'd rather not have it in the query.)
- Save.
Send a test inbound message to your Postmark inbound address. Postmark posts to us; the ticket appears in your workspace inbox within a few seconds.
Step 3 — Custom inbound domain (recommended)
The default <random>@inbound.postmarkapp.com address works but looks weird in your "email us at..." messaging. To use tickets@inbox.acme.com instead:
- In Postmark, Servers → [your server] → Settings → Custom inbound domain.
- Postmark gives you DNS records to add to
acme.com. - Add the MX record on
inbox.acme.compointing at Postmark's servers (Postmark provides the exact value). - Verify in Postmark. Once verified, your inbound address becomes
<token>@inbox.acme.com.
Now customers can email tickets+<your-inbox-token>@inbox.acme.com (or a forwarded address) and Postmark routes it to us.
Step 4 — Tell Nura24
Settings → Tickets → confirm the inbound address shown matches what you're advertising. The token is auto-generated; you reference it in customer-facing communication.
Common Postmark gotchas
- Stripped vs full body — Postmark's
TextBodyfield strips email signatures and quoted text from the reply. Our parser uses this when present, falling back to the full body otherwise. Result: clean ticket descriptions in most cases. - Spam scoring — Postmark assigns a spam score to inbound. We don't currently reject high-score messages; they create tickets like anything else. If spam becomes a problem, configure a filter rule in Postmark to drop high-score before webhook.
- Bouncebacks — replies sent from agent inbox aren't yet emailed back to customers (it's on the roadmap). Don't set up outbound bounce handling yet.
Pricing
Postmark Inbound is metered. Their free tier covers the typical small workspace; check their current pricing for your volume.