Inbound Mail Failures in Go — MX Priorities and Leftover Provider Records
go
dev.to
The page fires after inbound player-support mail disappears during a gaming zone cutover. The application is healthy. Outbound mail still leaves. Those signals are distractions: list the complete MX set, compare every target and priority with the intended state, delete records left by the old provider, and list again. TL;DR: an MX upsert doesn't replace the set. A stale destination can remain eligible, and equal priorities across old and new providers produce unpredictable routing rather than a