Docs Get key
All guides
Bulk email

Postal for bulk email: run your own delivery

Decide whether Postal fits your bulk sending, then use its API and webhooks without mistaking queue acceptance for delivered mail.

Reviewed

Postal is a self-hosted mail delivery platform with SMTP submission, an HTTP send API, message activity, and inbound routing. Choose it when operating delivery is intentional: you want your own sending IPs, DNS, queue, and message history, and your team can own reputation and upgrades. Do not choose it because a newsletter editor feels expensive; Postal is the transport layer, not a campaign manager.

This guide covers the bulk-send boundary: what to put in front of Postal, how to call it safely for many recipients, and why an accepted request is not a delivered message. Installation and inbound routing live in the dedicated Postal server guides.

What Postal does and does not own

Postal owns SMTP/HTTP submission, outbound delivery, per-recipient message records, and (when configured) inbound routing. It does not own subscriber segmentation, campaign drafts, unsubscribe preferences, or a newsletter editor. A listmonk, Keila, Mautic, or application layer belongs upstream.

The Postal prerequisites require containers, MariaDB, and outbound port 25. MySQL is not a supported substitute for MariaDB. You also need a dedicated hostname, correct forward and reverse DNS, and a provider that permits outbound SMTP. If any of those are outside your control, a hosted sender is the simpler boundary.

Decide before you install

Use Postal when at least one of these is true:

  • You need delivery infrastructure you control, not only a send API.
  • You send enough volume that provider pricing or policy is a real constraint.
  • You already operate mail infrastructure and can absorb another queue, database, and DNS surface.

Choose a managed sender when you cannot staff blocklist checks, PTR records, DKIM rotation, queue monitoring, backups, and abuse response. Self-hosting moves cost from a bill to operations; it does not remove delivery work.

Send many messages without breaking the model

Postal’s HTTP API accepts either message attributes or a complete raw message, authenticated with X-Server-API-Key. A single request can address multiple recipients, and the response maps each recipient to its own message ID and token. That is useful for tracking, but it is not personalization: if each recipient needs different content or an individual unsubscribe token, send one message per recipient or render the content before submission.

A safe bulk loop has four properties:

  1. Persist intent first. Store job, recipient, content version, and a unique idempotency key before calling Postal.
  2. Bound concurrency. Postal and your provider have connection and rate limits; a batch size is not a rate. Start small and raise concurrency only with observed acceptance.
  3. Check the JSON status. HTTP success alone is not application success. The API response carries a status field, and multi-recipient sends return per-recipient identifiers.
  4. Reconcile before retrying. A timeout can happen after Postal accepted the message. Query message history or wait for an event before resending.

The Postal API send guide includes a Node.js request and the response handling in more detail.

Close the feedback loop

Configure Postal’s message status and bounce webhooks. Persist the provider message ID, recipient, event type, and timestamp, then process duplicate and out-of-order events idempotently. A bounce or complaint must update your suppression state; it must not trigger an unbounded resend loop.

Postal’s API does not cover every administrative function. Treat DNS, domain verification, worker health, queue age, and blocklist status as separate operational checks with their own dashboards or alerts.

Costs and failure modes to budget

  • Hosting: a server, MariaDB, storage, backups, and monitoring.
  • DNS and reputation: a stable IP, PTR, SPF, DKIM, DMARC, and a process for blocklist removal.
  • Operations: upgrades, certificate renewal, disk growth, and queue recovery.
  • Abuse handling: a complaint path and a way to stop a bad sender without taking down every domain.

A working dashboard and a successful API call do not prove inbox placement. Test a controlled message, inspect the received headers, and verify alignment before sending real traffic. Read the Postal installation guide and inbound receiving guide before production.

Where MailKite fits

MailKite, which we build, is a hosted sending and receiving API. It replaces the delivery platform rather than the campaign application. It supports broadcasts and personalized batches but prohibits unsolicited bulk or commercial mail, sending without consent, and sending after opt-out.

If you want the campaign layer but not the mail server, pair a campaign tool with MailKite and read using MailKite alongside Postal. If you are moving an existing stream, replacing Postal inbound with MailKite covers the inbound cutover. Neither is an in-place failover: verify domains, credentials, and suppression state separately.

Next steps

Sources reviewed 2026-11-07: Postal prerequisites, Postal API, Postal webhooks, and the Postal license.