Email Forwarding and Aliases: Getting More from Your Inbox

You Can Have Multiple Addresses Without Multiple Inboxes

Here's something that surprises a lot of business owners: you can have dozens of email addresses that all deliver to the same inbox. You don't need a separate account — with a separate login, separate password, and separate inbox to check — for every address.

Email forwarding, aliases, and distribution groups let you present different email addresses to the world while keeping your actual inbox manageable. It's one of the most practical email features that most people never learn about.

What Is an Email Alias?

An email alias is an alternative address that delivers mail to an existing mailbox. No separate account, no separate login — messages sent to the alias land in your regular inbox.

For example, you might have a primary address of [email protected], but you also create aliases like:

All three deliver to Sarah's inbox. When she replies, she can choose which address appears in the "From" field, so the customer sees a reply from sales@ rather than from Sarah's personal address.

Why this matters:

Professional appearance — customers email [email protected] instead of a personal name
Role-based addresses — if someone new takes over sales, you redirect the alias instead of creating a whole new account
Privacy — you can give out different aliases for different purposes and know where incoming mail came from

What Is Email Forwarding?

Email forwarding sends a copy of incoming mail from one address to another. It's similar to an alias, but with a key difference: forwarding typically works between different email services or accounts.

Common uses:

Old email to new email — You moved from [email protected] to [email protected] but don't want to miss messages sent to the old address
Domain email to personal account — You want [email protected] to forward to your existing Gmail account so you don't have to check two inboxes
Multiple team members — Forwarding [email protected] to three different employees so they all see incoming requests

The catch with forwarding: When you reply to a forwarded message, the reply comes from whatever account you're using — not the original forwarded address. This can confuse customers if they emailed [email protected] but the reply comes from [email protected]. Aliases handle this more cleanly.

What Is a Catch-All Address?

A catch-all is an email setting that captures any message sent to your domain, regardless of whether that specific address exists.

If your domain is yourbusiness.com and someone emails [email protected] — even [email protected] — the message gets delivered to your catch-all inbox.

Why businesses use catch-all:

Catching typos — If a customer misspells [email protected] as [email protected], you still get the email
Tracking sources — You can give unique email addresses to different contexts. Use [email protected] on your website and [email protected] on your business cards. When emails arrive, you know where people found you.
No missed messages — Even if someone guesses an address that doesn't exist, you still see the email

The downside: Catch-all addresses also catch spam. Spammers often blast emails to random addresses at known domains, and a catch-all collects all of it. You'll want solid spam filtering if you enable this feature.

What Are Distribution Groups?

A distribution group (sometimes called a mailing list or group alias) is an email address that delivers to multiple people simultaneously.

For example, [email protected] might deliver to all five of your employees. [email protected] might deliver to you and your business partner.

This is different from forwarding because:

It's managed centrally — add or remove members without changing the address
Everyone gets the message at the same time
It's designed for groups, not just one-to-one redirection

Practical examples:

[email protected] — Reaches everyone (good for company announcements)
[email protected] — Reaches your support team
[email protected] — Reaches anyone who handles finances

Setting These Up

The exact steps depend on your email provider, but here's the general idea:

Google Workspace (Gmail for Business)

Aliases: Added in the Admin Console under user settings
Groups: Created through Google Groups — acts as both a distribution list and a collaborative inbox
Forwarding: Set up in individual Gmail settings or via routing rules in Admin Console

Microsoft 365 (Outlook)

Aliases: Added in the Microsoft 365 Admin Center under the user's account
Distribution groups: Created in the Exchange Admin Center
Shared mailboxes: A step up from aliases — a full mailbox that multiple people can access without needing a separate license

Cloudflare Email Routing

Perfect for forwarding domain email to existing accounts
Set up forwarding rules and catch-all addresses in the Cloudflare dashboard
Free with any domain on Cloudflare — no need for a separate email hosting plan if you already have a personal Gmail or Outlook account

Tips for Keeping It Organized

Document your aliases and forwarding rules. It's easy to set them up and forget how the mail flows. Keep a list of what goes where.
Use consistent naming. Stick with a pattern: info@, support@, billing@, sales@. Don't create random aliases you won't remember later.
Review periodically. When employees leave or roles change, update your forwarding rules. Mail going to someone who left six months ago is mail that's not getting answered.

The Bottom Line

You don't need a separate mailbox for every email address your business uses. Aliases give you professional, role-based addresses. Forwarding connects old and new accounts. Catch-all makes sure nothing slips through the cracks. Distribution groups get messages to the right team. Used together, they make your business email look polished while keeping your actual inbox manageable.

Want help setting up email aliases and forwarding for your domain? Get in touch — we'll make sure your mail goes exactly where it should.

Email Routing Under the Hood: MX Records, Headers, and Shared Mailboxes

Let's dig into how email forwarding and aliases actually work at a technical level, and explore some more advanced options.

How Email Routing Actually Works

When someone sends an email to [email protected], here's what happens:

The sender's email server looks up the MX (Mail Exchange) records for yourbusiness.com in DNS
The MX records point to your email provider's servers (Google, Microsoft, Cloudflare, etc.)
Your provider's server receives the message and checks its routing rules
Based on those rules, it delivers the message to the appropriate mailbox, forwards it, or expands it to a group

Aliases are handled at step 4 — the server knows that info@ is an alias for sarah@ and drops the message into Sarah's mailbox. The message's headers still show it was addressed to info@, which is how Sarah knows which alias was used.

Forwarding is also handled at step 4, but instead of local delivery, the server creates a new outbound message to the forwarding destination. This is where things can get complicated (more on that below).

The Forwarding Problem: SPF and DKIM Breakage

Email forwarding sounds straightforward, but it has a technical wrinkle that can cause deliverability problems.

When [email protected] forwards to [email protected], the forwarding server sends a message to Gmail that:

Claims to be from the original sender (let's say [email protected])
But is actually coming from your email server

Gmail checks the SPF record for theircompany.com and sees that your server isn't authorized to send mail for that domain. This can cause the forwarded message to land in spam or get rejected entirely.

SRS (Sender Rewriting Scheme) is one solution — it rewrites the envelope sender address during forwarding so SPF checks pass. Most major email providers handle this automatically, but it's worth knowing about if you're seeing forwarded messages disappear.

DKIM is more resilient to forwarding because it signs the message content rather than relying on the sending server's IP address. As long as the forwarding server doesn't modify the message body, the DKIM signature remains valid.

Shared Mailboxes vs. Aliases vs. Groups

Three features that sound similar but serve different purposes:

Aliases — Multiple addresses, one mailbox, one person. Sarah reads everything. Good for: one person wearing multiple hats.

Distribution groups — One address, multiple mailboxes, everyone gets a copy. Good for: broadcasting information to a team.

Shared mailboxes — One address, one shared mailbox, multiple people have access. Good for: collaborative inbox management where the team works through incoming messages together.

The key difference with shared mailboxes is that replies come from the shared address (not individual addresses), and team members can see what others have already replied to. This prevents the awkward situation where three people all reply to the same customer email.

In Microsoft 365, shared mailboxes are free — they don't require a separate license. In Google Workspace, you can achieve similar functionality with Collaborative Inbox in Google Groups.

Plus Addressing: Free Aliases You Already Have

Most email providers support plus addressing — you can add +anything before the @ symbol and the email still arrives. For example:

All three deliver to [email protected]. The +tag is preserved, so you can create filters that sort incoming mail based on the tag.

This is useful for:

Tracking who shares your email — Sign up for a service as [email protected]. If you start getting spam to that specific address, you know who sold your data.
Automatic sorting — Create inbox rules that filter based on the +tag
Testing — Sign up for your own service multiple times with different plus addresses

Caveat: Some (poorly designed) websites reject email addresses with + in them, claiming it's not a valid character. It is valid per RFC 5321, but not everyone follows the rules.

Subaddressing and Custom Rules

Beyond basic forwarding, most business email providers let you create sophisticated routing rules:

Conditional forwarding — Forward to different people based on subject line keywords, sender domain, or time of day
Splitting — One incoming address delivers to a mailbox AND forwards a copy elsewhere
Moderated delivery — Messages to a group address are held for approval before being distributed (useful for all-staff@ groups to prevent reply-all storms)
Auto-reply and routing — Incoming messages to support@ trigger an auto-acknowledgment while also routing to the support team

Cloudflare Email Routing: The Free Power Tool

If your domain is on Cloudflare, Email Routing gives you many of these features for free:

Create unlimited forwarding addresses for your domain
Set up catch-all routing
Define custom rules with specific actions per address
No separate email hosting needed — forward everything to your existing Gmail, Outlook, or any other email account

This is an excellent option for small businesses that want professional @yourbusiness.com addresses without paying for full email hosting. The limitation: you can't send from these addresses through Cloudflare Email Routing (it's receive/forward only). For sending, you'd configure your Gmail or Outlook to "Send As" your business address.

Email Retention and Compliance

If your business is in a regulated industry (healthcare, finance, legal), you may have email retention requirements. Key considerations:

Forwarding doesn't always preserve originals — If you forward and delete, you might violate retention requirements
Aliases into one mailbox — If that mailbox gets deleted, all aliased mail history goes with it
Journal rules — Microsoft 365 and Google Workspace offer journaling that captures a copy of every message for compliance, regardless of forwarding or aliases

Understanding these distinctions matters when setting up your email architecture.

Need help designing an email routing setup for your business? Reach out to us — we'll make sure every message gets to the right place.

Last reviewed for accuracy: February 2026

Rate this article