{"id":"6a8b3187236e0222b447f3e8","title":"2026 08 23","path":"how-to/committee/release-notes/2026-08-23","contentMarkdown":"# 23-Aug-2026 — detect inbox threads no mailbox can view and let an admin remap them [ref #363](https://github.com/nbarrett/ngx-ramblers/issues/363)\n\n## [build 847](https://github.com/nbarrett/ngx-ramblers/actions/runs/32655164885) — [commit 68c0405](https://github.com/nbarrett/ngx-ramblers/commit/68c0405e2c2167955f8dc0c9854575dc271a29b3)\n\n_____\n\nInbox thread visibility is data-driven from the committee config, so renaming or\nremoving a role - or an own-sent reclassify tagging a thread with a non-mailbox role -\ncould leave threads whose roleType matches no configured mailbox. Those threads became\nviewable by nobody, with no way to reach them, though nothing was ever deleted.\n\n- Detect orphaned threads (a roleType that is not a configured mailbox) and, for each,\npropose a target from the mailbox its inbound message was addressed to.\n- An admin-only inbox panel groups them by former mailbox with a message count, a target\nselector and a Remap action, plus a separate line to restore threads that have no folder.\n- Remap and restore are admin decisions with visible confirmation - nothing auto-heals.\n- Guard the own-sent reclassify so it never assigns a roleType that is not a configured\nmailbox, preventing new orphans.\n- Warn from Committee Settings on save when a role change orphans inbox threads.","contentHtml":"

23-Aug-2026 — detect inbox threads no mailbox can view and let an admin remap them ref #363

\n

build 847 — commit 68c0405

\n
\n

Inbox thread visibility is data-driven from the committee config, so renaming or\nremoving a role - or an own-sent reclassify tagging a thread with a non-mailbox role -\ncould leave threads whose roleType matches no configured mailbox. Those threads became\nviewable by nobody, with no way to reach them, though nothing was ever deleted.

\n\n"}