Every connected provider, one control layer.
A sending server in Mailers.io is any source of outbound email you've connected — provider APIs, mailboxes, or raw SMTP. Manage them uniformly, cap them individually, and let routing handle the rest.
- Providers + SMTP
- MixedProviders + SMTP
- Per workspace
- ScopedPer workspace
- Per-server limits
- CappedPer-server limits
- Auto health checks
- HealthyAuto health checks
One table for every source you send through.
No more jumping between provider dashboards to understand your outbound posture.
| Server | Type | Workspace | Used / cap (today) | Status |
|---|---|---|---|---|
| ses-marketing-us | Amazon SES | Marketing | 41% of 80k | Healthy |
| sg-cold-pool | SendGrid | Outbound | 92% of 50k | Throttle |
| mailgun-txn | Mailgun | Product | 23% of 120k | Healthy |
| gmail-sales-07 | Gmail SMTP | Outbound | 68% of 500/day | Healthy |
| custom-smtp-eu | SMTP | Backup | 3% of 20k | Degraded |
What you can set per sending server.
Hourly & daily caps
Define sending limits that respect provider appetite and deliverability posture.
Priority & scope
Put servers into priority pools and scope them to specific workspaces or domains.
Automatic health checks
Ongoing probes mark servers healthy, degraded, or unavailable so routing adapts.
Encrypted credentials
All API keys and SMTP passwords encrypted at rest. Never logged.
Any RFC-compliant SMTP
Mix managed providers with raw SMTP endpoints from your own infrastructure.
Hot add / remove
Add, pause, or retire servers live. Routing reconfigures without a redeploy.
Per-server reporting
Delivery, bounce, and complaint breakdown for every server you operate.
Alerts & events
Get notified on authentication failures, quota exhaustion, and health transitions.
What engineers and ops ask.
Treat providers and SMTP the same way — finally.
Configure caps, priorities, and health checks once. Let routing use them consistently across every outbound message.