How to Clean Your MailerLite Email List

MailerLite is a popular platform for small businesses, creators, and newsletter operators: known for its clean interface, generous free plan, and responsive pricing as your list grows.

It is also one of the few email platforms that manually reviews large contact imports. If you import a list that does not meet MailerLite's quality standards, the import can be delayed or rejected. The review process checks for list acquisition method, import size relative to your existing list, and apparent quality signals.

The practical implication: cleaning before you import is not just a deliverability best practice. For MailerLite users importing a large batch, it is part of getting your import approved quickly.

Step 0: what verification covers

MailerLite handles unsubscribes and bounces reactively, the same way most ESPs do. Verification gives you the proactive layer, catching bad addresses before they reach MailerLite's servers.

Surface checks (syntax, MX, disposable detection) catch the obvious problems: broken-format addresses, domains with no mail configuration, throwaway inbox services. This covers maybe 15-20% of the actual problem on a typical imported list.

SMTP mailbox probing catches the rest. MailCull opens a direct connection to the receiving mail server and issues RCPT TO for each specific address. The server's response. 250 (accept), 550 (user unknown), 4xx (temporary deferral), tells you whether the mailbox exists. The 550 responses are hard bounces. You see them before importing.

Microsoft 365 HTTP enumeration matters for any list with business email addresses. M365's EOP layer accepts RCPT TO for all addresses on a tenant, including non-existent ones. An SMTP probe returns 250 OK; delivery hard-bounces. MailCull's HTTP cascade uses Microsoft's own APIs to verify whether the specific account is real. For lists with a mix of consumer and business addresses, this catches a meaningful share of false-positives.

Catch-all detection identifies domains that accept all RCPT TO regardless of mailbox existence. These are flagged as risky since individual address verification is impossible.

Each result includes an evidence chain showing what drove the verdict.

Step 1: export your subscriber list

Export the group you want to clean as a CSV from your current list source. This might be:

• An existing MailerLite subscriber group: for regular maintenance.
• A new import batch from another tool: a migration from ConvertKit, a CRM export, a newsletter platform migration.
• A list from an older source: a spreadsheet, a paper sign-in sheet that was digitalised, an old database.

Keep fields you need for reimport: email, name, tags, custom fields.

Step 2: upload to MailCull

Upload the CSV to Verify List. MailCull handles multi-column files and finds email addresses across all columns.

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

Results group into: 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. Remove before importing into MailerLite. These are confirmed bad addresses. Importing them contributes to your bounce rate from day one and increases the likelihood that MailerLite's import review flags the batch.

Deliverable. Import. These passed the full check stack.

Risky. Judgment call:

• Catch-all: include but monitor. These exist at the domain level even if individual mailbox existence is uncertain.
• Role address - info@, contact@, hello@, technically valid but shared inboxes. Appropriate for some sends; not ideal for personalised newsletters.
• M365 disagreement: be conservative. Exclude from the initial import if you have a large batch pending review.
• Greylisted: usually resolves. Include with monitoring.

For a first import into MailerLite where manual review is possible, removing undeliverable and flagged risky contacts reduces the risk of review delay.

Unknown. Similar treatment to risky. The server was inconclusive.

Step 4: import into MailerLite

Import the cleaned CSV into MailerLite's subscriber list or group. Because you removed obvious bad addresses, the import starts from a higher-quality baseline.

When MailerLite asks about your list acquisition method during import (they often do), "subscribers from [source], verified with SMTP probing before import" is an accurate and honest answer. It demonstrates you took quality seriously.

MailerLite-specific notes

Free plan contacts count. MailerLite's free plan caps subscribers at 1,000. If you are near that cap, removing undeliverable addresses first preserves your free headroom for real subscribers.

Import approval timing. MailerLite can take 24-48 hours to manually review large imports. Uploading a clean, verified list reduces the likelihood of flags during review, which means faster approval and faster time to first send.

Billing by subscriber. MailerLite charges by subscriber count on paid plans. Removing dead addresses from your list directly reduces your platform cost.

Ongoing maintenance

MailerLite grows quiet over time if you do not actively maintain it. Subscribers go stale: they change jobs, abandon inboxes, let domains expire. The platform's engagement filtering helps identify low-engagement contacts, but it fires reactively.

A quarterly verification pass, especially on older segments and any imported batches, keeps the list representative of people who can actually be reached.

---

You came here to import a clean, reliable list into MailerLite and get through import review quickly. MailCull verifies every address at the SMTP level before it touches the platform.

Clean your MailerLite import with MailCull, free with 500 validation credits/month →