@bobfrankston/rmfmail 1.2.224 → 1.2.225

package/client/android-bootstrap.bundle.js

@@ -6649,8 +6649,21 @@ ${bodyEncoded}`;
     return this.notImpl("openAttachment");
   }
   // Spam / abuse
-  async markAsSpamMessages(_accountId, _uids) {
-    return this.notImpl("markAsSpamMessages");
+  /** Mark as spam = move to the account's \Junk folder, exactly as desktop's
+   *  MailxService.markAsSpamMessages does. This was a notImpl() stub, which
+   *  is worse than it sounds: the client optimistically removes the rows
+   *  from the list BEFORE calling this, then only writes the rejection to
+   *  the status bar. So on Android the spam button looked like it worked,
+   *  nothing moved on the server, and the next sync brought every message
+   *  straight back (Bob 2026-08-07: "attempts to delete spam but they keep
+   *  coming back"). moveMessages was implemented all along — spam just never
+   *  got wired to it. */
+  async markAsSpamMessages(accountId, uids) {
+    const target = this.db.getFolders(accountId).find((f) => f.specialUse === "junk");
+    if (!target)
+      throw new Error(`No \\Junk/\\Spam folder found for ${accountId}`);
+    await this.moveMessages(accountId, uids, target.id);
+    return { targetFolderId: target.id, moved: uids.length };
   }
   async recordSpamReport(_accountId, _uid, _folderId) {
     return this.notImpl("recordSpamReport");