Why Email Deliverability Is ESP-Specific (and How to Configure Each Platform)
Mailbox filtering algorithms evaluate technical infrastructure uniquely across email platforms. Switching or setting up an ESP is no longer plug-and-play; shared subnet reputations and unbranded tracking links directly dictate whether campaigns land in the primary inbox or spam folder, making platform-specific DNS and link configuration critical to protecting inbox placement.
- Identical campaigns achieve drastically different deliverability rates across ESPs due to underlying IP and subnet configurations.
- Default, shared link-wrapping domains compromise deliverability; custom click tracking is mandatory.
- Microsoft EOP and modern anti-spam filters scrutinize infrastructural reputation alongside domain identity.
- Aggregated 99% 'delivered' metrics frequently mask severe inbox placement drop-offs at specific mailbox providers.
What changed
A technical report from the Mailora Blog revealed that mailbox provider filtering engines—including Microsoft Exchange Online Protection (EOP) and SmartScreen—evaluate underlying sending architecture differently across major ESPs like Klaviyo, SendGrid, Amazon SES, and Postmark.
The analysis highlighted that deliverability relies heavily on granular elements such as IP pool quality, subnet-level health, and how platforms manage custom click-tracking domains (CNAMEs). Because each ESP handles shared infrastructure and link wrapping differently, identical email content and sender domains can yield drastically different deliverability outcomes depending on platform setup.
Why it matters for email marketers
For years, email teams treated ESP selection primarily as a feature-and-pricing decision, operating under the naive assumption that basic SPF and DKIM setup leveled the playing field. In reality, relying on default ESP infrastructure leaves your inbox placement exposed to 'bad neighbor' fallout. If your provider routes campaigns through low-reputation IP subnets or generic, shared click-tracking domains, your sender equity is penalized before an inbox filter even inspects your creative or subject line.
Furthermore, this architectural variance wrecks pipeline reporting and campaign economics. When Microsoft EOP or Google algorithms silently relegate messages to junk folders due to ESP link wrappers, surface-level dashboard 'delivery rates' remain deceptively high while actual open rates collapse. Deliverability must be managed as an ongoing infrastructure protocol rather than an onboarding checklist; teams migrating between systems without isolating their click-tracking domains and evaluating IP pooling risk devastating their deliverability.
What to do about it
- 1Audit and implement custom branded click-tracking domains (CNAME records) inside your ESP to ensure tracked URLs match your primary sending domain instead of shared ESP endpoints.
- 2Evaluate your ESP's sending infrastructure to determine whether your sending volume and consistency warrant migrating from a shared IP pool to a dedicated IP address.
- 3Inspect provider-level engagement metrics (specifically Microsoft/Outlook vs. Gmail) to spot IP- or subnet-level filtering anomalies that aggregate deliverability rates conceal.
- 4Isolate operational and transactional message streams from marketing campaigns by assigning distinct subdomains and separate DKIM selectors across your sending platforms.
Who this affects: This affects email marketing managers, CRM leads, and revenue operations teams overseeing cross-platform email programs or evaluating ESP migrations.
Original reporting by Mailora Blog. The analysis above is EmailVersed's own.
More email industry analysis on Email News, or ask the community on Q&A.