Skip to content

docs(readme): add inbound email section#39

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

docs(readme): add inbound email section#39
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 in the Features list.
  • Short "Inbound email" section with the unified webhook URL, the `config :escalated, mail_domain: ..., email_inbound_secret: ..., inbound_parsers: [...]` snippet, the required router scope, and the Message-ID → signed Reply-To → subject-reference resolution chain.
  • Link out to the full setup docs.

Stacked PR

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

mpge added 2 commits April 24, 2026 06:24
Documents the new single-webhook inbound email ingress
(Postmark + Mailgun adapters), the symmetric email_inbound_secret
config, the required router scope, and the three-way message
resolution chain. Links to the full setup docs for
provider-specific configuration.
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