Someone on your team wants info@yourbusiness.ca to land in their Gmail. The cPanel screen offers a forwarder and a full mailbox. They pick forwarder because it looks simpler. Six months later deliverability is weird, sent mail still says @gmail.com, and nobody can find that quote from March.
Forwarders and mailboxes are not interchangeable. Both can work. They solve different problems.
What a forwarder does
A forwarder accepts mail for an address on your domain and relays it to another inbox (Gmail, Outlook, a personal account). Mail may pass through your host's mail server briefly, then leave to the destination.
Good for:
- Aliases that should all end up in one existing inbox (sales@, hello@ → you@gmail.com)
- Temporary routing during a migration
- Addresses you do not need to send from
Limitations:
- Sending as @yourdomain still requires SMTP from the host or a proper mailbox/Google Workspace setup
- Spam filtering happens in two places; forwarded mail can look suspicious to Gmail
- No central archive on the server unless the destination keeps everything
- Loops if you forward A→B and B→A (yes, people do this)
What a full mailbox does
A mailbox stores mail on the server (IMAP/POP) or syncs through the host's webmail. You log in with you@yourdomain.ca credentials.
Good for:
- Staff who send and receive as the business domain
- Shared inboxes with retention (office manager, billing)
- Compliance or "we keep mail in Canada on our host" conversations
- Clients who want phone mail apps pointed at mail.yourdomain.ca
You manage quotas, passwords, and backups (ask your host what is included).
Forwarder vs mailbox: quick comparison
- Storage on host: forwarder minimal; mailbox uses disk quota
- Send as domain: mailbox + SMTP natural; forwarder alone is receive-only
- Google Workspace / Microsoft 365: usually full hosted mail, not cPanel forwarders (MX points to Google/Microsoft)
- Cost: forwarders cheap; mailboxes count toward plan limits
- Deliverability: mailboxes with proper SPF/DKIM on the host can be cleaner than long forward chains
After a hosting move, read SPF, DKIM, and DMARC after hosting change and moving email when you change hosts before you flip MX records.
Common Canadian SMB patterns
Solo consultant: Google Workspace for you@domain.ca, no cPanel mail. Website on Swift Host, MX at Google.
Small office on cPanel hosting: mailboxes for staff, forwarders only for aliases (info@ → jane@ on same server).
Agency: mailboxes per client on reseller accounts; discourage forward-to-Gmail for client-facing support addresses unless clients insist and understand deliverability risk.
WordPress site only: use SMTP plugin to SendGrid/Mailgun or workspace SMTP for form mail; do not rely on PHP mail() from the web server IP.
When forwarders break expectations
- Recipient marks forwarded newsletter as spam and hurts your domain reputation
- Large attachments bounce at the forward step
- DMARC fails on forwarded messages (recipient sees "via yourhost.com")
- Employee leaves; forward still points to their personal Gmail
Audit forwarders yearly. Remove stale routes.
When to upgrade off forwarders
If you send invoices, contracts, or PHI-adjacent mail as @yourdomain, use a real mailbox or workspace with SPF/DKIM configured. If multiple people need the same address, use a shared mailbox or help desk tool, not six forwarders to six phones.
When to separate email from web hosting covers splitting website and mail for cleaner architecture.
Bottom line
Use forwarders for simple aliases into an inbox you already manage. Use mailboxes (or Google/Microsoft) when the address is a business identity you send from, archive, and defend in a deliverability audit. Mixing them without a plan is how info@ ends up in a personal spam folder.
Setting up cPanel mail on Canadian hosting? Talk with Swift Host or see email hosting for mailboxes, forwarders, and migration help.
