@bobfrankston/rmfmail 1.2.288 → 1.2.289

package/.commitmsg

@@ -1,29 +1,12 @@
-Trust: a message that never crossed a trust boundary proves itself
-
-Bob 2026-08-27, on his own reply to John Levine about spam handling: "why is
-my own mail spam". It carried no Authentication-Results at all — his own
-authenticated submission never left his systems, so nothing added one — and
-`proved` therefore came back false, dropping it to a caution banner that told
-him not to open the links in prose he had just written. What flagged it was
-`URIBL_DBL_SPAM` 8.0 on blueorchestra.org: the domain he was QUOTING, in a
-discussion about spam. Guilt by association at its purest.
-
-SpamAssassin states two proofs in its own rule list that such mail carries
-instead of an AR header:
-
-  ALL_TRUSTED    Passed through trusted hosts only via SMTP
-  DKIM_VALID_AU  Message has a valid DKIM or DK signature from author's domain
-
-DKIM_VALID_AU is the same evidence DMARC alignment rests on — the author
-domain signed it and the signature verified — so it proves the From line on
-its own. ALL_TRUSTED says nothing untrusted handled the message in transit.
-`proved` now comes from any of the three, and `provedBy` names which, so the
-banner says WHICH proof rather than asserting DMARC that isn't there. His
-message is now a grey note: "…but bob.ma proved it sent this. Valid signature
-from bob.ma, the sending domain itself (DKIM_VALID_AU)."
-
-Forgery still outranks proof — across the store the danger count is unchanged
-at 294 of 1,131 flagged; caution 599, quiet 238.
-
-Also: the Insert menu gains Blockquote and Quoted text (paste) — rmf-tiny
-0.1.53, see its .commitmsg.
+The spam chip has to name the proof it actually has
+
+Follow-up to v1.2.288, caught by looking at the rendered chip on Bob's own
+message: the banner correctly said "Valid signature from bob.ma (DKIM_VALID_AU)"
+while the chip's tooltip underneath asserted "the sending domain passed DMARC"
+— on a message that carries no Authentication-Results header at all. A claim
+the reader cannot check is exactly what this whole change set exists to remove.
+
+`SpamScore` now carries `provedBy` alongside `proved`, and the chip's tooltip
+says which of the three proofs applied: the server's DMARC verdict, a valid
+signature from the sending domain, or never having passed through an untrusted
+host.

package/client/android-bootstrap.bundle.js

@@ -2530,6 +2530,7 @@ function spamScoreOf(input) {
     flagged: a.flagged,
     kind: a.kind,
     proved: a.proved,
+    provedBy: a.provedBy,
     reasons: a.reasons
   };
 }