{"id":"6a76fe43cb5169fafe5c0e48","title":"2026 08 08 Issue 307","path":"how-to/committee/release-notes/2026-08-08-issue-307","contentMarkdown":"# 08-Aug-2026 — put website enquiries in the site inbox under Contact Us ([ref #307](https://github.com/nbarrett/ngx-ramblers/issues/307), [#338](https://github.com/nbarrett/ngx-ramblers/issues/338))\n\n## [build 816](https://github.com/nbarrett/ngx-ramblers/actions/runs/31251447156) — [commit 996e15c](https://github.com/nbarrett/ngx-ramblers/commit/996e15c9a12c6eacce2c5b054f88fdcd4a58755b)\n\n_____\n\n## What's new\n\nWebsite Contact Us forms on directed-to-inbox sites now write straight into the Email inbox under the Contact Us role, instead of only sending mail that can fall through Cloudflare to the safety-net Gmail. Contact Us is a valid catch-all role in the page builder, and inbox From/To lines show the visitor and the role the same way at the top of the conversation and on the message.\n\n## At a glance\n\n- General \"Contact us\" buttons can target the Contact Us role without a form error\n- Submissions appear under `contact-us@…` in the Email inbox on directed-to-inbox sites\n- Inbox conversation and message headers use the same From (visitor) and To (role) wording\n- Branded contact-us layout (banner/logo) is used when filing into the inbox, without a Contact Us sign-off that made the site look like the sender\n- Email branding URLs use the public site address, not localhost","contentHtml":"<h1>08-Aug-2026 — put website enquiries in the site inbox under Contact Us (<a href=\"https://github.com/nbarrett/ngx-ramblers/issues/307\">ref #307</a>, <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/338\">#338</a>)</h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/31251447156\">build 816</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/996e15c9a12c6eacce2c5b054f88fdcd4a58755b\">commit 996e15c</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<p>Website Contact Us forms on directed-to-inbox sites now write straight into the Email inbox under the Contact Us role, instead of only sending mail that can fall through Cloudflare to the safety-net Gmail. Contact Us is a valid catch-all role in the page builder, and inbox From/To lines show the visitor and the role the same way at the top of the conversation and on the message.</p>\n<h2>At a glance</h2>\n<ul>\n<li>General &quot;Contact us&quot; buttons can target the Contact Us role without a form error</li>\n<li>Submissions appear under <code>contact-us@…</code> in the Email inbox on directed-to-inbox sites</li>\n<li>Inbox conversation and message headers use the same From (visitor) and To (role) wording</li>\n<li>Branded contact-us layout (banner/logo) is used when filing into the inbox, without a Contact Us sign-off that made the site look like the sender</li>\n<li>Email branding URLs use the public site address, not localhost</li>\n</ul>\n"}