Re:Mailcheck.js - How we decreased sign up confirmation emai...
by eli on Tuesday March 20, 2012 @04:50PM
(#3731487)
Be careful. Some legit domains might not have an MX record. (but could still work; messages will usually go to the A address)
Re:Mailcheck.js - How we decreased sign up confirmation emai...
by dko on Tuesday March 20, 2012 @03:58PM
(#3731210)
No problem! The Mailgun webhooks helped us collect and analyze the delivery failures, so that was really helpful. Thanks for that.
A mx checking service sounds awesome. Keep us posted if you guys do it.
Re:Mailcheck.js - How we decreased sign up confirmation emai...
by asuth on Tuesday March 20, 2012 @04:46PM
(#3731470)
Just doing DNS checks might not be enough:
`$ dig hotnail.com MX` yields results but is still invalid.
Re:Mailcheck.js - How we decreased sign up confirmation emai...
by Zarel on Tuesday March 20, 2012 @05:54PM
(#3731859)
Well, technically, it's valid; it's just unlikely to be what you meant to type. That sort of case should probably be handled separately.
Re:Mailcheck.js - How we decreased sign up confirmation emai...
by jtheory on Wednesday March 21, 2012 @08:15AM
(#3733986)
Well worth noting: auto-correcting the email addresses would be a very bad idea; ditto for stopping them from submitting the form if this is triggered.
But just showing a little note "are you sure you didn't mean [email protected]", then letting them submit anyway, isn't generally annoying even for misfires.
Because there actually are going to be occasional users who mistype "ymail.com" when they mean gmail. Hey, thanks for the warning; the y is right near the g.
Edit: Another good idea from hinathan.