How to use this order
Work from the top and stop at the first step that fails. Routing, forwarding, authentication and migration faults can each look like "my email is missing", and the fix for one is wrong for the others. Keep the bounce text, the date and the sender, and change nothing you cannot put back. No step here needs you to share a password. Most checks are public lookups, a message you send yourself or a header you read; where a step needs a setting inside a control panel, you or your host look at it.
- Send test messages from two outside providers, and save any bounce.
- Keep the previous value of anything you change, and the time you changed it.
1. Read the bounce
Collect two or three bounce messages and read the three-part status code and the line of text. They separate a bad address, a domain that cannot receive mail and a policy refusal, and tell you which of the next steps to take.
- Guide: reading a bounce message.
2. Where do the MX records send mail?
Look up the domain's MX records and check that each name resolves to an address, none is an alias, and only one provider is listed. Compare with the values your provider says it expects.
- Guide: MX records. Repair: the mail routing job. Existing guide: DNS and email migration.
3. Does your web host think it is the mail server?
If outside mail arrives but messages from your own website or old webmail do not, check the host's routing setting and the host's local MX entries.
- Guide: host mail routing after a mail move. Example: the routing test matrix. Repair: the mail routing job.
4. Is anything forwarded?
If mail passes through a forwarding rule, read the verdict lines of a forwarded message and the provider's forwarding policy. Consider an alias, group or shared mailbox instead.
- Guide: forwarding and sender checks. Repair: the forwarding job.
5. Does it arrive but land in junk?
Mail that arrives in junk is an authentication question, not a routing one. Check SPF, DKIM and DMARC for every service that sends as your domain.
- Existing guide: email authentication. Existing repair: the SPF, DKIM and DMARC job.
6. Is mail being moved, and who keeps it healthy?
If you are changing provider, plan the copy and the MX switch together, and decide what labels or folders become. Afterwards, keep the records checked against a baseline rather than waiting for the next bounce.
- Guides: Gmail labels in a migration; existing IMAP mailbox migration. Repairs: the Google Workspace and cPanel mailbox moves. Standing route: the domain responsibility.
Sources and limits
- RFC 3463: Enhanced Mail System Status Codes Checked 2026-10-11.
- Status codes separate permanent from temporary failures and addressing faults from policy faults.
- RFC 2181, section 10.3: MX and NS records Checked 2026-10-11.
- The name inside an MX record must not be an alias.
- cPanel: Email Routing Checked 2026-10-11.
- A host's routing setting can keep mail for a domain on the server instead of passing it to another mail exchanger.
- Microsoft: Control external email forwarding Checked 2026-10-11.
- A tenant policy can block automatic external forwarding and return a 5.7.520 bounce.