# Suppression Lists, Bounces and Complaints Explained

> What hard bounces, soft bounces, complaints and unsubscribes mean for your suppression list, how to read bounce codes, and who never gets mailed again.

Canonical: https://www.cresca.xyz/blog/suppression-lists-and-bounces
Author: Lalit Kumar Jangid
Published: 2026-08-29
Last updated: 2026-10-26

A suppression list is the set of addresses you have decided never to email, no matter which list, segment or import they turn up in. It sits in front of every send as a final filter.

For how large sends are paced and temporary failures retried, see [why queued sending matters at scale](https://www.cresca.xyz/blog/queued-sending-why-it-matters-at-scale).

Getting it right is one of the cheapest ways to protect your sender reputation. Getting it wrong, usually by re-importing an old spreadsheet, can undo months of careful sending in a single campaign.

## What are the four reasons an address gets suppressed?

An address gets suppressed for one of four reasons: a hard bounce, repeated soft bounces, a spam complaint or an unsubscribe. A hard bounce for a non-existent mailbox, a complaint and an unsubscribe are suppressed straight away, while soft bounces are retried first and, under a sensible house rule, suppressed after failing on several consecutive campaigns.

### Hard bounce

The receiving server said the message can never be delivered as sent. The most common cause is that the mailbox does not exist. In the standard bounce codes defined in [RFC 3463](https://www.rfc-editor.org/rfc/rfc3463), these are the 5.X.X "permanent failure" codes, and X.1.1 specifically means the destination mailbox does not exist.

**Rule:** suppress on the first hard bounce for a non-existent mailbox. Do not retry.

### Soft bounce

Delivery failed for a reason that might clear up, such as a full mailbox or a server that is temporarily refusing mail. RFC 3463 calls the 4.X.X class "persistent transient failure": the message itself is fine, but something temporary stopped it.

**Rule:** retry, but do not keep retrying forever. Google's [sender guidelines](https://support.google.com/a/answer/81126) recommend automatically unsubscribing recipients whose messages bounce repeatedly. A sensible house rule is to suppress after soft bounces on several consecutive campaigns, with no successful delivery in between. Pick a number, write it down and apply it consistently.

### Spam complaint

The recipient clicked "Report spam." This is the strongest negative signal you can get, because it tells the mailbox provider directly that your mail was unwanted.

**Rule:** suppress immediately and permanently. Never send that person marketing again unless they opt in again themselves.

### Unsubscribe

The recipient asked to stop. This is a legal obligation in most countries as well as a reputation issue.

**Rule:** suppress immediately. Google's [bulk sender FAQ](https://support.google.com/a/answer/14229414) expects unsubscribe requests to be honoured within 48 hours, and Yahoo's [sender FAQs](https://senders.yahooinc.com/faqs/) say an unsubscribe not honoured within 2 days does not meet their requirement.

## Reading real bounce messages

Bounce messages contain a three-digit SMTP reply, an enhanced status code and some human-readable text. Gmail publishes its [SMTP error reference](https://knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes), and a few codes come up again and again:

| Code | What Gmail says | Type | What to do |
| --- | --- | --- | --- |
| 550 5.1.1 | The email account that you tried to reach does not exist | Hard | Suppress now |
| 452 4.2.2 | The recipient's inbox is out of storage space | Soft | Retry; suppress if it persists across sends |
| 421 4.7.28 | Gmail has detected an unusual rate of email | Soft (about you, not the recipient) | Slow down; check volume and complaints |
| 550 5.7.1 | A policy prohibits the email that you sent | Policy block | Investigate content, authentication and reputation before resending |

Notice the last two rows. Not every bounce is about a bad address. Rate limits and policy blocks say something about **you**, and suppressing those recipients would hide the real problem. If a large share of a campaign gets the same 4.7.x or 5.7.x code, treat it as a deliverability incident, not as list cleaning. Our guide to [why emails go to spam](https://www.cresca.xyz/blog/why-emails-go-to-spam-and-how-to-fix-it) covers the usual causes.

## Where do spam complaints come from?

You only learn about a spam complaint when the mailbox provider tells you. Yahoo's Complaint Feedback Loop sends a report each time a recipient marks your DKIM-signed mail as spam, while Gmail's Postmaster Tools shows only your overall spam rate. You will never see every complaint, so act on the pattern.

You only learn about a complaint if the mailbox provider tells you. Yahoo runs a [Complaint Feedback Loop](https://senders.yahooinc.com/complaint-feedback-loop/) that sends a report each time a recipient marks your mail as spam. It only works for DKIM-signed mail, because the signature is how Yahoo knows which domain to report to. Gmail works differently: its Postmaster Tools shows your overall spam rate rather than a list of who complained, and Google asks senders to keep it below 0.1% and never reach 0.3%.

The practical consequence: you will never see every complaint. Treat the ones you do see as a sample and act on the pattern, not just the individual address.

## How Cresca handles suppression

Cresca suppresses hard-bounced addresses across the whole platform, so an address that has proved not to exist is not mailed again by anyone. Complaints are suppressed per sender: if someone reports your mail, you will not mail them again, without affecting other senders. If a campaign's bounce or complaint rate climbs too high, sending pauses automatically so you can investigate before more damage is done. Campaign reports show bounces, complaints and unsubscribes for each send, which is where you spot a problem source.

## Five rules for a suppression list that holds

1. **Suppression beats everything.** If an address is suppressed, it does not matter which tag, segment or import contains it. The send skips it.
2. **Never delete suppressed contacts to "clean up."** Deleting the record also deletes the memory of why they were suppressed. The next CSV import brings them straight back.
3. **Check imports against your suppression list before sending.** Old CRM exports and event lists are the most common way bad addresses sneak back in.
4. **Keep the reason and the date.** "Hard bounce, 2026-03-14" is useful. A bare flag is not.
5. **Only the person can reverse it.** If someone who unsubscribed or complained wants back in, they should sign up again themselves. Do not add them back on their behalf because they emailed support.

## How do you know your suppression process has a gap?

Your suppression process probably has a gap if bounce rates are high right after an import, the same addresses bounce on several campaigns, people reply saying they already unsubscribed, or complaints rise when you mail an old segment you have not used in a while. Trace any one of these back to its source.

- Bounce rates are high on campaigns sent right after an import
- The same addresses show up as bounced on several campaigns
- People reply to a campaign saying "I already unsubscribed"
- Complaint rates rise when you mail an old segment you have not used in a while

Any one of these is worth tracing back to its source. For the wider routine that keeps a list healthy, see our [list hygiene protocol](https://www.cresca.xyz/blog/list-hygiene-protocol-that-protects-reputation).
