The SendDart journal
Guides and practical notes on email automation, deliverability, and building reliable delivery into your product.
Page 11 of 14 · 161 articles
Articles — page 11
Email Sending Domain Rollout Checklist: Verify the Whole Path
Roll out a sending domain with ownership checks, controlled DNS changes, representative message tests and a bounded traffic plan.
Transactional Email Queue Architecture: Design Claims, Expiry and Recovery
Build a transactional email queue with durable intent, concurrency-safe claims, immutable payloads and separate recovery paths for uncertain outcomes.
Email Delivery Failure Debugging: Trace the First Broken Boundary
Debug missing transactional email by tracing intent, queue execution, provider submission and delivery events before changing providers or resending.
Email API Testing Without Real Sends: Build Three Layers of Evidence
Test email rendering, provider adapters and event workflows using local fixtures and SendDart simulator addresses before a controlled live canary.
Email API Secrets Management: Rotate Keys Without Losing Control
Design email API credential storage, rotation and incident response across web applications, workers and deployment environments.
Email Complaint Suppression Workflow: Stop, Record and Investigate
Build complaint handling that stops affected sending, preserves event evidence and prevents queued or migrated workflows from re-enabling recipients.
Email Bounce Suppression Workflow: Turn Delivery Evidence Into Safe Decisions
Implement bounce suppression with authenticated events, scoped reasons and controlled recovery instead of deleting contacts or retrying every failure.
Email Provider Rate Limits: Protect the Queue Instead of Flooding Retries
Handle email API rate limits with bounded queues, fair scheduling and clear separation between short-term request limits and account quotas.
Email Delivery Status vs Inbox Placement: Explain What the Evidence Proves
Understand accepted, queued and delivered email states, and investigate missing messages without treating server acceptance as proof of inbox placement.
Transactional Email Observability: Follow Intent, Attempts and Outcomes
Build an email observability model that connects business events, queue delay, provider attempts and delivery evidence without logging private content.
Email API Retry and Backoff: Separate Rejection From Uncertainty
Design email retries with bounded budgets, Retry-After handling, stable operation keys and explicit stops for partial or uncertain sends.
Email API Idempotency Keys: Model the Intended Message
Use email idempotency keys correctly by preserving operation identity, immutable payloads and recovery evidence instead of generating a new key per retry.