@bobfrankston/rmfmail 1.1.218 → 1.1.220

package/packages/mailx-imap/index.ts

@@ -187,18 +187,29 @@ async function extractPreview(source: string): Promise<{ bodyHtml: string; bodyT
         // remaining base64 data: URIs (rare: text/plain copies generated
         // from a Quill compose pasted-image HTML) collapsed to [image] too.
         let raw: string;
-        if (bodyHtml) {
-            // Drop the CONTENTS of style/script/head blocks and HTML comments
-            // first — a plain tag-strip removes the <style> tags but leaves the
-            // CSS rules between them, which then leak into the preview as
-            // `*{box-sizing:border-box}` / `@media …{ … }` garbage (Bob's
-            // 2026-05-31 marketing-mail shot). Order matters: kill blocks, then
-            // images → [image], then any remaining tags.
+        // PREFER the plain-text rendering for the summary. The HTML→[image]
+        // path turns an image-heavy marketing/tracking email into a useless
+        // "[image] [image] [image]…" wall — the "[no summary]" Bob hit
+        // 2026-06-04. mailparser's `text` is the text/plain alternative when
+        // present, otherwise a tags-and-images-stripped rendering of the HTML,
+        // i.e. the actual words. Only fall back to HTML when there's no usable
+        // text at all (genuinely image-only mail).
+        const textCandidate = (bodyText || "").replace(/\s+/g, " ").trim();
+        if (textCandidate.length >= 3) {
+            raw = bodyText;
+        } else if (bodyHtml) {
+            // No usable text part. Strip style/script/head + comments (CSS would
+            // otherwise leak into the preview — Bob 2026-05-31), then prefer an
+            // <img alt="…"> caption over the bare "[image]" token, and collapse
+            // runs of placeholders so even this fallback isn't a wall.
             raw = bodyHtml
                 .replace(/<!--[\s\S]*?-->/g, " ")
                 .replace(/<(style|script|head)\b[^>]*>[\s\S]*?<\/\1>/gi, " ")
+                .replace(/<img\b[^>]*\balt\s*=\s*"([^"]+)"[^>]*>/gi, " $1 ")
+                .replace(/<img\b[^>]*\balt\s*=\s*'([^']+)'[^>]*>/gi, " $1 ")
                 .replace(/<img\b[^>]*>/gi, " [image] ")
-                .replace(/<[^>]+>/g, " ");
+                .replace(/<[^>]+>/g, " ")
+                .replace(/(\[image\]\s*){2,}/g, "[image] ");
         } else {
             raw = bodyText;
         }
@@ -1323,13 +1334,20 @@ 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.
+                    // 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) — almost certainly a mis-parsed range; falling back to set-diff reconcile instead of mass-deleting/wedging.`);
+                    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.83",
+  "version": "0.1.85",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@bobfrankston/mailx-imap",
-      "version": "0.1.83",
+      "version": "0.1.85",
       "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.83",
+  "version": "0.1.85",
   "type": "module",
   "main": "index.js",
   "types": "index.d.ts",