SMTP (Sending Email)
What this feature is for
SMTP access lets you send email from any standard email client or application using your Inboxlayer inboxes. Messages sent via SMTP are delivered through AWS SES and automatically appear in your Sent folder.
Connection settings
| Setting | Value |
|---|---|
| Server | smtp.inboxlayer.dev |
| Port | 587 (STARTTLS) or 465 (implicit TLS) |
| Encryption | Required. STARTTLS on 587, TLS on 465 |
| Authentication | PLAIN or LOGIN |
| Username | Your inbox email address |
| Password | An API token from your account |
| Max message size | 25 MB |
Authentication
SMTP authentication uses API tokens, not account passwords.
- Sign in to your Inboxlayer account.
- Go to Account Settings > API Keys.
- Create a new token or copy an existing one.
- Use the full token value as your SMTP password.
The username is your inbox email address:
- Default domain:
inbox_name@inboxlayer.dev - Custom domain:
inbox_name@yourdomain.com(if domain is verified)
What happens when you send
- Your client connects and authenticates with the API token.
- Inboxlayer verifies token ownership and checks your send quota.
- The message is relayed through AWS SES.
- A copy is written to your inbox's Sent folder automatically.
- An
OutboundEmailrecord is created and tracked for delivery status.
Quotas and limits
Send quotas are enforced at the SMTP level, same as the API. If your plan's send limit is reached, the SMTP server will reject the message. Check your plan details for specific limits.
Ports
Use port 587 with STARTTLS for most clients. This is the recommended configuration.
Port 465 (implicit TLS) is also supported. Some ISPs or corporate networks block port 465, so 587 is the safer default.
Port 25 is reserved for inbound mail delivery and cannot be used for sending.
Notes for agents
- API tokens used for SMTP are the same tokens used for API and IMAP access.
- Tokens can be revoked independently without affecting other tokens.
- Track
OutboundEmailstatus via the API if you need delivery confirmation. - The same rate limits apply whether sending via SMTP or the REST API.