email-deliverability

# Email Deliverability Get email into inboxes, not spam folders. Set up authentication. Monitor reputation. Diagnose problems before they hurt the business. --- ## When to use - Setting up email for a new domain - A meaningful percentage of email is going to spam - Customers report they're not receiving emails - Setting up DMARC, SPF, or DKIM - Hardening against domain spoofing - Migrating email service providers - Sender reputation has dropped - Pre-launch audit before sending volume increases ## When NOT to use - Writing the email content itself (use `email-sequences`) - Designing the email program strategy (use `email-sequences`) - DNS records in general (use `domain-strategy`) - Outbound spam coming FROM your account (different problem; investigate compromised credentials) --- ## Required inputs - The sending domain(s) - The email service provider (ESP, transactional service, mail server) - Current DNS records (or access to them) - Email volume (transactional vs marketing, daily volume) - Current deliverability state (if known: bounce rate, spam complaints) --- ## The framework: 3 pillars Email deliverability rests on three pillars. Weakness in any one limits the others. ### Pillar 1: Authentication Mailbox providers verify email is actually from who it claims to be from. Three records. **SPF (Sender Policy Framework)** Lists which servers are authorized to send mail for the domain. Published as a TXT record at the apex. ``` v=spf1 include:_spf.mailprovid...