[Feature] Reusable SMTP batch sessions with preflight, reconnect, and pause-on-failure #16

Open
opened 2026-07-14 20:08:43 +02:00 by zemion · 1 comment
Owner

Problem / User Need

Campaign mail sending should improve SMTP reliability and progress behavior by reusing SMTP sessions per campaign batch where possible, reconnecting on connection failure, preflighting DNS/connectivity, and pausing on systemic SMTP failures.

Acceptance Criteria

  • SMTP sending can reuse a session/connection for a campaign batch when server policy allows it.
  • Transient connection failures trigger controlled reconnect behavior.
  • Preflight checks validate DNS/connectivity/auth where possible before the send starts.
  • Systemic SMTP failures pause or block the batch instead of producing many repeated failures.
  • Progress and failure reasons are clear to campaign users.

Notes / Decisions

Campaign send-progress UI should consume the clearer progress/failure states.

## Problem / User Need Campaign mail sending should improve SMTP reliability and progress behavior by reusing SMTP sessions per campaign batch where possible, reconnecting on connection failure, preflighting DNS/connectivity, and pausing on systemic SMTP failures. ## Acceptance Criteria - SMTP sending can reuse a session/connection for a campaign batch when server policy allows it. - Transient connection failures trigger controlled reconnect behavior. - Preflight checks validate DNS/connectivity/auth where possible before the send starts. - Systemic SMTP failures pause or block the batch instead of producing many repeated failures. - Progress and failure reasons are clear to campaign users. ## Notes / Decisions Campaign send-progress UI should consume the clearer progress/failure states.
Author
Owner

Drift note, 2026-07-20: the shared dirty workspace contains an uncommitted process-local rate-limit fallback. Treat it only as WIP for this delivery-safety issue: process-local coordination is not sufficient for multi-worker production, and integration requires an explicit distributed/fail-safe contract plus tests.

Drift note, 2026-07-20: the shared dirty workspace contains an uncommitted process-local rate-limit fallback. Treat it only as WIP for this delivery-safety issue: process-local coordination is not sufficient for multi-worker production, and integration requires an explicit distributed/fail-safe contract plus tests.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-mail#16
No description provided.