Configure cPanel Email Routing Separately from MX DNS

cPanel Email Routing tells the hosting server how to handle incoming mail for a domain. It does not automatically publish the correct MX records, configure another provider or create a complete backup-mail service. Incorrect local routing can misdirect website-generated mail even while outside senders appear to deliver normally.

Check DNS and local routing separately

Identify the authoritative DNS provider and the mail provider that should receive this domain’s messages. Set the required MX records at the authoritative DNS service, following that mail provider’s exact instructions. Editing a non-authoritative local zone alone does not update public DNS.

Then inspect the cPanel server’s local routing decision. Automatic detection uses its local zone data, not a live authoritative DNS lookup. It should not be treated as a continuously self-correcting watcher for future DNS changes. Recheck local routing after moving mail to or from another provider.

Select the intended route

1. Open the verified HTTPS cPanel interface, then Email > Email Routing.
2. Select the exact domain and review the current state before changing it.
3. Choose the appropriate mode below, or ask support if the server’s role is unclear.
4. Save with Change, reopen the page and confirm the saved mode.

Mode	Role and boundary
Automatically Detect Configuration	Derives local, backup or remote behavior from the server’s local MX zone information. This is not proof the public zone agrees.
Local Mail Exchanger	Accepts the domain’s mail for local delivery. It does not mean delivery to both a local and an unrelated remote mailbox.
Remote Mail Exchanger	Treats delivery as remote, using the appropriate MX route rather than hosting the domain’s receiving mailbox locally.
Backup Mail Exchanger	Acts as a secondary exchanger, holding mail for a lower-numbered exchanger when that exchanger is unavailable. It needs an intentional secondary-MX design; selecting it alone creates no mailbox replica or indefinite retention guarantee.

Verify from more than one source

Check authoritative MX answers, send a harmless external test to a real mailbox, and test an authorized website/application notification from this hosting server. Inspect delivery logs, bounces and the actual destination. Lower MX numbers indicate higher preference, but successful DNS resolution does not prove a server accepts the domain or recipient.

Preserve the previous configuration and rollback plan. Do not remove the old mailbox or change unrelated DNS records before proving the new route. A spam filter, encryption interface or delivery-tracking screen cannot guarantee that every valid message reaches an inbox. For account-specific uncertainty, open a support ticket with timestamps and redacted routing errors.

References: cPanel Email Routing and automatic-detection limits and cPanel Zone Editor.

Reviewed October 15, 2026. Documentation review only; no MX record, mail route or backup exchanger was changed or tested.