Headless email communication and evidence service.
Find a file
2026-06-02 01:19:09 +02:00
config feat: start mailbox evidence scanner 2026-06-02 01:19:09 +02:00
docs feat: start mailbox evidence scanner 2026-06-02 01:19:09 +02:00
reports feat: start mailbox evidence scanner 2026-06-02 01:19:09 +02:00
spec Seeded repo with intent and PRD 2026-06-01 23:56:07 +02:00
src/email_connect feat: start mailbox evidence scanner 2026-06-02 01:19:09 +02:00
tests feat: start mailbox evidence scanner 2026-06-02 01:19:09 +02:00
workplans feat: start mailbox evidence scanner 2026-06-02 01:19:09 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-06-02 00:46:07 +02:00
.gitignore feat: start mailbox evidence scanner 2026-06-02 01:19:09 +02:00
AGENTS.md chore: register with state hub 2026-06-02 00:36:01 +02:00
CLAUDE.md chore: register with state hub 2026-06-02 00:36:01 +02:00
INTENT.md Seeded repo with intent and PRD 2026-06-01 23:56:07 +02:00
LICENSE Initial commit 2026-06-01 21:37:38 +00:00
pyproject.toml feat: start mailbox evidence scanner 2026-06-02 01:19:09 +02:00
README.md feat: start mailbox evidence scanner 2026-06-02 01:19:09 +02:00
SCOPE.md chore: register with state hub 2026-06-02 00:36:01 +02:00

email-connect

Headless, provider-neutral email communication and evidence service.

The first implementation slice is the Mailbox Evidence Scanner MVP: scan a return mailbox or fixture directory, classify inbound email-channel evidence, store scan state locally, and generate timestamped CSV reports without overclaiming delivery, awareness, or coordination success.

Quickstart

PYTHONPATH=src python3 -m unittest discover -s tests
PYTHONPATH=src python3 -m email_connect.cli adapter-descriptor
PYTHONPATH=src python3 -m email_connect.cli scan-mailbox --config config/mailbox.example.yml --out reports/

The example config uses tests/fixtures/mailbox as a mailbox source. Runtime state is written to .email-connect/state.sqlite; generated CSV reports are written to reports/.

Current Scope

  • Coordination-engine spec review and references.
  • Initial adapter descriptor, capability profile, evidence ceiling, and limitations.
  • Conservative mailbox message parser and evidence mapper.
  • SQLite state store with message and evidence deduplication.
  • CSV report generation.
  • Golden fixture tests for hard bounce, soft bounce, out-of-office, and human reply signals.

IMAP access, provider webhooks, outbound sending, suppression workflows, and a UI are planned work, not complete in this first slice.