What is hybrid sending (ESP + custom MTA)?

Most email programs run through a single Email Service Provider (ESP) for everything. Marketing, transactional, automated, all of it. Hybrid sending is the practice of splitting that traffic across two systems: an ESP for some email types and a self-hosted Mail Transfer Agent (MTA) for others.

The most common reason to go hybrid: separating marketing email from transactional email. Marketing email (newsletters, promotions) generates complaints from unengaged recipients. Transactional email (receipts, password resets) is expected by recipients and has very low complaint rates. If you send them both from the same IP and domain, a bad marketing campaign can damage the reputation of your transactional sending. And your customers stop getting their password resets. Separating them protects the most critical sends.

Other common hybrid configurations:

ESP for marketing, custom MTA for high-volume transactional. ESPs charge per send. At very high transactional volumes, running your own MTA is significantly cheaper. And gives you full control over delivery timing, retry logic, and log access.

Custom MTA as baseline, ESP for peak capacity. Your own infrastructure handles normal volume. During major campaigns or seasonal spikes, the ESP absorbs overflow.

The tradeoffs worth knowing: hybrid adds operational complexity. You're now maintaining two systems with potentially different authentication configurations, bounce handling, and suppression lists. If a subscriber unsubscribes from your marketing ESP, that suppression needs to sync to your MTA before the next transactional send. And vice versa.

Check your SPF record includes authorized sending IPs from both systems, and that DKIM keys are set up for both. Two systems sending on behalf of the same domain with inconsistent authentication is a common hybrid mistake. Our SPF checker can help you verify all your sending sources are covered.