Blog

What is a catch-all address

A catch-all address collects every message sent to your domain that matches no real mailbox. Where that helps, what it quietly swallows, and who should read it.

Point a catch-all at your domain and mail addressed to a name that does not exist there stops bouncing and lands in one mailbox instead. Someone who guesses [email protected] when you created help@ still reaches a person. So does every bulk sender working through a list of common names.

That is the whole trade. A catch-all swaps a bounce you would have seen for a message you now have to sort.

What a catch-all address does

A catch-all is a routing rule rather than a mailbox of its own. It rewrites the recipient of incoming mail that matched nothing, and the account you point it at does the storing.

Google Workspace implements it that way: catch-all routing sends messages addressed to non-existent or incorrect addresses at your domain to a single account, which can be an existing user, a new user, or a Google Group, according to Google’s admin documentation for catch-all mailboxes. The rule applies to unrecognized and inactive accounts, so mail to a working mailbox or a group still goes where it was addressed. Google notes that the change can take up to 24 hours to apply and needs the Gmail Settings admin privilege.

What the catch-all sees therefore depends on everything else in the domain already existing.

What the sender typed Where it lands
An address that matches a live mailbox That mailbox, and the catch-all is not involved
A group address The group, because the setting excludes active groups
A name nobody created yet, or a suspended user The catch-all account

How a catch-all differs from an alias and a distribution list

An alias is a second address on a mailbox that already exists, so mail to the alias is delivered to that mailbox’s primary address, as Microsoft’s documentation for mailbox addresses describes. It names a real mailbox and delivers there.

A distribution list is an address with members and no mailbox behind it. Every member gets a copy, the address keeps nothing of its own, and what a distribution list is covers that shape in full.

A catch-all names nothing. It is the address of last resort, the row at the bottom of the routing table that takes whatever the specific rules did not.

When a catch-all saves you

Three cases earn their keep.

A customer guessed the address. Your site says [email protected] and they wrote to [email protected], or info@, or hi@. Small teams change their support address and miss a page that still shows the old one. A catch-all means the guess arrives instead of disappearing at the other end with no reply.

An address you have not created yet. Someone writes to [email protected] to report a vulnerability before the mailbox exists, or to billing@ before billing has an owner. On a domain without a catch-all, that message bounces and the sender usually does not try again.

A founder’s name at the domain. Investors, candidates and former colleagues write to [email protected] because they know a first name rather than the team address. A catch-all collects the mail the website never advertised.

In all three cases the catch-all is a net under a domain that is still growing, and what it prevents is silence.

When a catch-all hurts

The messages in that net are not a tidy list of near-misses from confused customers. They are everything addressed to your domain that matched no mailbox.

Spam arrives with them. A catch-all accepts mail that would otherwise have been refused, so a sender working through common names at your domain has nowhere to bounce. The rule cannot separate the customer who mistyped from the sender who guessed on purpose, because both wrote to an address you never created.

Some of it was never yours to read. Senders drop a letter from a customer’s address, or reply to a name that belongs to a company with a similar domain, and the result lands in your account. That mail was meant for somebody else, and holding it is a liability rather than a service.

Some of it is mail for people who left. If a departed teammate’s account is suspended and their name is still on a contract or a support page, the catch-all absorbs their mail and the person who should have inherited it never sees it.

And some of it is the mail that should have told you something was missing.

The mailbox you never created

A bounce is feedback. When a domain is authoritative for its mail, the mail service is responsible for generating a non-delivery report for recipients that do not exist, as Microsoft’s accepted domains documentation puts it. The sender gets an error, and you get the signal that somebody wanted an address you have not built.

A catch-all removes that signal. The message that should have produced a bounce becomes one more row in a folder, and nobody learns that [email protected] was expected to exist. Teams that run a catch-all for a year usually find that gap by accident, when a customer mentions a reply that never came.

So the honest question is who reads what the net catches.

What to do with the mail a catch-all collects

There are two defensible answers, and both beat a catch-all pointed at one person’s mailbox.

Leave it off, and let the bounce do its job. If nobody is going to read the caught mail, a catch-all turns a clear error into a silent loss. The sender learns nothing, you learn nothing, and the message sits unread.

Keep it on, and point it at a shared inbox with rules. A catch-all aimed at one person becomes a folder that person stops opening by the second week. Google’s own guidance suggests a group as the catch-all account so more than one person can check the mail, and a shared inbox does the same job with a queue attached: who owns this, what state it is in, and what is left to answer.

Route by the address that was typed, so mail for a departed colleague goes to whoever took over their work, tag the obvious bulk mail, and leave the rest for a rota. Then check the rota actually holds, because a rule that files caught mail is only as good as the person who opens the folder. The boundary between that queue and a ticket system is shared inbox vs help desk, and caught mail sits on the queue side of that line.

The test is the same either way. If you cannot name who reads the catch-all, you should not run one.

Chirp and the catch-all inbox

Chirp is a shared inbox for small software teams that track their work in Linear. If you keep a catch-all, connect the mailbox that receives it to Chirp, and the caught mail becomes a queue instead of a folder.

A rule can tag, assign, snooze or archive a thread, and it can write a draft. No rule sends email, so a caught message reaches a sender only when a teammate answers it. Press i in a thread to link it to a Linear issue, and when every linked issue is Done or Canceled the thread comes back with a reply drafted for you that names the issue.

Each inbox carries its own access list, and the roles are Admin, Agent and Viewer. Chirp costs $9 per user per month.

Next step

If the catch-all is the net under your domain, the address most of that mail was trying to reach is the thing to get right. What a shared inbox is covers the address several people answer from, and what has to sit in front of the mailbox before they can.

FAQ

Is a catch-all address the same as an alias?

No. An alias is a second address on a mailbox that already exists, and mail to it goes to that mailbox. A catch-all catches mail addressed to names that match no mailbox at all.

Does a catch-all address stop spam?

It does the opposite. It accepts mail that would otherwise have been rejected, so a sender working through common names at your domain reaches the catch-all rather than a bounce.

What happens to mail for a suspended user?

A suspended account is one the routing rule covers, so a departed teammate’s mail can fall to the catch-all rather than to the colleague who inherited the work.

Should a small team use a catch-all address?

Only with a named reader. If someone checks it, route it to a shared inbox with rules and treat it as a queue. If nobody will, leave it off and let the bounce tell the sender the truth.

Can a catch-all receive mail for an address that does not exist at your domain?

That is what it is for. The setting accepts mail for addresses you never created, which makes it useful during a change of support address and noisy afterwards.