Mailforge provisions infrastructure. It does not qualify contact lists.
Mailforge manages the sending layer: provisioning domains and mailboxes, handling warmup, rotating sending identities across campaigns. It builds and maintains the infrastructure that cold email campaigns run on.
What Mailforge does not do is check whether the email addresses your campaign will target actually exist or should be contacted. That decision happens at the list layer, before any record enters the sending infrastructure Mailforge manages.
These are two distinct responsibilities in the same cold email workflow. Mailforge owns the sending layer. BillionVerify owns the list layer. Neither replaces the other. Both are needed for the investment in cold email infrastructure to produce consistent, predictable campaign results.
Cold Email Verification Framework
This page covers one sender or workflow. The full framework explains the complete path from list source through verification, segmentation, and import into your sender.
What Mailforge manages — and what it does not.
| Mailforge handles | Mailforge does not handle |
|---|---|
| Domain and mailbox provisioning for cold email | Checking whether individual email addresses are deliverable |
| Warmup sequences for new sending infrastructure | Removing invalid, catch-all, or role-based records from contact lists |
| Sending rotation across multiple domains and mailboxes | Classifying contact records by risk before they enter the sending system |
| Inbox placement infrastructure management | Maintaining a suppression file for bounced or opted-out contacts |
| Technical sending setup and DNS configuration | Pre-import list qualification decisions |
Mailforge is infrastructure tooling. The value it provides — healthy sending domains, warmed mailboxes, rotation to protect individual inbox health — depends on the quality of the contact data those domains and mailboxes are used to reach.
Poor list quality does not stay contained at the list level. It flows downstream into the infrastructure Mailforge built. Bounce signals from invalid addresses degrade the domain reputation that warmup worked to establish. Complaints from role-based inboxes weaken the sending health of the mailboxes in rotation.
Why infrastructure investment is wasted without list quality.
Building cold email infrastructure through Mailforge takes time and ongoing management. Domain warmup typically runs for 4 to 8 weeks before a domain is ready for full campaign volume. Setting up rotation across multiple mailboxes, configuring DNS records, and establishing clean sending patterns represents real operational investment.
That investment is undermined when the contact list entering the infrastructure has not been qualified. A few hundred invalid records on a 3,000-contact list can produce enough hard bounces to damage a newly warmed domain. A domain that took six weeks to warm can see its inbox placement degrade within a single campaign if list quality was never addressed.
The infrastructure is sound. The list is the variable. Verification addresses the variable before it reaches the infrastructure.
The combined workflow: verify, then send through Mailforge.
Source list from database, CRM, or enrichment tool
→ Run through BillionVerify before any import
→ Remove invalid, risky, and disposable records
→ Segment catch-all into lower-volume sending track
→ Move role-based records to separate messaging track
→ Hold unknown records for manual review
→ Import only valid records into the sending platform
→ Distribute contacts across Mailforge-provisioned infrastructure
→ Monitor campaign results by sending domain and mailbox
→ Re-verify any list before reuse after 60 to 90 days
Verification happens once per list, upstream of the Mailforge layer. Mailforge handles the mechanics of sending from that point forward. The list decision and the infrastructure decision are separate — each should have a clear owner.
Route each result before entering Mailforge-provisioned infrastructure.
| BillionVerify result | Action before sending through Mailforge |
|---|---|
| Valid | Import into campaign contact list |
| Invalid | Do not import — bounces damage domain reputation Mailforge built |
| Catch-all | Separate lower-volume segment, monitor closely per domain |
| Role-based | Separate messaging track — weak engagement hurts inbox placement signals |
| Unknown | Hold for manual review — exclude until routing decision is made |
| Risky or disposable | Do not import |
Other workflows that apply similar decisions.
Verify Emails Before Warmup
Understand why list verification must happen before warmup, not after.
Pre-Import List Cleaning
Apply a consistent cleaning rule before any list enters a sender or CRM.
Catch-All Policy for Cold Email
Define a routing policy for catch-all results before they enter cold email campaigns.
Cold Email Bounce Rate Control
Control bounce rate at the list level — before the sender is ever involved.
Warmup vs Email Verification
Understand which problem warmup solves and which problem verification solves.
Built-In Verifier vs Third-Party Verification
Compare native sender verification against a dedicated pre-send quality gate.
Folderly + BillionVerify Workflow
Verify lists before Folderly deliverability optimization — clean data makes warmup work.
Mailforge and BillionVerify workflow common questions.
1. If Mailforge warms up my sending domains, do I still need list verification?
Yes. Warmup builds domain reputation by establishing a history of positive sending signals. Bounces from invalid records produce negative signals that work against the warmup progress. Even a well-warmed domain suffers reputation degradation from hard bounces. Verification ensures the addresses entering the warmed infrastructure will not generate the kind of bounce signals that undermine the warmup investment.
2. Does list verification need to integrate directly with Mailforge?
No. The most common approach is to export the contact list, run it through BillionVerify, then import only the valid segment into the campaign platform connected to Mailforge infrastructure. Verification happens outside the sending system. No integration between BillionVerify and Mailforge is required — the value is in the pre-import decision, not in the connection between tools.
3. Can I send to catch-all addresses through Mailforge?
You can, but they should be treated as a separate lower-volume segment. Catch-all addresses carry uncertain delivery risk — the domain accepts mail but the specific mailbox may not exist. Sending a lower volume to catch-all addresses and monitoring the results per sending domain helps you identify which domains deliver successfully and which produce silent failures or late bounces. Do not mix catch-all records with confirmed valid addresses in the same campaign rotation.
4. What happens to domain reputation if I send to invalid addresses through Mailforge?
Hard bounces from invalid addresses generate a negative bounce signal that inbox providers associate with the sending domain. Consistent bounce signals degrade domain reputation over time, reducing inbox placement rates and eventually causing filtering or blocking. Mailforge can manage domain rotation to distribute risk, but it cannot eliminate bounce damage from invalid records. The only prevention is removing invalid records before they are sent to.
5. Should I re-verify a list that caused bounce problems in a Mailforge-managed campaign?
Yes, and also review which sending domains absorbed the highest bounce volume. The contact list should be re-verified, invalid records added to a permanent suppression file, and catch-all records reviewed for domain-level patterns before reuse. Domains that accumulated elevated bounce rates may need additional warmup-equivalent clean sending before they are ready for another high-volume campaign.