Email.com docsOpen the app

Guides

SMTP relay guide

Send through the platform from any application or device that speaks SMTP: legacy apps, off-the-shelf software, printers and scanners, cron jobs. The relay accepts your message the way the REST API does (same streams, same policy, same delivery events) and answers with the message id you can follow in the panel or through the API. Your message is relayed as you built it: no link rewriting, no open pixel and no header injection happen on the SMTP path.

Endpoint

SettingValue
Hostsmtp.<your platform domain> (the panel's Settings page shows the exact host)
Port 587STARTTLS: connect in plain text, issue STARTTLS, then authenticate
Port 465Implicit TLS: the connection starts with the TLS handshake
Port 25Closed
TLSTLS 1.2 or newer with a public certificate; the server name is the host above
AuthenticationAUTH PLAIN or AUTH LOGIN, only after TLS (an AUTH before STARTTLS answers 538)
Username and passwordAn SMTP credential created in the panel under SMTP credentials; one credential is bound to one stream

What one credential can do

recipients`. Every recipient becomes its own message with its own id.

Replies to expect

ReplyMeaningWhat to do
250 2.0.0 queued as msg_… msg_…Accepted: one message id per recipient, in RCPT TO orderStore the ids; delivery, bounces and opens arrive as events and in the panel
421 4.3.2 service not available (at the banner)The product is paused or in maintenanceRetry later; nothing was accepted
421 4.7.0 connection refused, try again laterYour IP is temporarily banned (see below) or over the connection rateWait; fix the client that loops
535 5.7.8 authentication credentials invalidWrong username or passwordCheck the credential; it is bound to one stream
535 5.7.8 too many failed authentication attempts, try again laterLockoutWait 15 minutes and fix the stored password
550 5.7.1 rejected by policyAdmission refused the message (suppressed recipient, missing unsubscribe on a broadcast stream, quota)Read the reason in the panel's message view or the API's reason_codes
451 4.3.0 temporary failure, try again laterA transient platform errorRetry with backoff
538 (before STARTTLS)AUTH was attempted on a plain connectionIssue STARTTLS first, or use port 465
550 5.6.0 the credential binds no usable streamThe credential's stream is gone or unusableCreate a new credential in the panel
550 5.6.0 message refusedThe message could not be accepted as builtCheck the From, the size and the headers

Lockouts and bans

Five failed AUTH for one credential, or from one IP, within 15 minutes lock that credential or that IP for the rest of the window; twenty failures ban the source for one hour. A ban is lifted on request by support (the platform's unban action) after the client that produced the failures has been fixed. Use one credential per application so a leaked or rotated password affects one integration only, and rotate from the panel: the old password stops working as soon as the platform's credential index is updated.

Client settings that work

Tracking and unsubscribe

Messages relayed over SMTP are stored and sent as you built them: no open pixel, no link rewriting and no unsubscribe header are added (the stream's Track opens / Track clicks settings and its default unsubscribe URL apply to the REST API path only). Delivery, bounce and complaint events still arrive. A message on the broadcast lane must carry its own List-Unsubscribe header; a broadcast without one is refused by policy (550 5.7.1 rejected by policy).

Following a message

The message ids from the 250 reply work everywhere: GET /v1/emails/{message_id} and its events, the panel's message page (timeline, attempts, the built message for download), and the email.* webhook events (email.accepted.v1, email.sent.v1, email.delivered.v1, email.bounced.v1, ...). A quick test: send to success@simulator.amazonses.com (delivered) or bounce@simulator.amazonses.com (hard bounce) and watch the timeline; these addresses never reach a mailbox.