How to clean an EmailOctopus email list and cut your bill

EmailOctopus keeps its price low by keeping its feature set lean, and its list hygiene follows the same rule: it automatically removes hard bounces so you stop mailing addresses that have already failed, and then it largely leaves you to it. That automation is genuinely useful, but it is close to the whole story — there is no engagement-scoring engine or predictive cleanup running underneath. So to clean an EmailOctopus list properly you have to cover the rest yourself, and on a plan priced by subscriber count that gap costs you money as well as deliverability. Deliverability has two halves, though, and a clean list is only one of them — even a spotless list still lands in spam unless you authenticate your EmailOctopus sending domain with SPF, DKIM, and DMARC. This guide covers what EmailOctopus handles natively, the addresses it can never see, and the export → verify → act loop that keeps your list lean before your next send.

What EmailOctopus already does for you#

EmailOctopus's native hygiene is built around automatic bounce removal:

• Hard bounces are removed automatically. When an address hard-bounces, EmailOctopus stops sending to it — the contact is flagged as bounced and dropped from future campaigns, typically after a single hard bounce.
• Complaints and unsubscribes are honoured. Spam complaints and unsubscribes are suppressed automatically, so you don't keep mailing someone who has already opted out or reported you.
• Soft bounces are tracked. A contact that keeps soft-bouncing across sends is eventually treated like a hard bounce and removed.

EmailOctopus behavior above last verified against the EmailOctopus help center, July 2026.

Credit where due: for addresses EmailOctopus has actually mailed, this is reliable, hands-off hygiene. The catch is that a lean ESP gives you little else — there is no separate validity-cleaning tool to fall back on, so everything the bounce handler can't see is on you.

What EmailOctopus can't catch#

Every mechanism above is reactive — it needs a send and a bounce to fire. That leaves the blind spot every ESP shares, made sharper here by the smaller toolset:

• Never-mailed invalid addresses. Imports from another platform, old signups, and typos captured at the form have never bounced because they have never been sent to. EmailOctopus has no signal on them until your first campaign lands — and that first campaign is exactly when a mailbox provider forms its first impression of you.
• Disposable addresses accepted at signup that will quietly stop existing.
• Role addresses (info@, support@) that skew your engagement numbers — see role, disposable and free addresses.
• Decayed addresses that look healthy today and will bounce next month.

An imported list is the worst 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. Verify before the import, not after the first send.

Step-by-step: export, verify, act#

Direct ESP connections are paused while we rebuild our integrations platform (see integrations), so the dependable path today is the CSV loop — the same flow as the MailerLite and Brevo guides, in EmailOctopus's terms:

1. Export from EmailOctopus. Open the list you want to clean in your account's contacts area and export it to CSV (include the email column).
2. Verify the file. Upload it 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.
3. Read the results. Every address returns deliverable, risky, undeliverable, or unknown with a reason code, a 0–100 score, and sub-flags (catch-all, disposable, role, full mailbox), plus the MX provider as evidence. Download the cleaned CSV.
4. Remove the undeliverables in EmailOctopus. Filter your results to undeliverable, then delete those contacts — or move them to a separate list you never send to. On a subscriber-priced plan, taking them out of your active list is what actually removes them from the count you pay for.
5. Handle everything else per verdict — the table below.

What to do with each verdict#

Keep the subscriber count lean#

This is where cleaning pays for itself on EmailOctopus specifically. Most EmailOctopus plans are priced on how many subscribers you store — with sending limits layered on top — so your bill tracks the size of your list, not just how much you send. That makes a lean list a cheaper list.

The subtlety is that 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. Check how your plan counts contacts, then delete the confirmed-dead addresses your verification pass turns up — that is the step that trims the count and can drop you under a pricing tier. See pricing for how Qualisend's per-address cost compares to carrying dead weight month after month.

Verifying before an import is the strongest version of the same move: junk that never enters the list never counts toward your tier in the first place. The one trade-off to weigh is delete versus keep-and-suppress. A hard delete is simplest and frees the count immediately, but loses the record — so a future re-import could add the same dead address straight back. Keeping confirmed-dead addresses on a separate list you never mail preserves that record to de-dupe against later, at the cost of the subscriber slots. On a tight budget, deleting the obvious invalids and keeping a short suppression export outside EmailOctopus is often the best of both.

How often to re-clean#

There is no universal number, and we won't invent a decay statistic. The real drivers are how fast your list grows and how it is sourced: a double-opt-in list decays slowly, while one fed by imports and pop-ups accumulates junk continuously. Three habits cover most senders:

• Before any high-stakes send — a launch or seasonal campaign.
• After any import, before the first send touches it — and before those addresses start counting toward your subscriber tier.
• On a regular cycle sized to your volume, with your per-campaign bounce rate as the tripwire between cleans. If bounces climb toward the warning thresholds, clean now (see why bounce rate matters).

For a fuller schedule, see how often to clean an email list.

Frequently asked questions#

Does cleaning my list lower my EmailOctopus bill?#

It can, because EmailOctopus is priced on the number of subscribers you store, so a smaller list is a cheaper one. The nuance is that automatic bounce removal stops the sends without necessarily removing a contact from your stored count. The saving comes from verifying and then deleting the undeliverable and disposable addresses — especially the never-mailed invalids that have never bounced and so are still sitting in your list.

Should I delete dead contacts or keep them on a separate list?#

For confirmed-undeliverable addresses, deleting is the cleanest way to free up your subscriber count immediately. The one downside is that a delete loses the record, so a future import could re-add the same dead address. If you import often, keep a short suppression list of known-bad addresses — ideally exported outside EmailOctopus — so you can de-dupe against it before the next import.

Can I verify addresses before they enter EmailOctopus?#

Yes, and it is the highest-leverage option: verifying at signup through the API keeps typos and disposable addresses out of EmailOctopus entirely, so they never become billable subscribers in the first place. A native EmailOctopus integration is part of the platform we're rebuilding; until it ships, the CSV loop above is the supported path.

Does EmailOctopus verify email addresses before sending?#

No — EmailOctopus removes addresses after they hard-bounce, which means the first campaign to a bad address is still sent and still counts against your sender reputation. Verification checks whether an address is valid and deliverable before you send, so the bounce never happens. The two are complementary: let EmailOctopus catch what fails in the field, and verify to remove the invalids before they ever go out.

Want to see it before you commit? Run a single address through the free email checker, then clean your whole exported EmailOctopus list in bulk — see pricing to weigh the per-address cost against a month of paying to store dead subscribers.