HackerNews中文版

我使用MongoDB Cloud已经超过7年，注册的账户邮箱以.con结尾——这只是一个简单的拼写错误，应该是.com。这些年来，一切运作得非常顺利：注册、账单、访问，都是正常的。但最近，我突然被锁定，原因是“无法验证您的电子邮件”。当然，.con根本不是一个有效的通用顶级域名（gTLD）。这意味着MongoDB的系统不仅在注册时接受了这个域名，而且在没有问题的情况下运作了7年。现在我无法访问我的数据或账户，而支持团队表示由于安全政策要求验证错误的gTLD电子邮件，他们无法对账户进行更改。我理解人类错误是会发生的——但允许一个不可能的域名存在近十年，感觉像是一个值得关注的验证问题。有没有其他人在生产系统中遇到过类似的情况？

查看原文

I’ve been using MongoDB Cloud for over 7 years with an account registered under an email ending in .con — just a simple typo for .com.Everything worked perfectly for years: sign-up, billing, access, all fine.Then recently, I was suddenly locked out because “you can not verify your e-mail.”Of course, .con isn’t even a valid gTLD. Which means MongoDB’s system not only accepted it during registration, but let it function for 7 years without issue.Now I can’t access my data or account, and support says they can not make changes to the account due to security policy that requires verification with wrong gLTD e-mail.I understand human errors happen — but allowing an impossible domain for nearly a decade feels like a validation issue worth flagging.Anyone else seen something similar in production systems?

MongoDB云服务在锁定我的账户之前，接受了一个带有.con后缀的邮箱长达7年。