placeholder/generic thank you email?

[tttp]

for all the emails we didn't manage to classify, send them a "please hold the line while we process your message"?

just a receipt acknowledgement, or (post MVP) offer the supporter the option to select if their message concerns one of the active campaign?

[1v4n4]

If we classify, should we tell them that we processed the message? It may never be answered, should we report about the stage message is at?

[tttp]

I assume that they will process them in one point. I personally don't like when I receive an acknowledgement "yeah, I received it", unless it has as specific information like a deadline "it will be processed in 48 hours max"

otherwise, if it's just to tell that email works, yeah, let's skip that one IMO (unless we use it as a sneaky way to validate that the sender's email is valid?) post mvp IMO

[debiB]

1. Create Email Service Interface:

• Define a EmailService interface in src/services/email.ts to decouple the logic from the provider.
• Why: Allows switching between providers (Stalwart API, Resend, etc.) without changing core logic.

2. Implement Provider:

• Implement the chosen provider (e.g., StalwartHttpEmailService or ResendEmailService ) using fetch (compatible with Cloudflare Workers).
• Add necessary environment variables (e.g., EMAIL_API_KEY , EMAIL_API_URL ) to Env .

3. Update processEmailForRecipient in stalwart.ts :

• Identify "Unclassified" messages
• Async Execution: Use context.waitUntil() to send the email asynchronously. This ensures we return the routing response to the MTA immediately without waiting for the outgoing email to send.

4. Loop Prevention:

• Implement a helper isAutoReply(headers) to check for:
  • Auto-Submitted: *
  • X-Auto-Response-Suppress: *
  • Precedence: bulk/list/junk

Questions

1. Sending Mechanism (Critical): Since the backend runs on Cloudflare Workers, we cannot use standard SMTP (port 25/587) easily.

• Option A: Do we have a transactional email API provider (e.g., Resend, SendGrid, MailChannels)?
• Option B: Does our Stalwart instance have an HTTP API enabled for sending emails that we can call securely?
• Option C: Should we configure this on the Mail Server level (Sieve scripts) instead of the application logic? (Harder to customize logic later).

2. Sender Identity:

• From which address should the acknowledgement be sent? (e.g., no-reply@circulardemocracy.org , support@... , or the politician's address?)
• Do we have the credentials/tokens ready for this sender?

3. Content & Copy:

• What is the exact subject line and body text for the "please hold" email?
• Should it be plain text only or simple HTML?

4. Trigger Logic:

• The current "low confidence" threshold is 0.3 . Should we send this email for all messages below this score, or a different threshold?
• Should we send it immediately upon receipt, or should there be a delay (to allow for potential manual classification first)?

5. Loop Prevention:

• To avoid infinite auto-reply loops with other bots, we will standardly ignore emails with headers like Auto-Submitted: auto-generated . Are there any other specific exclusion rules?