Catch-All Leads in a Cold Email Sequence: What Step 1 Tells You About the Follow-Ups
A catch-all address that did not bounce on step 1 is not proven to exist. Catch-all domains accept mail for any address at the door, and some of them send a bounce later, after your tool has already marked the email delivered. So treat step 1 to catch-all leads as a test, not a confirmation. Run them as their own campaign behind your confirmed leads, leave at least three days before step 2 so delayed bounces arrive, and let a lead continue only on real evidence: a reply, an auto-reply naming the person, or a forwarding notice. Cut the catch-all sequence shorter than your main one.
Whether to email catch-alls at all is a separate decision. Our decision framework for catch-all addresses covers the bounce-budget maths. This post is about what to do once they are in a sequence.
What step 1 can and cannot tell you
When your sequencer sends to anna.k@catchall-company.com, the receiving server says "OK" whether Anna exists or not. Then one of four things happens:
| What the server does next | What you see | Does the address exist? |
|---|---|---|
| Delivers to Anna's mailbox | Nothing, or a reply | Yes |
| Delivers to a shared or admin mailbox | Nothing, occasionally a reply from someone else | Unknown; nobody named Anna may read it |
| Sends a bounce message later | A bounce hours or days after "delivered" | No |
| Drops the message silently | Nothing | Unknown |
Three of the four look the same from your side: silence. That is why "no bounce" is weak evidence. Our post on why follow-ups bounce more than step 1 covers how late bounces get attributed to the wrong step.
Structure: catch-alls get their own campaign
Mixing catch-all leads into your main sequence makes both harder to read and riskier to send.
- Separate campaign or separate segment. Your confirmed-valid leads go in the main campaign. Catch-all leads go in their own, so their bounce rate is visible on its own.
- Send after the main campaign, not before. Early sends from an inbox set its tone. Start a day's sending with confirmed addresses.
- Cap the catch-all share per inbox. A rule of thumb is that catch-all sends should be a minority of any inbox's daily volume, so one bad domain cannot push the inbox over its bounce threshold.
- Order catch-alls by grade. If your verifier grades catch-all rows, send the higher-graded ones first and stop if the bounce rate climbs. SimpleVerifier's catch-all scoring explains how grades are set.
- Spread them across domains. Do not send fifty catch-all leads at the same company on the same day. See how many people at one company to email.
Timing: wait long enough for late bounces
The gap between step 1 and step 2 is your detection window.
| Gap before step 2 | Risk |
|---|---|
| Same day or next day | Late bounces often have not arrived; step 2 goes to dead addresses |
| 3 days | Most delayed bounces from catch-all and gateway domains have usually landed |
| 5-7 days | Safer, and a normal cold email gap anyway |
Check that your sequencer reads bounce messages from the inbox and stops the lead automatically. Most do, but it only works if the bounce has arrived before the next step fires. Also check that a bounce stops the lead in every campaign it is in, not only the one that sent. Our suppression list guide covers keeping one global list.
Signals that let a lead continue
After step 1, sort catch-all leads by what came back.
| Signal after step 1 | Evidence | What to do |
|---|---|---|
| Real reply from the person | Strong: the address works | Move to your normal reply flow |
| Auto-reply naming the person (out of office, "back on Monday") | Strong: a real mailbox | Continue the sequence |
| Auto-reply saying they have left, with a new contact | Strong: the address is dead or redirected | Stop; research the new contact. See the email is valid but the person left |
| Generic auto-reply from a shared inbox ("Thanks for contacting us") | Weak: mail lands somewhere, maybe not with the person | One follow-up at most |
| Bounce, any time | Strong: does not exist | Stop and suppress globally |
| Nothing after 3-7 days | Weak | Shorter sequence: one follow-up, then stop |
Out-of-office replies are useful evidence because a real mail system wrote them on behalf of a named person. Keep them in your sequencer's records rather than deleting them, and read the text: many say when the person is back, and some say they have left and who to contact instead.
How long a catch-all sequence should be
A shorter sequence for unconfirmed addresses is a sensible default:
| Lead type | Suggested steps |
|---|---|
| Verified valid | Your normal sequence, often 3-5 steps. See how many follow-ups |
| Catch-all, high grade | 2-3 steps |
| Catch-all, low grade | Step 1 only, or skip |
| Catch-all with a sign of life after step 1 | Normal sequence |
The reasoning: each follow-up to an address nobody reads adds bounce and complaint risk with little chance of a reply. Shared mailboxes are also where spam complaints come from, because the person reading them did not ask to hear from you.
Watch the catch-all campaign's numbers on their own
| Measure | Why |
|---|---|
| Bounce rate per step | Late bounces show up as a step-2 spike |
| Bounces by domain | One catch-all domain can produce most of the bounces. See bounces from one domain |
| Reply rate vs main campaign | If catch-alls reply at a fraction of the main rate, shorten or drop them |
| Complaints and unsubscribes | Shared mailboxes complain more |
If the catch-all campaign's bounce rate climbs past your limit, pause it and leave the main campaign running. That is the point of keeping them separate.
A worked example
Illustrative numbers for a 2,000-lead campaign after verification:
| Segment | Leads | Plan |
|---|---|---|
| Valid | 1,400 | Main campaign, four steps, 5-day gaps |
| Catch-all, higher grade | 350 | Own campaign, step 1 and one follow-up after 5 days |
| Catch-all, lower grade | 150 | Held back for now |
| Invalid, unknown after retry | 100 | Removed |
The team sends the main campaign first each morning and the catch-all campaign afterwards, capped at a third of each inbox's daily volume. After step 1 to the 350, eight bounces arrive over the next three days, four of them from one company's domain. Those eight are suppressed everywhere, and the rest of that one domain's leads are dropped from the follow-up. A dozen auto-replies name real people, so those leads move to the main sequence. Everyone else gets one follow-up, then stops.
The lower-graded 150 are only tried if the higher-graded batch bounced well inside the team's limit. If it did not, they are skipped. Our guide to catch-all emails and what to do with them covers grading in more depth.
Free tools that help
- Bulk catch-all checker: find which domains in a list accept everything before you build the campaign.
- Bounce Doctor: sort bounce messages and auto-replies into bad address, sender block, gateway and temporary.
- Bounced email extractor: pull bounced addresses out of a pile of bounce messages for your suppression list.
- Email list splitter: split a verified file into valid and catch-all campaigns.
Where SimpleVerifier fits
SimpleVerifier never reports a catch-all address as valid. Catch-alls come back risky with a grade, so you can split them into their own campaign and send the better-graded ones first. Valid means a mail server confirmed the mailbox. Upload a list on the verify page, then filter the results by status to build the two campaigns. The first 100 checks are free with a Google sign-in, and Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off. See pricing, or read more about catch-all email verification.
Common questions
If a catch-all email did not bounce, does the address exist?
Not necessarily. A catch-all server accepts mail for any address at the domain, and some of them later send a bounce message for addresses that do not exist, minutes or days afterwards. Others silently drop or route the mail to a shared mailbox. No bounce after a few days is weak evidence, not proof.
Should catch-all leads get the full follow-up sequence?
Usually a shorter one. Each extra step to an unconfirmed address adds bounce risk and complaint risk without the same chance of a reply. Many teams send step 1 and one follow-up to catch-alls, then stop unless there was a sign of life.
How long should I wait after step 1 before following up on catch-all leads?
At least three days, and longer is safer. Delayed bounces from catch-all and gateway-protected domains often arrive within a day or two, and you want them recorded before step 2 is sent.
Can I re-verify a catch-all address after step 1?
Re-verifying will give the same catch-all result, because the server still accepts everything. The useful evidence after step 1 comes from what happened to the email: a reply, an auto-reply, or a bounce.
Check your list before you send
Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.