A raw lead file rewards the wrong instinct. The number is visible, so teams try to preserve it. Every row removed feels like lost opportunity.
In this Ink Persuasion run, preserving the source meant something different: retain every original row and every reason code, but release only the records that passed the usable-lead contract.
The source held 8,252 rows. The final campaign-usable tab held 5,602. The remaining records were not quietly erased. They were reconciled into blank, duplicate, invalid, needs-review, and security-provider evidence paths in a separate native Google Sheet.
Start with source reconciliation
Before verification, we proved what the source actually contained:
The immutable starting count used for final reconciliation.
Five rows had no email address and could not enter mailbox verification.
Duplicate email rows were retained in the audit rather than counted as fresh prospects.
Every unique nonblank address reached the verifier completion gate.
The equation is exact: 8,231 unique nonblank addresses, 16 duplicate email rows, and 5 blank-email rows reconcile to all 8,252 source rows.
Verification is only one gate
MailTester Ninja returned a machine-readable address result and the recipient MX. The run completed all 8,231 unique addresses at the documented conservative Pro-plan rate of 11 request starts per 10 seconds.
The first verifier pass produced 6,660 initially valid addresses. It also identified invalid and uncertain outcomes that needed their own routes. A valid mailbox result did not automatically mean the record was approved for this campaign.
Important: mailbox validity answers whether an address appears able to receive mail. It does not answer whether the company is in scope, suppressed, duplicated, protected by a recipient security gateway, or safe for a particular campaign.
The recipient security gate changed the usable count
The list was also checked for recipient domains whose MX or provider evidence identified email security infrastructure, including Mimecast, Barracuda, Proofpoint, Cisco, Sophos, and other observed providers.
That stage produced 1,742 security-provider removals across the processed records. This number overlaps earlier verifier outcomes, so it must not be added to the valid, invalid, and review counts as though every number were an independent bucket.
Microsoft 365 and Google Workspace were preserved when the evidence showed only ordinary mailbox hosting. A domain was removed for the security gate only when provider or MX evidence supported that decision.
Why the final file had 5,602 usable leads
The six-tab destination made the result inspectable: Summary, Final Valid Clean, Needs Review, Invalid Emails, Security Removed, and Duplicates Removed. The original source Sheet remained unchanged.
Why 8,252 minus 5,602 is not a failure
The removed or held rows represented costs the raw file was hiding. They included wasted sequencing capacity, avoidable bounce risk, ambiguous recipient infrastructure, duplicate prospect touches, and records that could not support a confident decision.
A list is not more valuable because it is larger. It is more valuable when an operator can explain why every released row passed and where every unreleased row went.
The two rules that kept the audit honest
- Do not overwrite the source. Cleaned names went into `Company Name Clean`; the original company field and source workbook stayed intact.
- Do not force uncertainty into valid. Catch-all, timeout, MX error, provider ambiguity, and other unresolved states belong in review until new evidence resolves them.
What campaign-ready means here
The 5,602 records passed this list-cleaning workflow. They were delivered as the usable output, but campaign-specific suppression, field mapping, identity checks, and destination reconciliation still belong at import time.
Use the two-gate email verification workflow to design the verifier and security checks, the lead-list reconciliation guide to preserve row-level truth, and the campaign import gate before launch.
How often should you clean a cold email list?
Clean it before every new import and repeat verification when the underlying data is old enough that mailbox status may have changed. Keep prior results as dated evidence rather than treating them as permanent truth.
Should catch-all emails be included in cold outreach?
Not automatically. Catch-all means the domain accepts addresses broadly enough that the verifier cannot prove the individual mailbox. Route those records to a controlled review or separate test lane instead of mixing them into the fully verified file.
What is the difference between email verification and list cleaning?
Email verification classifies mailbox evidence. List cleaning combines that result with deduplication, blanks, suppression, identity, recipient infrastructure, campaign fit, and final destination reconciliation.
