Email Forwarding

Email forwarding sends mail arriving at one domain address to another address, for example [email protected] to a personal Gmail. In cPanel, the feature is called Forwarders; a catch-all captures addresses that were never created.

Common types

Impact on authentication

Simple forwarding can break SPF because the message is relayed from another server, and it can break DKIM if headers change. Common fixes are SRS (Sender Rewriting Scheme) or forwarding through a service that handles authentication. Test from Gmail, Outlook, and another domain.

What to watch for

• Catch-all invites spam. Enable it only when truly needed.
• Do not forward to an inactive address. Bounces damage reputation.
• Keep a copy in the source mailbox when you need an audit trail.
• Forwarding is not a backup. Mail can still be lost if the destination deletes it.
• Avoid loops. Two forwarders pointing at each other can loop.
• SPF alignment. If the destination checks alignment, forwarded mail can fail even when the source SPF is valid.

If the goal is to read domain email in Gmail, consider a full mailbox over IMAP or an email service that supports a custom domain. Simple forwarding is quick to set up but more fragile for important mail. For team addresses, use a group/list or shared mailbox so replies still come from your domain. Test SPF/DKIM after forwarding.

In cPanel, open Email → Forwarders → Add Forwarder, fill in the source and destination addresses, and save. Then send a test email and inspect the Authentication-Results and Received headers to see whether SPF/DKIM still pass.

FAQ