[Task] Inject SMTP temporary failure, SMTP permanent failure, connection drop, IMAP append failure, and worker restart/interruption #5

Open
opened 2026-07-06 11:20:47 +02:00 by zemion · 1 comment
Owner

Imported from the consolidated GovOPlaN product backlog.

  • Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/backlog.md
  • Line: 88
  • Section: Milestones > Milestone 3 - Controlled Sending And Send Test
  • Source status: FINISHING.

Imported backlog item:

- [ ] Inject SMTP temporary failure, SMTP permanent failure, connection drop, IMAP append failure, and worker restart/interruption.
<!-- codex-backlog-fingerprint:19abda6dbab739c54f346f37 --> Imported from the consolidated GovOPlaN product backlog. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/backlog.md` - Line: `88` - Section: `Milestones > Milestone 3 - Controlled Sending And Send Test` - Source status: `FINISHING.` Imported backlog item: ```markdown - [ ] Inject SMTP temporary failure, SMTP permanent failure, connection drop, IMAP append failure, and worker restart/interruption. ```
zemion added this to the Milestone 3 - Controlled Sending And Send Test milestone 2026-07-06 13:11:18 +02:00
Author
Owner

Codex State: progress

Summary

  • The Campaign acceptance runner now proves SMTP connection loss before transmission as temporary, SMTP authentication rejection as permanent, and IMAP authentication rejection after SMTP acceptance as an append failure.
  • The success path proves one SMTP acceptance, one IMAP append, one unique provider-side match in each mailbox, and no duplicate provider effect after a repeated ordinary send.

Changed Files

  • dev/mail-testbed/run_campaign_acceptance.py
  • tests/test_mail_testbed_acceptance.py

Verification

  • 197 tests passed; live loopback GreenMail journey and all implemented drills passed

Next / Blocked

  • Explicit SMTP temporary response, partial recipient refusal, post-DATA connection-loss ambiguity, and a real worker restart/interruption remain open.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - The Campaign acceptance runner now proves SMTP connection loss before transmission as temporary, SMTP authentication rejection as permanent, and IMAP authentication rejection after SMTP acceptance as an append failure. - The success path proves one SMTP acceptance, one IMAP append, one unique provider-side match in each mailbox, and no duplicate provider effect after a repeated ordinary send. ### Changed Files - `dev/mail-testbed/run_campaign_acceptance.py` - `tests/test_mail_testbed_acceptance.py` ### Verification - `197 tests passed; live loopback GreenMail journey and all implemented drills passed` ### Next / Blocked - Explicit SMTP temporary response, partial recipient refusal, post-DATA connection-loss ambiguity, and a real worker restart/interruption remain open. Suggested status label: `status/in-progress`
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-campaign#5
No description provided.