---
title: "Discussion on \"Why Email Verification Gets It Wrong: 5 False Verdicts\" | Hashnode"
description: "Discussion on \"Why Email Verification Gets It Wrong: 5 False Verdicts\". Five false verdicts from building an email verifier: Microsoft 365 550s, Yahoo accepting all, fake No MX, dropped connections and stale caches."
url: "https://hashnode.com/posts/why-email-verification-gets-it-wrong-5-false-verdicts/6acf49da8fdafeedaf15c980"
---

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

Discussion

# [Why Email Verification Gets It Wrong: 5 False Verdicts](https://tuanleanh.hashnode.dev/why-email-verification-gets-it-wrong-5-false-verdicts?utm_source=hashnode&utm_medium=feed)

Five false verdicts from building an email verifier: Microsoft 365 550s, Yahoo accepting all, fake No MX, dropped connections and stale caches.

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

-   [#python](https://hashnode.com/tag/python)
-   [#email](https://hashnode.com/tag/email)
-   [#email-marketing](https://hashnode.com/tag/email-marketing)
-   [#smtp](https://hashnode.com/tag/smtp)
-   [#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 1

Markdown supported · ⌘↵ to post

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

[Oct 15](https://hashnode.com/posts/why-email-verification-gets-it-wrong-5-false-verdicts/6acf49da8fdafeedaf15c980/comment/6ad133d11543d809d9d3892a)

The catch-all case is the one that bites most teams. Treating "accepts everything" as valid inflates the list, treating it as invalid throws away real people. Keeping it as its own unknown bucket and mailing it slowly, with a lower volume cap, has worked better for me than forcing a yes or no.
