Why use catch-all
You indulgently accept mail from those who make mistakes in your name.
Indeed, I used to add sound-alike aliases for most local-parts, being responsible for mail subsystem.
You use different addresses for different services/subscriptions.
BTW, a good move to reveal the source of data leak, if you get spammed, for instance.
Common case
There is no problem,
- if you have a full-fledged Google Workspace account, with Email routing and delivery options accessible;
- you have Primary only domain specified, with or without domain aliases.
This way you will get all the mail for your primary domain and domain aliases.
The problem and How to
In terms of the example configuration above you will not get “catch-all” mail for the secondary domain, i.e. for *@vp... users not configured explicitly.
Whenever you have specified a Secondary domain for your G Organization, the Catch-all address in the primary domain is the only option you have.
So how on earth to configure a Catch-all for the Secondary?
An observation that suggested a workaround, I noticed *@alias-like records in Contact information for the recipient configured as Catch-all address above, but adding *@vp... directly there became a challenge:
But then I tried to add the same to the Alternative email addresses section,
and, hey presto, that was automatically moved to the desired Contact information after saving changes.
Finally, all the mail for any address (not belonging to explicitly configured Users) in the Primary domain (@one…), and its aliases, and the Secondary domain (@vp…) is successfully diverted to the Catch-all address specified (as in Common case above). Glad to share.