@bobfrankston/rmfmail 1.1.217 → 1.1.219

package/packages/mailx-imap/index.ts

@@ -1307,12 +1307,36 @@ export class ImapManager extends EventEmitter {
                 const qr = await (client as any).resyncFolder(folder.path, prevUidValidity, prevModSeq);
                 console.log(`  [qresync] ${accountId}/${folder.path}: vanished=${qr.vanishedUids.length} changed=${qr.changedMessages.length} newModSeq=${qr.newHighestModSeq} in ${Date.now() - __qrT0}ms`);
 
+                // No real folder vanishes this many UIDs in one QRESYNC cycle.
+                // iflow-direct can mis-expand a VANISHED *range* (e.g. the
+                // server reports "VANISHED 1:4828883" when our modseq watermark
+                // is stale) into millions of individual UIDs. Applying that
+                // literally = 4.8M synchronous DB calls that wedge the whole
+                // event loop (frozen window) AND delete every local row caught
+                // in the range (INBOX wiped → the viewer's open message
+                // vanishes / shows a stale unrelated eml). Bob 2026-06-04.
+                const VANISHED_ABSURD_CAP = 50000;
                 if (qr.uidValidityChanged) {
                     // UIDVALIDITY rolled — our local UIDs are stale. Fall through
                     // to the full set-diff path; that'll discover the new state
                     // and the deletion safeguards (50% threshold) will keep us
                     // from wiping anything we shouldn't.
                     console.log(`  [qresync] ${accountId}/${folder.path}: UIDVALIDITY changed (was ${prevUidValidity}, now ${qr.exists}); falling back to full sync`);
+                } else if (qr.vanishedUids.length > VANISHED_ABSURD_CAP) {
+                    // Refuse the absurd VANISHED set; do NOT iterate/apply it.
+                    const localCount = this.db.getMessageCount(accountId, folderId);
+                    console.error(`  [qresync] ${accountId}/${folder.path}: REFUSING VANISHED of ${qr.vanishedUids.length} UIDs (folder has ${localCount} locally) — mis-parsed range; self-healing (advance watermark) + falling back to set-diff.`);
+                    // SELF-HEAL: advance the modseq watermark to the server's
+                    // CURRENT value. Without this the next QRESYNC re-requests the
+                    // same giant `(EARLIER) 1:N` range every cycle forever (Bob saw
+                    // it recur 21:03 → 21:20) — refusing without advancing isn't
+                    // self-healing. The set-diff reconcile below discovers + applies
+                    // the ACTUAL deletions via Message-ID identity (bounded, 50%
+                    // guard), so skipping the literal VANISHED loses nothing; it
+                    // just breaks the stale-modseq loop so future QRESYNCs are clean.
+                    if (qr.newHighestModSeq !== undefined) {
+                        this.db.updateFolderSync(folderId, prevUidValidity, String(qr.newHighestModSeq));
+                    }
                 } else {
                     // Apply VANISHED — server says these UIDs are gone. No
                     // tombstone, no diff, just delete the local rows.

package/packages/mailx-imap/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@bobfrankston/mailx-imap",
-  "version": "0.1.82",
+  "version": "0.1.84",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@bobfrankston/mailx-imap",
-      "version": "0.1.82",
+      "version": "0.1.84",
       "license": "ISC",
       "dependencies": {
         "@bobfrankston/iflow-direct": "^0.1.27",

package/packages/mailx-imap/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bobfrankston/mailx-imap",
-  "version": "0.1.82",
+  "version": "0.1.84",
   "type": "module",
   "main": "index.js",
   "types": "index.d.ts",

package/packages/mailx-store/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bobfrankston/mailx-store",
-  "version": "0.1.44",
+  "version": "0.1.45",
   "type": "module",
   "main": "index.js",
   "types": "index.d.ts",