How to Do Email Routing in cPanel?

Although all hosting servers run all emails with their domain, cPanel allows users to send and manage email accounts through email clients like webmail via SMTP/POP/IMAP connection protocols. Also, cPanel clients can use email routing to direct or “route” incoming domain emails to a different server.
As the domain’s DNS records automatically reflect the changes made in the cPanel, it is a preventive step that aids in the operation of email hosting. It is a fantastic tool that serves as an email backup server in case of server outages or breakdowns.

To Configure Email Routing

1. Log in to cPanel.
2. Click on Email Routing in the EMAIL section.

The Email Routing application will open.

1. Select a Domain from the dropdown list to route its incoming mail to another server.
2. Select the configuration for email routing:
   • Automatically Detect Configuration : Local – It is a recommended configuration setting for email routing. It considers the priority of your MX Records and automatically selects a configuration among Local, Backup, or Remote mail Exchanger.
   • Local Mail Exchanger – By selecting this option, the system will be able to deliver emails to the local mailbox and accept all emails without showing any choice.
   • Backup Mail Exchanger – If the primary mail exchanger with a proper MX entry is down, this option will allow the server to act as a backup exchanger. It can then hold all the incoming mail until the primary mail exchanger comes back online.
   • Remote Mail Exchanger – No mail from this domain will route to the server, i.e., the server will not accept mail for this domain. Instead, it will send all of this domain’s mail to the lowest numbered mail exchanger.
3. Click the Change button.

“Warning: This setting needs to be accurate as it will affect the email activity of an entire domain. If you have no experience or knowledge of email routing or any related cPanel configurations, we suggest you contact support.”

Read more: Encountering a “No such file or directory” error while attempting to remove a NodeJS application via CloudLinux