Hacker News Reader

Comment by tyingq | Hacker News Reader

>but couldn't that be determined by just checking for a bounce when a message is sent to it

The fewer times you bounce, the better your chances of not being marked as a spammer.

This could also be useful for an ecommerce site, where you want to be able to easily contact the buyer if there's a delay, address correction needed, etc. People typo their own email at a rate that's surprising.

View on HN

I use email validation via MailGun for exactly this purpose with a productized service business. If we don't have a good email, then we can't deliver the service once complete. That leads to angry customers, even if the issue was a typo when they created the account. Easier to try and catch it during signup rather than at the time of delivery when emails start bouncing and you have no way to get ahold of the person.

Mailcheck is also helpful to catch things like "user@gnail.com" and other common typos when the user types it in:

https://github.com/mailcheck/mailcheck

Fork modified for React: https://github.com/eligolding/react-mailcheck#readme

I somewhat lol'd when the demo allowed "user@gnail.com" just fine. Guess kickstarter isn't using mailcheck anymore. Looks like it's an open issue:

https://github.com/mailcheck/mailcheck/issues/179

Oh, yeah, that's not good. Not sure why they didn't just repoint to the suggested https://codepen.io/ianneub/pen/BajKKBy demo.

Reply on news.ycombinator.com