An email address can be technically valid and still be a poor choice for your next campaign.
That sounds obvious once you say it out loud. Yet many sending decisions still begin and end with a single question: Will this inbox accept the message?
That is useful information. It is not the whole picture.
A mailbox may exist but belong to a shared team inbox. It may sit behind a catch-all domain. It may be widely circulated, breached or linked with higher-risk sending patterns. Or it may simply be an inbox nobody has used for months.
None of those cases necessarily means “delete immediately”. But they do mean you should stop treating every deliverable address as equally safe to email.
The better question is not only “Can I send here?” It is “What should I do with this contact in this campaign?”
Deliverable is a technical result, not a sending recommendation
Email verification answers an important first question: can this address likely receive mail?
That covers basics such as syntax, domain configuration and mailbox-level checks. It helps remove clear problems before they become hard bounces, wasted spend or a messy CRM record.
But a deliverable result does not tell you:
● whether the contact gave meaningful consent
● whether the inbox belongs to one person or a shared function
● whether the address carries extra risk
● whether the person still works at that company
● whether the inbox is actively used at all
This is where a lot of teams get caught out. They clean a list, see a reassuring number of deliverable contacts, then send the same message to everyone left.
That is not list hygiene. It is a slightly tidier version of spraying and hoping.
Google’s sender guidance is pretty clear on the bigger point: spam reports can hurt domain reputation over time. So the job is not merely to eliminate addresses that bounce. It is to avoid sending unwanted or low-value messages to people who are unlikely to engage with them. Google recommends keeping spam rates low and sending only to people who want to receive your messages.
The six email categories that need different treatment
A sensible email programme needs more than a “keep” and “delete” bucket. These are the contact types that should trigger a different decision.
- Undeliverable addresses: suppress them
This is the easy one.
An address marked as undeliverable should not remain in your normal sending audience. Keeping it around because it was once a valuable lead does not make it less likely to bounce next time.
Suppress it, update the CRM and move on.
There may be a separate process for finding a replacement contact at the same company. But that is a prospecting task, not a reason to keep emailing a dead inbox.
Bouncer Email Verification can help identify addresses that are unlikely to receive mail before they hit your campaign. - Disposable addresses: match the rule to the use case
Disposable email addresses are not always malicious. Someone signing up for a one-off webinar might use one because they do not want another newsletter. Someone testing a free tool may just want to see how it works.
The issue is not that these people are automatically bad leads. The issue is that a disposable address is rarely a strong foundation for an ongoing customer relationship.
For a newsletter form, you may choose to block disposable addresses completely.
For a free tool, you might allow access but avoid adding the contact to your main marketing
audience.
For a trial, you may want an additional verification step rather than an instant rejection.
The point is to have a rule. “We will deal with it later” is not a rule. It is how temporary addresses quietly end up in every future campaign. - Role-based addresses: useful, but not the same as named contacts
Addresses such as info@, sales@, support@ or hello@ are not inherently risky.
In many B2B companies, they are the right place for a partnership request, supplier query or general enquiry. In other cases, they are monitored by a rotating team that has no interest in receiving marketing emails.
Treat them as a separate audience.
A role address might make sense for an operational announcement or account-related message. It is usually a weaker fit for a personalised nurture sequence that assumes one person owns the inbox.
That distinction matters because a shared inbox can technically receive your campaign while producing very little meaningful engagement. - Catch-all addresses: do not panic, but do not send blindly
Catch-all domains accept mail sent to almost any address at that domain. That makes verification harder. A message may appear deliverable even when you cannot fully confirm that the named mailbox exists.
The lazy answer is to suppress all catch-alls. That can be costly, especially in B2B, where some valid prospects sit behind catch-all configurations.
The reckless answer is to treat them exactly like confirmed addresses.
A better middle ground is to segment them.
Keep catch-all addresses separate from your strongest, recently engaged audience. Start with smaller sends. Use a clear relevance threshold. Watch bounce behaviour and engagement closely before scaling.
Bouncer supports catch-all verification and can add extra context around verification results.
That still does not turn every catch-all contact into a green light. It gives you a better starting point for a cautious sending policy. - Toxic or high-risk addresses: flag before they become a problem
Some addresses look technically fine but carry signals you should not ignore.
They may be widely circulated, linked to breaches, associated with complaints or resemble potential spam-trap risks. You do not need to assume every flagged contact will hurt your deliverability. You do need to stop placing those contacts into your highest-volume campaigns without a second thought.
This is where Bouncer Toxicity Check is useful. It adds a risk layer that basic verification does not cover.
The right action depends on context. A high-risk address might move into a review queue. It may be excluded from a reactivation send. It may only receive genuinely necessary transactional communication.
What it should not do is flow straight into the same campaign as your cleanest and most engaged contacts. - Deliverable but inactive inboxes: the category most teams miss
This is the awkward one.
An inbox can work perfectly. It can accept mail. It may not be disposable, role-based or obviously risky.
It can still be a poor recipient for your next campaign.
That does not mean you should purge every low-activity contact. Email engagement is nuanced. Someone may ignore newsletters for months and still open one important update at exactly the right moment.
But it does mean you should stop pretending that technical deliverability tells you everything that matters.
Bouncer Email Engagement Insights adds an extra signal around how active a contact appears to be in their inbox overall. It is useful for prioritising, segmenting and deciding where to apply more caution.
It is not a replacement for your own engagement data.
A contact can be active in their inbox and uninterested in your brand. Another can appear quiet but still be a paying customer who needs product updates. Use mailbox activity as context, not as an automatic delete button.
A practical framework: send, segment, pause or suppress
Once you have more than one data point, your sending policy can become much more useful.
Send normally
Use this for contacts that are deliverable, low-risk and relevant to the campaign.
This is your core audience. It should include people with recent brand engagement, clear consent or a strong reason to receive the message.
Segment carefully
Use this for contacts that may be valid but need a different approach.
Catch-all addresses, role accounts and older leads can sit here. Send them smaller batches, with more relevant messaging and closer monitoring. Do not make them carry the same volume or frequency as your best audience.
Pause and review
Use this for addresses with higher-risk signals, unclear source history or weak relevance.
This does not have to mean a manual investigation of every contact. It can mean applying a sunset rule, running a re-engagement campaign or excluding the segment from high-stakes
sends such as a major launch.
Suppress
Use this for clearly undeliverable addresses, contacts that should no longer receive marketing and records that breach your own data policy.
The key is consistency. A suppression decision should update the systems that matter, not live in a forgotten spreadsheet on someone’s desktop.
Build a sending policy around the campaign, not just the contact
The same address can deserve different treatment depending on what you are sending.
A product-security notice is not the same as a promotional newsletter. A customer renewal reminder is not the same as a cold outbound sequence. A launch announcement is not the same as a reactivation email.
That is why blanket rules tend to fail.
Instead, define which categories can receive which types of messages. For example:
● a catch-all contact may be acceptable for a genuinely relevant B2B announcement, but not for a broad weekly newsletter
● a role address may work for a service update, but not for a personal nurture flow
● a low-activity inbox may be excluded from a high-volume promotion but included in a carefully targeted re-engagement campaign
● a high-risk address may be held back from marketing until you have a clearer reason to contact it
This takes a little more thought than checking a “valid” column and pressing send. It also gives you a more defensible process when campaign performance starts to slip.
Where Bouncer fits into the decision
Bouncer can support the different layers of this workflow:
● Email Verification helps identify addresses that are deliverable, undeliverable or uncertain.
● Toxicity Check adds risk signals that basic verification cannot provide.
● Bounce Estimate can help you assess the likely risk across a full list before a send.
● Email Engagement Insights adds context about overall mailbox activity.
● Deliverability Kit helps you check the infrastructure and placement side of the equation as well.
None of these tools can fix poor targeting, weak consent or irrelevant content. They are not supposed to.
Their job is to help you make better decisions before bad data turns into avoidable deliverability damage.
A verified address is the start of the decision, not the end
Verification is still one of the most practical things a sender can do. It helps cut obvious waste and keeps clear problems out of your campaigns.
But “deliverable” should be the first filter, not the final verdict.
The senders who protect their reputation best are not the ones who find a perfect list. They are the ones who treat contact quality as a set of signals, apply context and know when not to send.
Because an inbox that can receive your email is not always an inbox that should.
Disclosure: We provide our members the opportunity to blog and share insight on our site, subject to editorial rules and guidelines. Bouncer is an enterprise member.
