How to set up email forwarding in cPanel shared hosting

You will configure automatic email redirection so that messages sent to a specific address are delivered to another inbox without the recipient needing to check both accounts. These steps target cPanel 118.x on shared hosting environments where you have access to the control panel. You will create forwarders, set up aliases, and handle domain-to-domain redirection.

Prerequisites

• Root access or an account with reseller privileges to manage the cPanel interface.
• A valid cPanel account running version 118.x or later.
• Active email accounts on the destination server to receive the forwarded mail.
• Knowledge of the exact email addresses involved in the redirection.

Step 1: Log into the cPanel interface

Open your web browser and navigate to the cPanel login URL for your hosting provider. Enter your username and password to access the dashboard. Locate the "Email" section in the main navigation menu and click on the "Forwarders & Aliases" icon.

https://your-server-ip:2083
Username: your-username
Password: your-password

Once logged in, you will see the list of existing forwarders and aliases on the left side of the screen. The right side contains the form to create a new rule. Ensure you are on the correct domain account if you are managing a reseller account.

Step 2: Create a new email forwarder

Enter the email address that will receive the incoming messages in the "Email Address" field. This is the address currently assigned to the mailbox you want to forward. In the "Forward To" field, type the destination email address where the messages should be delivered. Select the delivery method from the dropdown menu to choose between "Forward to another address" or "Forward to multiple addresses".

Email Address: user@example.com
Forward To: admin@example.com
Delivery Method: Forward to another address

Choose whether to forward the entire message or only the message body. If you select "Forward the entire message", the original headers and attachments are included. If you select "Forward only the message body", only the text content is sent to the destination. Click the "Add Forwarder" button to save the configuration.

Step 3: Create a domain-to-domain forwarder

For redirection where emails sent to a specific domain go to a different domain, use the "Forward to another domain" option. Enter the source domain in the "Email Address" field, such as info@example.com. Select "Forward to another domain" from the dropdown menu. Type the destination domain in the "Forward To" field, such as info@example.net.

Email Address: info@example.com
Forward To: info@example.net
Delivery Method: Forward to another domain

This setting is useful for migrating domains or handling legacy addresses. The system will automatically append the original subject line and body text to the forwarded message. Click "Add Forwarder" to apply the rule. You can add multiple rules for different addresses within the same domain by repeating the process.

Step 4: Configure an alias

An alias allows you to create a new email address that forwards to an existing mailbox without creating a new account. In the "Email Address" field, enter the alias address, such as support@example.com. In the "Forward To" field, enter the primary mailbox address that should receive the mail, such as john@example.com. Select "Forward to another address" from the dropdown menu.

Email Address: support@example.com
Forward To: john@example.com
Delivery Method: Forward to another address

Aliases are useful for distributing support tasks among multiple staff members. When a message arrives at the alias, it is immediately delivered to the primary inbox. Click "Add Alias" to save the configuration. You can create multiple aliases for a single mailbox to manage different departments or projects.

Step 5: Manage existing forwarders

To modify or delete existing rules, scroll down to the list of active forwarders and aliases. Click the gear icon next to a specific entry to view its details. You can edit the destination address or change the delivery method from this menu. Click the "Delete" button to remove a forwarder or alias entirely. Confirm the deletion when prompted to ensure the rule is removed permanently.

Verify the installation

Send a test email from an external client like Outlook or Gmail to the forwarder address you just configured. Check the destination inbox to confirm that the message arrived with the original subject line intact. If you configured a domain-to-domain forwarder, send a test email to the source domain and verify it appears in the destination domain's inbox.

Command: echo "Test message" | mail -s "Test Subject" user@example.com

Expected output in the destination inbox should show the message body and the original headers. If the message does not arrive within 5 minutes, check the server's mail logs for delivery errors. Ensure the destination mailbox has sufficient storage space to accept the forwarded messages.

Troubleshooting

• Messages bounce back to sender: Verify that the destination email address is spelled correctly and that the destination server is not rejecting the connection. Check for typos in the destination address in the forwarder settings.
• Forwarding loop detected: Ensure that the destination address does not forward back to the original address. A loop occurs when Address A forwards to Address B, and Address B forwards back to Address A. Remove the conflicting forwarder immediately.
• Attachments not received: If you selected "Forward only the message body", attachments will be lost. Change the setting to "Forward the entire message" to preserve attachments.
• Mail queue full: Check the server's mail queue status. If the queue is full, messages will be rejected. Contact your hosting provider to clear the queue or increase the limit.
• Spam filter blocking forwarded mail: Some destination providers block mail from shared hosting IP ranges. Add the sending server's IP to the recipient's whitelist or use a dedicated mail server for forwarding.

Command: tail -f /var/log/maillog | grep "user@example.com"

Monitor the mail log to see real-time delivery attempts and errors. Look for "550" or "554" error codes which indicate permanent failures. If the error is "550 User unknown", the destination address does not exist. If the error is "550 Relay access denied", the destination server does not trust the source IP.

cPanel updates breaking forwarders: Occasionally, cPanel updates reset forwarder settings. Re-create the forwarders after any major cPanel update. Backup your forwarder list before performing updates to avoid data loss.

Follow these steps to ensure your email forwarding rules are active and reliable. Regularly review the list of forwarders to remove outdated rules. Keep the destination addresses updated to prevent messages from being lost.