How to Set Up a Catch-All Email in Google Workspace (and When Not To)

Google Workspace has no switch labelled “catch-all”. It has something more flexible: routing rules in the Admin console. One of them, set up correctly, sends every message addressed to a non-existent address on your domain to a single mailbox. Google documents this as getting misaddressed email in a catch-all mailbox, and it takes about five minutes if you have the right admin role.

This guide walks through the exact settings, explains the limits that apply once mail starts flowing, and is honest about the cases where a Workspace catch-all is the wrong tool. Steps and menu names were checked against Google’s Admin Help on 2 November 2026.

If you are new to the idea itself, what a catch-all email address is and how it works covers the DNS and SMTP side. Here we stay inside Workspace.

Before you start

You need three things:

1. A Google Workspace account with your domain verified. Catch-all routing works on the domains your Workspace account already receives mail for. Free Gmail cannot do this; see what works with a free Gmail account instead.
2. The Gmail Settings administrator privilege. A super admin has it. A delegated admin needs it granted explicitly.
3. A destination for the mail. Google allows three choices:
   • an existing user account, for example your own;
   • a new user account created only to collect catch-all mail;
   • a Google Group, using the group’s address, so several people in your organisation can read what arrives.

A dedicated user or a group is cleaner than your own inbox. Catch-all mail is noisy, and you will want to filter or ignore it without touching your normal mail.

Step-by-step: create the catch-all routing rule

1. Sign in to the Admin console and open Menu > Apps > Google Workspace > Gmail > Routing.
2. On the Routing tab, scroll to the Routing section and click Configure (or Add another rule if rules already exist).
3. In the Add setting box, fill in:
   • Name. Something like Catch-all for unknown addresses. The rule cannot be saved without a name.
   • Messages to affect: tick Inbound messages.
   • Action: choose Modify message, tick Change envelope recipient, select Replace recipient, and enter the catch-all address you picked above.
4. Click Show more options.
5. Under Select all account types this action applies to, tick All inactive and unrecognized accounts, and make sure Archive accounts with assigned delegate is also ticked. Leave Active user account and Group account unticked, otherwise the rule would also redirect mail for your real users.
6. Optionally, use the Envelope filter boxes to limit the rule to certain senders or recipients, for example only addresses matching a pattern.
7. Click Save.

Google says changes can take up to 24 hours to apply, though they usually work much sooner. To test, send a message from an outside account to an address that does not exist, such as random-test-123@yourdomain.com, and check the catch-all mailbox.

To turn it off later, go back to the Routing tab, point at the rule, and choose Disable or Delete.

Routing or Default routing?

The Admin console also has a Default routing page, with a recipient option called All recipients that covers non-recognized addresses too. It can be made to behave like a catch-all, but Google’s own catch-all article uses the Routing page with the account-type options above, because that is the cleanest way to touch only unknown addresses. Default routing is lower priority than other Gmail routing settings, so a conflicting rule elsewhere wins. If you do not have a reason to prefer it, use the steps above.

What “unknown address” means to Google

The rule only fires for addresses Workspace does not recognise as an active user or group. Google counts as non-recognized: addresses of suspended users, users whose Gmail is turned off, and any address on a verified domain that is not tied to a user. So sales@ keeps going to the real Sales group, and whatever-i-typed@ goes to the catch-all.

One Workspace detail catches people out: periods matter in Workspace usernames. On gmail.com, jane.doe and janedoe are the same mailbox; in Workspace they are not. If you have a user janedoe and someone writes to jane.doe@yourdomain.com, that message is now “unknown” and lands in the catch-all rather than with Jane. Add an alias for her if that variant is common.

The limits you should know about

A catch-all multiplies the mail one account receives, so Gmail’s receiving limits matter more than usual. Google publishes these per account:

Limit	Value
Messages received per minute	60
Messages received per hour	3,600
Messages received per day	86,400

Google states these apply to all editions and cannot be increased. If an account hits a limit, receiving is typically restricted for about 24 hours, and mail sent during that window cannot be recovered. For a business catching the odd misspelled address, you will never come close. For anything automated, you might.

Google’s own suggestion for automated mail is to send it to a Google Group rather than a user, because groups have a separate set of limits. If you expect real volume, make the catch-all destination a group.

Two further points are not limits but are worth weighing:

• Spam goes up. With a catch-all, nothing is rejected as “no such user”, so every dictionary-attack and guessed address arrives. Gmail’s spam filtering still runs, but the volume landing in the catch-all mailbox grows.
• It is your company domain. Everything that arrives shares the reputation and the admin attention of your main business mail.

When a Workspace catch-all is the right choice

• You want to stop losing mail sent to typos like suport@ or to people who left.
• You hand out a different address per service or supplier and want them all in one place.
• You run light testing of sign-up and password-reset flows on your own product.
• The volume is human-scale: dozens or hundreds of messages a day, not thousands.

For all of these, the Workspace rule is the simplest option you have: no extra provider, no DNS changes, and it lives next to the rest of your mail.

When it is the wrong tool

Automation at volume. SEO and account-creation tools such as GSA Search Engine Ranker, RankerX or XRumer can generate thousands of addresses a day and expect to poll a mailbox over POP3 or IMAP to click confirmation links. Pointing that at your company Workspace means sharing the 86,400-a-day receiving budget with your real mail, filling an admin-managed mailbox with registration traffic, and tying your business domain’s reputation to it.

You need the domain to be disposable. Domains used for mass registrations end up on blocklists sooner or later. You do not want that to be the domain your invoices come from.

You are paying per user just for this. A Workspace seat bought only to hold catch-all mail is a monthly cost for a feature that dedicated services include by default.

For those cases a separate catch-all domain is the better fit: a domain that exists only to receive, with POP3 and IMAP your tool can read directly, and that you can replace without touching your business mail. That is what AllMail provides for SEO tools, with step-by-step setup for GSA SER.

Questions

Is there a catch-all setting in Google Workspace?

Not as a single switch. You create a routing rule in Gmail > Routing that replaces the envelope recipient for all inactive and unrecognized accounts with your chosen catch-all address. The steps are above.

Can a Google Group be the catch-all destination?

Yes. Google lists a group’s email address as one of the allowed destinations. It lets several people read the mail and, for higher volume, uses the separate receiving limits that groups have.

How long does the catch-all rule take to work?

Google says up to 24 hours. In practice it is often minutes. Test with an address that does not exist on your domain.

Will the catch-all catch mail for my real users too?

Not if you leave Active user account and Group account unticked. The rule then applies only to addresses Workspace does not recognise.

Does this work with free Gmail?

No. Catch-all is a per-domain feature, and gmail.com is Google’s domain, not yours. See catch-all options for a free Gmail account.

Is a Workspace catch-all good for GSA SER or other link building tools?

It works technically, but it shares receiving limits and reputation with your business mail. For continuous automation a dedicated catch-all domain is safer; see how catch-all email works for GSA SER.