@bobfrankston/mailx-imap 0.1.72 → 0.1.74

package/index.d.ts

@@ -398,6 +398,13 @@ export declare class ImapManager extends EventEmitter {
     private prefetchFailures;
     private markPrefetchEmpty;
     private isPrefetchEmpty;
+    /** Clear a UID's prefetch-failure record after a successful fetch, so a
+     *  message that healed (e.g. a transient iflow protocol desync that
+     *  resolved on retry) doesn't carry a stale backoff count into the
+     *  future. Without this, a once-failed-then-succeeded UID keeps its
+     *  count and would back off longer than warranted if it ever re-enters
+     *  the candidate set. */
+    private clearPrefetchEmpty;
     /** Background body-cache backfill. Public so the Reconciler can schedule
      *  the periodic tick under its priority/back-pressure rules; existing
      *  in-method post-sync nudges (sync, fetchSince, fetchOne) call this

package/index.js

@@ -2467,14 +2467,29 @@ export class ImapManager extends EventEmitter {
         // Quick STATUS check (above) and actions/outbox drain (above)
         // stay here because they're tightly tied to IMAP connection state
         // and the `syncing` flag.
-        // Full sync (all folders + IDLE restart) at configured interval.
-        // Stays here because callers pass `intervalMinutes` directly —
-        // moving it would mean threading the value through MailxService
-        // → Reconciler with a separate setter, for no behavior gain.
+        // LAZY FOLDER SYNC (Thunderbird model — Bob 2026-05-28). The full
+        // sweep of ALL folders no longer runs on the tight `intervalMinutes`
+        // (5 min) timer. On a mailbox with 79 folders + a 135k INBOX, that
+        // sweep ran longer than 5 minutes (folders timing out at 360s) and
+        // was therefore ALWAYS running, saturating the 4-permit connection
+        // semaphore. That starved the three things that actually matter —
+        // new INBOX mail (IDLE re-establish), body prefetch, and click-to-read
+        // — producing the session's running complaints: "slow to get codes",
+        // "lots not prefetched", "Loading… forever".
+        //
+        // New model:
+        //   - INBOX: IDLE push (instant) + the 5-min quick STATUS check above
+        //     (safety net). Unchanged — INBOX stays fresh.
+        //   - Every other folder: synced ON OPEN (the client fires syncFolder
+        //     when the user selects a folder) + a slow background sweep at
+        //     FULL_SWEEP_MIN so nothing goes stale indefinitely.
+        // The slow sweep keeps connection headroom free for the hot paths.
+        const FULL_SWEEP_MIN = 30;
         const fullInterval = setInterval(() => {
             this.runFullSync().catch(e => console.error(`  [periodic] full sync error: ${e?.message || e}`));
-        }, intervalMinutes * 60000);
+        }, FULL_SWEEP_MIN * 60000);
         this.syncIntervals.set("all", fullInterval);
+        console.log(`  [periodic] full all-folders sweep every ${FULL_SWEEP_MIN}min (lazy model — folders also sync on open); INBOX stays live via IDLE + ${intervalMinutes}min quick check`);
     }
     /** One-shot full sync + IDLE restart. Public so callers (Reconciler,
      *  user-initiated "Sync now") can fire it on demand. The original body
@@ -2870,6 +2885,15 @@ export class ImapManager extends EventEmitter {
                     : 12 * 3600_000;
         return Date.now() - f.lastTried < backoffMs;
     }
+    /** Clear a UID's prefetch-failure record after a successful fetch, so a
+     *  message that healed (e.g. a transient iflow protocol desync that
+     *  resolved on retry) doesn't carry a stale backoff count into the
+     *  future. Without this, a once-failed-then-succeeded UID keeps its
+     *  count and would back off longer than warranted if it ever re-enters
+     *  the candidate set. */
+    clearPrefetchEmpty(accountId, folderId, uid) {
+        this.prefetchFailures.delete(`${accountId}:${folderId}:${uid}`);
+    }
     /** Background body-cache backfill. Public so the Reconciler can schedule
      *  the periodic tick under its priority/back-pressure rules; existing
      *  in-method post-sync nudges (sync, fetchSince, fetchOne) call this
@@ -3095,6 +3119,7 @@ export class ImapManager extends EventEmitter {
                                             const parsed = await extractPreview(source);
                                             this.db.updateBodyMeta(accountId, uid, bodyPath, parsed.hasAttachments, parsed.preview);
                                             this.emit("bodyCached", accountId, uid);
+                                            this.clearPrefetchEmpty(accountId, folderId, uid); // healed — drop stale backoff
                                             counters.totalFetched++;
                                             madeProgress = true;
                                         }

package/package.json

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