19-Jun-2026 — Inbox & membership-run follow-ups from committee testing (June 2026) #293

build 705commit a3f5247


Follow-ups from committee testing of the new inbox: the two inbox bugs EKWG committee (early testers) hit (read state shared by everyone, role filter showing "no messages"), the gap where members who can't be emailed were never deleted, a click- heavy composer, several email-client conveniences for the inbox, and a fix for broken welcome-email images.

What's new

See https://github.com/nbarrett/ngx-ramblers/issues/293

At a glance

Area Before Now
Marking read Cleared unread for everyone Per committee member
Role filter Only mail addressed to the role Also mail sent from the member's identity
Expiry run, un-emailable members Skipped, left in the database Included, tagged "not emailable", deleted in the same pass
Composer steps Always six steps Compose/Events skippable per email type
Thread list Mouse only Arrow keys to move, Delete to delete
Read filter None Funnel toggle for unread only
Opening a mailbox First conversation auto-marked read Previewed only; read on user action
Welcome-email images Broken (editing host baked into the URL) Relative paths, render correctly

Where to find it

Above: how the inbox looks when you first visit it

How it behaves

Why it is restricted

How to try it out

  1. Admin -> Email inbox: open a conversation as one member, then check it is still unread for another member. Use the funnel to show unread only.
  2. Click into the list and use Up/Down to move between conversations and Delete to remove one. Land on the mailbox fresh and confirm the first conversation is previewed but stays unread until you act on it.
  3. Select the Membership role filter and confirm sent membership mail now appears (run "rescan general" once to re-bucket existing threads).
  4. In the composer, choose the missing-from-bulk-load email type and confirm no-email and blocked members are included and tagged. Tick "Skip the Compose step" / "Skip the Events step" on the welcome type in the notification template editor and confirm those steps disappear.

Technical changes

User-facing behaviour is above; the implementation details follow.