[Feature] Support campaign-owned individualized invitation delivery #6

Open
opened 2026-07-07 13:55:03 +02:00 by zemion · 0 comments
Owner

Goal

Provide the mail-side delivery capability needed for campaign bulk invitation sends.

Scope

  • Accept campaign-owned individualized send requests through a stable capability/API boundary.
  • Preserve message traceability back to campaign recipient/send IDs.
  • Return delivery, failure, and bounce state in a form campaign reporting can consume.
  • Support calendar invitation payloads/attachments once the calendar module provides the invite contract.

Acceptance Criteria

  • Mail can send individualized invitation messages for a campaign without campaign importing mail internals.
  • Delivery status is correlated back to the originating campaign recipient/send record.
  • Failure states are structured enough for campaign reporting and retry decisions.

Core tracking issue: add-ideas/govoplan-core#205

## Goal Provide the mail-side delivery capability needed for campaign bulk invitation sends. ## Scope - Accept campaign-owned individualized send requests through a stable capability/API boundary. - Preserve message traceability back to campaign recipient/send IDs. - Return delivery, failure, and bounce state in a form campaign reporting can consume. - Support calendar invitation payloads/attachments once the calendar module provides the invite contract. ## Acceptance Criteria - Mail can send individualized invitation messages for a campaign without campaign importing mail internals. - Delivery status is correlated back to the originating campaign recipient/send record. - Failure states are structured enough for campaign reporting and retry decisions. Core tracking issue: https://git.add-ideas.de/add-ideas/govoplan-core/issues/205 <!-- codex-fingerprint: bulk-invite-mail-module -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-mail#6
No description provided.