{"id":"6afcda6c6109a073ab264a30","title":"2026 11 17 Issue 407","path":"how-to/committee/release-notes/2026-11-17-issue-407","contentMarkdown":"# 17-Nov-2026 — stop mail apps reloading mailboxes in a loop and show conversations that come back to a [#407](https://github.com/Ramblers-GB/ngx-ramblers/issues/407)\n\n## [build 1099](https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/44192316959) — [commit 165818e](https://github.com/Ramblers-GB/ngx-ramblers/commit/165818efc975138c227e70bc7d97976de34bf94b)\n\n_____\n\n- A conversation that leaves a folder and comes back, for example moved to Deleted or a custom folder on the website and then returned to Inbox, now appears again in Apple Mail, Outlook and Thunderbird. Before, it stayed on the website but never came back in the mail app.\n- A message deleted in a mail app stays hidden in that folder while its conversation stays there, as before. If the whole conversation is later restored on the website, it appears again.\n- While a mail app has a folder open, NGX no longer reloads that folder every few seconds. Database traffic from connected mail apps now depends on what changes, not on how many apps are connected.\n- Live privilege changes (View As, admin rights, revoked access) still reach open browser sessions immediately, with far fewer background database checks while nothing is changing.\n\n- UID memberships now distinguish a message deleted in a mail app (`active: false, expunged: true`, set by `expungeImapMessage`) from one retired because its conversation moved (`active: false`). `synchroniseThread` only keeps expunged messages out while the conversation is still in that mailbox, and clears the flag once it leaves, so a return gets a fresh UID.\n- `loadMailboxMessages` no longer treats expunged messages as unsynced, and its catch-up sync passes `bumpUnchangedMailboxes: false`, so a sync that changes nothing does not bump the mailbox revision. Before, listed messages with only an inactive membership were re-synchronised on every load, each sync bumped the revision, the snapshot was discarded and the next IDLE refresh reloaded again. Website changes through the model hooks still bump the revision, so read state and folder moves reach mail apps as before.\n- Existing inactive memberships without the flag are treated as retired, so conversations already affected get a fresh UID on the next load.\n- `MAX_MAILBOX_SNAPSHOTS` in `mail-client-imap-mailbox.ts` raised from 8 to 256 so one site's mailboxes do not evict each other.\n- The `members` change stream in `member-session-watcher.ts` now waits up to `MEMBER_SESSION_STREAM_MAX_AWAIT_MS` (20 seconds, below the 30 second socket timeout) per `getMore` instead of the 1 second default; events are still returned as soon as they occur.\n- Database tests (`MAIL_CLIENT_UID_TEST_MONGODB_URI`) updated for shared-folder mailbox keys, with new cases for deletion in a mail app, restoration, retired identifiers and read-state revision bumps.","contentHtml":"<h1>17-Nov-2026 — stop mail apps reloading mailboxes in a loop and show conversations that come back to a <a href=\"https://github.com/Ramblers-GB/ngx-ramblers/issues/407\">#407</a></h1>\n<h2><a href=\"https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/44192316959\">build 1099</a> — <a href=\"https://github.com/Ramblers-GB/ngx-ramblers/commit/165818efc975138c227e70bc7d97976de34bf94b\">commit 165818e</a></h2>\n<hr>\n<ul>\n<li><p>A conversation that leaves a folder and comes back, for example moved to Deleted or a custom folder on the website and then returned to Inbox, now appears again in Apple Mail, Outlook and Thunderbird. Before, it stayed on the website but never came back in the mail app.</p>\n</li>\n<li><p>A message deleted in a mail app stays hidden in that folder while its conversation stays there, as before. If the whole conversation is later restored on the website, it appears again.</p>\n</li>\n<li><p>While a mail app has a folder open, NGX no longer reloads that folder every few seconds. Database traffic from connected mail apps now depends on what changes, not on how many apps are connected.</p>\n</li>\n<li><p>Live privilege changes (View As, admin rights, revoked access) still reach open browser sessions immediately, with far fewer background database checks while nothing is changing.</p>\n</li>\n<li><p>UID memberships now distinguish a message deleted in a mail app (<code>active: false, expunged: true</code>, set by <code>expungeImapMessage</code>) from one retired because its conversation moved (<code>active: false</code>). <code>synchroniseThread</code> only keeps expunged messages out while the conversation is still in that mailbox, and clears the flag once it leaves, so a return gets a fresh UID.</p>\n</li>\n<li><p><code>loadMailboxMessages</code> no longer treats expunged messages as unsynced, and its catch-up sync passes <code>bumpUnchangedMailboxes: false</code>, so a sync that changes nothing does not bump the mailbox revision. Before, listed messages with only an inactive membership were re-synchronised on every load, each sync bumped the revision, the snapshot was discarded and the next IDLE refresh reloaded again. Website changes through the model hooks still bump the revision, so read state and folder moves reach mail apps as before.</p>\n</li>\n<li><p>Existing inactive memberships without the flag are treated as retired, so conversations already affected get a fresh UID on the next load.</p>\n</li>\n<li><p><code>MAX_MAILBOX_SNAPSHOTS</code> in <code>mail-client-imap-mailbox.ts</code> raised from 8 to 256 so one site&#39;s mailboxes do not evict each other.</p>\n</li>\n<li><p>The <code>members</code> change stream in <code>member-session-watcher.ts</code> now waits up to <code>MEMBER_SESSION_STREAM_MAX_AWAIT_MS</code> (20 seconds, below the 30 second socket timeout) per <code>getMore</code> instead of the 1 second default; events are still returned as soon as they occur.</p>\n</li>\n<li><p>Database tests (<code>MAIL_CLIENT_UID_TEST_MONGODB_URI</code>) updated for shared-folder mailbox keys, with new cases for deletion in a mail app, restoration, retired identifiers and read-state revision bumps.</p>\n</li>\n</ul>\n"}