@bobfrankston/mailx-imap 0.1.73 → 0.1.75

package/index.js

@@ -594,7 +594,19 @@ export class ImapManager extends EventEmitter {
         if (!config)
             throw new Error(`No config for account ${accountId}`);
         const host = config.server || accountId;
-        const releaseHostSlot = await this.acquireHostSlot(host);
+        // IDLE bypasses the host semaphore. The semaphore caps concurrent
+        // connection OPENS so a multi-account-on-one-host setup can't blow the
+        // server's connection limit — but IDLE is a SINGLE long-lived socket
+        // per account (the subscription), established once and parked. Gating
+        // it behind the same 4 permits that sync/prefetch/fast churn through
+        // meant that when sync saturated the pool (folders timing out at 360s),
+        // IDLE could not get a slot to (re)subscribe — so new mail stopped
+        // arriving by push and the user fell back to slow polling (Bob
+        // 2026-05-29: "you should be subscribed and not depend on sync"). The
+        // subscription must NEVER be starved by sync. One extra socket per
+        // account is well within any server cap.
+        const skipSemaphore = purpose === "idle";
+        const releaseHostSlot = skipSemaphore ? (() => { }) : await this.acquireHostSlot(host);
         let client;
         try {
             // Verbose IMAP wire trace for ops connections only — that's the
@@ -2467,14 +2479,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

package/package.json

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