Sending with Postmark?

Postmark email landing wrong or not at all? We bring it back.

Postmark is usually the thing that just works until a receipt stops arriving at a Yahoo address, DMARC shuts down the help desk's inbound mailbox, or the webhook that parses replies starts dropping attachments. We walk the DNS, the message stream and the webhook handlers until the delivery picture is clean on every major provider.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

postmark-send.log

still broken

What it is

Postmark at a glance

Postmark is a transactional email service from the ActiveCampaign group, aimed at the messages that have to arrive: receipts, password resets, invoices, notifications and the like. It separates transactional and broadcast streams precisely because mixing them is what gets senders into reputation trouble.

The API is small on purpose: send a single message, send a batch, use a template, parse an inbound reply, subscribe to a webhook on delivery or bounce. Behind that are message streams, approved sender signatures, DKIM, DMARC alignment, and bounce handling that teams discover the hard way when a redeploy or a DNS change knocks something out of place.

Type
Transactional email service
First released
2010
License
Proprietary SaaS, per-message pricing
Maintained by
Wildbit (part of ActiveCampaign)
Typically used for
Transactional email, receipts, password resets, invoices, inbound parsing

The honest version

Postmark pros and cons

No technology is all upside. This is where Postmark earns its place and where it tends to cause trouble.

Where Postmark is strong

  • Reputation is actively protectedPostmark separates transactional and broadcast streams and refuses to send marketing blasts on the transactional IPs, which is why the inbox rates stay as high as they do.
  • The dashboard shows real deliverabilityPer-message events, bounces, spam complaints and delivery times are visible per recipient rather than hidden behind an aggregate graph.
  • Inbound parsing is first classYou get a parsed JSON webhook with headers, attachments and the parsed text, which saves building your own MIME parser for help desk style flows.
  • Simple, stable APIThe surface is small enough to learn in an afternoon, and the SDKs across most languages do what the docs say they will.
  • Templates with real variable handlingMustachio templates, layouts, test data and a safe preview flow make non-engineers able to change wording without pushing code.

Where Postmark bites

  • Not designed for marketing volumePostmark will slow down or disable accounts that start running campaign-style sends. If you need mass marketing, this is not the tool, and that is deliberate.
  • Volume pricing can biteAt low volume the per-message price is reasonable, at high volume it adds up fast, and the step pricing means crossing a tier mid-month is expensive.
  • Approval friction for new sendersNew accounts and new domains have to be approved before they can send freely, which is good for reputation and annoying when you need to ship a staging flow today.
  • Bounces and complaints need your handlingPostmark surfaces them, but suppression, resubscription and user-visible state is still your application's problem to implement.
  • DMARC alignment can break silentlyA DKIM key rotation or a DNS provider change can take alignment from pass to quarantine with no obvious log line; you find out when Gmail starts filing receipts into spam.
  • No full marketing feature setIf you also need segmentation, automation and campaign reporting, you end up pairing Postmark with another tool rather than replacing one with it.

Sound familiar?

Common Postmark problems we fix

The Postmark problems that bring people to us, and what you have once each one is fixed.

ErrorCode 406 Inactive recipient

Mail refuses to send to known addresses

A hard bounce or spam complaint moved the recipient onto Postmark's suppression list, and every subsequent attempt returns 406 until the state is reconciled against your own user table.

Suppressions reconciled, delivery restored

DKIM NXDOMAIN

DKIM is failing on major receivers

A domain registrar move, a DNS provider swap, or a DKIM rotation where the new selector was added but the old one was not retired on time.

DKIM aligned on every inbox provider

ErrorCode 412 account approval

New domain refuses to send

Postmark holds sending until the account and sender signature are approved, which is correct behavior and still trips teams up on launch day.

Account approved, sender signatures verified

inbound webhook 503

Inbound parsing webhook keeps failing

Your inbox endpoint is slow or flaky under load, Postmark retries a few times, and after that the message sits in the dashboard but your app never sees it.

Inbound handler fast and idempotent

SpamComplaint

Spam complaints are climbing

Often a transactional message that reads like marketing, a password reset sent to the wrong person, or a confirmation sent twice because of a retry bug.

Content and retry logic cleaned up

DMARC alignment failed

Gmail is filing receipts as spam

DKIM signs, SPF passes, but neither aligns with the From header domain, so DMARC fails and Gmail quietly treats the message as suspicious.

DMARC alignment confirmed across clients

Template variable undefined

Templates render blank or error

A template that expects a nested object, a missing variable in the production payload, or a localization change that renamed a key.

Templates rendered with real payloads

message stream reputation dropped to 92

Reputation is slipping on one stream

A badly targeted broadcast, a surge of inactive addresses, or a mixed transactional/marketing payload on one stream dragging the reputation score down.

Streams separated, reputation recovering

What we do

Postmark help, from first send to stable delivery

Call us for one failing template, or let us own the whole sending stack.

Rescue
Receipts missing, DKIM broken, or Postmark suspending the account on approval. We get mail flowing again and then explain what went wrong.
DNS and deliverability
SPF, DKIM, DMARC and feedback loops set up and verified across every inbox provider that matters to your customers.
Bounce and complaint handling
Suppression lists reconciled with your own user state, so hard bounces, complaints and unsubscribes are honored once rather than every service separately.
Inbound parsing
Inbound webhooks hardened, attachments extracted correctly, and the handler made idempotent so retries never duplicate conversations.
Templates and localization
Mustachio templates, layouts and translation workflows set up so copy changes do not need an engineering deploy.
Managed Tech
Delivery dashboards, DNS monitoring, and a team that notices when a DKIM rotation goes sideways instead of waiting for support to raise a ticket.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Postmark alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Postmark questions

Something else? Call+1 737 727 7327

Why are my Postmark receipts going to spam at Gmail?

Most of the time DMARC alignment is the culprit. DKIM signs with a different domain than the From header, SPF is on the envelope sender not the visible sender, and Gmail quietly downgrades the message. Fix the alignment, confirm with mail-tester or a DMARC aggregate report, and the inbox placement usually recovers within a day.

Can I use Postmark for marketing emails?

Not on the transactional streams. Postmark provides a broadcast stream for list sends that keeps marketing traffic separate from receipts, with its own reputation. Anything that looks like a campaign on a transactional stream will get the account rate-limited or paused, by design.

Why did Postmark suspend my account?

The most common triggers are new accounts that have not finished sender signature approval, sudden spikes in hard bounce rate, and spam complaint rates over a threshold. The dashboard always says which one. The fix is usually a cleanup of the recipient list and a conversation with Postmark support, not a config change.

How do we handle Postmark inbound reliably?

Acknowledge fast, store the raw JSON, and process asynchronously. The inbound webhook only retries three times before giving up, so a slow handler is the same as a lost email. Store the Postmark MessageID and dedupe on it so your handler is safe to retry.

Should I move from SendGrid or Mailgun to Postmark?

For transactional traffic, usually yes. Postmark's inbox placement for receipts and password resets is consistently stronger. For high-volume marketing it is probably the wrong move, and a lot of companies run Postmark for transactional alongside another tool for campaigns.

How much does Postmark help cost?

We quote for free. Describe what the sending stack is doing wrong and we reply with a scoped price.

Free estimate

Postmark giving you trouble?

Tell us which message stream or inbound flow is misbehaving and we come back with a plan and a price.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.