A common misconception in B2B email deliverability is that a catch-all (accept-all) domain accepts every possible email address without exception—and therefore no address on that domain can ever return an INVALID hard bounce during verification.
In reality, production mail servers frequently accept random, non-existent addresses (250 2.1.5 OK) while simultaneously rejecting specific addresses on the exact same domain with 550 5.2.1 (Mailbox disabled) or 550 5.1.1 / 5.7.1 (Recipient rejected).
If your email verification tool blindly overwrites every address on a catch-all domain as CATCH_ALL, those disabled former-employee accounts stay hidden in your list and guaranteed-bounce the moment you launch your campaign. Below is the exact protocol and vendor documentation proving why this happens.
1. Protocol Proof: IETF RFC 5321 & RFC 3463
Every outbound email delivery follows the SMTP command sequence defined in IETF RFC 5321 §3.3 (Mail Transactions):
MAIL FROM:<[email protected]>— identifies the envelope sender.RCPT TO:<[email protected]>— asks the receiving server whether it will accept mail for this specific recipient.DATA— transmits the email headers and body.
Under RFC 5321 §4.2.5, when a receiving mail server responds to RCPT TO with a permanent 5xx failure code, the transaction for that recipient is terminated immediately at the perimeter. Your mail server is prohibited from advancing to the DATA step and must generate a hard-bounce Delivery Status Notification (DSN).
Specifically, RFC 3463 §3.3 (Enhanced Mail System Status Codes) defines status code X.2.1 (550 5.2.1):
X.2.1 — Mailbox disabled, not accepting messages: “The mailbox exists, but is not accepting messages. This may be a permanent error if the mailbox will never be re-enabled.”
# Same SMTP session on a Google Workspace Catch-All domain (example-corp.com)
S: 220 mx.google.com ESMTP
C: EHLO verifier.mailveri.com
S: 250-mx.google.com at your service
C: MAIL FROM:<[email protected]>
S: 250 2.1.0 OK
# 1. Random nonexistent address -> Accepted by Catch-All routing rule!
C: RCPT TO:<[email protected]>
S: 250 2.1.5 OK
# 2. Former employee whose account was Suspended by Admin -> Hard Bounce!
C: RCPT TO:<[email protected]>
S: 550-5.2.1 The email account that you tried to reach is disabled. Learn more at
S: 550 5.2.1 https://support.google.com/mail/?p=DisabledUser2. Google Workspace Proof: Directory Users vs. Unrecognized Catch-All
Why would Google’s mail servers (aspmx.l.google.com) accept a gibberish address like [email protected] while rejecting [email protected] with 550 5.2.1?
The answer lies in how Google Admin Console separates Directory Users from Unrecognized Addresses:
- Catch-All Applies Only to Unrecognized Addresses: In Google’s official admin guide, Get misaddressed email in a catch-all mailbox and Add routing settings for Gmail, administrators configure catch-all routing under Account types to affect, which separates checkboxes into
Users,Groups, andUnrecognized / Catch-all. Standard catch-all rules check onlyUnrecognized / Catch-all—meaning the rule only catches addresses that do not match any account in Google Directory. - Suspended Accounts Still Exist in Google Directory: When an employee leaves a company, IT admins rarely delete the account right away because deleting it wipes the employee’s Google Drive, Docs, and Vault audit history. Instead, admins follow Suspend a user, which explicitly states:
“While suspended, a user can’t: Sign in to their Google Workspace account… Receive new email (messages sent to the user bounce back to the sender).”
- Immediate
550 5.2.1Rejection atRCPT TO: Because the suspended user still exists in the Directory, an email sent to them does not fall into theUnrecognized / Catch-allbucket. Instead, Google evaluates the user’s suspended status and returns the exact bounce documented in Google Workspace SMTP Error Reference:550 5.2.1 The email account that you tried to reach is disabled.
3. Microsoft 365 (Exchange Online) Proof: Internal Relay vs. Explicit Rejections
Microsoft 365 follows a similar architectural separation documented in Microsoft Learn:
- Catch-All via Internal Relay: By default, Directory-Based Edge Blocking (DBEB) rejects unrecognized recipients at the Exchange Online Protection (EOP) perimeter with
550 5.4.1 Recipient address rejected: Access denied. A Microsoft 365 domain acts as catch-all only when the admin switches the domain type in Manage accepted domains in Exchange Online from Authoritative to Internal Relay, causing EOP to accept unprovisioned addresses (250 2.1.5 Recipient OK) for downstream routing. - Per-Recipient Blocklists & Mail Flow Rules Fire First: Even on an Internal Relay domain, specific former-employee or decommissioned addresses added to the tenant blocklist or matched by Exchange Mail Flow Rules (Transport Rules) with the Reject the message with status code action are rejected directly at the perimeter with
550 5.7.1or550 5.1.1.
Summary: How MailVeri Protects Your Bounce Rate on Catch-All Domains
| Recipient State on a Catch-All Domain | Server Reply at RCPT TO | What Happens If You Send? | MailVeri Verdict |
|---|---|---|---|
| Active or Unrecognized Address | 250 2.1.5 OK | Accepted by catch-all gateway | CATCH_ALL |
| Suspended / Disabled Directory User | 550 5.2.1 Disabled | 100% Immediate Hard Bounce | INVALID |
| Explicitly Blocked / Decommissioned User | 550 5.1.1 / 5.7.1 | 100% Immediate Hard Bounce | INVALID |
| Mailbox Over Storage Quota | 452 / 552 5.2.2 | Deferred Retry → Bounce | FULL_INBOX |
Many legacy verifiers take a shortcut: once they detect a catch-all domain, they label every address on that domain as CATCH_ALL—even when the server explicitly returned 550 5.2.1 Disabled for a former employee. When sales teams later run cautious outreach to their catch-all segment, those masked disabled accounts immediately hard-bounce and damage sender reputation.
MailVeri never masks an explicit rejection: while we unify ambiguous and unverifiable addresses on a confirmed catch-all domain into CATCH_ALL for clean list segmentation, any address that returns an explicit 550 disabled/rejected code or a FULL_INBOX quota error is strictly flagged as INVALID or FULL_INBOX—keeping your bounce rate safely under 2% at a fraction of legacy verification costs (starting at $0.0002/check, up to 90% cheaper than ZeroBounce). See how this directly impacts scraped B2B lead lists in Why Apollo “Verified” Emails Still Bounce, and compare our catch-all pricing in our BounceBan & Scrubby Catch-All Alternative Guide and ZeroBounce vs NeverBounce Pricing Audit.
Frequently Asked Questions
Can a catch-all corporate domain still return 550 INVALID for specific addresses?
Yes. Under RFC 5321/3463 and official Google Workspace and Microsoft Exchange Online routing rules, a domain configured to accept unrecognized addresses can still explicitly reject suspended, disabled (550 5.2.1), or access-restricted (550 5.4.1) directory accounts.
Why does Google Workspace bounce a suspended user even when catch-all routing is enabled?
Google Workspace catch-all routing applies to unrecognized local parts; when an address matches an existing directory user whose account has been suspended by an administrator, Gmail rejects mail for that disabled user with a 550 5.2.1 error.
