Email forwarding lets you receive mail at a custom domain address and redirect it automatically to another inbox, without storing a single message on your server. It is a lightweight, practical solution for role addresses, alias management, and consolidating email from multiple addresses into one place. This guide covers how forwarding works, how to set it up in cPanel and at the DNS level, the common use cases it serves well, and the limitations you need to understand before relying on it.
A forwarder is not a mailbox. It receives an incoming message and redirects it to a destination address, typically a Gmail, Outlook, or other inbox you already use. No email is stored on your hosting server, which means there is no storage quota to manage and no separate inbox to log in to.
This is the key distinction from a full mailbox. A mailbox (IMAP account) stores mail on the server and lets you connect via any email client. A forwarder simply passes the message along. If the destination inbox rejects the message or is unavailable, the original message is lost, there is no retry queue held at your domain level.
Forwarding works at the mail transfer agent (MTA) level. When a message arrives for info@yourdomain.com, your mail server rewrites the envelope destination and sends it onward before it ever touches an inbox.
Log in to cPanel and go to Email → Forwarders → Add Forwarder. In the Address to Forward field, type the username (e.g., info) and select your domain from the dropdown. In the destination field, enter the email address you want mail delivered to, this can be any address, including an external Gmail or Outlook account.
You do not need to create an actual email account for the source address first. cPanel will forward mail to info@yourdomain.com even if no info@ mailbox exists on the server. This is what makes forwarding so low-overhead.
To forward a single address to multiple destinations, simply add multiple forwarders from the same source address. Each one will receive a copy of every incoming message. You can also set the default address (catch-all) under Email → Default Address, which catches all mail sent to usernames that do not match any existing mailbox or forwarder.
If you are not using a cPanel hosting account but still own a domain, you can forward email using a third-party forwarding service such as ImprovMX, ForwardEmail, or Cloudflare Email Routing. These services handle the mail server infrastructure for you, you just point your domain's MX records at them.
The setup process is the same across most providers. Add the MX records they specify in your DNS zone. For example, ImprovMX uses mx1.improvmx.com (priority 10) and mx2.improvmx.com (priority 20). Then log in to the forwarding service dashboard and define which addresses forward where. DNS changes typically propagate within an hour, though up to 24 hours is possible.
Cloudflare Email Routing is worth highlighting if your domain is already on Cloudflare, it is free, requires no third-party account, and is configured entirely within the Cloudflare dashboard under Email → Email Routing. You add destination addresses, verify them, and create routing rules in a few clicks.
Role addresses: info@, hello@, support@, sales@, and billing@ are standard business addresses that visitors expect to find. Rather than creating and maintaining a full mailbox for each, you can forward them all to the one or two inboxes your team actually monitors. A sole trader might forward all five to their personal Gmail account.
Alias addresses: You can create firstname@yourdomain.com for a new staff member before their actual mailbox is provisioned, forwarding their mail to a shared inbox in the interim. Or you can create variant spellings (john.smith@ and jsmith@) that both reach the same destination.
Catch-all forwarding: A catch-all forwarder ensures you never lose mail sent to a mistyped or legacy address. Set your default address to forward to your main inbox and you will catch any message addressed to any username at your domain, regardless of whether that mailbox exists.
Department routing: Forward support@ to a helpdesk tool like Freshdesk or Zendesk, sales@ to your CRM, and billing@ to your accounting software. Each department's email goes directly to the right system without manual sorting.
DMARC and spam classification: This is the most significant practical problem with email forwarding. When your server forwards a message originally sent from, say, a Gmail account, the forwarded message arrives at the destination still appearing to come from Gmail's domain, but now it is being sent by your mail server's IP, which Gmail did not authorise. This breaks DMARC alignment and SPF checks, causing many destination mail servers to classify forwarded messages as spam or reject them outright.
The workaround is SRS (Sender Rewriting Scheme), which rewrites the envelope sender so the forwarded message appears to originate from your domain. Many cPanel servers implement SRS by default, and forwarding services like ImprovMX and ForwardEmail use it automatically. If forwarded mail is landing in spam at your destination inbox, SRS implementation is the first thing to investigate.
Reply-from address problems: When you reply to a forwarded message, your reply comes from your personal Gmail or Outlook address, not from info@yourdomain.com. This is fine for internal use but looks unprofessional in customer-facing communication. If you need to send and receive from your custom domain address, you need a proper mailbox, not just a forwarder.
No server-side archiving: Forwarded messages are never stored on your server. If you need to audit past communications, search across old threads, or meet a compliance requirement to retain business email, forwarding alone is insufficient.
Forwarding works well when you need a professional-looking address that receives mail, and you are happy to manage everything from an existing inbox. A freelancer who just wants hello@mybusiness.com to reach their Gmail account has no reason to set up a full mailbox. Forwarding handles it cleanly with almost zero maintenance.
Forwarding is not enough when you need to send from your custom domain address, when you need server-side message storage or archiving, when you are part of a team that needs shared inboxes or calendars, or when deliverability issues from DMARC failures are creating problems. In those situations, a proper hosted mailbox, either through cPanel, Google Workspace, or Microsoft 365, is the right tool.
Many businesses use both: a hosted mailbox for the addresses people actively send from, and forwarders for role addresses, catch-alls, and old addresses that need to stay active after a domain rebrand.
Every HostBible hosting plan includes custom domain email. No extra charge, no third-party account required.
View Hosting Plans