[{"data":1,"prerenderedAt":87},["ShallowReactive",2],{"blog-post-en-spam-traps":3},{"post":4,"related":69,"locales":85},{"id":5,"title":6,"author":7,"body":8,"date":54,"description":55,"draft":56,"extension":57,"image":58,"meta":59,"navigation":60,"path":61,"readingMinutes":62,"seo":63,"stem":64,"tags":65,"updated":67,"__hash__":68},"blog_en\u002Fblog\u002Fspam-traps.md","A working address can still be a spam trap","MailOK",{"type":9,"value":10,"toc":49},"minimark",[11,15,26,29,34,37,40,43,46],[12,13,14],"p",{},"A spam trap is an address used to observe unwanted email. It can accept a message successfully, which is why a positive verification result doesn't rule it out.",[12,16,17,18,25],{},"Trap addresses can be created for that purpose, arise from common typing mistakes, or use mailboxes that were abandoned and later repurposed. ",[19,20,24],"a",{"href":21,"rel":22},"https:\u002F\u002Fwww.spamhaus.org\u002Fresource-hub\u002Fdeliverability\u002Fspamtraps-fix-the-problem-not-the-symptom\u002F",[23],"nofollow","Spamhaus explains these categories"," and the collection problems they expose.",[12,27,28],{},"An SMTP response doesn't announce that an address is a trap. Treat promises to remove every trap with caution.",[30,31,33],"h2",{"id":32},"work-on-how-addresses-enter-and-stay-on-the-list","Work on how addresses enter and stay on the list",[12,35,36],{},"Use a confirmation step for subscriptions. A form alone can receive mistyped addresses, bot submissions or someone else's email. A confirmation step reduces those risks; it isn't an absolute guarantee.",[12,38,39],{},"Carry forward unsubscribes and delivery suppressions. Review inactive contacts using more than open tracking. Don't assume a purchased or unexplained list becomes suitable for mailing after verification.",[12,41,42],{},"These habits matter more than trying to identify one secret address.",[12,44,45],{},"If a provider or blocklist operator reports a trap problem, pause the affected campaign and investigate the source of those contacts. Follow the operator's guidance. Removing a suspected row and immediately restarting leaves the collection problem in place.",[12,47,48],{},"Verification can find some bad addresses. Keep using it for that job, without treating the result as a certificate that the list is safe to send to.",{"title":50,"searchDepth":51,"depth":51,"links":52},"",2,[53],{"id":32,"depth":51,"text":33},"2025-08-26","Why verification cannot certify a list as trap-free, and what to change when trap problems appear.",false,"md","\u002Fog\u002Fblog\u002Fen\u002Fspam-traps.png",{},true,"\u002Fblog\u002Fspam-traps",1,{"title":6,"description":55},"blog\u002Fspam-traps",[66],"Deliverability",null,"t0koY54uL6O2eoQW3iyTAv1r17D5GS2hY3gCu6oF1b0",[70,78],{"path":71,"title":72,"description":73,"date":74,"tags":75,"readingMinutes":62},"\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",[76,77],"Guides","List hygiene",{"path":79,"title":80,"description":81,"date":82,"tags":83,"readingMinutes":62},"\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",[84,76],"API",[86],"en",1790300927023]