Move Dapier email receiving and sending to Relay

オープン
  • 何か問題がありますか？
#25 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
aws, python
領域
api, backend, cloud, devops, security

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Python
スター
0
フォーク
0
平均マージ
6分
マージ済み PR（30日）
10

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

DataTalksClub/dapier のほかの issue

DataTalksClub/dapier の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。