How do ISPs differ in spam folder vs block behavior?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
You sent a campaign and the numbers look off. Opens are low, but you're not sure if your emails are sitting in spam folders or never arriving at all. Those are two very different problems, and the ISP your subscribers use plays a big role in which one you're dealing with.
Here's the core difference. Getting spam-foldered means your email was accepted and delivered, just not to the inbox. Getting blocked means the receiving server rejected your email outright, usually before it ever touched a folder. Both hurt your results, but you diagnose and fix them very differently.
How the big three handle it
Gmail strongly prefers spam-foldering over blocking. When Gmail doesn't like a sender, it accepts the message and quietly routes it to the spam folder. This means your ESP will report the email as "delivered" even though no one will ever see it. Low open rates on Gmail-heavy lists are often the first real signal that something is wrong.
Outlook (and Microsoft 365) is more willing to block at the connection level. If your sending IP has a bad reputation in their systems, Microsoft's SmartScreen filters may reject the connection entirely and send back a bounce. You'll see a 550 or 421 error in your sending logs. The message never arrived. No delivery, no folder, nothing.
Yahoo Mail (which also powers AOL Mail) tends to mix both behaviors depending on what's triggering the issue. A rate-limiting problem usually shows up as a temporary 421 deferral first. A content or reputation problem tends to result in spam-foldering rather than an outright block.
Why the difference exists
Each ISP has a different user base, infrastructure philosophy, and risk tolerance. Gmail runs on massive engagement data and machine learning, so it can make nuanced placement decisions rather than blunt blocks. Microsoft serves a lot of enterprise customers where blocking bad mail at the perimeter is considered the right security posture. Yahoo sits somewhere in the middle and has historically been quicker to defer or throttle high-volume senders before making a permanent filtering decision.
Authentication also plays differently across each one. SPF, DKIM, and DMARC failures are more likely to trigger an immediate block or rejection at Microsoft than at Gmail, where a failing authentication record might just lower your reputation score gradually over time. You can read more about how ISPs weigh authentication signals differently if you want to go deeper on that.
How to tell which one is happening to you
This is the practical part. Look at your bounce reports first. A hard bounce (5xx error code) or a deferred retry storm (4xx codes) points to blocking or throttling. If you're seeing 250 OK responses in your sending logs but opens are dead, you're almost certainly getting spam-foldered somewhere.
Breaking your campaign reports down by domain helps a lot. If Gmail subscribers show 8% open rates and Microsoft subscribers show 1.2%, that's a signal worth acting on. Some ESPs let you filter by recipient domain natively. If yours doesn't, you can export and segment manually.
Google Postmaster Tools gives you inbox placement and spam rate data specifically for Gmail. Microsoft's SNDS (Smart Network Data Services) does something similar for their network. These are free and worth setting up even if nothing feels broken right now.
If you're not sure whether your domain is sitting on a blocklist (which often causes connection-level rejections), you can check with our free blocklist checker. It runs your domain and IP against the major lists in seconds. If something shows up there, that explains a lot.
And if you're genuinely stuck trying to piece together what's happening across different ISPs, our SOS hotline is free. We'll help you read the signals without trying to sell you anything.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.