Introduction

A cPanel mailbox can stop receiving mail after a server migration even when the website itself works on the new host. Mail delivery depends on more than mailbox passwords. MX records, local mail routing, Exim or mail service state, mailbox recreation, and copied account data all need to line up on the destination server. The safest fix is to verify both DNS routing and the mailbox state on the new cPanel host instead of assuming the transfer copied mail exactly as it existed before.

Symptoms

  • A cPanel email account stops receiving new mail right after server migration
  • Webmail opens, but inbound messages never arrive in the mailbox
  • The domain website loads from the new server while mail delivery stays broken
  • Some senders get bounces, while others see silent non-delivery or delays
  • The issue started after moving hosting, changing IPs, or updating DNS records

Common Causes

  • MX records still point to the old server or another mail host
  • The domain's mail routing or local mail exchanger setting is wrong on the new cPanel server
  • The mailbox account was not recreated correctly during migration
  • Exim, Dovecot, or related mail services are unhealthy on the destination server
  • DNS and mailbox migration finished in different stages, leaving mail split across old and new hosts

Step-by-Step Fix

  1. Confirm whether incoming mail should land on the new cPanel server or an external provider, because that determines whether local mailbox delivery is even the intended design.
  2. Check the live MX records and make sure they point to the correct mail destination after the migration.
  3. Review the domain's mail routing setting in cPanel so the server treats the domain as local mail only when it truly hosts the mailbox.
  4. Verify the mailbox account exists on the new server with the expected storage, permissions, and login details.
  5. Check webmail, mail logs, and service health on the destination server to confirm Exim and related mail services are actually accepting and delivering mail.
  6. Inspect whether some messages still route to the old host because of stale DNS caches, split MX state, or partial migration timing.
  7. Send controlled test messages after each fix and track whether they hit the new mailbox, bounce, or queue on the wrong server.
  8. If mail data remained on the old host, migrate or reconcile the mailbox contents before decommissioning the previous server.
  9. Keep a mail migration checklist covering MX, routing mode, mailbox recreation, service health, and test delivery so future cPanel moves do not strand inbound mail.