On this page
Short answer
A high bounce rate usually means the list has old or unverified addresses. Read the bounce texts: 'account does not exist' is a bad address, while reputation or policy texts are blocks and need a different fix. Stop the campaign, verify and clean the list, remove every hard-bounced address everywhere, and don't retry permanent failures. Check whether the bounces come from cold email or from warmup.
Two kinds of bounce
Not every bounce means a bad address. Sort them by the text before you act:
Type | Example text | Meaning | Fix |
|---|---|---|---|
Bad address | Gmail | The address is dead | Remove it everywhere |
Block | Gmail | The provider refused the sender | See 550 5.7.1 |
Temporary | Gmail | Deferred; your server retries | Slow down; see 421 4.7.28 |
Authentication | Gmail | SPF, DKIM or DMARC failed | See 550 5.7.26 |
Codes and texts are from Google's SMTP error reference and Microsoft's documentation.
A high rate of bad-address bounces is a list problem. A high rate of blocks is a reputation problem that list cleaning won't fix. When the bounce text names a blocklist, run an email blacklist check on the sending domain and its IPs.
Why lists bounce
Age. Contact data decays as people change jobs. A list bought or scraped months ago has more dead addresses than it had at the start.
No verification, or weak verification. Verifiers can't confirm every address. Personal Gmail addresses are hard to verify, and some providers hide whether an address exists. On business lists this hits Google Workspace domains hardest (data below).
Re-uploading the same list. Addresses that bounced in one campaign get added again in the next.
Domains without working mail. Companies that closed or moved no longer accept email at the old domain.
Why a verifier returns catch-all for so many Google Workspace addresses
Outreach2day data, September 2026
When we verified 141,508 B2B addresses in September 2026, 44% of the ones hosted on Google Workspace came back catch-all, against under 1% on Microsoft 365. Domains behind a security gateway were catch-all for half of their addresses.
Recipient mail host | Addresses | Valid | Catch-all | Invalid |
|---|---|---|---|---|
Google Workspace | 66,589 | 43.4% | 44.3% | 12.2% |
Microsoft 365 | 39,738 | 82.2% | 0.8% | 17.0% |
Security gateway | 8,041 | 41.0% | 50.4% | 7.3% |
Other mail hosts | 25,930 | 50.5% | 26.1% | 19.6% |
All | 141,508 | 55.1% | 28.7% | 15.4% |
How we measured. 141,508 B2B addresses on 80,425 company domains from our own outreach lead pool, checked with one commercial verifier on 25 September 2026 and grouped by each domain's MX records (security gateway: Proofpoint, Mimecast, Barracuda or Cisco in front of the mailbox). Valid, catch-all and invalid are the verifier's verdicts; the rest came back unknown (0 to 4% per row). One list skewed to small tech and agency companies; actual bounce rates per group were not measured.
A catch-all verdict means the receiving server accepted a test address that should not exist, so the verifier cannot tell live mailboxes from dead ones on that domain. It describes the domain and says nothing about the person. On a list where half the contacts use Google Workspace, about a fifth of the whole list can land in this group, and their bounce risk is invisible before you send.
What to do with them:
Keep them out of your main campaign. Send verified addresses first, so a bad catch-all batch can't raise the bounce rate of your best leads.
Test a small slice. Send a few hundred catch-all addresses at low volume per mailbox and stop that group if bounces pass 2%.
Drop catch-alls entirely only when you can afford to. On a Google-heavy list that removes almost half of the Google contacts.
Still verify Microsoft 365 lists. Almost every address there gets a clear answer, and 17% of them came back invalid in our data, more than on Google Workspace.
What the providers expect
Yahoo: "You should not retry delivery of the message. It will never complete successfully. You should remove the email address from your mailing list" (Yahoo error codes).
Google recommends to "Automatically unsubscribe recipients who have multiple bounced messages," and, when messages start bouncing or being deferred, to "reduce the sending volume until the SMTP error rate decreases" (sender guidelines).
Microsoft asks senders to "Remove invalid addresses regularly to reduce spam complaints, bounces, and wasted messages" (Outlook requirements).
Yahoo also lists "Excessive unknown recipients" as a reason it may refuse your mail. Many bounces are also a reputation signal.
What to do
Pause the campaign that is bouncing.
Sort bounces by text. Bad address, block, temporary or authentication. The email bounce decoder sorts one bounce at a time.
Verify the rest of the list before sending again. Move catch-all addresses into their own small campaign, and remove them and other risky addresses if the bounce rate stays high. The free email list cleaner removes duplicates, malformed and role addresses from the CSV first.
Suppress hard bounces everywhere, across all campaigns and sending tools, so they are never re-uploaded.
Check warmup separately. Bounces in warmup traffic point to the warmup network.
Resume at lower volume and watch the bounce rate per mailbox for a few days.
Free guide19 min read
Send 100,000 cold emails a month
Domains and mailboxes you need, DNS, warmup, lists, copy and follow-ups, with a launch checklist, sent to your inbox.
When the bounce rate is zero
A bounce rate of exactly 0% on a large send is suspicious. Some setups don't pass bounces back to the sending tool, so dead addresses go unnoticed and a "pause above X% bounces" rule never fires. Verify lists anyway, and use placement tests and auto-reply rates as a second check.
Questions
Do role-based addresses bounce more in cold email?
Not as a rule: a role address such as info@, sales@ or support@ can be valid, invalid or catch-all like any other address, so verify it the same way. Keep one only when that shared inbox is the right recipient for your offer. For cold outreach the free email list cleaner removes role addresses from the CSV before you verify the rest.
What we recommend at Outreach2day
Each mailbox shows its bounce rate next to its warmup inbox and spam rate, so you can see which campaign or list is bouncing. Clean lists before sending, keep to up to 25 cold emails per mailbox a day, and remove dead addresses for good.
Sources
- Google Workspace Admin Help: Gmail SMTP errors and codes: support.google.com/a/answer/3726730
- Yahoo Sender Hub: SMTP error codes: senders.yahooinc.com/smtp-error-codes
- Google: Email sender guidelines: support.google.com/a/answer/81126
- Microsoft: Outlook's new requirements for high-volume senders: techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730
Related answers
- What Does a 550 5.7.1 Bounce Mean, and How Do I Fix It?Bounces and errors
- What Spam Complaint Rate Is Too High for Cold Email?Bounces and errors
- Are Inbox Placement Tests Reliable for Cold Email?Warmup
- Should I Send Cold Email to Personal Gmail Addresses?Gmail and Google
In depth on the blog
- How to Choose an Email Verification Program9 min read
- Email Campaign Performance Metrics: What to Track7 min read

