[VS-NfD] Add retention for mail_outbox
#234
Labels
No Label
area:auth
area:docs
area:export
area:ops
area:storage
area:supply-chain
auth
backend
blocked
collab
deployment
docs
effort:L
effort:M
effort:S
frontend
plugins
qa
vs-nfd
vs-nfd:blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: stwaidele/dorfteich#234
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plan reference: n/a —
10-ist-aufnahme.md-> I-23ADR: n/a
Effort: S (1 AT)
Depends on: —
Context
Sent mails are kept forever, and digest mails contain page titles plus who
edited them. For a classified page the title alone can be protected
information, so this is an unbounded copy of content-adjacent data.
Current state
MailOutboxstorestext_bodyandhtml_bodypermanently(
apps/api/prisma/schema.prisma:683–697); no pruning job is registered.apps/api/src/notifications/digest.service.ts:16,125,146(
- ${page.pageTitle}: … (${actorNames})).(
apps/api/src/mail/mail-templates.ts:25–44).Acceptance criteria
period with a documented default; the retry logic for pending
entries is unaffected.
failed-and-retryable entry kept.
docs/architecture/security.md(privacy section) and #229 name theperiod.
pages is decided and recorded — either suppressed or accepted in
#231.
Out of scope
Changing the mail templates' content beyond that decision, and mail
delivery logging.
Implemented in PR #255 (commit
69d9072, CI run 511 green, fast-forward merged on Stefan's standing go-ahead for the M24 merges).Evidence against the acceptance criteria:
Full api suite green (473) on a fresh DB. CD verification follows.