Email Best Practices

**Judgment:** Strong, well-structured best-practices guide for building production-grade email systems that are deliverable, compliant, and operationally robust. Good fit as a default reference when designing or reworking email flows. **Where it’s strongest** - End-to-end view from email capture → consent → sending → events → list hygiene. - Clear architectural patterns: validation, double opt-in, consent recording, suppression checks, idempotent send + retry, and webhook-driven updates. - Practical deliverability focus (SPF/DKIM/DMARC and DNS) aligned with real-world issues like spam and Gmail/Yahoo rejection. - Explicit handling of transactional vs marketing emails, plus a catalog-based approach to planning required messages. - Compliance-aware, covering CAN-SPAM/GDPR/CASL at a conceptual level. **Risks / Limitations** - Regulatory guidance may not capture the latest legal changes or jurisdiction-specific nuances; legal review is still required for strict compliance. - Provider-specific quirks (e.g., exact Gmail/Yahoo bulk requirements, specific ESP APIs) may not be fully covered. - Performance and scaling recommendations are architectural rather than benchmarked; teams with extreme-scale needs will still need load testing and tuning. **Recommended scenarios** - Designing email systems for new products or major rewrites of existing email flows. - Investigating spam or bounce issues and verifying authentication and suppression/list hygiene setups. - Implementing or tightening marketing consent flows and opt-in/opt-out management. - Establishing reliable sending patterns with retries, idempotency, and webhook-driven state updates across user lists.