Sending email crosses an application queue, a mail provider, and a recipient mailbox. A provider accepting a request is not proof that the person read the message. This track follows case-review notices and account links from event creation through template rendering, sender identity, bounce handling, and suppression. It keeps marketing preference separate from security or transactional purpose, while recognizing that every sender must respect provider and recipient rules. Application state should record intent and observed delivery events without copying private case data into transport logs.
Topics in this track
- Email Intent, Outbox, and Idempotent Send — Record one message intent with the business event and handle uncertain provider responses.
- Email Template Data and Account Link Boundaries — Render limited message data and keep action links short-lived, single-purpose, and server-verified.
- Email Provider Events, Bounces, and Suppression — Reconcile accepted, delivered, bounced, and complained-about messages without unsafe repeated sends.
- Sender Identity, Reputation, and Message Observability — Configure authenticated sending domains and measure delivery without exposing message content.
Prerequisite paths
Background Jobs and the Outbox Boundary; Web Push and Notification Delivery.
Neighbor track
File Ingestion and Private Asset Lifecycle.
Practice path
Build Project: account email delivery and check decisions in Web Development: file and email delivery decisions quiz.