Skip to content

Email list checklist before sending: 9 steps to run on every campaign list

· 6 min read · Email validation

Before sending to an email list, run these steps in order: deduplicate, normalize, remove system addresses, review role addresses, verify every address that hasn't been checked recently, decide what to do with risky and catch-all results, apply your bounce, complaint and unsubscribe suppressions, and split the list by engagement so the warmest contacts go first. The order matters. Deduping first means you don't pay to verify the same address twice, and suppressions go last so nothing you've cleaned can quietly re-add someone who asked to leave.

The checklist assumes a CSV or a list export from your email platform. It works the same for a newsletter, a product announcement or a cold outreach sequence, with a note at the end on where cold lists differ.

The checklist at a glance

# Step Removes or changes Cost
1 Deduplicate Exact duplicate rows Free
2 Normalize Whitespace, case, stray brackets Free
3 Fix obvious syntax errors jane@acme,com, missing @ Free
4 Remove system addresses noreply@, mailer-daemon@, bounce@ Free
5 Review role addresses info@, sales@, support@ Free
6 Verify Dead mailboxes, dead domains, disposable addresses Paid per address
7 Decide on risky, catch-all and unknown Nothing yet, you set the rule Free
8 Apply suppressions Bounces, complaints, unsubscribes Free
9 Segment by engagement Sending order and volume Free

1. Deduplicate on a normalized key

Exact duplicates are easy to miss when one row says Jane@Acme.com and another says jane@acme.com . Build a key by trimming whitespace and lowercasing the whole address, then keep one row per key (usually the most recently updated one, so you keep the best name and fields).

Technically the local part (before the @) can be case-sensitive under RFC 5321, but no mainstream provider treats it that way, and two rows that differ only in case are almost always the same person.

Gmail is a special case. It ignores dots in the local part and everything after a +, so j.ane+news@gmail.com and jane@gmail.com reach the same inbox. You can dedupe on that canonical form, but send to the address the person actually gave you. Gmail dots, plus addressing and duplicate accounts has the rules per provider.

2. Normalize what you'll send to

Fix the formatting problems that break sends or skew matching later:

  • Strip surrounding whitespace and angle brackets (<jane@acme.com>).
  • Lowercase the domain part. Mail domains are case-insensitive.
  • Convert international domain names consistently (punycode or Unicode, pick one) so suppression matching works.
  • Split cells that contain two addresses (jane@acme.com; ops@acme.com) into separate rows, or drop them.

3. Fix or drop obvious syntax errors

Look for commas instead of dots, missing @, spaces inside the address and trailing punctuation. A simple pattern check catches these; a verifier will mark them invalid_syntax anyway, but fixing jane@acme,com by hand recovers a contact instead of losing one. Common typos of big providers (gmial.com, hotmal.com) are worth correcting too, and a verification API that returns a "did you mean" suggestion will flag them for you.

4. Remove system addresses

Addresses like noreply@, no-reply@, mailer-daemon@, postmaster@ and bounce@ are never read by a person. They end up on lists through form scrapes, CRM syncs that import email headers, and copy-paste from notification emails. Remove them. There's no case for sending marketing to a mailbox that exists to send.

5. Review role addresses instead of deleting them

info@, sales@, support@, hello@ and admin@ are different. They often reach a real person or a shared inbox, and at small companies info@ may be the owner's main address. They also tend to produce more complaints, because several people see the mail and none of them signed up.

Our recommendation: keep role addresses that opted in themselves (a newsletter signup from hello@smallshop.com is a real subscriber), and drop role addresses on cold or purchased lists. Role-based email addresses goes through the trade-offs.

6. Verify everything that hasn't been checked recently

Verification is the step that catches what formatting can't: domains that no longer exist, domains with no mail server, mailboxes the server says don't exist, and disposable addresses. Lists decay as people change jobs and companies shut down or rebrand, so a list that was clean six months ago isn't clean now.

You don't need to re-verify everything every time. Verify:

  • every address added since your last check,
  • every address that hasn't engaged in your re-engagement window (often 90 to 180 days),
  • the whole list if it hasn't been checked in several months, or if a recent send bounced more than usual.

A verifier returns one of four outcomes. With pingutil's /v1/verify and /v1/verify/batch (up to 50 addresses per call) they are valid, invalid, risky and unknown, each with a reason and a score. If you'd rather not write code, the dashboard takes CSV uploads, and the verification demo shows what a result looks like for a single address.

Remove every invalid. Those are the hard bounces of your next send, and a high hard-bounce rate damages sender reputation faster than almost anything else.

7. Decide what risky, catch-all and unknown mean for this send

This is a policy decision, not a technical one. Write it down before you look at the counts, so you're not tempted to keep everything because the list shrank.

Result What it means Suggested rule
risky / accept_all Catch-all domain; mailbox can't be confirmed Keep if engaged recently, otherwise send separately in a small batch or skip
risky / role_based Mailbox exists but it's a role address Apply your rule from step 5
risky / mailbox_full Server says the mailbox is full Skip this send; often an abandoned inbox
risky / randomized_local_part Looks machine-generated Skip unless the person engaged recently
unknown Server didn't give a definite answer (greylisting, block, timeout) Re-check after an hour or more; keep engaged contacts

Some free webmail providers accept every address during the check. Yahoo is the common example, which is why addresses at yahoo.com often come back accept_all rather than valid. Engagement history is the best tiebreaker there. Our post on catch-all email domains covers why no verifier can resolve these with certainty.

8. Apply suppressions last

Suppression lists override everything above. Remove:

  • Hard bounces from previous sends. A verifier might say valid today (mailboxes do come back), but an address that hard-bounced recently should stay suppressed until you have a reason to trust it.
  • Repeated soft bounces, according to your platform's rule.
  • Spam complaints. Permanently.
  • Unsubscribes, from every list and every tool, not just the platform you're sending from. Google's email sender guidelines require bulk senders to support one-click unsubscribe and honor requests within two days.

Doing this last matters because a re-import or merge earlier in the process can bring back a row you suppressed months ago. Match suppressions on the normalized key from step 1.

9. Segment by engagement and send the warmest first

Mailbox providers watch how recipients react. Sending first to people who opened or clicked recently, and holding back long-unengaged contacts, keeps early complaint and bounce rates low and gives you a chance to stop if something looks wrong.

A simple split:

  1. Engaged in the last 30 days.
  2. Engaged in the last 31 to 90 days.
  3. Engaged 91 to 180 days ago.
  4. No engagement in 180 days, or never: re-engagement campaign only, or leave out.

Watch the first segment's bounce and complaint numbers before you release the next. The guide to cleaning an email list before sending walks through the same flow with tooling for each step.

Where cold outreach lists differ

Cold lists have no engagement history and no opt-in, so steps 5, 7 and 9 tighten: drop role addresses, drop catch-all and unknown results unless you have another signal that the person exists, and send in small daily volumes.

Print the nine steps, tick them off on every send, and the list you hand to your email platform will be the smallest, cleanest version of itself.

Questions people ask

What should I check on an email list before sending a campaign?
Remove duplicates, normalize the addresses, remove system addresses like noreply and mailer-daemon, verify the list, decide what to do with risky and catch-all results, apply your bounce, complaint and unsubscribe suppressions, and send to your most engaged contacts first.
Do I need to verify a list I already sent to last month?
Not every address. Verify the contacts added since the last check, plus anyone who hasn't opened or clicked in a long time. Addresses that bounced last month should already be on your suppression list and never be re-verified back into a send.
Should I remove catch-all email addresses before sending?
Usually not all of them. Catch-all domains accept every address during verification, so the check can't confirm the mailbox. Keep catch-all contacts with recent engagement, and send unengaged ones in a small, separate batch or leave them out.