How to Set Up a Catch-All Email Address in Google Workspace
Someone types sale@yourcompany.com instead of sales@, and their message bounces with “the email account that you tried to reach does not exist”. A catch-all email address in Google Workspace collects mail sent to any address at your domain that doesn’t belong to a real user. This guide gives you the exact Admin console rule Google documents today, an honest look at when a catch-all is a bad idea, and how to stop it becoming a spam bucket.
What a catch-all email address does, and when it hurts
Normally Gmail refuses mail for an address that doesn’t exist in your Google Workspace account, and the sender gets a bounce along the lines of 550 5.1.1 The email account that you tried to reach does not exist. A catch-all accepts those messages instead and delivers them to one mailbox you choose.
There is no dedicated “catch-all” switch any more. In current Google Workspace, a catch-all is a routing rule that rewrites the envelope recipient of mail addressed to what Google calls inactive and unrecognized accounts. You build it under Apps → Google Workspace → Gmail → Routing (Google’s current instructions) or under Default routing (the method most older guides describe). Step 2 covers both.
The honest pros and cons
Reasons to want one:
- Typos stop costing you customers.
sale@,sales@andsalse@all land where a human will see them. - Old addresses keep working. Mail to a former employee or to the address on an old brochure still arrives (our offboarding guide covers the tidier way to handle leavers).
- Unlimited throwaway addresses. Give
netflix@yourdomain.comto a service without creating an alias. Aliases stop at 30 per user; a catch-all has no limit. - Painless migrations. If your previous email host had a catch-all, nothing changes for your contacts.
Reasons to think twice:
- It is a spam magnet. Spammers guess addresses by the thousand, and a catch-all accepts every guess.
- Senders lose their safety net. A bounce tells someone they mistyped your address. With a catch-all they assume the message arrived, even if nobody reads that mailbox.
- Someone has to own it. An unwatched catch-all is worse than a bounce.
- One destination per rule, unless you write extra rules per domain.
Alternatives to consider first
| Option | Cost | What it catches | Best for |
|---|---|---|---|
| Email alias | Free, up to 30 per user | Exact addresses only, delivered to one user | A few known addresses that one person handles |
| Google Group | Free, unlimited | Exact addresses, delivered to several people, with moderation | Shared role addresses such as info@, support@, billing@ |
| Catch-all rule | Free | Every unrecognised address, typos included | A safety net behind the two options above |
Our advice for most small businesses: create aliases or groups for every address you publish, then add a catch-all pointed at a group as the safety net. If all you want is sales@ delivered to two people, a group alone is cleaner.
Before you start
- Sign in at
admin.google.comas a super admin, or with a role that includes the Gmail Settings admin privilege (see admin roles explained). - Your MX records must already point to Google; a catch-all can only catch mail that Google receives.
- Decide on the destination: an existing user, a new user or a group. A new user is a paid seat (from $8.28 per user per month on Business Starter; see pricing), while a group is free.
- If your account dates from before 2017, open Apps → Google Workspace → Gmail → Routing and look for a legacy Email routing table showing a catch-all address with a Clear link. Google asks you to clear it before creating the new rule (see its catch-all migration note).
- Nothing to buy: Routing and Default routing are included in every Business and Enterprise edition.
14-day free trial · 10% off your first year with our referral link
Step 1: Decide where misaddressed mail should land
Google’s help page says the catch-all can be an existing user, a new user or a Google Group, and recommends a group so that several people can check the messages. We agree: nobody’s personal inbox gets flooded, you can turn on Collaborative Inbox later to assign messages, and group moderation is the closest thing to a free spam quarantine.
If you go with a group, create it first, then open it in Google Groups → Group settings and check two things. Who can post must be Anyone on the web, otherwise the group bounces outside senders and your catch-all silently fails (Google explains the setting in its group posting help). The message moderation options then decide whether mail from non-members is delivered straight away or held for approval.
If you prefer a dedicated user such as catchall@example.com, create it, protect it with 2-Step Verification, and either assign someone to check it or delegate the mailbox.
Heads-up: don’t point the catch-all at your own primary mailbox. Within a week most of your inbox will be guessed-address spam.
Step 2: Add the catch-all routing rule
Google currently documents the catch-all as a rule on the Routing page. These are the exact labels as of October 2026, taken from Google’s catch-all mailbox help page.
Option A: the Routing rule (Google’s current instructions)
- Go to Menu → Apps → Google Workspace → Gmail → Routing.
- Scroll to the Routing section and click Configure (or Add Another Rule if a rule already exists). The Add setting box opens.
- Routing: enter a name such as
Catch-all for example.com. You can’t save without one. - Select when this action is applied: tick Inbound messages only.
- Action: choose Modify message. Tick Change envelope recipient, choose Replace recipient and enter the address from Step 1, for example
catchall@example.com. - Click Show more options.
- Under Select all account types this action applies to, tick All inactive and unrecognized accounts and keep Archive accounts with assigned delegate ticked. Make sure Active user account and Group account are unticked, otherwise you would reroute mail for real users and groups too.
- Leave the Envelope filter boxes clear for now (Step 3 uses them) and click Save.
How to check it worked: the rule appears in the Routing table under the name you gave it. Google says changes can take up to 24 hours but typically happen much faster, so give it a little time before the tests in Step 4.
Option B: the Default routing rule (the method in older guides)
Many tutorials, and Google’s own migration note, build the catch-all under Default routing. It works just as well; the difference is that Default routing rules have a lower priority than every Routing or compliance rule, which is what you want from a safety net. Google’s Default routing help page lists every option.
- Go to Menu → Apps → Google Workspace → Gmail → Default routing and click Configure or Add another rule.
- Under Specify envelope recipients to match, choose All recipients.
- Under If the envelope recipient matches the above, do the following, keep Modify message, tick Change envelope recipient, choose Replace recipient and enter the catch-all address.
- Under Options, select Perform this action only on non-recognized addresses. This one setting turns a “reroute everything” rule into a catch-all; the other choice, Perform this action on non-recognized and recognized addresses, would hijack every message in your domain.
- Click Save and confirm the rule shows up in the Default routing table.
Google defines a non-recognized address as one belonging to a suspended user, a user whose Gmail service is turned off, or an address at one of your verified domains that isn’t associated with any user: exactly the mail that would otherwise bounce. Pick Option A or Option B, not both; two catch-all rules don’t break anything, but they make troubleshooting confusing.
Where did the old “Catch-all address” setting go?
Years ago the Admin console had a dedicated Catch-all address box with Forward the mail to and Discard options. Today that section only exists for the discontinued free Standard Legacy edition. Paid accounts created before Google’s 2017 routing migration may still show a legacy Email routing table on the Routing page; Google’s advice is to clear it and use a routing rule as above. Everyone else simply won’t see it.
Step 3: Limit the catch-all to one domain (optional)
Both rules above apply to every domain and domain alias in your account (see adding multiple domains). If you only want a catch-all on one of them, or a different destination for each, add a pattern:
- Routing rule (Option A): in the Add setting box, scroll to Envelope filter, tick Only affect specific envelope recipients, choose Pattern match and enter a regular expression such as
^.*@example\.com$. - Default routing (Option B): under Specify envelope recipients to match, choose Pattern match instead of All recipients and enter the same expression.
Google’s pattern matching uses RE2 syntax, is case-sensitive by default, and the dot before the domain ending must be escaped with a backslash, as in the example. For a second domain, add a second rule with its own pattern and its own Replace recipient address. Keep expressions short; Google’s regular expression guidelines warn that heavy patterns can slow delivery.
14-day free trial · 10% off your first year with our referral link
Step 4: Test it
- Wait a little. Google says routing changes can take up to 24 hours, though most rules are working within the hour. If you are iterating, Google’s faster rules testing tips suggest applying rules to a small test organizational unit first.
- Send a test from outside. From a personal Gmail or any external account, email an address that definitely doesn’t exist, such as
typo-test-123@example.com. - Check the catch-all mailbox or group. The message should arrive with the original address still in the To line; only the delivery envelope was changed.
- If nothing arrives, open Admin console → Reporting → Email Log Search, search by the test address and date, and open the message. The recipient details list every address the message was actually delivered to. Don’t panic if the top-level status says Dropped: Google notes that status can also appear when a catch-all or routing rule changed the message.
- Send one more test to a real user and confirm it still reaches that person. If it went to the catch-all, you ticked Active user account (Option A) or chose the recognized-addresses option (Option B).
Step 5: Keep the spam under control
Within days you will see what a catch-all really catches: mail to admin@, test@, hr@ and random strings of letters. Here is how to keep it manageable.
- Leave Gmail’s spam filter alone. Google doesn’t even offer the bypass-the-spam-filter option for the inactive and unrecognized account type. Messages that land in the catch-all mailbox still go through Gmail’s normal spam filtering, so obvious junk ends up in that mailbox’s Spam folder rather than its inbox.
- Use group moderation as your quarantine. Google’s admin quarantine (Apps → Google Workspace → Gmail → Manage quarantines, see the email quarantine page) can only be attached to rules for active user accounts, so you can’t quarantine on the catch-all rule itself. A group that holds messages from non-members gives you a review queue for free.
- Auto-label by original address. Because the To header is untouched, Gmail filters in the catch-all mailbox work on it. Go to Settings → See all settings → Filters and Blocked Addresses → Create a new filter, put
sales@example.comin the To field and apply a label or forward it to the right person. For addresses you never published, skip the inbox or delete. - Promote the repeat offenders. If the same misspelling keeps arriving, create an alias for it so it bypasses the catch-all. If a role address you forgot about shows up, make it a group.
- Review monthly, then decide. Many businesses run a catch-all for six months after a migration, convert the addresses that actually get mail into aliases or groups, then disable the rule. Our forwarding and routing guide covers the more targeted rules you can use instead.
Troubleshooting, and how to turn the catch-all off
- Senders still get “The email account that you tried to reach does not exist”. Either the rule hasn’t propagated yet (allow up to 24 hours), the wrong account type is ticked (it must be All inactive and unrecognized accounts in Option A, or only on non-recognized addresses in Option B), or the rule was created with a child organizational unit selected instead of your top-level organization. Google’s bounced email help explains the message itself.
- Real users’ mail is going to the catch-all. You ticked Active user account or Group account in Option A, or chose “non-recognized and recognized addresses” in Option B. Edit the rule.
- The group bounces outside senders. Set Who can post to Anyone on the web, and check the pending moderation queue; held messages don’t appear in members’ inboxes until approved.
- A Reject rule wins. Google always gives Reject actions the highest priority and Default routing the lowest, so a routing or compliance rule that rejects unknown addresses beats the catch-all regardless of order. Check the Reorder numbers on the Default routing page (1 is highest) and your compliance rules.
- Mail to a secondary domain isn’t caught. The pattern in Step 3 doesn’t match (case-sensitive, dot escaped), or your pre-2017 account still has the legacy catch-all username Google’s migration note describes.
- Too much spam. Move the destination to a moderated group, tighten the Gmail filters, or narrow the pattern to one domain. If it still isn’t worth it, turn the rule off.
Turning the catch-all off
Go to Apps → Google Workspace → Gmail → Routing (or Default routing), point at the rule, click Disable to pause it or Delete to remove it, and confirm. Within 24 hours, mail to unknown addresses bounces again with the standard 550 5.1.1 error. Disable is the safer first move, because you keep the configuration in case you want it back.
14-day free trial · 10% off your first year with our referral link
Related setup guides
- All Google Workspace setup guides
- Google Workspace Email Aliases: Full Guide
- Create a Google Group for Business Email
- Google Groups Collaborative Inbox Setup
- Google Workspace Email Forwarding & Routing
- Add Multiple Domains to Google Workspace
- Employee offboarding checklist for Google Workspace admins
- Google Workspace pricing with our 10% discount
Frequently asked questions
Does Google Workspace have a catch-all email address?
Yes, but not as a single switch. In current Google Workspace a catch-all is a routing rule in the Admin console (Apps → Google Workspace → Gmail → Routing, or Default routing) that changes the envelope recipient of mail sent to unrecognized addresses at your domain and delivers it to a user or group you choose. It is included in all Business and Enterprise editions.
Is a catch-all the same as an email alias?
No. An alias is one extra address that delivers to one user, and you can have up to 30 per user. A catch-all accepts mail for every address that does not exist at your domain, typos included, and sends it all to one destination. Aliases are precise and low-spam; a catch-all is broad and attracts spam, so use it as a safety net behind aliases and groups.
Can I use a Google Group as the catch-all address?
Yes, and Google recommends it so that several people can check the messages. Create the group, set Who can post to Anyone on the web so external senders are not rejected, decide whether messages from non-members should be moderated, and enter the group address in the Replace recipient field of the routing rule.
Does a catch-all work on Google Workspace Business Starter?
Yes. The Routing and Default routing settings used to build a catch-all are part of the Gmail admin settings in every Business and Enterprise edition as of October 2026, including Business Starter. You only need an account with the Gmail Settings admin privilege, which super admins have by default.
Why do senders still get a bounce after I set up the catch-all?
Usually the rule has not propagated yet (Google says up to 24 hours, usually much sooner), the wrong account type was selected (it must apply to all inactive and unrecognized accounts, or only to non-recognized addresses in Default routing), or a Reject rule with higher priority is catching the message first. Email Log Search in the Admin console shows what happened to a specific message.
Will a catch-all increase spam?
Almost certainly. Spammers send to guessed addresses, and a catch-all accepts all of them instead of bouncing them. Gmail’s spam filter still runs on the catch-all mailbox, but expect more junk. Pointing the catch-all at a moderated group or a dedicated mailbox rather than your own inbox keeps it manageable.
Can I set a catch-all for only one of my domains?
Yes. In the Routing rule, use the Envelope filter with Only affect specific envelope recipients and a Pattern match such as ^.*@example\.com$. In Default routing, choose Pattern match instead of All recipients. Add one rule per domain if each domain needs its own catch-all destination.
How do I turn off a catch-all in Google Workspace?
Go to Apps → Google Workspace → Gmail → Routing (or Default routing), point at the catch-all rule, and click Disable to pause it or Delete to remove it, then confirm. Within 24 hours mail to unknown addresses bounces again with the standard 550 5.1.1 error.
MyOwnGoogle is reader-supported. If you start a Google Workspace trial through our links we may earn a commission, at no extra cost to you. This never affects what we recommend.