Key takeaways
- Multi-provider routing: Connect several sending providers (Amazon SES, SendGrid, Mailgun, generic SMTP, Gmail OAuth) to a single workspace and manage them from one place.
- Weighted load balancing: Assign each server a share of outbound traffic based on cost, daily quota, and maximum send rate.
- Automatic failover: When a provider returns throttling or availability errors (for example HTTP 429, HTTP 5xx, or an SMTP 421 from the relay), queued messages are rerouted to a backup server in real time.
Once your volume reaches hundreds of thousands or millions of emails a month, relying on a single sending provider becomes a single point of failure. A provider outage, scheduled maintenance, throttling, or an unexpected hit on your daily sending quota can delay campaigns and transactional mail that the business depends on.
The multi-provider infrastructure in eMailBase addresses this by turning your sending servers into a flexible, self-healing pool instead of a single pipe.
1. The technical benefits of a multi-server architecture
Running multiple sending servers from one control panel gives you three operational advantages:
Automated failover
When the primary server cannot be reached or rejects submissions with a temporary error (such as SMTP 421 from the relay, or HTTP 429 or 5xx from a provider API), eMailBase automatically moves the affected messages in the queue to a preconfigured backup server so the campaign keeps running. Deferrals issued by the recipient's mailbox provider (for example a 4xx from Gmail or Outlook) are retried on schedule rather than failed over, since switching providers does not resolve a recipient-side block.
Throughput and quota scaling
Every cloud sending account has a maximum send rate (emails per second) and, on most providers, a daily or monthly quota. Spreading traffic across several servers lets your aggregate throughput approach the combined capacity of all of them, so large campaigns finish faster. In practice, receiving-side throttling by major mailbox providers still applies, so pace sends to each recipient domain according to your reputation.
Traffic segmentation by purpose
You can dedicate separate servers to each mail stream: a Google Workspace account (Gmail OAuth) for personal one-to-one sales follow-ups, an Amazon SES pool for recurring newsletters, and Twilio SendGrid for event-triggered transactional email. Keeping streams separate also isolates their reputations, so a weak newsletter campaign does not drag down password resets and receipts.
2. Common sending infrastructure models
| Architecture model | Configuration | Primary operational goal |
|---|---|---|
| Cost-optimized with failover | Amazon SES (80% weight) + SendGrid (20% weight and failover target) | Capture the low per-message cost of Amazon SES while keeping a warm, reliable backup route on SendGrid. |
| Flexible starter setup for SMBs | Gmail OAuth 1-click (one-to-one email) + Amazon SES (campaign email) | Use the existing business mailbox to get started quickly for personal outreach, while SES handles bulk volume. Google Workspace caps sending at roughly 2,000 messages per user per day, and bulk sending to Gmail still requires SPF, DKIM, and DMARC on your domain. |
| Large enterprise | Multiple Amazon SES accounts across regions (US East, EU West, Asia Pacific Southeast) | Gain independent per-region quotas and send rates, keep data in the required region for residency compliance, and stay online if one AWS region has an incident. |
3. How to configure server routing in eMailBase
- Open the BYO Sending Hub in your workspace.
- Connect each provider by entering its API key or SMTP credentials, or link a Google account with 1-click OAuth.
- Adjust the Weight slider for each server to set the traffic split you want.
- Choose the server that acts as the failover destination and set the retry threshold, the number of failed attempts allowed before traffic switches routes.
