Skip to content
All articles

Deliverability · 4 November 2026 · 8 min read

Bounce and complaint rates: what is normal and when to stop sending

Rampsend team

Know when to stop sending

Two numbers tell mailbox providers most of what they need to know about a sender. The bounce rate says whether your list is made of real, working addresses. The complaint rate says whether the people on it want your mail. Get both right and the rest of deliverability becomes much easier. Let either drift and your mail starts landing in spam for everyone, including the people who signed up gladly. This guide explains how each rate is calculated, what normal looks like and where to stop.

How the two rates are calculated

The formulas are simple. The denominators are where people go wrong.

Bounce rate = bounced emails ÷ emails sent. Every message you attempt counts in the denominator, because a bounce is a message that was sent and refused.

Complaint rate = spam complaints ÷ emails delivered. Bounced mail never reached an inbox, so it cannot be reported as spam and is left out of the denominator.

A worked example: you send 10,000 emails. 150 bounce, 120 of them hard. Of the 9,850 delivered, 8 people click "report spam".

MetricCalculationRate
Total bounce rate150 ÷ 10,0001.5%
Hard bounce rate120 ÷ 10,0001.2%
Complaint rate8 ÷ 9,8500.08%

That send is healthy on both counts, but the hard bounce rate is worth watching: another few hundred bad addresses and it would cross 2%.

Both rates are usually measured over a rolling window rather than per send, and the providers calculate their own versions per mailbox provider. Gmail's complaint rate is based on Gmail recipients only. A blended average across all providers can look fine while one provider is unhappy.

Hard bounces, soft bounces and blocks

Not every bounce means the same thing. Receiving servers return an SMTP status code, and the first digit tells you most of what you need: 5 is permanent, 4 is temporary.

TypeTypical codesWhat it meansWhat to do
Hard bounce550 5.1.1, 5.1.2The mailbox or domain does not existSuppress at once, never retry
Soft bounce4.2.2, 4.4.xMailbox full, server busy or unreachableRetry; suppress if it keeps failing
Deferral or throttle421, 4.7.xThe provider is slowing you downRetry later; reduce volume to that provider
Block (policy)5.7.xRejected for authentication, reputation or contentFix the cause; do not blame the address

Hard bounces are the ones that matter most. They are the clearest signal of an old, bought or mistyped list, and providers weigh them heavily. A typo like gmial.com, an employee who left the company or an address made up to get past a signup form all bounce hard.

Soft bounces are usually temporary. Sending systems retry them for a while before giving up. An address that soft-bounces on every send for weeks is effectively dead and should be treated like a hard bounce.

Blocks look like hard bounces but are about you, not the recipient. A 5.7.x rejection mentioning authentication means your SPF, DKIM or DMARC needs attention (see SPF, DKIM and DMARC setup). One mentioning reputation or spam means the provider has decided your recent mail is unwanted. Suppressing the address does not fix either.

What counts as normal

These are reasonable working ranges for a permission-based list. They are not official limits, except where noted.

RateHealthyWatch closelyStop and investigate
Hard bounce rateUnder 1%1–2%Above 2%
Complaint rateUnder 0.1%0.1–0.3%0.3% or more

The complaint lines come from Gmail and Yahoo, which require bulk senders to keep their spam rate under 0.3% and recommend staying below 0.1%. The Gmail, Yahoo and Outlook requirements cover the rest of those rules.

Transactional email should sit at the low end of both ranges. Receipts and password resets go to addresses that just used your product, so bounces are rare and complaints rarer. If your transactional rates look like a cold newsletter's, something is wrong with how addresses are collected — often a signup form with no confirmation step.

Why complaint rates are undercounted

When someone clicks "report spam", the provider records it. Whether you hear about it depends on the provider.

Yahoo, Microsoft and several others run feedback loops: they send a report back to the sender for each complaint, which your sending platform turns into a complaint event and a suppression. Gmail does not send individual reports. It shows an aggregate spam rate in Google Postmaster Tools instead.

So the complaint rate in your sending platform mostly reflects non-Gmail recipients, and for a list that is largely Gmail it can look reassuringly low while Postmaster Tools tells a different story. Check both. If Postmaster Tools is the only place a problem shows up, look at what you sent to Gmail recipients over the previous few days.

Where the trouble comes from

High bounce and complaint rates almost always trace back to the audience, not the infrastructure.

High bounces usually come from:

  • importing an old list that has not been mailed in months or years;
  • buying, renting or scraping addresses;
  • signup forms without validation or confirmation, which collect typos and fake addresses;
  • B2B lists, where people change jobs and company mailboxes are closed.

High complaints usually come from:

  • mailing people who did not clearly ask to hear from you;
  • a sudden jump in frequency, or a long silence followed by a send;
  • content that does not match what people signed up for;
  • an unsubscribe link that is hard to find, so the spam button is easier.

The fix follows the cause. Remove the segment, tighten the signup flow, and make unsubscribing easy: Gmail and Yahoo require one-click unsubscribe for bulk marketing mail, and it measurably lowers complaints because people use it instead of reporting you.

When to stop sending

Rates are lagging indicators. By the time a provider reacts, the mail that caused it has already gone. That makes it worth stopping early.

  • A single send bounces hard above 5%. Stop the rest of that send. The list it came from is not safe to continue with.
  • Your rolling hard bounce rate passes 2%. Pause marketing sends, find the segment responsible and remove it before resuming.
  • Your complaint rate passes 0.1%, or Postmaster Tools shows a Gmail spam rate rising towards 0.3%. Stop sending to anyone who has not engaged recently, and review your last few emails for anything that would surprise a subscriber.
  • Blocks with 5.7.x codes spike at one provider. Check authentication first, then reputation with that provider.

Resuming at full volume straight after a problem tends to recreate it. Restart with your most engaged recipients and build back up, much as you would warm up a new domain.

How suppression and auto-pause help

Two mechanisms do most of the protective work, and both should be automatic rather than something you remember to do.

A suppression list stops you emailing an address that has already told you no. Once an address hard-bounces, complains or unsubscribes, it goes on the list, and every future send checks it. That turns a bad address into one bounce instead of one bounce per campaign. The suppression list guide covers what should go on it and when, if ever, something should come off.

Automatic pausing stops a bad send before it finishes. A human might notice a bounce spike hours later; a monitor that pauses sending when rates cross a threshold limits the damage to the first few hundred messages.

In Rampsend both are on by default. Hard bounces, complaints and unsubscribes are suppressed automatically across transactional and marketing mail. When you send to a suppressed address, that recipient comes back with the status suppressed in the send response and is not charged. Sending pauses for the workspace if, over the previous 24 hours, the hard bounce rate reaches 8% (with at least 200 emails sent) or the complaint rate reaches 0.4% (with at least 1,000 delivered); while paused, send requests return sending_paused. Those are emergency brakes, not targets. Our acceptable use policy asks customers to stay below 2% hard bounces and 0.1% complaints, the same lines as above.

The deliverability dashboard shows your bounce and complaint rates and the top bounce reasons, and GET /api/v1/emails/:id returns each message's status and bounce details. An AI assistant connected over MCP can read the same numbers with get_stats; see the MCP docs.

Keeping both numbers low

Healthy bounce and complaint rates come from a few habits: collect addresses with consent and confirmation, mail people regularly so lists do not go stale, make unsubscribing easier than complaining, and let suppression and monitoring run automatically. Most of the work happens before the send, not after. If you are choosing a platform partly on how it handles this, the pricing page shows what each plan includes, and contacts vs emails pricing explains why a clean list also costs less.

Frequently asked questions

What is a good email bounce rate?

For a permission-based list, a hard bounce rate under 1% is healthy and under 2% is acceptable. Consistently above 2% means the list has a quality problem worth fixing before you send more.

What complaint rate is too high?

Aim for under 0.1%, about one complaint per thousand delivered emails. Gmail and Yahoo require bulk senders to stay below 0.3%, and placement suffers well before you reach it.

Should I retry a hard bounce?

No. A hard bounce means the address does not exist or will never accept your mail. Suppress it immediately; retrying only adds more hard bounces to your record.

Why is my complaint rate lower than Postmaster Tools shows?

Gmail does not send individual complaint reports to senders, so your platform's complaint count mostly comes from providers with feedback loops, such as Yahoo and Microsoft. Postmaster Tools is the only place to see the Gmail figure.

Does Rampsend charge for emails to suppressed addresses?

No. Recipients on your suppression list — past hard bounces, complaints and unsubscribes — are skipped, returned with the status suppressed and not charged.

Guides · 6 November 2026 · 6 min read

How an email suppression list works

What goes on an email suppression list, how to handle soft bounces, global vs account lists, and why sending to suppressed addresses hurts deliverability.