How to Clean an Email List in Omnisend

Omnisend is built for ecommerce email and SMS: abandoned cart flows, post-purchase sequences, win-back campaigns, and promotional sends to segmented customer lists. The platform's strength is automation depth and multi-channel coordination.

The weakness that applies to all ecommerce email tools: contact databases grow from multiple sources (storefronts, opt-in forms, imported customer files, loyalty platform exports), and quality is uneven across those sources. A customer who bought from you two years ago may have changed their email address, abandoned the inbox, or moved to a role address at work. The purchase history is valuable. The address may no longer be.

Sending to bad addresses on Omnisend affects your sending reputation on the platform and your deliverability at inbox providers. Cleaning before a campaign is cheaper than recovering after.

Step 0: what proper verification covers

Omnisend's built-in tools suppress hard bounces and unsubscribes reactively, after they happen. Verification is the proactive layer.

Surface checks catch obviously broken rows: syntax errors, domains with no MX records, known throwaway providers. Useful, but they miss the larger category of addresses on real domains where the specific mailbox no longer exists.

SMTP mailbox probing is where the real signal comes from. MailCull's engine opens a direct connection to the receiving mail server, performs an EHLO handshake, and issues RCPT TO for each address being verified. The server's response. 250 (accept), 550 (user unknown), 4xx (temporary deferral), tells you the actual answer. A 550 from the server is a hard bounce confirmed before delivery.

Microsoft 365 HTTP enumeration handles the B2B addresses in your Omnisend database. If you sell to businesses, professional buyers, or corporate accounts, a meaningful share of your email list is on M365 tenants. M365's EOP layer accepts RCPT TO for any address on the tenant, regardless of whether the mailbox exists. An SMTP probe returns 250 OK; delivery hard-bounces. MailCull's HTTP cascade queries Microsoft's authentication APIs directly to confirm whether the account is real.

Catch-all detection flags domains that accept all RCPT TO regardless of mailbox existence, common on smaller ecommerce supplier and wholesale domains.

Every result includes an evidence chain showing the specific signals that drove the verdict.

Step 1: export the audience or segment

Start with the contacts you are planning to send to. For Omnisend ecommerce workflows, the most valuable export targets:

All active contacts, a periodic full audit. If you have not verified your contact base in 12+ months, it is time. Ecommerce contact lists decay faster than most: customers change jobs, abandon secondary inboxes, or use temporary addresses at checkout.

Contacts from a specific acquisition source: if you imported a batch from a loyalty platform, a marketplace integration, or a trade show, verify that batch specifically. Import quality varies by source.

Re-engagement campaign targets, if you are preparing a win-back campaign for contacts who have not purchased in 90+ days, verify the segment first. Win-back flows are high-value sends; you want them going to real addresses.

High-value customer segments: VIP customers, high-LTV buyers, loyalty tier members. These are your most important sends. The verification investment is clearly worth it.

Export as CSV. Keep the fields needed for reimport: email, name, customer tags, any custom properties.

Step 2: upload to MailCull

Upload the CSV to Verify List. MailCull handles Omnisend export files including multi-column formats with properties and metadata.

Check stack: syntax validation, domain/MX, typo detection, disposable detection, SMTP probe, M365 HTTP enumeration, catch-all detection.

Results: deliverable, risky, undeliverable, unknown.

Free: 500 validation credits/month, recurring (no credit card). Pro: 100,000 validation credits/month at $9/month flat (REST API + MCP access for AI agents included).

Step 3: act on the results

Undeliverable. Suppress in Omnisend before the next campaign. These are confirmed hard bounces. For ecommerce flows with high send frequency (abandoned cart, post-purchase sequences), undeliverable contacts generate bounce events at high volume quickly.

Deliverable. Include in all flows.

Risky. Inspect by reason:

• Catch-all domain: common on wholesale buyer and B2B customer domains. Include in low-frequency campaigns; exclude from high-frequency automations where accumulating bounces is a risk.
• M365 disagreement: HTTP cascade and SMTP gave conflicting signals. Treat conservatively for high-value sends.
• Role address (purchasing@, orders@, info@), exists but shared. Lower engagement signal for ecommerce campaigns.
• Greylisted: temporary deferral, usually resolves. Include with monitoring.

Unknown, similar judgment to risky. The probe was inconclusive.

Step 4: update Omnisend

Suppression approach, upload undeliverable contacts to Omnisend's unsubscribe list or exclusion groups. They stop receiving sends without losing contact history or purchase data.

Delete approach, for contacts with no purchase history and confirmed undeliverable status, deleting is cleaner and may reduce your contact count for billing purposes.

For most ecommerce operations, suppression is preferable, you want to keep purchase history and event data intact for attribution and analytics, even if the address is no longer sendable.

Timing around ecommerce sends

The highest-leverage moment for Omnisend list cleaning is before seasonal campaigns: holiday sends, sale events, new product launches. These are high-volume sends where:

1. Deliverability problems have direct revenue consequences (lost inbox placement = lost sales)
2. Omnisend's domain reputation effects are amplified by send volume
3. A bad batch in a promotional send can affect warm-up domain reputation for weeks after

Running verification 2-3 weeks before a major campaign gives you time to process results, suppress bad contacts, and let any domain signals stabilise before the high-stakes sends go out.

---

You came here to protect your Omnisend deliverability and keep ecommerce flows running on clean data. MailCull verifies every address at the SMTP level, handles the M365 edge cases that standard tools miss, and shows the evidence for every verdict.

Clean your Omnisend list with MailCull, free with 500 validation credits/month →