Catch-all address
What is Catch-all address?
A catch-all address is a mail server setting that delivers messages sent to any address at a domain -- even ones never created -- to one inbox instead of bouncing them, which also makes the domain an easy target for spammers harvesting addresses. AdminKit's guide to bounces and backscatter explains how to avoid that cost.
By AdminKit team, Netbase JSC · Updated
A catch-all address (or catch-all mailbox) is a mail server configuration that delivers messages sent to any address at a domain — including addresses that were never specifically created — to one designated inbox instead of bouncing them as undeliverable, the same behavior Google Workspace’s own admin documentation describes, the behavior RFC 5321 (also tracked on the IETF Datatracker) expects an SMTP server to perform only for addresses it actually recognizes. It’s commonly used so a typo in a customer’s email, like sales@ instead of sale@, still reaches someone, but it carries a real security and hygiene cost: a domain with a catch-all accepts mail to any made-up address, making it a convenient target for spammers harvesting addresses, and it prevents legitimate bounce messages (RFC 3464 delivery status notifications) from ever signaling that an address doesn’t exist. Hosted mail-routing services expose the same switch: Cloudflare Email Routing’s catch-all rule, once enabled, forwards every email sent to the domain, including misspelled local parts, to a single destination. This also interacts with backscatter, where a server using a catch-all forwards or auto-responds to spoofed senders instead of silently dropping mail to nonexistent addresses. A parked domain is the opposite case: it should accept no mail at all and say so in DNS. AdminKit’s guide to email bounces and backscatter explains how this failure mode shows up and how to avoid it.
The catch-all tradeoff:
- Upside: a typo’d address (sales@ vs sale@) still reaches an inbox instead of bouncing.
- Downside: every made-up address also gets accepted, which spammers use to harvest valid-looking targets.
- Downside: real RFC 3464 bounce notifications never fire, so you lose the signal that an address doesn’t exist.
Catch-all address is part of AdminKit’s email authentication cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What's the upside of running a catch-all address?
A typo'd address, like sales@ instead of sale@, still reaches an inbox instead of bouncing -- useful for catching customer typos that would otherwise mean a lost message.
What's the main downside of a catch-all address?
It accepts mail to any made-up address, making the domain a convenient target for spammers harvesting addresses, and it prevents legitimate RFC 3464 bounce notifications from signaling that an address doesn't exist.
How does a catch-all address interact with backscatter?
A server using a catch-all forwards or auto-responds to spoofed senders instead of silently dropping mail to nonexistent addresses, so it's especially exposed to generating backscatter.
What SMTP behavior does a catch-all override?
RFC 5321 expects an SMTP server to accept mail only for addresses it actually recognizes -- a catch-all deliberately accepts everything instead, trading that signal for convenience.
Sources
- RFC 5321 -- Simple Mail Transfer Protocol
- RFC 3464 -- An Extensible Message Format for Delivery Status Notifications
- IETF Datatracker -- RFC 5321 (SMTP) document status
- Google Workspace Help -- Get misaddressed email in a catch-all mailbox
- Email routing rules and addresses · Cloudflare Email Service docs