When an email doesn't reach its destination, the receiving server sends back a bounce message explaining why. That explanation falls into one of two categories: soft bounce or hard bounce. They require completely different responses, and handling them wrong will damage your sender reputation in ways that carry into every future campaign you run.
A soft bounce is temporary. The email couldn't be delivered right now, but the address itself is valid. A hard bounce is permanent — the email can't be delivered to that address, full stop. If you treat hard bounces the way you treat soft bounces and keep retrying, you'll rack up complaint signals that train mailbox providers to send your emails to spam across your entire list.
What Is a Soft Bounce?
A soft bounce means the email reached the recipient's mail server but couldn't be delivered at that moment due to a temporary condition. The server recognized the address as valid but couldn't accept the message right now. Most sending platforms will automatically retry soft bounces after a delay.
Common Causes of Soft Bounces
- Mailbox full. The recipient has hit their storage limit and can't accept new messages. Common with older or less-maintained inboxes. Usually resolves on its own once the recipient clears space.
- Server temporarily unavailable. The recipient's mail server was down, overloaded, or undergoing maintenance when your email arrived. A retry 15-30 minutes later often succeeds.
- Message too large. Your email exceeded the size limit the receiving server will accept. Heavy attachments or image-heavy HTML emails commonly trigger this. Keep cold emails lean. Plain text or minimal HTML performs better anyway.
- Greylisting. Some servers deliberately delay emails from unknown senders on first contact and accept them on retry. This is a soft bounce that resolves automatically on the second attempt.
- Sending limits exceeded. If you're sending at high volume and hit rate limits at the receiving server, emails queue up and bounce temporarily until the rate drops.
Soft bounces are normal at low rates. A campaign with a handful of soft bounces means nothing. When soft bounce rates climb, or when the same addresses keep bouncing repeatedly, that's when you need to act.
What Is a Hard Bounce?
A hard bounce means permanent delivery failure. The email can't be delivered to that address, and retrying will not change that outcome. Hard bounces are a signal to remove the address from your list immediately and never send to it again.
Common Causes of Hard Bounces
- Invalid or nonexistent email address. The address was typed wrong, the user made a typo, or it was never real in the first place. The receiving server has no record of this mailbox.
- Domain doesn't exist. The domain portion of the email address (
@company.com) doesn't have valid DNS records or no longer resolves. The company may have rebranded, gone out of business, or the domain lapsed. - Address has been deleted or deactivated. The account existed but has been shut down. A former employee whose inbox was closed is a common example.
- Receiving server permanently blocking your domain or IP. The server has a policy-level block on your sender domain or IP address. Every email you send from that infrastructure will bounce for every recipient at that server.
Hard bounces require immediate action. Every hard bounce is a negative signal to the mailbox providers watching your sending behavior. Accumulate enough of them and your sender reputation takes damage that follows your domain and IP address into every future campaign.
The Deliverability Impact of Each Bounce Type
Bounce rate is one of the signals mailbox providers use to evaluate your sender reputation. It's one of the most visible ones, and it's entirely within your control if you manage your lists correctly.
How Hard Bounces Damage Sender Reputation
Every hard bounce tells the receiving server: this sender is mailing addresses that don't exist. That's a spam signal. Real email senders — businesses communicating with customers, partners, and prospects — have clean lists with minimal invalid addresses. Senders with high hard bounce rates are either buying junk lists, not verifying addresses, or not maintaining their lists over time. Mailbox providers know this and penalize accordingly.
The damage compounds. A domain that sends to invalid addresses gets its domain reputation dinged. Its emails start landing in spam across the board, not just at the specific domains that generated the bounces. The same thing happens at the IP level: if your sending IP is associated with high bounce rates, that IP's reputation drops and takes every domain sending from it down with it.
How Soft Bounces Affect Deliverability
Individual soft bounces don't meaningfully harm your reputation. Repeated soft bounces to the same address do. If you keep retrying an address that soft bounces 3, 4, 5 times, you're exhibiting a pattern that looks like blasting addresses regardless of engagement. Suppress persistently soft-bouncing addresses after 2-3 failures. They're either bad addresses being misclassified or permanently unavailable inboxes. Either way, continuing to send to them hurts more than it helps.
Bounce Rate Thresholds: What's Acceptable and What Causes Damage
Here are the thresholds to keep in mind:
- Hard bounce rate under 0.5%: Healthy. This is the target for well-maintained lists with verified addresses.
- Hard bounce rate 0.5%–1%: Worth investigating. Your list hygiene may be slipping or you're pulling from sources with lower address quality. Fix it before it gets worse.
- Hard bounce rate above 2%: Active reputation damage. You're in territory where mailbox providers are noticing. Gmail and Outlook both treat 2% as an informal threshold where increased filtering begins. Your inbox placement will drop across the board, not just for the bounced addresses.
- Soft bounce rate under 2%: Normal and expected. Nothing to act on.
- Soft bounce rate above 5%: Look at your list quality and sending patterns. Something is off — possibly stale data, overloaded receiving servers, or send volume triggering rate limiting.
Google's updated bulk sender guidelines (rolled out 2024) explicitly call out bounce rates as a deliverability factor. If you're sending more than 5,000 emails per day to Gmail addresses and your bounce rate climbs, expect to see direct inbox placement consequences.
How Gmail and Outlook Handle Bounces
The two dominant B2B email providers behave differently when processing bounces, and understanding each helps you respond faster when something goes wrong.
Gmail / Google Workspace
Google is aggressive about protecting inbox quality. It monitors bounce rates closely and will begin filtering more of your emails to spam when hard bounce rates climb. With repeated sends to invalid addresses or sustained high bounce rates, Google will issue a temporary block on your sending domain or IP. Google's Postmaster Tools gives you access to your domain reputation and spam rate data, which is worth checking regularly if you're running meaningful volume to Gmail addresses.
Outlook / Microsoft 365
Microsoft uses its SmartScreen filtering system and maintains its own sender reputation database called the Smart Network Data Services (SNDS). Microsoft tends to give sending domains more rope before hard filtering, but it has a reputation for issuing outright blocks (550 5.7.1 errors) when senders consistently ignore bounce signals. Once you're blocked at the Microsoft level, getting unblocked requires submitting a delisting request that takes time and doesn't always resolve quickly. Avoiding hard bounces is far easier than recovering from a Microsoft block.
How to Reduce Bounce Rates
Bounce management isn't complicated, but it requires consistency. Here's what actually moves the needle:
Email Verification Before Sending
The most effective lever for reducing hard bounces is verifying email addresses before they enter your sending sequence. Email verification tools check whether an address is deliverable by pinging the mail server and confirming the mailbox exists, without sending an actual email. Tools like BounceBan, Scrubby, NeverBounce, or ZeroBounce can clean your list before you send a single message.
For cold outreach, skipping this step will cost you. Lists pulled from Apollo, LinkedIn, or data providers always contain some percentage of stale or invalid addresses. The rate varies, but running verification typically removes 3-8% of addresses from a fresh list. Those are hard bounces you just avoided.
Regular List Hygiene
Even a list you verified six months ago is degrading. People change jobs. Companies get acquired. Email addresses get deactivated. The longer a list sits without being cleaned, the more hard bounces it will generate when you send to it. Build list cleaning into your regular workflow, not just a one-time step before launch.
Suppression Lists
Every address that hard bounces should go into a suppression list immediately. Most cold email software handles this automatically, but verify that it's actually happening — a misconfigured integration that fails to suppress bounced addresses will keep sending to invalid addresses and keep accumulating bounce rate damage.
Monitor Bounce Signals Actively
Don't wait for your deliverability to drop to start looking at bounces. Build a routine of reviewing bounce reports after every campaign. Look for patterns: Are bounces concentrated on a particular domain? Are they coming from one sending inbox more than others? Are certain data sources producing more invalid addresses than others? Patterns in bounce data usually point to fixable root causes. For a deeper look at how bounce rates connect to broader deliverability health, see our cold email deliverability guide.
How Cold Email Infrastructure Affects Bounce Rates
The infrastructure decisions you make before you send a single email have a direct effect on your bounce rates. Most teams don't realize this until they're already dealing with the consequences.
Dedicated Sending Domains Protect Your Reputation
When you use dedicated sending domains for cold outreach, separate from your primary business domain, bounce damage stays contained. If one sending domain takes reputation hits from a batch of hard bounces, that damage stays isolated to that domain. Your primary domain and your other sending domains stay clean. Domain separation is non-negotiable for anyone sending cold email at meaningful volume.
Using your primary domain for cold outreach means every hard bounce you generate damages the same domain you use for customer communications, proposals, and internal email. That's a routine outcome for teams that skip this step.
IP Reputation and Shared vs. Dedicated IPs
Your IP address carries its own reputation separate from your domain. On shared IP infrastructure, where your emails route through the same IP as hundreds of other senders, someone else's bounce problem becomes your problem. Their invalid addresses and spam complaints drag down the shared IP's reputation, which hurts your inbox placement even if your own list is clean.
With dedicated IPs, your reputation is determined entirely by your own sending behavior. Dedicated IPs require proper warmup though — a brand-new IP needs to build reputation from scratch, which is why the right email warmup strategy is a prerequisite before you start sending cold.
Authentication Records and Bounce Misrouting
Improperly configured SPF, DKIM, or DMARC records can cause legitimate emails to bounce in ways that look like hard bounces. A server that rejects your email because your DKIM signature failed is logging a delivery failure that looks identical to a hard bounce from the sender's side. These authentication bounces are entirely avoidable, but they compound your bounce rate and hurt your reputation all the same. Check your authentication setup regularly — our flagged mail guide covers the most common authentication-related delivery failures and how to fix them.
How ScaledMail Manages Bounces
Bounce management is built into how ScaledMail operates. Every inbox we manage runs with full SPF, DKIM, and DMARC authentication configured correctly from day one, which eliminates the class of bounces caused by authentication failures. Our dedicated sending domains keep bounce damage isolated, and we monitor domain and IP reputation continuously so problems get caught before they compound.
At the scale we operate — 217,600+ inboxes across hundreds of clients — bounce rate monitoring is automated, tracked, and flagged when thresholds are hit. Teams running their own infrastructure often only notice bounce rate problems after the damage is already done. Recovery from a burned sender reputation takes weeks.
The cleaner your infrastructure from the start, the lower your baseline bounce rate will be. Proper domain setup, verified lists, and active monitoring keep hard bounces near zero and soft bounces at normal levels, which means your emails keep hitting inboxes instead of getting filtered.
Putting It Into Practice
Soft bounces are temporary delivery failures you handle by retrying and eventually suppressing. Hard bounces are permanent failures you handle by removing addresses immediately. Both affect your sender reputation when they reach meaningful rates, with hard bounces doing damage much faster and more severely.
The teams with the lowest bounce rates verify addresses before sending, suppress bounced addresses immediately, and run on dedicated infrastructure that keeps reputation damage contained. None of that is complicated. It's the operational baseline that makes everything else work.
If your bounce rates are climbing or your infrastructure isn't clearly defined, ScaledMail provides managed email infrastructure for cold outreach teams: dedicated sending domains, pre-warmed mailboxes, full authentication setup, and deliverability monitoring built in. Setup is 2-4 business days and you keep using whatever sequencer you're already on. Get started at scaledmail.com.
