Back to Building what's next (Interview).
How Can a Mail Record Silently Stop Company Email?
Zeno Rocha says receiving email is tricky because an MX record can compete with Google Workspace on priority. Setup starts by adding an MX record. People who already use Google Workspace then face a fight over which record wins, and the team has to teach them how to handle the conflict.
A distracted setup might break a whole organization. Incoming mail can stop with no warning, and there is no observability that shows the MX record order is wrong. After mail can neither be received nor sent, no channel is left to report the failure.
Building what's next (Interview) ·
From the transcript
But that's just my take. Yeah, receiving is tricky because first, just the setup can be tricky. You add an MX record. But then if folks use Google Workspace, now there's a competition between the priority of the MX record. So you've got to deal with that. You've got to teach users how to deal with that once there's a conflict. So that was one challenge.
And we think a lot about friction. And that can be an action that if someone is just distracted and they try to set up in a way, they might break their whole organization. And they don't even know, oh, my emails are not, you know, I'm not getting any. It's silent, too. It's like there's no observability for you. You know, for like, oh, I broke my MX record ordering.