email-best-practices

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Email 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 issuesDeliverability
Build password reset, OTP, confirmationsTransactional Emails
Plan which emails your app needsTransactional Email Catalog
Build newsletter signup, validate emailsEmail Capture
Send newsletters, promotionsMarketing Emails
Ensure CAN-SPAM/GDPR/CASL complianceCompliance
Decide transactional vs marketingEmail Types
Handle retries, idempotency, errorsSending Reliability
Process delivery events, set up webhooksWebhooks & Events
Manage bounces, complaints, suppressionList Management
需要...查看
配置SPF/DKIM/DMARC、解决垃圾邮箱问题可送达性
构建密码重置、一次性验证码(OTP)、确认邮件事务性邮件
规划应用所需的邮件类型事务性邮件目录
构建新闻通讯注册、验证邮箱邮件捕获
发送新闻通讯、推广邮件营销邮件
确保符合CAN-SPAM/GDPR/CASL合规要求合规性
区分事务性邮件与营销邮件邮件类型
处理重试、幂等性、错误发送可靠性
处理送达事件、配置WebhookWebhook与事件
管理退信、投诉、抑制列表列表管理

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).
新应用? 先从事务性邮件目录开始,规划应用所需的邮件类型(如密码重置、验证邮件等),然后在发送第一封邮件前配置可送达性(DNS认证)。
邮件进入垃圾邮箱? 首先查看可送达性——认证问题是最常见的原因。Gmail/Yahoo会拒收未认证的邮件。
营销邮件? 遵循以下流程:邮件捕获(收集用户同意)→ 合规性(法律要求)→ 营销邮件(最佳实践)。
生产环境就绪的发送服务? 提升可靠性:发送可靠性(重试 + 幂等性)→ Webhook与事件(跟踪送达状态)→ 列表管理(处理退信)。