# 07-Jul-2026 — More reliable direct-to-inbox email routing [ref #307](https://github.com/nbarrett/ngx-ramblers/issues/307)

## [build 752](https://github.com/nbarrett/ngx-ramblers/actions/runs/28854735024) — [commit 3daeaf1](https://github.com/nbarrett/ngx-ramblers/commit/3daeaf14b3981bfe6376bc17003070e6c3897a1f)

_____

## What's new
Cloudflare direct-to-inbox routing now behaves consistently from setup through live delivery. Committee mailbox routing is pushed to site-specific Cloudflare workers, inbound messages are stored under the correct role or general mailbox, replies stay attached to the direct-inbox connection, and shared committee settings refresh across connected admin clients.

## At a glance
- Direct inbox setup routes committee addresses to a site-specific Cloudflare worker.
- Live inbound mail posts to the Fly origin instead of looping back through the public Cloudflare-hosted domain.
- Unmatched catch-all mail lands in the general inbox rather than being silently discarded.
- Committee settings changes propagate to connected clients without requiring a manual reload.
- The direct-delivery setup success alert has clearer spacing in the admin UI.

## Technical changes
- Derive Cloudflare ingress aliases from committee roles and add general mailbox fallback handling.
- Generate per-site inbox router workers with explicit webhook URLs and shared router secrets.
- Accept both shared router and per-site inbound webhook signatures on the inbox endpoint.
- Store outbound reply writebacks against the mailbox connection provider.
- Broadcast config updates over websockets and refresh committee settings consumers.