@bobfrankston/rmfmail 1.2.296 → 1.2.298

package/.commitmsg

@@ -1,29 +1,33 @@
-A star set on the phone now reaches the desktop in seconds, not minutes
+The signature in accounts.jsonc never reached compose
 
-Bob 2026-08-29: "how long should it take for a * on the phone to get to my
-desktop?" Measured, on his own log: a median of 5 minutes and up to 20.
+`sig` has been a documented field on AccountConfig for months and three of the
+four accounts carried one, yet no signature has ever appeared in a compose
+window. The reason is a projection: `MailxService.getAccounts()` builds the
+client's account list field by field — id/name/email from the DB row, then
+label, defaultSend, primary*, identityDomains from the config — and `sig` and
+`signature` were simply not on the list. `normalizeAccount()` resolved them
+correctly, `openCompose` forwarded `a.sig` faithfully, and compose.ts appended
+`acct.sig` exactly as designed; the value was undefined by the time any of that
+ran.
 
-Why: gal.iecc.com does not advertise NOTIFY, so the desktop watches INBOX with
-plain IDLE. The server DOES push a flag change there as an unsolicited
-`* 1234 FETCH (FLAGS (\Seen \Flagged))` — iflow-direct dropped it (fixed in
-0.1.67), and mailx had nothing to receive it with. The 5-minute quick check
-could not help either: it is a STATUS poll, and MESSAGES / UNSEEN / UIDNEXT do
-not move when a message is starred. So the only path was the periodic full
-sync's QRESYNC pass — which is why the numbers above are the sync cadence
-rather than any property of flags.
+Both fields are now carried, with a comment saying why the enumeration stays an
+enumeration rather than becoming `...cfg`: cfg holds the IMAP and SMTP
+passwords, which have no business crossing into the WebView. Anything new that
+the client needs has to be added in that spot deliberately.
 
-The IDLE watcher now takes `onFlagChange` and, debounced 1.5 s, runs the
-folder's normal QRESYNC pass — the same one that already reconciles flags and
-took 53 ms in that log. Marking ten messages read on the phone arrives as ten
-pushes and costs one pass. Our own STOREs bounce back as flag pushes too, so
-the handler skips while this account has sync actions draining; the local store
-already has those.
+The signature itself moved to the top level of accounts.jsonc — three
+byte-identical per-account copies replaced by the one the file format already
+supports, which every account without its own `sig` inherits. It is now
+`Bob Frankston<br>https://Frankston.com` with `html: true`; the previous text
+relied on bare newlines for its line break (HTML collapses those to a space)
+and pointed at a relative `href='Frankston.com'`, which resolves against
+whatever page the mail client happens to be rendering.
 
-INBOX only, because IDLE watches one mailbox per connection. Flags changed in
-other folders still wait for that folder's turn in the sync cycle.
+Two stale comments corrected while here. `AccountSignature.html` was documented
+in both mailx-types and compose.ts as "reserved for future use / currently
+ignored". It has never been ignored — compose has always branched on it — and
+now that a signature actually renders, the difference between escaped text and
+raw HTML is the thing an author needs to know.
 
-Also in this build: the log noise behind it. `[search]` / `[fetch]` per-command
-lines moved behind iflow's existing `verbose` flag, and the repeated
-per-folder reconcile lines now go through `logIfChanged` — first occurrence,
-every change, and an hourly restatement — instead of once per folder per cycle
-forever. On Android each of those lines was an HTTP request to the log server.
+Compose only. Nothing in the send path or the daemon appends a signature; the
+body that leaves the editor is the body that goes out.