SMTP Reference
SMTP relay settings for sending email with Samva — host, ports, TLS, authentication, limits, sender address, tracking, and troubleshooting.
SMTP Reference
Settings for sending email through the Samva SMTP relay. For step-by-step setup, see the how-to guides:
SMTP is staged. The relay accepts connections and authenticates with your API key, but it is not yet accepting message submissions. Use the API or SDK to send email today; this reference describes the SMTP path so you can prepare your integration.
Send via SMTP
Configure an SMTP client and send your first message.
SMTP platform setup
Connect Samva SMTP to common platforms and frameworks.
Connection Settings
| Setting | Value | Notes |
|---|---|---|
| Host | smtp.samva.app | |
| Port (STARTTLS) | 587 | Recommended. Connection starts unencrypted, upgrades via STARTTLS |
| Port (SSL/TLS) | 465 | Implicit TLS. Connection is encrypted from the start |
| Encryption | TLS required | Both ports require TLS encryption |
Authentication
| Setting | Value |
|---|---|
| Method | PLAIN or LOGIN |
| Username | samva |
| Password | Your Samva API key (e.g., sk_sm_...) |
The username is ignored — all authentication is done via the API key password. Use samva by convention. This matches the approach used by other email providers.
Limits
| Limit | Value |
|---|---|
| Max message size | 25 MB (including attachments) |
| Max recipients per message | 50 |
| Sender domain | Must be verified in Samva dashboard |
Port Selection
Port 587 (STARTTLS) — Recommended for most integrations. The connection starts as plain text and upgrades to TLS via the STARTTLS command. This is the standard submission port defined in RFC 6409.
Port 465 (Implicit TLS) — The connection is encrypted from the first byte. Some legacy applications or strict firewall environments require this port.
Port 25 — Not supported. Most cloud providers block outbound port 25.
Sender Address
The From: address in your email must use a domain that is verified in your Samva dashboard. Sends from an unverified sender domain are rejected. See Verify your domain.
Message Tracking
Once SMTP submissions are enabled, messages sent through the relay route through the same delivery pipeline as API sends, so they share the same tracking and deliverability handling as API-sent email. Until then, use the API or SDK to send and track email.
Troubleshooting
Authentication failed
- Verify your API key is correct and not expired
- Ensure the API key is enabled in your dashboard
- Confirm you are passing the API key as the password (the username is ignored — use
samva)
Domain not verified
- The sender address domain must be verified in your Samva dashboard
- See Verify your domain for setup steps
Connection timeout
- Ensure your network allows outbound connections on port 587 or 465
- Some corporate firewalls block SMTP ports — contact your network administrator
- Try switching between port 587 and 465
Message size exceeded
- The maximum message size is 25 MB including all attachments
- Consider using smaller attachments or linking to hosted files