Blog

Email aliases, catch-all and forwarding

An alias, a catch-all and a forward are three shapes for one support address. What each does when a message arrives, and which to pick at 20 a week and at 200.

You have a support address and one decision left: what sits behind it. [email protected] can be a second name on one person’s mailbox, a net that catches everything, or a pipe that moves mail somewhere else. Each choice decides who sees a customer’s message and what the team keeps afterwards.

Only one of the three is a queue. An alias, a catch-all and a forward all move a message to a destination, and none of them shows who picked it up, so the answer depends on how many people have to see what arrives.

Three shapes, one address

The three words describe how a message travels, not three products you buy.

An alias is a second name on a mailbox that already exists. Mail to the alias goes to that mailbox’s primary address, as Microsoft’s mailbox address documentation describes.

A catch-all is a rule for everything addressed to your domain that matches no mailbox at all. What a catch-all address is covers that shape in full. It never bounces, which is both the point and the problem.

A distribution list is an address with members and no mailbox behind it. What a distribution list is has the detail.

Forwarding moves a message from one address to another, inside your company or outside it. The address being forwarded keeps no inbox.

An alias points at a mailbox. A forward points at another address. A catch-all points at everything.

What an alias does at a support address

An alias costs nothing and takes a minute. It is also the shape that bends first.

Google’s admin documentation is explicit. Only one user can use a Workspace alias, multiple users cannot share one, and an address several people need to answer should use delegation instead, per Add or delete an alternate email address (email alias). The same article notes that up to 30 aliases can hang off one user at no extra cost, and that aliases are not private, so a colleague searching Gmail can surface mail sent to one.

An alias is cheap, instant and correct while one person answers everything. It becomes the wrong shape the moment a second person needs to see the mail, because the second person has no mailbox to open.

Why a catch-all is not a support address

A catch-all never bounces, which is what you want from a net under a domain and not what you want from the address you publish. It accepts what it catches and tells the sender nothing.

Keep the net on for the guesses and give the published address a mailbox. The detail lives in what a catch-all address is.

What forwarding does at a support address

Forwarding is what a team reaches for when someone leaves support, or when a founder wants a copy of everything. It is a routing rule rather than a mailbox, at either the account or the domain level.

Google Workspace admin routing offers two versions of the same map. A redirect excludes the original recipient, so the message is not delivered there. A forward includes them, so both destinations receive it. The settings page, Redirect or forward Gmail messages to another user, puts “also route to the original destination” in front of the admin as a separate choice.

Microsoft draws the line at the mailbox: forwarding is off by default, and “Deliver message to both forwarding address and mailbox” is a box the admin has to tick, per Configure email forwarding for a mailbox in Exchange Online.

Neither vendor treats a copy at the source as automatic. Someone chose, at the address, whether the mail survives there.

Two smaller facts matter too. Gmail sends a verification link to the destination before automatic forwarding starts, per Automatically forward Gmail messages to another account. The same page asks what happens to the copy in the source mailbox: keep it, archive it, or delete it.

The forwarding loop, and what it costs

Two addresses that forward to each other do not exchange one message. They exchange one message repeatedly.

Each delivery is new incoming mail at the other end, so the same message is forwarded again and the servers involved add a hop every time. Google documents forwarding limits per organization, counted over a 24-hour period and including redirects. Microsoft documents how many times a message can be redirected, forwarded or replied to automatically by Inbox rules, and states what happens at the limit: a message that satisfies both rules is sent to the first destination only.

Neither outcome is tidy. Google warns that users might get an error when a forwarding limit is exceeded, and Microsoft’s dropped recipients never hear about the message at all. The customer is no closer to an answer either way.

What a forward loses that a support address needs

A forwarded message arrives with no state attached. Nobody can see that it was opened, answered, or claimed by anyone.

It lands in a personal inbox, where that person’s filters, folders and archive rules apply to it. Whether it is read today or in a month depends on one person’s settings, and the address it was sent to keeps no record of it.

Reply to a forwarded message and the reply goes back to the customer from the individual’s address, so a conversation that started at [email protected] ends somewhere the team cannot search.

The route belongs to the person the mail was forwarded to as well. When they change role or leave, nobody remembers to move it, and it keeps running or it stops.

Support email is a queue. It needs an owner per message, a visible state, and a reply that goes out from the address the customer wrote to. Forwarding provides none of the three, and no setting makes it provide them.

Which shape to use at 20 emails a week, and which at 200

Shape Who receives it Keeps a record Someone can claim it Fits a support address
Alias One person’s mailbox Yes, in that mailbox No At low volume, with one person answering
Forward The destination address No, unless the source also keeps a copy No For a handover, not as the permanent route
Catch-all The account you point it at Yes, if the account stores mail No As a net for guesses, never as the published address
Shared mailbox Everyone with access Yes, one Inbox and one Sent Permission only, no status Yes
Shared inbox Everyone with access, in a queue Yes, and per inbox Yes, assignment and status Yes

The test is whether one person needs to see what arrives or two.

At around 20 emails a week, an alias or a forward to the one person who answers is enough. The volume is small, the person is known, and a queue would be ceremony. Decide the shape on the week someone takes leave, because that is when the single point of failure shows itself.

At around 200 emails a week, neither survives. Two people answer, both need to see the same thread, and the question that starts every collision is whether a customer already got a reply. That needs a mailbox several people open, and then a queue on top of it. How to set up a shared inbox in Gmail has the steps rather than a repeat of them, and shared mailbox vs distribution list settles which shape holds the record.

Chirp and the support address

Chirp is a shared inbox for small software teams that track their work in Linear. It connects to your mailbox, which stays the record, and puts the queue in front of the team.

Press i in a thread to link it to a Linear issue, create one, or find the one that already exists. When every linked issue is Done or Canceled, the thread comes back with a reply drafted for you that names the issue.

A rule can tag, assign, snooze or archive a thread and write a draft, and no rule sends email. Inboxes carry their own access lists, with the roles Admin, Agent and Viewer, and Chirp costs $9 per user per month.

An alias or a forward decides where a message lands. Chirp is the part that decides what happens next, and shared inbox vs help desk covers where that queue should stop.

Next step

If the support address has outgrown one pair of eyes, the next question is which shape holds the record: shared mailbox vs distribution list works through it, and what a shared inbox is covers what has to sit in front of the mailbox before several people can answer one address without colliding.

FAQ

What is the difference between an email alias and a separate mailbox?

An alias has no mailbox of its own. It is a second address on a mailbox that already exists, so mail to it lands in that mailbox. A separate mailbox has its own Inbox and its own address.

Can two people share one email alias?

Not on Google Workspace. The admin documentation states that only one user can use an alias, that multiple users cannot share one, and that an address several people answer should use delegation. A Microsoft 365 shared mailbox is the other route to the same result.

Is a catch-all the same as an alias?

No. An alias has one mailbox behind it and delivers there. A catch-all has no specific address of its own and takes whatever matched nothing else at the domain.

What happens to email forwarding if the person leaves?

The forward keeps running to an address nobody is watching, or it stops when their account is closed.

Should the support address be a forward or a mailbox?

A mailbox, once more than one person answers. A forward moves a message to a person and keeps no state, so two people cannot see who replied.

What is the difference between an email alias and email forwarding?

An alias delivers to a mailbox that already exists and is part of that mailbox. Forwarding sends the message on to another address, and whether the original address also keeps a copy is a separate setting.