Documentation

SMTP submission

Authenticated SMTP submission on 587 and 465 with the same durable acceptance path as the API.

Existing applications can submit mail over SMTP without switching to HTTPS. Submission is scoped to an authenticated workspace: it is not an open relay, and every envelope sender must be on a domain verified in that workspace. The server returns 250 only after the same message, delivery and outbox transaction used by the API commits.

SettingValue
Hostmail.transmitly.io
STARTTLS587 (required before AUTH)
Implicit TLS465
Usernameapikey, or the key prefix shown in the dashboard
PasswordThe full API key (txk_…), shown once at creation
Scopesend or admin
SenderMAIL FROM and the From header must be the same verified domain
Message size50 MiB
RecipientsUp to 50, or the plan's per-message cap
AttachmentsUp to 20 files, 40 MiB total; HTML body up to 1 MiB
authenticated submission
# 587 STARTTLS or 465 implicit TLS
Host:      mail.transmitly.io
Username:  apikey
Password:  $TRANSMITLY_KEY

MAIL FROM:<[email protected]>
RCPT TO:<[email protected]>
DATA
From: Acme <[email protected]>
To: Ada <[email protected]>
Subject: Your workspace is ready
Content-Type: text/html; charset=utf-8

<p>Hello from SMTP.</p>
.

Standard MIME is parsed into the same message model as the API: multipart/alternative bodies, quoted-printable and base64 transfer encodings, text and HTML charsets, inline CID images and attachments. Optional X-Transmitly-Stream (transactional or marketing) and X-Transmitly-Topic headers map to the API fields. Test-only keys and the synthetic @transmitly.test addresses behave the same way as the API.

SMTP has no idempotency key. A Message-ID is preserved when present, but a client that retries after a timeout can create a duplicate; prefer the API with Idempotency-Key when exactly-once acceptance matters. Submission still enforces workspace quotas, sender-domain ownership, suppression checks, per-tenant rate limits and DKIM signing on the outbound MTA path.

Need the full API surface? OpenAPI 3.1.