Move Dapier email receiving and sending to Relay

Open
  • Is something wrong?
#25 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
aws, python
Domain
api, backend, cloud, devops, security

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
0
Forks
0
Avg merge
6m
Merged PRs (30d)
31

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DataTalksClub/dapier

All issues in DataTalksClub/dapier

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.