Home / Outbound Benchmarks / Bounce rate by security gateway

Cold email bounce rate by recipient security gateway: Mimecast, Sophos, Proofpoint, Microsoft 365, Google

We resolved the MX records of every bounced and accepted domain in two campaigns. Domains behind Mimecast bounced 90 to 1; Sophos 8 to 0; Proofpoint 0 bounces on 21 domains. Half of all our bounces across 5,650 sends were Mimecast.

Key finding: Recipient domains whose MX points to Mimecast bounced on 90 domains against 1 accepted in one campaign and 30 against 1 in another, independently of email verification. Excluding Mimecast and Sophos domains with a free DNS lookup took a campaign from 16.95% to 0.84% bounce per lead. Proofpoint, Microsoft 365, Google, Barracuda, Cisco IronPort and others all sat around 1%.
Measured onAugust 7, 2026
Sample2 cold email campaigns (2,856 and 623 leads) with per-lead bounce status, then a 5,650-send baseline; 714-lead follow-up test
MethodFor every recipient domain in each campaign, MX records resolved via DNS and classified by provider (Mimecast, Sophos, Proofpoint, Microsoft 365, Google, Barracuda, Cisco IronPort, Trend Micro, Fortinet, Zoho, GoDaddy). Bounce = per-lead bounced status in the sending platform, not per-send analytics.
SourceVision Media internal measurement (campaign and API logs)
Domains bounced vs accepted, by gateway (two campaigns, August 2026)
Gateway in MXCampaign A (marketing leaders, hiring signal)Campaign B (DTC brands)Other campaigns
Mimecast90 domains bounced / 1 accepted30 bounced / 1 acceptedabout 99% bounce
Sophos8 bounced / 0 acceptedsame pattern, small volume100% in the sample
Proofpoint0 bounced / 21 accepted0 bouncedabout 1%
Microsoft 365, Google, Barracuda, Cisco IronPort, Trend Micro, Fortinet, Zoho, GoDaddyabout 1%about 1%about 1%
Effect of removing Mimecast and Sophos domains before sending
CampaignShare of pool removedBounce per lead beforeBounce per lead after
A (hiring signal, marketing leaders)16.7%16.95%0.84% (116 of the 121 bounces were Mimecast)
B (DTC brands)1.3%1.76%0.72% predicted, 0.30% measured in production on the next sends

Why no verifier sees it

Mimecast rejects at the SMTP handshake based on the reputation of the sending domain, not on whether the mailbox exists. A fresh sending domain (lookalike, recently warmed) is refused whatever the address. Verifiers test whether the recipient domain accepts a recipient at the SMTP stage, which Mimecast gladly does before rejecting the actual delivery. The result is a bounce on addresses scored 99/100 and not catch-all. In the platform logs these show up with a generic provider code rather than a Google or Microsoft code.

On a 5,650-send baseline, 51% of all bounces came from Mimecast-gated domains, which bounced at 98%. Outside Mimecast, addresses rated 'Deliverable' bounced at 4.0% and catch-all addresses scored 90 to 99 bounced at 2.6%.

The strict-verifier test that still bounced at 16.9%

Before we had the MX filter, 714 leads survived the strictest verifier gate we used (score 80 or more and not catch-all; that gate had already discarded 37% of the pool). Sent, they produced 121 bounces per lead, 16.9%. The bounced domains were large organizations (transport federation, health insurer, real estate, SaaS) behind Mimecast or Proofpoint-type gateways. Verification cannot fix a pool whose domains are the problem.

Proofpoint is innocent

Earlier post-mortems blamed 'Mimecast/Proofpoint'. The MX breakdown shows Proofpoint-gated domains at 0 bounces on 21 accepted domains in campaign A. Blocking Proofpoint would discard clean volume. Only Mimecast and Sophos are filtered.

The filter

One DNS MX lookup per recipient domain, cached, about 25 in parallel, zero cost. A domain is removed when any MX host contains 'mimecast' or 'sophos'. Cost of the filter: 1 to 17% of a pool depending on the population (B2B enterprise lists lose far more than DTC brand lists). This step now runs before every send, before the verifier.

What this measurement does not say

Questions

Should I exclude Mimecast domains from cold email lists?

If your sending domains are young, yes: in our data they bounced at about 99%. Exclude them with a DNS MX lookup before verification; it is free and removes about half of the bounces.

Does Proofpoint block cold email?

Not in our measurement: 0 bounces on 21 Proofpoint-gated domains. Do not filter Proofpoint.

Related measurements

Want this run on your pipeline?

We operate multichannel outbound (cold email, LinkedIn, paid retargeting, newsletters) for B2B companies, and we measure it the way these pages do.

Book a call