Email delivery infrastructure

Infrastructure you can inspect, not rent blindly.

Owned SMTP, a durable Postgres-backed control plane and per-attempt delivery events. Transmitly keeps the operational truth close enough to debug, without hiding the provider response behind a score.

Owned MTA

KumoMTA spool, controlled egress pools and forward-confirmed PTRs. No shared vendor queue deciding your rate.

Durable control plane

Message, deliveries, idempotency and outbox commit in one transaction before 202.

Provider-aware scheduling

Per-stream pools, tenant fairness, provider budgets, backoff with jitter and attempt caps.

Per-attempt truth

SMTP code, enhanced code, MX host and reason recorded for every attempt.

Isolated reputation

Transactional and marketing run on separate pools and boundaries.

Inbound routing

Forward, transparent relay with ARC, webhook-only or drop, scoped per address.

The delivery path

From API call to remote MX.

  1. 01

    Intake

    Authenticate the key, enforce tenant scope, quota, domain ownership and MIME limits.

  2. 02

    Commit

    Write the message, recipient deliveries, idempotency and outbox in one transaction.

  3. 03

    Schedule

    Choose the stream pool, provider budget and fairness slot; apply active control actions.

  4. 04

    Deliver

    Sign with DKIM, submit to KumoMTA and let the spool own SMTP retries.

  5. 05

    Normalise

    Ingest DSN/ARF and MTA feedback into classified attempts and provider windows.

  6. 06

    Explain

    Turn telemetry into incidents, proposals and audited control actions.

What “delivered” means

A 2xx response from the remote MX means the remote server accepted responsibility for the message. It does not mean the inbox, the promotions tab, or the spam folder. Transmitly labels it delivered_to_mx and stops there.

What we refuse to invent

  • • A single “deliverability score” with no methodology.
  • • An inbox-placement claim derived from SMTP acceptance.
  • • A retry policy that treats every 5xx as a bad address.
  • • A control action without scope, evidence and expiry.

Need a migration path?

Start with a verified subdomain, run transactional traffic in parallel, then graduate volume based on deferral and complaint rates.

Questions

Infrastructure FAQ

+Do you own the sending infrastructure?

Yes. Transmitly operates its own KumoMTA nodes and sending IPs. Messages are injected into the spool, retried durably and reported through signed delivery events back to the control plane.

+Can I keep transactional and marketing reputations separate?

Yes. The two streams use separate pools, budgets, priorities and blast-radius boundaries. A marketing surge cannot silently consume transactional capacity.

+What do you record for each delivery attempt?

Provider, MX host, SMTP code, enhanced status, classification and reason. These become the raw facts behind deferral pressure, error clusters and provider dashboards.

+Does the platform support inbound email?

Yes. Verified customer domains can accept mail for exact routes or catch-alls, then forward, relay transparently with ARC, deliver to a webhook, or drop.

+What happens when a provider starts deferring?

The scheduler backs off with jitter. Autopilot can propose a scoped action such as reducing provider concurrency or pausing a stream; deterministic policy validates it and issues a lease.

Put your sending on infrastructure you can see.

Bring a verified domain and a legitimate use case. We review the sending profile before graduating quotas.