Tooling to see and act on mail whose body blob was lost.
feat(admin): report and purge mail whose body blob is gone
Eight messages carry MailMeta records whose raw_message blob no longer exists,
left by the 2026-08-30 blob-GC incident. They appear in no per-user SQLite
index, which proves nothing: that row is written during indexing, and indexing
is what fails on a missing body.
Adds FindDanglingMail and DeleteDanglingMail, the /internal/mail/dangling and
/internal/mail/purge-dangling endpoints behind internal auth, and the
"bongo-go mail dangling" / "mail purge-dangling --confirm" commands, mirroring
the existing orphaned-address repair.
The report lists every MailboxMessage entry referencing each GUID, which is
what distinguishes orphaned metadata from a live message sitting in a mailbox.
Deletion removes those entries too, and before the MailMeta: the sequence is
several Raft commands and is not atomic, and this order leaves orphaned
MailMeta on an interruption -- which sweepOrphanedMail already reclaims --
rather than a mailbox entry pointing at nothing, which nothing cleans up.
Each blob is re-checked immediately before its record is removed, since blob
sync can pull one back from a peer between the scan and the delete.
Also corrects a false claim in v0.6.25's 14.5 work. It said a MailboxMessage
decoded as a MailMeta fails proto.Unmarshal on a wire-type clash, and that a
user could therefore disable blob GC by naming a mailbox "mail". The decode
does not fail; protobuf-go skips a wire-type mismatch on a known field number
as an unknown field. That denial-of-service never existed. The structural key
parse remains correct for the plainer reason that unmarshal success is not
evidence a value is the type you expected.
This release ships the report. No purge has been run.