mesh-mail: a send ask the operator channel can carry (issue 868)

Conversation 2 Commits 2 Files Changed 6

+644 -22

2 Commits

Author	SHA1	Message	Date
jochen	b0e4a12c88	mail_send's ask: judge messenger's real words, carry the content rule at run time, match display-name recipients (issue 868, review round 1) mesh/merge-gate head b0e4a12c8840 merged into trunk 21a499ba5976 — pass: builds mesh-mail → novox; no bus step; every machine composes with the change as i… Details mesh/repo-check head b0e4a12c8840 merged into trunk 21a499ba5976 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-… Details mesh/delivery delivered Details Review round 1: the test judged Headline+Explanation+Details, but messenger refuses an ask as a whole on Headline, Explanation, OnExpiry and each option's Label and Does alone (asks.go's TakeAsk); Details is filtered line by line instead (holder.go's sayOn). send.go's Ask() now builds that exact judged text and checks it with messenger's real content rule, carried at run time as content_rule.go (messenger's content.go, renamed, byte-identical, pinned by copies_test.go) rather than only in a test copy. When a subject or first line the masking does not catch (an IP, a hardware address, a path-shaped reference, a hex hash, ...) would still refuse the whole ask, the Explanation drops the subject and first lines and points at Details instead, so the ask always reaches the operator. A recipient written with a display name ('Name <addr>') is now matched against the operator's own accounts, and masked, by its address alone (net/mail.ParseAddress).	2026-10-16 02:04:32 +02:00
jochen	a76b0742ff	mail_send's ask names recipients and masks addresses so the operator channel can carry it (issue 868) messenger's content rule (ADR 0253 §3) refuses any message carrying a mail address, so mail_send's ask never reached the operator: no send could ever be approved. A recipient that is one of the operator's own mesh-mail accounts is now named by that account's name; any other loses its address and host; the subject and body's first lines have every address and link masked before they reach the ask. The mail itself is sent unchanged. Tests run messenger's real content rule against the asks mail_send builds (content.go copied verbatim as content_test.go, pinned byte-identical by copies_test.go, since messenger's package main cannot be imported from another module).	2026-10-16 01:57:06 +02:00

Author

SHA1

Message

Date

jochen

b0e4a12c88

mail_send's ask: judge messenger's real words, carry the content rule at run time, match display-name recipients (issue 868, review round 1)

mesh/merge-gate head b0e4a12c8840 merged into trunk 21a499ba5976 — pass: builds mesh-mail → novox; no bus step; every machine composes with the change as i…

Details

mesh/repo-check head b0e4a12c8840 merged into trunk 21a499ba5976 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…

Details

mesh/delivery delivered

Details

Review round 1: the test judged Headline+Explanation+Details, but messenger refuses an ask as a whole on
Headline, Explanation, OnExpiry and each option's Label and Does alone (asks.go's TakeAsk); Details is
filtered line by line instead (holder.go's sayOn). send.go's Ask() now builds that exact judged text and
checks it with messenger's real content rule, carried at run time as content_rule.go (messenger's
content.go, renamed, byte-identical, pinned by copies_test.go) rather than only in a test copy. When a
subject or first line the masking does not catch (an IP, a hardware address, a path-shaped reference, a
hex hash, ...) would still refuse the whole ask, the Explanation drops the subject and first lines and
points at Details instead, so the ask always reaches the operator. A recipient written with a display
name ('Name <addr>') is now matched against the operator's own accounts, and masked, by its address alone
(net/mail.ParseAddress).

2026-10-16 02:04:32 +02:00

jochen

a76b0742ff

mail_send's ask names recipients and masks addresses so the operator channel can carry it (issue 868)

messenger's content rule (ADR 0253 §3) refuses any message carrying a mail address, so mail_send's ask
never reached the operator: no send could ever be approved. A recipient that is one of the operator's own
mesh-mail accounts is now named by that account's name; any other loses its address and host; the subject
and body's first lines have every address and link masked before they reach the ask. The mail itself is
sent unchanged.

Tests run messenger's real content rule against the asks mail_send builds (content.go copied verbatim as
content_test.go, pinned byte-identical by copies_test.go, since messenger's package main cannot be
imported from another module).

2026-10-16 01:57:06 +02:00

mesh-mail: a send ask the operator channel can carry (issue 868) #326