@bobfrankston/mailx-store 0.1.43 → 0.1.45

package/db.d.ts

@@ -375,6 +375,16 @@ export declare class MailxDB {
         uid: number;
         folderId: number;
     }[];
+    /** Record a prefetch failure (0-body fetch / store-write fail) for a UID,
+     *  incrementing its backoff count. Persisted so it survives restarts. */
+    recordPrefetchFailure(accountId: string, folderId: number, uid: number): void;
+    /** Read a UID's prefetch-failure record (count + lastTried), or null. */
+    getPrefetchFailure(accountId: string, folderId: number, uid: number): {
+        count: number;
+        lastTried: number;
+    } | null;
+    /** Clear a UID's prefetch-failure record after a successful fetch. */
+    clearPrefetchFailure(accountId: string, folderId: number, uid: number): void;
     /** Highest server UID we've seen in this folder. After the
      *  message_folders refactor, this reads from the membership table
      *  rather than messages.uid — a server-side move from this folder

package/db.js

@@ -315,6 +315,23 @@ const SCHEMA = `
         PRIMARY KEY(scope, key)
     );
 
+    -- Prefetch-failure backoff, PERSISTED (was an in-memory Map that every
+    -- daemon restart wiped — so un-fetchable "ghost" UIDs, e.g. stale Outbox
+    -- rows for already-sent messages that return 0 bodies, got re-tried in
+    -- full on every launch and re-clogged the size-asc prefetch queue,
+    -- starving healthy folders. "So much unfetched, never drains" — Bob
+    -- 2026-06-01. Persisting the count+timestamp lets the 5min→12h backoff
+    -- survive restarts so zombies stay sidelined. Pure cache-control state;
+    -- safe to lose (worst case = one extra retry), so no reconstruction needed.
+    CREATE TABLE IF NOT EXISTS prefetch_failures (
+        account_id TEXT NOT NULL,
+        folder_id INTEGER NOT NULL,
+        uid INTEGER NOT NULL,
+        count INTEGER NOT NULL,
+        last_tried INTEGER NOT NULL,
+        PRIMARY KEY(account_id, folder_id, uid)
+    );
+
     -- Audit trail of every destructive DB operation. Writes ONLY — the row
     -- inserted here records the deletion the caller is about to (or just
     -- did) commit on the messages table. Lets the user retroactively answer
@@ -1666,7 +1683,12 @@ export class MailxDB {
                 EXISTS(
                     SELECT 1 FROM sync_actions sa
                     WHERE sa.account_id = m.account_id AND sa.uid = r.mf_uid
-                ) AS pending
+                ) AS pending,
+                -- Replied state OR'd across the Message-ID group (see
+                -- getUnifiedInbox) so the reply arrow is correct regardless of
+                -- which duplicate survives dedup. Bob 2026-06-01.
+                COALESCE((SELECT MAX(CASE WHEN m3.is_replied = 1 OR m3.flags_json LIKE '%Answered%' THEN 1 ELSE 0 END)
+                          FROM messages m3 WHERE m3.message_id = m.message_id AND COALESCE(m.message_id, '') != ''), m.is_replied) AS groupReplied
             FROM ranked r
             JOIN messages m ON m.id = r.m_id
             WHERE r.rn = 1
@@ -1689,7 +1711,7 @@ export class MailxDB {
             flags: JSON.parse(r.flags_json),
             size: r.size,
             hasAttachments: !!r.has_attachments,
-            isReplied: !!r.is_replied,
+            isReplied: !!r.groupReplied,
             preview: r.preview,
             bodyPath: r.body_path || "",
             pending: !!r.pending,
@@ -1737,7 +1759,16 @@ export class MailxDB {
                     WHERE sa.account_id = m.account_id AND sa.uid = r.mf_uid
                 ) AS pending,
                 (SELECT COUNT(DISTINCT account_id) FROM messages m2
-                 WHERE m2.message_id = m.message_id AND COALESCE(m.message_id, '') != '') AS dupeCount
+                 WHERE m2.message_id = m.message_id AND COALESCE(m.message_id, '') != '') AS dupeCount,
+                -- Replied state aggregated across the whole Message-ID group, not
+                -- just the dedup survivor. When duplicates collapse (same message
+                -- delivered to multiple self-addresses), the \Answered flag /
+                -- is_replied can live on a NON-surviving copy — so the survivor
+                -- showed no reply arrow even though TB did. OR it across the group
+                -- so the marker is correct regardless of which row wins dedup
+                -- (Bob 2026-06-01). Empty message_id → falls back to the row's own.
+                COALESCE((SELECT MAX(CASE WHEN m3.is_replied = 1 OR m3.flags_json LIKE '%Answered%' THEN 1 ELSE 0 END)
+                          FROM messages m3 WHERE m3.message_id = m.message_id AND COALESCE(m.message_id, '') != ''), m.is_replied) AS groupReplied
             FROM ranked r
             JOIN messages m ON m.id = r.m_id
             WHERE r.rn = 1
@@ -1759,7 +1790,7 @@ export class MailxDB {
             flags: JSON.parse(r.flags_json),
             size: r.size,
             hasAttachments: !!r.has_attachments,
-            isReplied: !!r.is_replied,
+            isReplied: !!r.groupReplied,
             preview: r.preview,
             bodyPath: r.body_path || "",
             pending: !!r.pending,
@@ -2017,6 +2048,23 @@ export class MailxDB {
             : "";
         return this.db.prepare(`SELECT uid, folder_id as folderId FROM messages WHERE account_id = ? AND (body_path IS NULL OR body_path = '')${exclusion} ORDER BY (size IS NULL OR size = 0), size ASC, date DESC LIMIT ?`).all(accountId, ...excludeFolderIds, limit);
     }
+    /** Record a prefetch failure (0-body fetch / store-write fail) for a UID,
+     *  incrementing its backoff count. Persisted so it survives restarts. */
+    recordPrefetchFailure(accountId, folderId, uid) {
+        this.db.prepare(`INSERT INTO prefetch_failures (account_id, folder_id, uid, count, last_tried)
+             VALUES (?, ?, ?, 1, ?)
+             ON CONFLICT(account_id, folder_id, uid)
+             DO UPDATE SET count = count + 1, last_tried = excluded.last_tried`).run(accountId, folderId, uid, Date.now());
+    }
+    /** Read a UID's prefetch-failure record (count + lastTried), or null. */
+    getPrefetchFailure(accountId, folderId, uid) {
+        const r = this.db.prepare("SELECT count, last_tried AS lastTried FROM prefetch_failures WHERE account_id = ? AND folder_id = ? AND uid = ?").get(accountId, folderId, uid);
+        return r ? { count: r.count, lastTried: r.lastTried } : null;
+    }
+    /** Clear a UID's prefetch-failure record after a successful fetch. */
+    clearPrefetchFailure(accountId, folderId, uid) {
+        this.db.prepare("DELETE FROM prefetch_failures WHERE account_id = ? AND folder_id = ? AND uid = ?").run(accountId, folderId, uid);
+    }
     /** Highest server UID we've seen in this folder. After the
      *  message_folders refactor, this reads from the membership table
      *  rather than messages.uid — a server-side move from this folder

package/package.json

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