@bobfrankston/mailx-imap 0.1.82 → 0.1.83

package/index.js

@@ -1272,6 +1272,15 @@ export class ImapManager extends EventEmitter {
                 const __qrT0 = Date.now();
                 const qr = await client.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
@@ -1279,6 +1288,15 @@ export class ImapManager extends EventEmitter {
                     // 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 and
+                    // do NOT return — fall through to the bounded set-diff
+                    // reconcile (same as the UIDVALIDITY-changed path). The
+                    // modseq watermark is left intact, so a healthy later QRESYNC
+                    // can still succeed.
+                    const localCount = this.db.getMessageCount(accountId, folderId);
+                    console.error(`  [qresync] ${accountId}/${folder.path}: REFUSING VANISHED of ${qr.vanishedUids.length} UIDs (folder has ${localCount} locally) — almost certainly a mis-parsed range; falling back to set-diff reconcile instead of mass-deleting/wedging.`);
+                }
                 else {
                     // Apply VANISHED — server says these UIDs are gone. No
                     // tombstone, no diff, just delete the local rows.

package/package.json

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