[{"data":1,"prerenderedAt":75},["ShallowReactive",2],{"blog-post-en-what-we-will-not-build":3},{"post":4,"related":57,"locales":73},{"id":5,"title":6,"author":7,"body":8,"date":42,"description":43,"draft":44,"extension":45,"image":46,"meta":47,"navigation":48,"path":49,"readingMinutes":50,"seo":51,"stem":52,"tags":53,"updated":55,"__hash__":56},"blog_en\u002Fblog\u002Fwhat-we-will-not-build.md","Before you guess someone’s email address","MailOK",{"type":9,"value":10,"toc":38},"minimark",[11,20,29,32,35],[12,13,14,15,19],"p",{},"You know someone's name and employer. The company appears to use ",[16,17,18],"code",{},"first.last@",", so you try the same pattern and run a check. It comes back valid.",[12,21,22,23,28],{},"You have evidence that the server may accept mail for that address. You haven't established that it reaches the person you named. There may be another employee with the same name, an old alias, or a ",[24,25,27],"a",{"href":26},"\u002Fblog\u002Fcatch-all-email-addresses","catch-all configuration"," accepting every guess.",[12,30,31],{},"The uncertainty matters if you're about to send a proposal, an invoice or anything intended for one person. A successful delivery to the wrong inbox is still a mistake.",[12,33,34],{},"For an existing customer, use a known channel to ask for the right contact address. If a company publishes an address for your particular enquiry, follow that route. Don't silently replace a bounced customer address with one inferred from a naming pattern.",[12,36,37],{},"And keep outreach decisions separate from technical checks. An address that can receive mail hasn't thereby requested your message.",{"title":39,"searchDepth":40,"depth":40,"links":41},"",2,[],"2026-02-16","A plausible naming pattern and a positive server response do not establish who will receive your message.",false,"md","\u002Fog\u002Fblog\u002Fen\u002Fwhat-we-will-not-build.png",{},true,"\u002Fblog\u002Fwhat-we-will-not-build",1,{"title":6,"description":43},"blog\u002Fwhat-we-will-not-build",[54],"Verification",null,"C3hn_n-_KakRSxVdv4tDt-D4mXxdUW4gaNtz1elPbRI",[58,66],{"path":59,"title":60,"description":61,"date":62,"tags":63,"readingMinutes":50},"\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",[64,65],"Guides","List hygiene",{"path":67,"title":68,"description":69,"date":70,"tags":71,"readingMinutes":50},"\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",[72,64],"API",[74],"en",1790300926658]