Files
jcoffey-dev 9fb690b53d
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 13m6s
Delivery history: show each message's subject
Inbound and Outbound Delivery History now have a Subject column between
To and Size (asked for in inbuxa-admin#228). x:Trace gets a server-set
subject: the first subject recorded in the trace, or null.

A new event, queue.message-subject (id 663), carries the Subject header,
cut to 255 characters. It's raised in the SMTP session when a message is
queued, and in the delivery attempt right after delivery.attempt-start,
read from the message's blob (a fresh message comes from the node's blob
cache, and delivery reads the blob anyway). It is debug level and the
trace history keeps it by name, so subjects reach the stored history but
no info-level log or OpenTelemetry tracer. With no tracing store set,
nothing is read or raised. The subject isn't added to the text search
keywords.

Key::Subject (id 66) is new. The packaged schema has the field, the two
list columns, the trace form field, the event and the key. The privacy
catalog now counts content in x:Trace and its events. Spec: MON-42.

Test: a unit test for the subject helper (encoded words, no header,
an empty subject, truncation). monitoring_tests checks that the inbound
session and its local delivery attempt both carry the subject.
2026-11-18 12:31:01 -07:00
..