---
title: "Comment by StackShortlist on \"Why Email Verification Gets It Wrong: 5 False Verdicts\" | Hashnode"
description: "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. K"
url: "https://hashnode.com/posts/why-email-verification-gets-it-wrong-5-false-verdicts/6acf49da8fdafeedaf15c980/comment/6ad133d11543d809d9d3892a"
---

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

Comment [Why Email Verification Gets It Wrong: 5 False Verdicts](https://hashnode.com/posts/why-email-verification-gets-it-wrong-5-false-verdicts/6acf49da8fdafeedaf15c980)

[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.
