{"id":"6a4add9bd6b1dfe81dd34807","title":"2026 07 05 Other","path":"how-to/committee/release-notes/2026-07-05-other","contentMarkdown":"# 05-Jul-2026 — Catch-all email: a clear prompt when a forwarding address needs verifying\n\n## [build 746](https://github.com/nbarrett/ngx-ramblers/actions/runs/28757133999) — [commit e85448c](https://github.com/nbarrett/ngx-ramblers/commit/e85448cdc7592c5e2593c4373bcd3856f7a47843)\n\n_____\n\n## What's new\n\nWhen you forward catch-all email to a single address (for example a connected Gmail inbox), that address has to be verified with Cloudflare first. Before, there was no sign when it was not verified, so saving simply failed, and if the address was already registered but not yet confirmed there was no way to send the verification email again.\n\n- The catch-all editor now shows a clear \"Destination not verified\" warning, with a \"Register & Verify\" or \"Resend verification\" button, whenever the chosen forwarding address has not been verified. It checks the live status each time you open the editor.\n- The button sends a fresh verification email, so the owner of that address gets a new link to confirm it. If you have hit Cloudflare's limit on how often this can be done, the editor tells you.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/2e5c695a-3dad-483a-96af-52918528c871.png)","contentHtml":"

05-Jul-2026 — Catch-all email: a clear prompt when a forwarding address needs verifying

\n

build 746 — commit e85448c

\n
\n

What's new

\n

When you forward catch-all email to a single address (for example a connected Gmail inbox), that address has to be verified with Cloudflare first. Before, there was no sign when it was not verified, so saving simply failed, and if the address was already registered but not yet confirmed there was no way to send the verification email again.

\n\n

\"\"

\n"}