How to Clean a MailerLite List: Remove Bad Emails Before They Bounce

To clean a MailerLite list, export your subscribers to a CSV, run the file through an email verifier, and remove everything marked invalid before your next campaign. Move the risky addresses into a separate group you send to more carefully. MailerLite already removes subscribers after they hard bounce, but that is cleanup after the damage. Verifying first stops the bounce from happening at all. SimpleVerifier Pro does the checking for $39 a month: the first 100,000 checks a month at full speed, then slower, never cut off, and you can try 100 free checks first.

MailerLite behaviour in this post comes from MailerLite's own help center, read on 10 November 2026. Settings and rules can change, so confirm anything critical in your account.

What MailerLite does when an email bounces

MailerLite's help center describes two kinds of bounce:

• Hard bounce: the email could not be delivered for a permanent reason. MailerLite says hard-bounced subscribers are removed from your active list automatically, to protect your sender reputation.
• Soft bounce: the email could not be delivered for a temporary reason. These subscribers stay on your active list, because the problem may clear. The help center adds that a subscriber who soft bounces three times in a row is treated as a hard bounce and removed from the active list.

That is useful housekeeping. Two things it does not do:

1. It does not prevent the first hard bounce. Every dead address on your list gets one send before MailerLite learns it is dead. If you import a few thousand old addresses, those first bounces land in a single campaign.
2. It does not tell you why an address is bad. A mailbox that does not exist, a domain with no mail server and a typo all end up in the same bounced pile.

Why a clean list matters even on a small plan

Mailbox providers watch how many of your messages bounce, and a sudden spike looks like a sender who bought or scraped a list. A newsletter with a few hundred subscribers can still trip that if a single import carries a bad batch. Bounces also waste sends: you are paying for every subscriber slot, and bounced addresses that linger in an export or an old group keep inflating counts elsewhere. For the wider picture, see how to improve sender reputation and what a high bounce rate does.

Step by step: clean a MailerLite list

1. Look at what already bounced

Open a recent sent campaign, go to its report, then the Subscriber activity tab, and switch the dropdown between Hard bounce and Soft bounce. MailerLite's help describes this path. Also open the All subscribers tab and filter to bounced subscribers to see who has already been moved out of your active list. Note the domains that appear repeatedly. If a handful of recipient domains account for most failures, paste them into the bounce domain hotspot finder.

2. Export the active subscribers

Export the subscribers you actually plan to send to. If you use groups or segments, export each one so you can match results back. Keep the original file untouched; work on a copy.

3. Remove duplicates and fix obvious column problems

Run the copy through the remove duplicate emails tool so you are not paying to check the same address twice. If the CSV has stray columns or broken rows, the CSV column editor tidies it. Our guide to fixing broken CSV rows before import covers the usual culprits.

4. Verify the file

Upload the cleaned CSV to the verify page or the CSV email verifier. Each address comes back valid, risky or invalid with a reason, so you can see what you are removing. For what each result means, read email verification statuses explained.

5. Decide what to do with each result

• Invalid: remove from your sending groups. These addresses will bounce.
• Risky and catch-all: do not delete by reflex. Keep them in their own group, send less often and watch the bounce count. The post on catch-all emails and what to do explains the trade-off.
• Valid: keep.
• Disposable and role addresses: decide by your audience. See role-based email addresses.

6. Apply the result back in MailerLite

Re-import the valid addresses as your sending group, or import the invalid ones into a group you exclude from campaigns. Do not delete the invalid file: keep it as your own record so a future import cannot quietly add the same addresses back. If you import from other sources regularly, read verifying before a MailerLite import first.

7. Send the next campaign and read the numbers

After the next send, open the report and compare hard bounces to what you expected. A clean list should show very few. If it does not, the bounce message analyzer helps you read the failure messages.

How often to repeat it

Email lists decay as people change jobs and abandon mailboxes. A list that was clean at signup is less clean a year later, even if nobody did anything wrong. Re-verify before big sends and after any import, and use the list cleaning frequency calculator and the list decay calculator to set a schedule that fits your growth. For subscribers who simply stopped opening, a sunset policy is a separate, complementary step: verification finds dead addresses, not uninterested people.

Common mistakes

• Waiting for MailerLite to clean it. Automatic removal happens after bounces. That is exactly the event you are trying to avoid.
• Verifying once and never again. An old clean list is not a clean list.
• Deleting every risky address. Many are real people on mail servers that accept all mail. Segment them rather than throwing away reach.
• Mixing a new import into your main group before checking it. Always verify imported files first.
• Confusing inactive with invalid. A subscriber who never opens may have a perfectly working mailbox.

A worked example

Say you run a small newsletter on MailerLite and have not cleaned it in a year. You export the active subscribers and find that the file mixes three sources: organic signups from your site, a batch imported from a giveaway and an old file from a previous tool. Verifying the file as one lump hides the pattern, so you split by source first. The organic group comes back mostly valid. The giveaway batch has a large share of invalid and disposable addresses, the kind people type to enter a contest and never read. The old file has a lot of risky results, because many of those addresses sit on company domains that accept all mail.

Now the decisions are easy. You keep the organic group. You drop the invalid giveaway addresses and consider whether giveaway entrants belong on the list at all. You move the old file's risky addresses into their own group and send to them in small batches. Your next campaign goes to people who can receive it, and your hard bounces in the report are close to nothing. That is the outcome a verification pass buys: bounces happen in a file, not in a live send.

Questions to ask before the next import

• Where did these addresses come from, and when?
• Did the people ask to hear from you?
• Have I verified this file, or only the last one?
• Is there a copy of the invalid addresses somewhere an import will not overwrite?

If any answer is no, pause the import and fix that first.

What it costs and how it fits

SimpleVerifier Pro is $39 a month. The first 100,000 checks a month run at full speed, then they run slower, and you are never cut off. For a newsletter or small business list that covers a full export plus every new import. You can run 100 free checks on a slice of your own MailerLite export first, no card, and see how many addresses would have bounced. Full details are on the pricing page.

Bottom line

MailerLite removes hard-bounced subscribers and treats three soft bounces in a row as a hard bounce. That protects future sends but not the one in front of you. Export, verify, group the results and send to the clean group. Try the 100 free checks on your own list before the next campaign.