---
title: "Discussion on \"Email Bounce Handling: Verify, Classify, Suppress Safely\" | Hashnode"
description: "Discussion on \"Email Bounce Handling: Verify, Classify, Suppress Safely\". How a Go email platform verifies, classifies and suppresses bounces without killing live addresses: SMTP codes, soft-bounce counters, circuit breakers."
url: "https://hashnode.com/posts/email-bounce-handling-verify-classify-suppress-safely/6acf4a166a87e0f10311528a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Email Bounce Handling: Verify, Classify, Suppress Safely](https://tuanleanh.hashnode.dev/email-bounce-handling-verify-classify-suppress-safely?utm_source=hashnode&utm_medium=feed)

How a Go email platform verifies, classifies and suppresses bounces without killing live addresses: SMTP codes, soft-bounce counters, circuit breakers.

Oct 14 · 6 min read · tuanleanh.hashnode.dev  
Read the article

-   [#golang](https://hashnode.com/tag/golang)
-   [#email](https://hashnode.com/tag/email)
-   [#email-marketing](https://hashnode.com/tag/email-marketing)
-   [#backend](https://hashnode.com/tag/backend)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)

## Written by

[Tuan Le Anh](https://hashnode.com/@tuanleanh)

@tuanleanh · Ho Chi Minh City, Vietnam

  
[View profile](https://hashnode.com/@tuanleanh)

Full Stack Developer · Next.js, NestJS, Go

Full stack developer in Vietnam, 4+ years of TypeScript. I build SaaS products end to end: Next.js on the front, NestJS or Go behind it. I write about email delivery, multi-tenant systems and AI inside products. Portfolio: https://tuanleanh.com

## Responses 3

Markdown supported · ⌘↵ to post

[StackShortlist](https://hashnode.com/@veristria)

[Oct 15](https://hashnode.com/posts/email-bounce-handling-verify-classify-suppress-safely/6acf4a166a87e0f10311528a/comment/6ad133d71543d809d9d38967)

Nice that you call out the cost of over-suppressing. A soft bounce counter with a time window (say 3 soft bounces across 14 days before suppression) avoids killing addresses that just had a full mailbox for a day. Do you also store the raw SMTP code with each suppression? It makes later audits much easier.

[Tuan Le Anh](https://hashnode.com/@tuanleanh)

[Oct 16](https://hashnode.com/posts/email-bounce-handling-verify-classify-suppress-safely/6acf4a166a87e0f10311528a/comment/6ad133d71543d809d9d38967#reply-6ad22d9c384c8807e1d70f40)

Thanks! A time window is a reasonable way to do it too. We went with "consecutive, reset on any delivery" instead: a mailbox that was full for a day gets one delivery afterwards and starts from zero, however long ago the bounces were. A window mostly matters when a contact is mailed rarely, where seven sends can span months.

On the audit question: not on the suppression row itself. That row keeps the category (hard bounce, complaint, unsubscribe, manual), where it came from, and an optional note. The raw SMTP code and the server's reply text live on the send/bounce event that caused it, so an audit goes suppression → source event → the exact response. Fully agree it's worth keeping. Most of the false-bounce fixes in the post were found by reading those raw replies, not the categories.

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/email-bounce-handling-verify-classify-suppress-safely/6acf4a166a87e0f10311528a/comment/6ad133d71543d809d9d38967#reply-6ad2a9723155b5a0737af409)

That reset-on-delivery rule is cleaner than a window for frequent senders, good call. Keeping the raw reply on the event row rather than the suppression row also keeps the suppression table small and fast to check at send time. Thanks for the detailed answer.
