HackerNews中文版

我使用 MongoDB Cloud 已经超过 7 年了，账户注册时使用的邮箱地址结尾是 .con —— 只是 .com 的一个简单笔误。多年来，一切运行完美：注册、账单、访问，一切正常。但最近，我突然被锁定了，原因是“您无法验证您的电子邮件”。当然，.con 甚至不是一个有效的通用顶级域。这意味着 MongoDB 的系统不仅在注册时接受了它，而且还让它运行了 7 年而没有出现问题。现在我无法访问我的数据或账户，并且支持部门表示，由于安全策略要求使用错误的通用顶级域电子邮件进行验证，他们无法更改账户。我理解人为错误是难免的——但允许一个不可能存在的域名运行近十年，感觉像是一个值得标记的验证问题。还有人在生产系统中遇到过类似的情况吗？

查看原文

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 年之后，才锁定了我的账户。