sending replies

[tttp]

once we have

• received the message REST API input channel #2 or Stalwart WEBHOOK #3
• identified the campaign what is the good model on CF to use for embedding? #1
• stored the message storing messages #4
• have the politician that has prepared a reply store reply models? #6

We can send the replies to each supporter

• we need to store when we sent it and what we sent storing messages #4
• and handle the potential automated replies handling bounces/spams/unsubscribes #8

We have the same potential problems we have on proca: should we send directly using our mail server that receives the message, use an external provider (AWS SES, Mailjet...), have a mix, failovers...

it might be the best to already think about sharing some of the infrastructure/logic, and that circular democracy "sends" messages by pushing a message on the same queue infrastructure (rabbitmq) using the same format

@1v4n4 can you specify the format used on proca for the action confirm, thank you or doi?

let's see if it makes sense, but I'd love to mutualise between the two projects

[1v4n4]

@1v4n4 can you specify the format used on proca for the action confirm, thank you or doi?

The whole concept of confirming, or you meant something else?

[tttp]

the way we create organisations and add templates (defined in mjml) and how that's used and the various rabbitmq queues involved

[tttp]

@debiB can you have a look at this one and assign to yourself?

[debiB]

okay

[debiB]

Phase 1: Integration Bridge

Goal: Connect message processing to reply template lookup

Phase 2: Sending Infrastructure

Goal: Build reply sending system

Implementation Steps:
Create src/reply_sender.ts with JMAP integration
Implement office hours scheduling (8-19 CEST)
Add background worker for scheduled replies
Create reply status tracking

Phase 3: Robustness

Goal: Handle edge cases and failures

Implementation Steps:

Bounce handling and retry logic
Template update handling
Error notification system

Questions

1. JMAP Provider Details
   Which JMAP provider will be used for sending replies? Need:

API endpoint URL
Authentication method (OAuth, API Key, etc.)
Rate limits and quotas
Webhook endpoints for delivery status

2. Reply Triggering Logic
   Should every processed message automatically trigger reply template lookup, or should there be filtering criteria? (e.g., skip duplicates, low confidence classifications, certain message types)

3. Background Processing Architecture
   For scheduled replies (office hours), should we use:

Cloudflare Workers cron jobs
External cron service
Database-driven polling

4. Email Identity Configuration
   What email addresses should be used for:

Sender address (technical campaign email?)
Reply-to address (politician's personal email?)
Domain authentication setup (SPF/DKIM records)

5. Failure Handling Policy
   When reply sending fails, should the system:

Retry automatically (how many times?)
Flag for manual review
Try alternative sending methods

6. Message Lifecycle Management
   After a reply is sent, when should the original message content be deleted from Stalwart? (immediately, after X days, or manual deletion)

7. Cross-Campaign Coordination
   If a sender messages multiple politicians in the same campaign, should they receive:

The same reply from each politician
Coordinated different replies
Only one reply total

@tttp can you take a look at this plan ?