cPanel email vocabulary confuses people: account, alias, forwarder, mailbox, address. These mean different things, behave differently, and have different costs. Picking the wrong type creates avoidable problems — missing mail, doubled storage, broken “send as” replies. This guide explains each, what they’re for, and how to pick.
Email account (full mailbox)
A full mailbox with its own login, password, and storage. Messages delivered to it are stored on the server until you read/delete them via webmail, Outlook, or IMAP client.
Use cases:
- You’re a real person who needs to receive and store email.
- Multiple people need to access the same mailbox (shared support@).
- Email must persist on server (compliance, multi-device access).
Create via cPanel → Email Accounts → Create.
Each account consumes mailbox quota. Limits set per account in cPanel.
Email forwarder
Routes email from one address to another. No storage at the forwarder address; messages immediately forwarded elsewhere.
Example: info@yourdomain.com forwards to you@yourdomain.com. Someone emails info@; the message lands in you@’s inbox. info@ has no mailbox of its own.
Create via cPanel → Email → Forwarders.
Forwarders are basically free — no storage, no quota impact. You can have hundreds.
Limitations:
- Forwarded mail can sometimes break SPF (your server sending mail “from” the original sender to the destination). Sender’s SPF doesn’t list your server.
- “Reply” replies to original sender; if the destination wants to reply AS info@yourdomain.com, you need additional setup (Send As alias).
- Forwarding TO external addresses (Gmail, Outlook.com) sometimes triggers spam filtering at destination.
Email alias (cPanel “Address-Specific Aliases”)
Within a single email account, an alias is an additional address that delivers to the same mailbox. The mailbox owns multiple addresses.
Example: account is you@yourdomain.com. You add aliases sales@yourdomain.com and contact@yourdomain.com. All three addresses deliver to one mailbox.
This is FUNCTIONALLY similar to a forwarder pointing to the same mailbox — but managed differently in cPanel and presented as part of the account.
cPanel’s mechanism for “aliases” varies by version. Often achieved with forwarders.
Default address (catch-all)
Special routing for mail to nonexistent addresses on your domain. Catch-all guide. Briefly: usually don’t enable.
Side-by-side comparison
| Account | Forwarder | Alias | |
|---|---|---|---|
| Storage on server | Yes (own quota) | None | Uses parent’s quota |
| Own password / login | Yes | No | No |
| Receives mail | Yes | Forwards to destination | Delivered to parent |
| Sends mail as this address | Yes (own SMTP) | No | Through parent’s SMTP |
| Count limit | Per hosting plan | Unlimited typically | Tied to account count |
| Typical cost | One mailbox | Free | Free |
Common scenarios — which to use
Sole proprietor, one person
- One account: you@yourdomain.com.
- Forwarders: info@, contact@, sales@, support@ → all to you@.
- Maybe alias if you need to send AS those addresses for replies.
Small team, 5 people
- 5 accounts: name@yourdomain.com per person.
- Shared inbox: support@yourdomain.com as forwarder to multiple team members, OR as its own account that team members access via shared IMAP login.
Multiple departments
- Each department has its own account (sales@, support@, billing@).
- Individuals have their own accounts.
- Personal forwarders for names that route to people (jane@ → jane.smith@).
Forwarding to external email
- Forwarder from you@yourdomain.com → you@gmail.com.
- Set up SPF/DKIM/DMARC correctly to reduce spam-filtering on forwarded mail. Authentication setup.
- Set up Gmail to “Send mail as” you@yourdomain.com so replies come from your domain.
Sending mail “as” a forwarder
Common confusion: forwarders receive but don’t send. Mail comes to info@; user replies; reply goes “From: you@” instead of “From: info@”.
To send AS info@yourdomain.com, you need:
- Either an actual mailbox for info@ (then it’s an account, not a forwarder), or
- “Send as” configuration in your mail client (Outlook, Gmail). Reply messages will show info@ as sender, even though there’s no info@ inbox.
Gmail “Send Mail As” instructions:
- Gmail → Settings → Accounts and Import → Send mail as → Add another email address.
- Enter info@yourdomain.com. Uncheck “Treat as alias” if you want SMTP from your domain.
- SMTP server: mail.yourdomain.com, port 465 SSL, your-account password.
- Gmail sends verification email. Click link.
- Now you can reply from info@ via Gmail.
When forwarders break
Modern mail systems treat forwarders cautiously due to abuse.
- Gmail / Outlook reject forwarded mail as spam. Solution: SRS (Sender Rewriting Scheme) — cPanel handles automatically.
- DMARC reject from sender’s domain. When sender’s domain publishes DMARC reject, forwarding can break authentication. Less you can do server-side.
- Forwarded mail loop. A forwards to B; B forwards back to A. Mail server detects after several hops and stops.
For business-critical reception, prefer an actual mailbox over a forwarder to external service.
Common questions
“Can I have a forwarder forward to multiple addresses?” Yes — list multiple destinations. Mail copies to each.
“Does forwarding count against bandwidth?” Yes — incoming + outgoing transfer. Usually small.
“Forwarder to Gmail — Gmail says ‘no such address.'” SPF issue or invalid destination. Check destination address is correct. SPF.
“How many forwarders can I have?” Typically thousands. Practical limit is your management overhead.
“Can I forward to a mailbox AND keep a copy?” Yes — make destination address an actual mailbox, then add additional forwarder pointing the same source to another destination. Both receive copies.
“If I delete the source account, does the forwarder break?” If source was an account with a forwarder layered on it, removing the account removes the forwarder. If source was a pure forwarder (no underlying mailbox), it stays until you delete it.
What’s next
- Catch-all (default address): Catch-all guide.
- Auto-responders: Vacation responses.
- Authentication: SPF/DKIM/DMARC.
The basic rule: accounts are mailboxes that store mail, forwarders route mail elsewhere, aliases are additional names for the same mailbox. Most small businesses need 1-5 accounts (real people, shared boxes) and 5-15 forwarders (info@, contact@, plus name routing). Done right, the setup is invisible — mail reaches the right person at the right address with no inbox bloat.
Was this helpful?
Thanks for your feedback!
