[{"data":1,"prerenderedAt":108},["ShallowReactive",2],{"blog-post-en-clean-email-list":3},{"post":4,"related":91,"locales":106},{"id":5,"title":6,"author":7,"body":8,"date":76,"description":77,"draft":78,"extension":79,"image":80,"meta":81,"navigation":82,"path":83,"readingMinutes":70,"seo":84,"stem":85,"tags":86,"updated":89,"__hash__":90},"blog_en\u002Fblog\u002Fclean-email-list.md","You inherited a mailing list. Start here.","MailOK",{"type":9,"value":10,"toc":68},"minimark",[11,15,18,23,26,29,33,36,39,43,52,55,59,62,65],[12,13,14],"p",{},"Before uploading an inherited list to a verifier, find the unsubscribe records. A fresh export can look reassuringly clean while quietly including people who asked you to stop emailing them.",[12,16,17],{},"Keep an untouched copy of the export. Then work through it in this order.",[19,20,22],"h2",{"id":21},"find-out-where-it-came-from","Find out where it came from",[12,24,25],{},"Look for signup dates, collection sources and records of what people agreed to receive. A missing source is a reason to investigate. It doesn't prove the list was bought, but it doesn't give you permission to use it, either.",[12,27,28],{},"Set aside contacts whose history you cannot establish. Verification won't fill that gap.",[19,30,32],{"id":31},"apply-exclusions-before-checking-addresses","Apply exclusions before checking addresses",[12,34,35],{},"Exclude unsubscribers, spam complainants and addresses already suppressed for delivery failures. Keep those exclusions in your sending system so a later import cannot reactivate them.",[12,37,38],{},"Remove duplicate entries carefully. Preserve the most restrictive subscription preference when records disagree. Don't strip dots or plus tags from every address; different providers handle them differently.",[19,40,42],{"id":41},"verify-the-remaining-addresses","Verify the remaining addresses",[12,44,45,46,51],{},"Read the reason behind each result before acting. A confirmed nonexistent mailbox belongs on your suppression list. A temporary failure may need a later check. A ",[47,48,50],"a",{"href":49},"\u002Fblog\u002Fcatch-all-email-addresses","catch-all result"," needs context from your own records.",[12,53,54],{},"Keep the check date too. A result from last year tells you what was found last year.",[19,56,58],{"id":57},"update-the-original-system","Update the original system",[12,60,61],{},"Cleaning an export alone is temporary. Record the result in the CRM or sending platform, then check that your next export respects it. Suppressing an address is usually more useful than deleting its entire contact history.",[12,63,64],{},"For a dormant list, start with recent subscribers who still have a reason to expect your mail. Watch delivery failures and complaints before expanding the send. Stop and investigate if they rise.",[12,66,67],{},"You don't need to recover every row. You need a list you can explain and use responsibly.",{"title":69,"searchDepth":70,"depth":70,"links":71},"",2,[72,73,74,75],{"id":21,"depth":70,"text":22},{"id":31,"depth":70,"text":32},{"id":41,"depth":70,"text":42},{"id":57,"depth":70,"text":58},"2025-01-31","Check its source, preserve exclusions, verify the addresses, and put the results back where they will be used.",false,"md","\u002Fog\u002Fblog\u002Fen\u002Fclean-email-list.png",{},true,"\u002Fblog\u002Fclean-email-list",{"title":6,"description":77},"blog\u002Fclean-email-list",[87,88],"List hygiene","Guides","2025-04-02","THbhLCKHZvsoJ3kfjYFy_ehxPfNGp6LO-X-xmsqm4QE",[92,99],{"path":93,"title":94,"description":95,"date":96,"tags":97,"readingMinutes":98},"\u002Fblog\u002Fspreadsheet-in-spreadsheet-out","Keep a contact ID in your verification file","A simple export makes it easier to return each result to the right contact without exposing your whole CRM.","2026-07-29",[88,87],1,{"path":100,"title":101,"description":102,"date":103,"tags":104,"readingMinutes":98},"\u002Fblog\u002Fthe-api-now-belongs-to-your-account","Before you connect an email verification API","Plan for unresolved checks, failed requests and changing addresses before putting verification into production.","2026-06-23",[105,88],"API",[107],"en",1790300928531]