Inbound Routing

Receive emails at your own domain and route them to your app via webhooks, forwarding, or direct storage.

1Automatic Inbound Support

Inbound receiving is enabled by default for all verified domains. Simply open the Domain Configuration panel and locate the Receiving MX Records section to get your configuration details.

2Update MX Records

To route mail to Transmit, you must point your domain's MX (Mail Exchange) records to our infrastructure.

Type
Priority
Value
MX
10
mx1.xmit.sh
MX
20
mx2.xmit.sh

Important: Remove any existing MX records (e.g., Google Workspace, Outlook) unless you want emails to be delivered to both services (not recommended).

3Choose Your Action

Every endpoint can be configured with a specific action. You can mix and match these across your domain to build complex workflows.

Webhooks

Receive parsed JSON payloads at your app URL. We handle the MTA complexity, parsing, and retries for you.

Email Forwarding

Route incoming mail to any external address. Requires your own AWS SES credentials (BYOK) for verified sending.

Direct Storage

Save emails directly to the Transmit database. Perfect for audit trails or building a custom inbox UI.

Silent Drop

Discard incoming mail silently. Useful for retiring old addresses or managing high-volume automated traffic.

4How it Works

Transmit uses a globally distributed architecture to ensure your emails are received instantly and processed reliably.

Haraka MTA Edge

Incoming connections are handled by our Haraka nodes. We perform real-time SPF/DKIM checks and spam scoring before accepting any mail.

Cloudflare Queues

Accepted emails are pushed into a distributed queue for asynchronous processing, ensuring your MTA never blocks on slow webhooks or API calls.

Secure Workers

Lite-weight workers decrypt your tenant-specific credentials, execute your configured action, and handle automatic failover to storage if your endpoint is down.

Architecture Detail

Transmit uses a distributed MTA (Mail Transfer Agent) architecture to ensure global low-latency email reception.

  • Emails are received by our high-performance Haraka-based MTA nodes.
  • Tenant identity and domain permissions are checked in real-time.
  • Attachments are processed and stored securely if enabled.