Send transactional email via SMTP

Send through Routee's MailerQ SMTP relay using your Connect application credentials — no OAuth token per message.

Before you start: Domain & authorized senders and Email — HTTP API vs SMTP relay.

1. Connection settings

Setting	Value
Host	`smtp10.amdtelecom.net`
Username	Connect Application Id
Password	Connect Application Secret
From	Verified authorized sender address

2. Choose port and TLS mode

Port	TLS	Client setting
25	STARTTLS after connect	swaks `--tls`; Python `SMTP` + `starttls()`
587	Implicit TLS from connect	swaks `--tls-on-connect`; Python `SMTP_SSL`

Do not use STARTTLS on a cleartext port 587 connection.

3. Test with swaks (port 25)

swaks --to [email protected] \
  --from [email protected] \
  --server smtp10.amdtelecom.net \
  --port 25 \
  --tls \
  --auth LOGIN \
  --auth-user "YOUR_APPLICATION_ID" \
  --auth-password "YOUR_APPLICATION_SECRET"

Expected: 235 Access granted → 250 after DATA.

4. Test with Python (port 587 implicit TLS)

import smtplib
from email.message import EmailMessage

msg = EmailMessage()
msg["From"] = "[email protected]"
msg["To"] = "[email protected]"
msg["Subject"] = "SMTP test"
msg.set_content("Hello from Routee SMTP.")

with smtplib.SMTP_SSL("smtp10.amdtelecom.net", 587) as server:
    server.login("YOUR_APPLICATION_ID", "YOUR_APPLICATION_SECRET")
    server.send_message(msg)

5. Verify in logs

SMTP sends appear in the same logs as HTTP API sends. After 1–2 minutes:

Portal: Email → Logs on go.routee.net
API: Search email tracking

SMTP does not support send-time webhooks — use the tracking API or portal for delivery status.

Portal copy-paste

Email → SMTP on go.routee.net shows host, ports, and your Application Id with copy buttons.

Full client matrix: Transactional Email — SMTP relay

E-mail
Send your first transactional email (HTTP alternative)