Deliverability

Sent isn't the metric. Delivered is.

Most providers report "sent" when they accepted your API call. We run Postfix, so a 250 from the receiving host becomes delivered — and a hard bounce or complaint auto-suppresses before the next send. Inbox-vs-spam seed tests are coming; we don't sell them as live.

Authenticate a domain Read the docs
Own MTAPostfix we operate — delivery status from the log
AuthSPF + DKIM generated; sending gated on verified
Pre-sendHard bounce and complaint auto-suppress
RFC 8058List-Unsubscribe + one-click headers injected
What ships today

Four layers between your API call and the receiving server

Each one is live in production. The suite that is not live is listed below, not mixed in.

Authentication & alignment

Auto-generated DKIM keys, derived SPF and DMARC, optional custom MAIL FROM. One-click DNS publishing on supported providers, copy-paste records for any registrar, and live re-verification. Unverified domains cannot send.

List hygiene & suppression

Hard bounces and complaints auto-suppress, and the per-project list is enforced pre-send. Optional /verify checks syntax, MX, disposable and role accounts, and Spamhaus DBL before a message leaves.

Delivery events from the mail server

Bounce and complaint arrive via DSN/ARF. Delivered is derived from Postfix status=sent (250 …) — not from hoping a receiver honors NOTIFY=SUCCESS. Signed webhooks fire for sent, delivered, bounced, and complained.

Bulk-sender headers

List-Unsubscribe and RFC 8058 one-click headers are injected on mail we relay. DMARC records are generated at domain setup with a guided path from p=none toward enforcement.

Google and Yahoo rules

What we handle automatically — and what we don't yet

RequirementToday
SPF + DKIM aligned Keys and records generated at domain setup; sending is blocked until the domain is verified.
DMARC published DMARC derived automatically with a guided path from p=none to enforcement.
One-click unsubscribe List-Unsubscribe and one-click headers injected; processed immediately.
Complaint rate under 0.3%We record complaints and show the rate on the dashboard. Automatic throttle / kill-switch is not live yet.
Forward & reverse DNSWe operate the sending hosts. PTR cutover for the public sending IP is an ops task, not a self-serve product.
On the roadmap

The rest of the deliverability suite

These are the paid, defensible layer. They are not in the product today.

Dedicated IP pools Coming

Per-tenant or per-stream IPs so a campaign cannot poison password resets. Today every tenant shares the mail server we operate.

Automated warmup Coming

Volume ramps per IP per day that react to bounce and complaint signals.

Seed-list placement Coming

Inbox / spam / missing, per mailbox provider. Until then we report accepted-by-receiver, not folder placement.

Customer blocklist alerts Coming

Platform operators already see DNSBL checks in God Mode. Tenant-facing listing alerts are not shipped.

DMARC report ingest Coming

Parsed aggregate reports — who sends as you, and where alignment fails.

Abuse auto-throttle Coming

Signup screening, send-pattern anomaly detection, and a complaint-rate kill-switch. Plan send caps are already enforced.

Stop guessing whether the receiver accepted it.

Authenticate a domain in minutes, send through a mail server we operate, and watch delivered / bounced / complained on the same dashboard. Drop-in compatible API — change the base URL and you're sending.

Start free Migrate from your current provider