email-best-practices
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseEmail Best Practices
邮件最佳实践
Guidance for building deliverable, compliant, user-friendly emails.
提供构建可送达、合规、用户友好的邮件的相关指南。
Architecture Overview
架构概览
[User] → [Email Form] → [Validation] → [Double Opt-In]
↓
[Consent Recorded]
↓
[Suppression Check] ←──────────────[Ready to Send]
↓
[Idempotent Send + Retry] ──────→ [Email API]
↓
[Webhook Events]
↓
┌────────┬────────┬─────────────┐
↓ ↓ ↓ ↓
Delivered Bounced Complained Opened/Clicked
↓ ↓
[Suppression List Updated]
↓
[List Hygiene Jobs][User] → [Email Form] → [Validation] → [Double Opt-In]
↓
[Consent Recorded]
↓
[Suppression Check] ←──────────────[Ready to Send]
↓
[Idempotent Send + Retry] ──────→ [Email API]
↓
[Webhook Events]
↓
┌────────┬────────┬─────────────┐
↓ ↓ ↓ ↓
Delivered Bounced Complained Opened/Clicked
↓ ↓
[Suppression List Updated]
↓
[List Hygiene Jobs]Quick Reference
快速参考
| Need to... | See |
|---|---|
| Set up SPF/DKIM/DMARC, fix spam issues | Deliverability |
| Build password reset, OTP, confirmations | Transactional Emails |
| Plan which emails your app needs | Transactional Email Catalog |
| Build newsletter signup, validate emails | Email Capture |
| Send newsletters, promotions | Marketing Emails |
| Ensure CAN-SPAM/GDPR/CASL compliance | Compliance |
| Decide transactional vs marketing | Email Types |
| Handle retries, idempotency, errors | Sending Reliability |
| Process delivery events, set up webhooks | Webhooks & Events |
| Manage bounces, complaints, suppression | List Management |
| 需要... | 参考 |
|---|---|
| 设置SPF/DKIM/DMARC、解决垃圾邮件问题 | Deliverability |
| 构建密码重置、OTP、验证邮件 | Transactional Emails |
| 规划你的应用需要哪些邮件 | Transactional Email Catalog |
| 构建时事通讯注册、邮件验证功能 | Email Capture |
| 发送时事通讯、推广内容 | Marketing Emails |
| 确保符合CAN-SPAM/GDPR/CASL合规要求 | Compliance |
| 区分事务性邮件与营销邮件 | Email Types |
| 处理重试、幂等性、错误问题 | Sending Reliability |
| 处理送达事件、设置webhook | Webhooks & Events |
| 管理退信、投诉、拒收列表 | List Management |
Start Here
入门指南
New app?
Start with the Catalog to plan which emails your app needs (password reset, verification, etc.), then set up Deliverability (DNS authentication) before sending your first email.
Spam issues?
Check Deliverability first—authentication problems are the most common cause. Gmail/Yahoo reject unauthenticated emails.
Marketing emails?
Follow this path: Email Capture (collect consent) → Compliance (legal requirements) → Marketing Emails (best practices).
Production-ready sending?
Add reliability: Sending Reliability (retry + idempotency) → Webhooks & Events (track delivery) → List Management (handle bounces).
新建应用?
先参考Catalog规划你的应用需要哪些邮件(密码重置、身份验证等),然后在发送第一封邮件前完成Deliverability(DNS验证)配置。
遇到垃圾邮件问题?
首先查看Deliverability——验证配置问题是最常见的诱因。Gmail/Yahoo会拒收未通过验证的邮件。
要发送营销邮件?
遵循以下路径:Email Capture(收集用户同意)→ Compliance(满足法律要求)→ Marketing Emails(最佳实践)。
需要生产环境可用的发送能力?
添加可靠性保障:Sending Reliability(重试+幂等性)→ Webhooks & Events(跟踪送达状态)→ List Management(处理退信)。