bvandeusenandClaude Opus 5.5 defad2e98b feat(email): delivery you can see: each alert's email in history, outgoing email on Settings -> System (#5509) ...

#5509 "Delivery you can see: each alert's email state in history, and
outgoing email on Settings -> System" (milestone 501).

- Alerts -> History: an alert's email reads from the outbox (#5506):
  "gathering" with when it sends, "sending", "retrying" with the attempt,
  next try and the server's last answer, "sent", or "failed" naming each
  reader it didn't reach and why (outbox.delivery / email_states). Events
  from before the outbox keep what they recorded. The Notified column
  shows once an alert has a queued email.
- Settings -> System gets "Outgoing email": every email of the last 7
  days not yet sent, failures first, then the longest retrying, with
  recipient, kind, state and last error, and a count of what was sent.
  Failures and anything still retrying after 5 minutes lead the page's
  verdict (outbox.outgoing).
- get_alert_history (MCP) adds `email`: the same delivery state.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-09 16:12:40 -04:00

..

alerting.md

feat(email): delivery you can see: each alert's email in history, outgoing email on Settings -> System (#5509)

2026-10-09 16:12:40 -04:00

ansible.md

fix(ansible): overlapping runs: one per host, one per schedule, one action run per alert rule (#5158)

2026-10-06 21:24:51 -04:00

configuration.md

chore: rename project Roundtable → Steward

2026-04-25 16:20:14 -04:00

mcp.md

feat(mcp): update_group_members puts hosts into an inventory group or takes them out (#5487)

2026-10-09 11:48:08 -04:00

monitors.md

chore: rename project Roundtable → Steward

2026-04-25 16:20:14 -04:00