A hard bounce is a "gone for good" reply.A hard bounce isn't a "maybe next time." It's the receiving server telling you, flat out, this address is gone for good. So here's the one rule that protects your whole list: remove it after the first failure.
⬡ title-card, big line "Remove on the first failure", subtitle "hard bounce = permanent"A hard bounce is a permanent delivery failure. The mailbox doesn't exist, the domain doesn't take mail, or the account's been shut off. It comes back as a 5xx SMTP code, and there's no retry that changes that answer. The server already said no, forever.
⬡ dissect, label a bounce line "550" then "5.x.x = permanent", the word "permanent" glowsDon't send a second time to "confirm."So the rule is simple. Suppress hard bounces immediately, after the first failure. Don't wait for a pattern. Don't send a second time to confirm it. One hard bounce is definitive, and every extra send to a dead address is you telling Gmail and Outlook you don't clean your list.
⬡ journey-flow, envelope flies out, flips red stamped "550", returns, gets dropped into a "Suppress" binHere's the mechanism, because it matters. Mailbox providers watch how much of your mail hits dead addresses. Keep hammering nonexistent mailboxes and your reputation drops, which drags down delivery for your real subscribers too. Some of those dead addresses even get recycled into traps later. Suppressing fast isn't housekeeping, it's protection.
⬡ gauge-meter, reputation needle slides toward red as dead-address sends pile upIf this is clearing things up, subscribe, we're working through every bounce and list-hygiene question one at a time.
One catch most people miss. Your ESP probably auto-suppresses hard bounces, which is great. But suppressed and removed aren't always the same thing. Some platforms stop mailing the address but keep the contact record, so you're still paying for a person you can never email. If you're billed per contact, purge them out entirely.
⬡ split-compare, LEFT "Suppressed (won't send)" vs RIGHT "Deleted (off your bill)", note "check your ESP"And watch the rate. If more than about two percent of a send hard bounces, that's not a few typos, that's a chunk of your list that's stale or was never valid. The fix is validating before your next big send, and taking an honest look at where those addresses came from.
⬡ talking-stat, big "2%", pill "validate before you send"So, hard bounces: permanent, remove on the first failure, purge if you pay per contact, and if your rate creeps past two percent, clean before you send. Catching bad addresses up front is a lot gentler on your reputation than finding out the hard way. That's what our list cleaning does, so a would-be hard bounce never leaves the dock.
⬡ checklist, "Suppress on first fail · Purge if billed per contact · Validate over 2%"Soft bounces are a totally different animal, those you don't remove right away. That's the next video. Subscribe and I'll see you there.
⬡ end-card, Subscribe + Next: "How to handle soft bounces" (005.006.002)How should you handle hard bounces? Remove them after the first failure, every time. A hard bounce is a permanent 5xx SMTP failure (dead mailbox, dead domain, disabled account), and there's no retry that fixes it. This video covers why one hard bounce is definitive, why repeat sends to dead addresses quietly wreck your sender reputation, why "suppressed" in your ESP isn't always "removed from your bill," and what a hard bounce rate over two percent is really telling you.
0:00 A "gone for good" reply
0:15 What a hard bounce is (5xx)
0:40 The one rule: suppress on first failure
1:05 Why repeat sends hurt reputation
1:35 "Suppressed" vs "deleted"
2:05 When the 2% rate is the warning
Concepts in this video: hard bounce, SMTP 5xx, suppression list, sender reputation.
Related: How to handle soft bounces → [005.006.002] · Common hard bounce reasons → [005.006.003]
Full written guide → reviewmyemails.com/emailalmanac/list-management-and-hygiene/bounce-handling-and-definitions/handling-hard-bounces
#email #deliverability #listhygiene