Move Dapier email receiving and sending to Relay

Aperta
  • Qualcosa non va?
#25 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
aws, python
Ambito
api, backend, cloud, devops, security

Direzione di ricerca

Start with src/dapier/connectors/ingress.py, scripts/deploy.sh, and template.yaml, then read Relay's worker-contracts.md. Trace the outbound callers listed in the issue, including email_send, notifications, reports, and backup.py. Done means inbound and outbound workflows, authentication, feedback handling, configuration, tests, and documented rollback all pass end-to-end before Datamailer and direct SES paths are removed.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Goal

Move Dapier's email receiving and sending paths to Relay. Datamailer is the current integration used for the first [email protected] experiment, not the intended long-term service. Keep existing email workflows working throughout the cutover.

Current dependencies

  • Inbound mail arrives via Datamailer's SNS topic and private S3 bucket, configured in scripts/deploy.sh and template.yaml. src/dapier/connectors/ingress.py normalizes the inbound-email event.
  • Dapier currently expects the inbound event to contain inline body and attachments; [email protected] inserts {body.text.value} into its headless-agent prompt. Relay's current contract instead publishes inbound_message_id and a raw_mime reference, with bodies and attachments stored privately.
  • Outbound paths include the email_send action, workflow failure notifications, alarms/error digests, headless-task completion reports, and backup failure mail. Most call SES directly; src/dapier/backup.py calls Datamailer's transactional API.
  • Email sender allow-list, reserved addresses, invoice/todo routes, SES bounce/complaint events, and the Console/CLI management surfaces also need to keep working.

Work

  • Decide the Relay-to-Dapier inbound delivery and authentication contract. Provision Relay receiving addresses and move the SES receipt path, preserving current addresses and routes.
  • Adapt Dapier's inbound normalizer and securely retrieve body text, raw MIME, and attachments from Relay's stored message. Preserve idempotency, replay, retention, and sender filtering. Require trustworthy sender authentication before allowing email to start an unrestricted headless agent.
  • Move applicable outbound mail to Relay's transactional API. Close any gaps needed for attachments, HTML, reply threading, idempotency, delivery status, and SES feedback before switching each caller.
  • Update configuration, IAM, tests, docs, and API/CLI/Console parity. Remove Datamailer-specific configuration and obsolete direct SES paths after their replacements are live.
  • Test real inbound mail through [email protected] (including a Zoom link), invoice/todo flows, completion reports, other notifications, and bounce/complaint handling. Cut over with a rollback path, then verify delivery and queue health.

This is a follow-up issue; the current mail route should remain operational until the Relay path passes the end-to-end checks.

Lingua principale
Python
Stelle
0
Fork
0
Merge medio
6m
PR unite (30g)
10

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DataTalksClub/dapier

Tutte le issue di DataTalksClub/dapier

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.