Skip to content

docs(readme): add inbound email section#30

Open
mpge wants to merge 2 commits intofeat/inbound-email-orchestrationfrom
docs/readme-inbound-email
Open

docs(readme): add inbound email section#30
mpge wants to merge 2 commits intofeat/inbound-email-orchestrationfrom
docs/readme-inbound-email

Conversation

@mpge
Copy link
Copy Markdown
Member

@mpge mpge commented Apr 24, 2026

Summary

Adds inbound-email coverage to the top-level README so host maintainers discover the feature without needing to read source.

  • New feature bullet (26th in the list).
  • New config snippet showing escalated.mail.domain + escalated.mail.inbound-secret (symmetric secret for signed Reply-To signing + inbound webhook verification).
  • Short "Inbound email" section describing the unified webhook URL, adapter selection, the Message-ID → signed Reply-To → subject-reference resolution chain, and a link out to the full setup docs.

Stacked PR

Based on `feat/inbound-email-orchestration` (#29) so the README only claims features that exist on this branch. Merge after the orchestration chain lands on main.

Test plan

  • Render README on GitHub after merge; verify anchors and the docs.escalated.dev link work.

mpge added 2 commits April 24, 2026 06:22
Documents the new single-webhook inbound email ingress
(Postmark + Mailgun adapters), the symmetric escalated.mail.inbound-secret
config, and the three-way message resolution chain. Links out
to the full setup docs for provider-specific configuration
and test recipes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant