Keep your EmailOctopus list lean and deliverable
EmailOctopus keeps its price low by keeping its feature set lean, and its hygiene follows the same rule: it automatically retires addresses that hard-bounce, but it has no engine to judge an address it has never sent to. Those never-mailed invalids are exactly what quietly erode your deliverability — and on a plan priced by subscriber count, they cost you money too. Qualisend closes that gap: export your list, verify every address, and remove the dead weight before your next send. Here's the workflow that works today, plus the API and no-code options.
One-click EmailOctopus sync is paused while we rebuild the platform
We've deliberately paused our one-click native connectors while we re-engineer the sync layer they run on — hardening how we authenticate, respect each platform's rate limits, and write results back — so that when the native EmailOctopus integration returns, it stays dependable at any list size rather than fragile at scale. None of this touches how Qualisend verifies an address.
Everything you need works today: the CSV export → verify → reimport loop below, and the API for verifying at signup, are both fully supported and running in production — that's how teams keep EmailOctopus clean right now.
What EmailOctopus cleans for you
EmailOctopus's native hygiene is built around automatic bounce removal: an address that hard-bounces is flagged and dropped from future campaigns, typically after a single hard bounce, and spam complaints and unsubscribes are suppressed automatically so you don't keep mailing someone who has opted out or reported you. A contact that keeps soft-bouncing across sends is eventually treated the same way and removed. For addresses EmailOctopus has actually mailed, that's reliable, hands-off hygiene — but a deliberately lean ESP gives you little else, so everything the bounce handler can't see is on you.
What it can't catch
The catch is that every one of those mechanisms is reactive — it needs a send and a bounce to fire, and EmailOctopus's smaller toolset makes the blind spot sharper because there's no separate validity-cleaning tool to fall back on. Never-mailed invalids from imports and signup forms, disposable addresses, role addresses, and decayed mailboxes all look healthy until your first campaign hits them — which is exactly when a mailbox provider forms its first impression of your domain. An imported list is the sharpest case: it arrives with its bounce history stripped, so addresses that were already failing on the old platform look brand new in EmailOctopus — and every one of them counts toward your subscriber total.
Why a clean EmailOctopus list matters
On EmailOctopus the stakes are double, because most plans are priced on how many subscribers you store, with sending limits layered on top — your bill tracks the size of your list, not just how much you send. The subtlety that costs people money: automatic bounce removal stops the sends but does not necessarily shrink the count you're billed on. A contact EmailOctopus has marked as bounced, or one you keep around "just in case", can still sit inside your stored subscriber total. Deleting the confirmed-dead addresses a verification pass turns up is the step that actually trims that count — enough to drop you under a pricing tier — while protecting the inbox placement that Gmail and Yahoo's 2024 sender rules judge on engagement and bounce rate.
The workflow that works today
Direct connectors are paused while we rebuild the platform, so the dependable path is the CSV loop: export from EmailOctopus, verify in Qualisend, reimport the clean file.
Export your list from EmailOctopus
Open the list you want to clean in your account's contacts area and export it to CSV, making sure the email column is included. For a targeted maintenance clean, export a single list rather than your whole account.
Verify the file in Qualisend
Upload the CSV to Qualisend bulk cleaning — up to 1,000,000 addresses, duplicates charged once — or paste addresses directly. The free plan's 100 credits cover a first sample.
Read the results
Every address returns deliverable, risky, undeliverable, or unknown with a reason code and sub-flags (catch-all, disposable, role, full mailbox), plus the MX provider and probe detail as evidence. Download the cleaned CSV.
Remove the dead addresses in EmailOctopus
EmailOctopus has no "archive" state, so retire dead addresses by filtering your results to undeliverable and deleting those contacts. On a subscriber-priced plan a hard delete is what frees the slot and takes them off the count you're billed on — a contact parked on a separate list inside EmailOctopus stops receiving mail but still occupies a billable subscriber slot. If you re-import often, delete inside EmailOctopus and keep a short suppression export outside it to de-dupe future imports against.
Or automate it at signup
Prefer to keep junk out from the start? Verify at the point of capture with the Qualisend REST API (scoped keys, rate limits, webhooks), or wire a no-code flow through Zapier, Make, or n8n so new EmailOctopus subscribers are checked before they're ever added — and before they start counting toward your subscriber tier.
What Qualisend flags on every address
- Never-mailed invalid addresses that would hard-bounce on your next campaign
- Disposable / throwaway domains built to expire
- Role addresses (info@, support@) that skew your engagement numbers
- Catch-all domains, flagged so you can move them to a separate list and throttle
- A 0–100 confidence score and machine-readable reason code for every address
A native, one-click EmailOctopus connector is part of the platform we're rebuilding — it's returning, not deprecated. Until it ships, the CSV loop above and the API are the fully supported path, and they work with any EmailOctopus plan.
What to do with each result
Every address comes back with a verdict and sub-flags. Here's the action that keeps your EmailOctopus list clean without throwing away contacts you can still reach.
deliverableKeep sending as normal.deliverable + role flagKeep for transactional content; exclude from engagement-judged automations.risky + catch-all flagMove to a separate list and throttle rather than blast.risky + disposable flagDelete — the inbox was built to expire.unknownKeep active and re-verify next clean — usually a transient greylisting or rate-limit, not a verdict on the mailbox.undeliverableDelete, or move to a suppressed list you never mail; don't wait for the bounce to prove it.Related reading
The full step-by-step: export, verify, and remove the dead addresses.
Cleaning is half of deliverability — authenticate your sending domain too.
Verify at signup so junk never enters your list.
How fast a dirty list compounds into a deliverability problem.
Set a re-clean cadence sized to how fast your list grows and how it's sourced.
The full picture beyond list hygiene.
EmailOctopus verification FAQ
Clean your EmailOctopus list in minutes
Start free with 100 credits that never expire — no card required. Export, verify, reimport, and protect your next campaign.