How to Set Up a Catch-All Email Address in Google Workspace
The short answer
Google Workspace has no native catch-all toggle. The workaround is a Default Routing rule in the Admin Console under Gmail Routing, set to deliver unrecognized-recipient mail to a target mailbox. You can set it up in about five minutes, but catch-alls reliably attract spam — targeted aliases handle most real use cases better.
Google Workspace has no native catch-all. Use a Default Routing rule in Admin Console to deliver unmatched mail to one mailbox — with a strong spam warning.
On this page
How to set up a catch-all email address in Google Workspace is a common admin question with a slightly unexpected answer: you cannot do it with a native setting. There is no single catch-all toggle in the Admin Console the way cPanel or Plesk provide one. What Google Workspace does have is a Default Routing rule — a configuration in the Gmail routing section that delivers messages addressed to unrecognized recipients to a mailbox you specify.
The practical outcome is the same as a native catch-all: mail that would otherwise bounce with a 550 user-unknown error lands somewhere you control. Setup takes a super admin roughly five minutes. Whether you should turn it on is a harder question, because any domain that accepts all incoming addresses also accepts every spam campaign aimed at guessing addresses at that domain.
The short answer#
In the Admin Console, navigate to Apps > Google Workspace > Gmail > Routing. Find the Default Routing section, click Configure, and set the rule to deliver mail to a target mailbox when the envelope recipient does not match any user, group or alias in your organization. That routing rule is Google Workspace's catch-all equivalent.
It is a routing workaround, not a built-in feature. Google Workspace has no wildcard addressing, no pattern-matched address range, and nothing labeled catch-all anywhere in the console. If you are handing these steps to another admin, tell them to look in Gmail routing — not in user settings or domain aliases — or they will not find it.
Before you start#
You need a super admin account. The Gmail Routing section is not available to delegated admins regardless of what other permissions they hold. If you are logged in as a delegated admin and cannot find the Routing option in Gmail settings, that is the reason.
You also need to decide on a target mailbox before you configure the rule. A Google Group is usually better than a single user account for catch-all traffic: multiple members can monitor it, messages can be archived before they reach anyone's inbox, and you can add moderation if spam volume becomes unmanageable. A user mailbox works, but one person will own everything that arrives — including every piece of directory-harvest spam the domain attracts.
If your Workspace account manages more than one domain — a primary domain and a legacy domain after a rebrand, for example — routing rules apply per domain. You configure a separate Default Routing rule for each domain where you want the catch-all behavior.
A catch-all is easier to enable than to cleanly disable
Steps: set up the Default Routing rule#
Have your target mailbox address ready to paste before you start. The rule takes effect within a few minutes of saving. Work through the steps in order.
- 1
Sign in to the Admin Console
Go to admin.google.com and sign in with a super admin account. From the home dashboard, click Apps, then Google Workspace, then Gmail.
- 2
Open the Routing section
On the Gmail settings page, look at the section list on the left. Scroll down to Routing and click it. This opens the Gmail Routing page, which is where all custom routing and Default Routing rules live.
- 3
Locate Default Routing
On the Routing page, find the Default routing row. If no rule exists yet, click Configure. If a rule already appears in the list, read it carefully before editing — it may exist for a different purpose, and overwriting it without understanding it can redirect mail you did not intend to move.
- 4
Set the recipient condition
In the rule configuration panel, set the message direction to inbound. Find the envelope recipient condition — it may be labeled 'Recipient address' or 'Envelope recipient' depending on the current Admin Console interface. Set it to match when the recipient does not correspond to any user, group, alias or distribution list in the domain. This is the condition that makes the rule behave like a catch-all rather than a forwarder for all mail.
- 5
Configure delivery to the target mailbox
Under the action section, choose to deliver or route the message to a specified address. Type or paste the email address of the target user account or Google Group. If you are routing to a Google Group, confirm the Group accepts mail from external senders — messages originating outside your domain will bounce at the Group otherwise, silently discarding them before any member sees them.
- 6
Test, save, and set a review reminder
Before saving, send a test message from an external account — a personal Gmail works — addressed to something that clearly does not exist at your domain, such as [email protected]. Wait two to three minutes, then check the target mailbox. If the message arrives, the rule is functioning. Save the rule and set a reminder to review the catch-all mailbox in two weeks: spam volume typically surges faster than most admins expect once the domain begins accepting all addresses.
Catch-all vs alias vs group in Google Workspace#
Google Workspace supports several ways to receive mail at addresses other than a primary account. Which one fits depends on whether the address is known and specific, or a safety net for anything unrecognized.
| Method | What it does | Requires explicit setup per address? | Best for |
|---|---|---|---|
| Default Routing rule (catch-all workaround) | Delivers mail to any unrecognized recipient to a single target mailbox | No — catches everything not matched by an account, group or alias | Capturing unknown-recipient mail domain-wide; keeping legacy addresses live after a migration |
| User alias | Adds an extra address to one user account; only that user receives it | Yes — each alias set up individually in Admin Console > Users | Known alternate names or address formats for a specific person |
| Google Group address | A shared address delivered to all Group members | Yes — the Group and its members must be created | Team inboxes, role addresses such as support@ or billing@, shared monitoring |
| Domain alias | Accepts mail for an entirely different domain and delivers it as if it were the primary domain | Yes — the alternate domain must be added and verified in Admin Console | Legacy domain names after rebrands or mergers; commonly misspelled domain variants |
| Wildcard or pattern-matched address | Accepts addresses matching a pattern such as noreply-*@yourdomain.com | Not natively available — approximated with a routing rule using a RegEx recipient filter | Narrowing a catch-all to a specific address pattern without accepting all mail |
How other platforms handle catch-all#
Google Workspace sits at the more complex end of the implementation spectrum. Traditional hosting panels treat catch-all as a one-click setting. The comparison below shows where Workspace stands against the platforms admins most often ask about.
| Platform | Native catch-all? | How to configure | Spam risk |
|---|---|---|---|
| Google Workspace | No — routing rule only | Admin Console > Apps > Google Workspace > Gmail > Routing > Default Routing | High — no pre-delivery filtering on unmatched traffic by default |
| Microsoft 365 | No — mail flow rule required | Exchange Admin Center > Mail flow > Rules, condition: recipient is not in the organization | High — same directory-harvest exposure as Google Workspace |
| cPanel | Yes | Email > Default Address setting, configured per domain | High — accepts all addresses with no filtering gate before delivery |
| Zoho Mail | Yes | Admin Console > Email Settings > Default Email Address toggle | Moderate — Zoho's spam filter runs before catch-all delivery |
| Fastmail | Yes | Settings > Addresses > enable catch-all per domain | Moderate — configurable spam scoring threshold before catch-all activates |
| Self-hosted (Postfix) | Yes | Virtual alias map or luser_relay directive in main.cf | Variable — depends entirely on the filtering stack configured upstream |
What to do when it doesn't work#
Most Default Routing problems in Google Workspace come from a short list of causes. If unrecognized mail is still bouncing after you save the rule, or the wrong mail is being caught, work through this table from the symptom you see.
| Symptom | Likely cause | Fix |
|---|---|---|
| Unrecognized addresses still return a 550 bounce | Rule saved to the wrong domain, or the recipient condition is not set to unrecognized recipients only | Open Admin Console > Gmail > Routing, confirm the rule is listed for the correct domain, and verify the condition fires only on addresses with no matching account, group or alias. |
| All mail — including mail to real users — arrives in the catch-all mailbox | Routing rule condition set to all recipients rather than unrecognized recipients only | Edit the rule so the condition applies only when the recipient has no matching account, group or alias. Delivering to all recipients duplicates every message. |
| Cannot find the Routing section in the Admin Console | Logged in as a delegated admin without super admin rights | Log in with a full super admin account. Gmail Routing is not available to delegated admins regardless of other permissions. |
| Target mailbox receives the test message but no real unmatched mail arrives | A more specific routing rule higher in the evaluation order is processing those messages first | Review all rules in Admin Console > Gmail > Routing. Rules are evaluated in order; a rule above Default Routing may be matching the same messages before the catch-all condition fires. |
| Target is a Google Group and messages never arrive | The Group does not accept mail from external senders | Open the Group settings, find 'Who can post,' and allow external or all senders. Messages from outside your domain are dropped by the Group's access controls before reaching any member. |
| The catch-all mailbox fills immediately with spam | The catch-all is functioning — the spam volume is expected behavior, not a malfunction | This is the standard outcome on any domain that begins accepting all addresses. Consider switching the target to a Google Group with moderation, or disabling the rule and using targeted aliases for the specific addresses you actually need. |
Does a catch-all increase spam?
A faster way to manage what lands in a shared mailbox#
The routing rule gets mail into a mailbox. What you do with it once it arrives is a separate problem. A catch-all target that receives hundreds of unidentified messages a week — a mix of genuinely misdirected mail and directory-harvest noise — needs its own triage layer on top of the routing rule.
We build AI Emaily, an AI-native email client that connects to Gmail, Outlook and IMAP accounts, including the kind of shared mailbox a catch-all typically routes to. Its Rules Brain lets you define routing logic that runs on arrival: file by sender domain, archive low-priority patterns automatically, or surface specific message types for review, without writing a new routing rule in the Admin Console every time the pattern changes. The spam protection layer evaluates inbound mail against sender behavior rather than address alone, so rotating-address campaigns from the same domain do not reset the filter with each new sending address.
That does not replace the routing rule — you still need the Workspace configuration above. What it changes is what happens to the mail after it lands. AI Emaily comes with a 7-day free trial on the Pro and Autopilot plans. See what it does at aiemaily.com or review plans at aiemaily.com/pricing.
Frequently asked
See it in AI Emaily
Keep reading
Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.