Vorlagen, Einstellungen pro Typ, Abmeldung mit einem Klick, Bounce-Behandlung.
Spec — Email notifications
Status: draft · Created: 2026-11-10
1. Context and goal
The product tells people about events by email in their language, only for the types they want, and stops writing to addresses that do not work.
2. Functional requirements (EARS)
- FR-1: THE SYSTEM SHALL render each notification type from a versioned template with HTML and plain-text parts in the recipient's language, falling back to English.
- FR-2: WHEN an event triggers a notification, THE SYSTEM SHALL queue the email outside the request and hand it to the provider within 60 seconds.
- FR-3: THE SYSTEM SHALL let each person turn every optional notification type on or off, and SHALL always send security and billing emails.
- FR-4: THE SYSTEM SHALL add
List-UnsubscribeandList-Unsubscribe-Postheaders (RFC 8058) and a footer link to every optional email, and stop that type within 1 minute of either being used, without sign-in. - FR-5: WHEN the provider reports a hard bounce or a spam complaint, THE SYSTEM SHALL stop all optional email to the address and ask the person to confirm an address at the next sign-in.
- FR-6: IF an address soft-bounces 5 times in 7 days, THEN THE SYSTEM SHALL treat it as a hard bounce.
- FR-7: IF the provider call fails, THEN THE SYSTEM SHALL retry with backoff for up to 1 hour, sending from a domain with SPF, DKIM and DMARC aligned.
- FR-8: THE SYSTEM SHALL log each email with its type, recipient, provider id and status (queued, sent, delivered, bounced, complained) for 90 days.
3. Out of scope
- Marketing campaigns.
- Daily or weekly digests.