@bobfrankston/mailx-settings 0.1.84 → 0.1.86

package/docs/allowlist.md

@@ -1,6 +1,6 @@
 # allowlist.jsonc
 
-> **Owned by rmfmail. Do not edit this file — your changes will be overwritten the next time the app starts.** This is reference documentation. To change allow-list data, edit `allowlist.jsonc` itself.
+> **This documentation file (allowlist.md) is owned by rmfmail — do not edit it; it is rewritten every time the app starts.** The data file `allowlist.jsonc` next to it is yours: hand-editing it is fine and is one of the two ways to undo an approval (the other is the same viewer action again, see Notes).
 
 ## What this file documents
 
@@ -54,9 +54,11 @@ doing; a trusted list then quiets the spam note and hides the score chip. SPF an
 failures, and phishing or malware URL listings, are never silenced: a list member can post
 a bad link like anyone else.
 
-The viewer offers **"Trust the ‹List-Id› list"** under a spam-verdict banner, and
-**"Trust the ‹List-Id› mailing list"** in the From address's right-click menu (the chip's
-tooltip says so — an unflagged post shows only the chip).
+The viewer offers **"Trust the ‹List-Id› list"** under a spam-verdict banner and beside the
+spam-score chip (an unflagged post shows only the chip), and **"Trust the ‹List-Id› mailing
+list"** in the From address's right-click menu. Once the list is trusted the chip and banner
+are gone, so the menu item becomes **"Stop trusting the ‹List-Id› mailing list"** — that is
+how an approval is undone from the viewer.
 
 ## Notes
 
@@ -64,5 +66,5 @@ tooltip says so — an unflagged post shows only the chip).
 - Multi-client safe: each device's save merges with the cloud copy (set-union), so adds from any device propagate.
 - Use the message viewer's "allow remote content" button to add a sender/domain to `senders`/`domains` interactively.
 - Use the right-click menu in the viewer to flag a sender/domain — adds to `flaggedSenders`/`flaggedDomains`.
-- "Stop warning about …" under a spam-score note adds to `trustedSenders`/`trustedDomains`; "Trust … as an intermediary" adds to `trustedIntermediaries`; "Trust the … list" adds to `trustedLists`. Each is a toggle: the same action again removes the entry.
+- "Stop warning about …" under a spam-score note adds to `trustedSenders`/`trustedDomains`; "Trust … as an intermediary" adds to `trustedIntermediaries`; "Trust the … list" adds to `trustedLists`. Each is a toggle: the same action again removes the entry. The banner buttons disappear with the banner once trust is written, so to undo a sender or intermediary approval edit `allowlist.jsonc` (remove the entry from its list); a list approval can also be undone from the From address's right-click menu ("Stop trusting the … mailing list").
 - JSONC: `// line comments` and trailing commas are allowed.

package/docs/spam-false-positives.md

@@ -228,7 +228,7 @@ pass for the Sender:/bounce domain, or DKIM pass for the list domain; ISOC's Mai
 and the From-vs-path rules (`LIST_RELAY_RULES`) are neutral: the list is the explanation.
 Trusted + proved silences the verdict and hides the chip, like a trusted intermediary. SPF
 and DMARC failures and URL/phishing listings are never silenced — a list member can post a
-bad link like anyone else. Shipped v1.2.311; see `docs/allowlist.md`.
+bad link like anyone else. Shipped v1.2.312; see `docs/allowlist.md`.
 
 ## Follow-ups, 2026-08-27 evening
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bobfrankston/mailx-settings",
-  "version": "0.1.84",
+  "version": "0.1.86",
   "type": "module",
   "main": "index.js",
   "types": "index.d.ts",
@@ -17,7 +17,7 @@
   },
   "license": "ISC",
   "dependencies": {
-    "@bobfrankston/mailx-types": "^0.1.90",
+    "@bobfrankston/mailx-types": "^0.1.92",
     "jsonc-parser": "^3.3.1"
   },
   "repository": {
@@ -33,7 +33,7 @@
   },
   ".transformedSnapshot": {
     "dependencies": {
-      "@bobfrankston/mailx-types": "^0.1.90",
+      "@bobfrankston/mailx-types": "^0.1.92",
       "jsonc-parser": "^3.3.1"
     }
   }