DIAGNOSTIC PLAYBOOK
Plan an email provider migration with parallel verification
A mail-provider migration affects inbound routing and outbound identity through separate mechanisms. Track MX, mailbox provisioning, SPF and DKIM as coordinated but distinct workstreams.
HealthCheck Email editorial team · · Examples are illustrative
How to investigate
- Provision and test recipients at the destination before changing inbound routing.
- Verify new outbound signing and authorization while retaining required old paths during transition.
- Compare incoming and outgoing samples, queues and authentication reports before retiring the old service.
What this looks like
ILLUSTRATIVE EXAMPLE
Inbound mail moves to the new provider, but an application still submits through the old one. Removing old authorization immediately breaks that remaining stream.
A mistake to avoid
Changing MX does not automatically move application SMTP settings or outbound DKIM signing. Inventory those dependencies explicitly.
Keep the result in context
A monitoring routine needs an owner, a baseline and a response to a meaningful change. Keep the sender inventory and approved DNS configuration alongside incident notes. HealthCheck Email supplies checks, history and supported alerts; publishing DNS changes and administering mail systems remain with your team.
Take the next step
Use the related check to gather evidence, then compare it with the affected message or service. Keep the result and time with your notes so a later change can be distinguished from the original problem.
Sources and further reading
The protocol references below explain the underlying behavior. Your sending or DNS provider supplies the account-specific settings for its service.