Identify the provider that actually hosts the domain’s mail and record the current routing choice. Check authoritative MX records, not only a DNS zone copied into cPanel.

1. Open Email Routing and select the domain.
2. Choose Local Mail Exchanger when this server accepts the domain’s mail into local mailboxes. Choose Remote Mail Exchanger when the domain uses an external provider.
3. Use Backup Mail Exchanger only for an intentionally configured backup-mail design. It is not the normal choice for Google Workspace, Microsoft 365 or another remote mailbox provider.
4. If using Automatically Detect Configuration, remember that cPanel evaluates its local zone records. It does not continuously discover later external DNS changes for you.
5. Save, send an external inbound message and trigger a test from a website on the same server. Confirm both arrive at the real provider.

Local website messages and external senders should reach the same intended mail system. Verify that no important message remains in an old local mailbox after a migration.

If external delivery works but the website’s mail does not, recheck routing, application SMTP settings and local filters. If neither works, inspect MX records and the destination provider. Revert only to a recorded configuration that matches the real mail service.

This setting controls local mail handling. You must separately publish the correct MX and supporting DNS records at the domain’s authoritative DNS provider.

• Tracing a missing message with cPanel Track Delivery
• Configuring an application to send through authenticated SMTP
• Choosing safe handling for mail sent to nonexistent addresses
• Suspending a mailbox login or outgoing mail without deleting it

• cPanel: Email Routing
• cPanel: Track Delivery