[{"data":1,"prerenderedAt":120},["ShallowReactive",2],{"blog-post-en-email-bounce-rate":3},{"post":4,"related":102,"locales":118},{"id":5,"title":6,"author":7,"body":8,"date":86,"description":87,"draft":88,"extension":89,"image":90,"meta":91,"navigation":92,"path":93,"readingMinutes":94,"seo":95,"stem":96,"tags":97,"updated":100,"__hash__":101},"blog_en\u002Fblog\u002Femail-bounce-rate.md","Read the bounce reason before you clean the list","MailOK",{"type":9,"value":10,"toc":82},"minimark",[11,15,18,70,73,76,79],[12,13,14],"p",{},"A high bounce rate tells you messages failed. It doesn't tell you why.",[12,16,17],{},"Before deleting contacts or buying another verification run, export the failure reasons from your sending platform. Read a few actual responses, especially from the domains where failures increased.",[19,20,21,34],"table",{},[22,23,24],"thead",{},[25,26,27,31],"tr",{},[28,29,30],"th",{},"What the response indicates",[28,32,33],{},"What to do",[35,36,37,46,54,62],"tbody",{},[25,38,39,43],{},[40,41,42],"td",{},"Mailbox does not exist",[40,44,45],{},"Suppress the address from future sends.",[25,47,48,51],{},[40,49,50],{},"Temporary server problem or rate limit",[40,52,53],{},"Let the platform retry according to its policy; investigate if it persists.",[25,55,56,59],{},[40,57,58],{},"Authentication failure or sender policy block",[40,60,61],{},"Fix the sending setup or reputation problem. The recipient may be perfectly valid.",[25,63,64,67],{},[40,65,66],{},"Mailbox full",[40,68,69],{},"Follow your platform's handling and watch for repeated failures.",[12,71,72],{},"Platforms group failures into “hard” and “soft” bounces, but their categories can differ. Even a permanent SMTP rejection doesn't always mean the mailbox is nonexistent. The response text and any enhanced status code matter.",[12,74,75],{},"There's no bounce percentage that makes every campaign safe. Compare like with like: the same platform, the same kind of send, and the same definition of a bounce. Check your provider's rules too.",[12,77,78],{},"Verification is useful when the problem is bad recipient data. If a new import contains misspellings and closed accounts, checking the unsent portion can prevent more failures. If every rejection mentions authentication, cleaning addresses won't fix it.",[12,80,81],{},"Keep suppression records in the system that sends your email. Otherwise the next import may bring those addresses straight back.",{"title":83,"searchDepth":84,"depth":84,"links":85},"",2,[],"2024-12-17","A bad address, a temporary delay and a policy block need different fixes.",false,"md","\u002Fog\u002Fblog\u002Fen\u002Femail-bounce-rate.png",{},true,"\u002Fblog\u002Femail-bounce-rate",1,{"title":6,"description":87},"blog\u002Femail-bounce-rate",[98,99],"Deliverability","Bounces","2025-06-25","0m3r2qjoCBRZ1D-XcDHemejcVc-CrZv_NmyBIPHBamk",[103,111],{"path":104,"title":105,"description":106,"date":107,"tags":108,"readingMinutes":94},"\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",[109,110],"Guides","List hygiene",{"path":112,"title":113,"description":114,"date":115,"tags":116,"readingMinutes":94},"\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",[117,109],"API",[119],"en",1790300928566]