Documentation
Inbound routing
Forward, relay, webhook and drop routes with ARC.
Transmitly is a sender, not a general-purpose mail host, but it can accept mail for your verified domains and forward or drop it. Routing happens before any customer webhook is emitted, so you control what leaves the platform.
Add an MX record for the receiving domain (DNS-only):
yourdomain.com MX 10 mail.transmitly.ioOnly addresses with a route are accepted; anything else is refused at RCPT with 550 5.1.1. The listener advertises STARTTLS with a valid mail.transmitly.io certificate, and DSN/ARF reporters are checked with SPF and aligned DKIM before a bounce or complaint is applied. Routes can target an exact address ([email protected]) or a catch-all (@yourdomain.com) and either:
- • Forward — re-injected as a transactional message from the inbound address, DKIM-signed as your domain, with
Reply-Toset to the original sender. It appears in Messages and gets retries, suppression and bounce handling. - • Relay — transparent forwarding: the original message is reinjected unchanged (headers, body, Message-ID and DKIM intact) with only unsigned
Delivered-To/X-Original-Toheaders added. There is no Fwd prefix and the original sender is preserved. Tradeoff: the envelope becomes our VERP bounce address, so SPF for the original domain will not align; DMARC passes only if the original message carries a valid DKIM signature. Every relay is ARC-sealed (ARC-Authentication-Results, ARC-Message-Signature, ARC-Seal) using the domain's DKIM key, so receivers that trust the chain (Gmail, Microsoft) can accept the message despite SPF not aligning. ARC does not make SPF pass, and receiver support varies. Unsigned mail is therefore better handled with forward. - • Webhook — nothing is sent by email. The
email.inboundevent carries the sender, recipient, subject, size, headers and the text/HTML bodies (capped at 32 KB each). Use this to parse or file mail without forwarding it. - • Drop — accepted and discarded, webhook carries metadata only.
A message with no matching route is refused at RCPT with 550 5.1.1 and produces no webhook, which avoids accepting spam or backscatter. To receive everything for a domain, add an @yourdomain.com catch-all route — point it at webhook if you want to process mail programmatically without forwarding. Every accepted route also emits email.inbound, so relay and forward routes can feed a webhook while still delivering mail.
{
"id": "evt_…",
"type": "email.inbound",
"data": {
"org_id": "org_…",
"route_id": "inr_…",
"from": "[email protected]",
"to": "[email protected]",
"subject": "Invoice 1042",
"action": "webhook",
"status": "received",
"size_bytes": 4821,
"text": "Plain text body…",
"html": "<p>HTML body…</p>",
"truncated": false
}
}Every accepted message is recorded with sender, recipient, subject, action and outcome. Forwards carry an X-Transmitly-Forward header and mail that already has it is dropped, which prevents forwarding loops. The platform emits an email.inbound webhook event after routing.
Inbound advertises STARTTLS with the same mail.transmitly.io certificate, and the receiving domain list is set per deployment with TRANSMITLY_INBOUND_DOMAINS. Pointing an MX at the apex routes all mail for that domain here, including previously unmapped addresses; prefer a subdomain such as in.yourdomain.com if you only want a subset.
Need the full API surface? OpenAPI 3.1.