cPanel offers several ways to route email beyond the simple “one mailbox per address” pattern. Forwarders, catch-alls, filters, and autoresponders each solve a specific problem. Knowing when to use which keeps your mail organized without creating dozens of mailboxes you’ll never check.
Forwarders — when one mailbox handles many addresses
A forwarder redirects mail from one address to another without creating a mailbox. Mail arrives at billing@yourdomain.com, server immediately forwards to you@gmail.com. No copy is stored locally.
- cPanel → Email → Forwarders.
- Click Add Forwarder.
- Source: e.g.
billing(gets@yourdomain.comappended). - Destination: full external address.
- Save.
Forwarders are ideal when:
- You want a branded address but already read mail somewhere else.
- You need an address only for receiving (replies go from the personal address).
- Multiple aliases all funnel to the same person.
Caveat: forwarders interact awkwardly with SPF. The forwarded mail still has the original sender’s “From:” header, but it’s being relayed from your server — receivers may reject it as failing SPF. The fix is SRS (Sender Rewriting Scheme), which cPanel supports automatically on most plans. If forwarded mail is being rejected, contact support to verify SRS is active.
Catch-all addresses
A catch-all forwards every message to ANY address @yourdomain.com (including misspellings, made-up names, mistakes) to a single mailbox.
- cPanel → Email → Default Address.
- Select your domain.
- Change from “Discard” to Forward to Email Address.
- Enter your destination mailbox.
- Save.
Use a catch-all when:
- You’re a solo operator and want to never lose mail to a typo.
- You’re a small business with frequently-changing address conventions.
- Your domain has low public visibility (less spam exposure).
Don’t use a catch-all when:
- Your domain is widely published. Spammers do “dictionary attacks” — sending mail to
a@,b@,contact@,info@etc. on any domain they find. Catch-all means you receive all of it. - You have multiple staff with shared addresses — catch-all routes everything to one inbox.
If spam volume becomes a problem, disable the catch-all and rely on specific addresses + forwarders.
Email filters — server-side rules
Filters run at the server before mail reaches a mailbox. They can route, delete, auto-reply, or forward based on conditions. Two scopes:
- Global Email Filters (Email → Global Email Filters) — applies to all mailboxes on the account.
- Email Filters (Email → Email Filters) — applies to one specific mailbox.
Creating a filter
- Click Create a New Filter.
- Give it a name.
- Set conditions: e.g. “Subject contains ‘invoice'”, or “From contains ‘newsletter@'”.
- Set action: Deliver to folder, Discard, Forward, Pipe to a Program, Stop Processing Rules.
- Save.
Useful filter examples
- Filter X-Spam-Flag YES → Trash. SpamAssassin marks suspected spam with a header; this rule moves all flagged mail straight to trash. Be cautious — review your spam folder regularly first to make sure SpamAssassin isn’t catching legitimate mail.
- From contains “noreply@” → folder “Notifications”. Automated mail (GitHub, AWS, monitoring) all in one place.
- Subject contains “[INVOICE]” → forward to
accounting@. Route specific business mail. - Body matches “unsubscribe” → folder “Newsletters”. Less reliable but useful as a catch.
Autoresponders
An autoresponder is an automatic reply to incoming mail. The most common use: out-of-office during vacations.
- cPanel → Email → Autoresponders.
- Click Add Autoresponder.
- Select interval (how often to reply to the same sender — usually 24 hours so you don’t spam them).
- Email: your address.
- From / Subject / Body — what the reply says.
- Start time / Stop time — when the autoresponder is active.
- Save.
Set a stop time. Forgetting to disable an autoresponder when you’re back from vacation leaves it running indefinitely — embarrassing for business communication.
Routing strategy — the practical pattern
For most small businesses and solo operators, a sensible setup:
- One real mailbox:
you@yourdomain.com— where everything actually lives. - Forwarders for common addresses:
info@,support@,billing@,hello@,contact@→ all forwarded toyou@. - Catch-all if you can tolerate the spam: → you@. Or set to Discard if not.
- Filters in your mail client (Gmail, Outlook, Apple Mail) rather than server-side: easier to manage, easier to undo.
This gives you the appearance of multiple addresses (good for branding) with the operational simplicity of one mailbox. When you actually grow into needing multiple mailboxes (multiple staff, distinct workflows), convert forwarders to real mailboxes as needed.
Common questions
“Forwarded email going to spam at Gmail.” SPF alignment problem. Either configure SRS (contact support) or migrate to a real mailbox + IMAP fetch in Gmail.
“Catch-all stops working after creating a regular mailbox.” Correct behavior — specific addresses are matched before catch-all. info@ mailbox now receives mail to info@; everything else still hits catch-all.
“Filter set up but mail still arrives normally.” Filter order matters — Global filters run before mailbox filters. If a global “Stop Processing Rules” matches first, your mailbox filter never runs. Check the order on both pages.
“Autoresponder sending replies to my own auto-replies (loop).” Standard mail servers detect this and stop. If you’re seeing it, check that the autoresponder’s interval is set higher than 0 minutes — interval 0 will reply infinitely.
“Want to forward all mail from a specific sender to someone else.” Use a filter, not a forwarder. Filter: “From contains specific@sender.com” → action “Forward to” → done.
What’s next
- Email authentication for forwarded mail: SPF/DKIM/DMARC guide.
- Diagnosing forwarding failures: Mail logs and bounces.
- Per-mailbox setup: Setting up email accounts.
Mail routing is the kind of feature you set up once and forget about. Get the pattern right early — one real mailbox, forwarders for the visible addresses, filters in the mail client — and your mail infrastructure stays manageable as your domain grows.
Was this helpful?
Thanks for your feedback!