* fix(inbox): trace every received mail and file multi-recipient mail once per inbox (#2181)
A mail sent to both the +lev and +ver address of one inbox was read as
its first recipient only, and an attachment whose processing threw left
no row at all: the webhook answered 200, Resend never retried, and the
document was gone with nothing for the user to find. Prod showed both
shapes for the reporter (a +lev mail Resend accepted with zero inbox
rows, and the second PDF of the +ver mail missing).
- The webhook now reads every shared-domain recipient, groups them per
inbox, files once per inbox with a company-scoped dedupe key, and
resolves contradicting tags (+lev and +ver on one mail) to no hint so
extraction classifies.
- The per-attachment catch writes an error row instead of only a
console line.
- One InboundMailReceived behandlingshistorik event per mail and inbox
records recipients, tags, hint, conflict and the outcome per
attachment (filed, duplicate, rejected, failed). No sender or
subject, matching the existing PII rule.
- GET /inbound-history?days=30 serves those events, company-scoped, and
the inbox workspace shows them under Källor as "Inkomna mejl", each
filed row a click away.
- The list says how many rows the type filter is hiding, with a click
back to all types.
- Migration 20260903190000 registers the event type and replaces the
(email, attachment) unique index with (company, email, attachment).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CoG2CXf8B33Q5wp8gk4kW4
* fix(inbox): keep addresses and sender-typed tags out of the mail record, and let redelivery heal a transient failure
Skeptic pass on #2244, two refutations:
- The InboundMailReceived payload carried the recipient addresses and every
plus-tag verbatim. An enskild firma's inbox local part is the owner's
name, the tag is whatever the sender typed, and processing_history is
append-only and outside the erasure path; a numeric tag also tripped the
PII validator so the record was silently dropped. The event now carries
inbox_id, the documented tags (+lev/+ver), an unknown-tag count and the
outcome codes. The history route resolves inbox_id to the company's own
address at read time. The DB strip trigger from 20260901110000 covers the
new type (and is recreated, since staging skipped that file).
- The catch-path error row made a Resend redelivery report "duplicate", so
a transient download or storage failure that used to self-heal on retry
became permanent. The row is marked transient and a redelivery replaces
it; rejections (bad type, too large) stay duplicates.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CoG2CXf8B33Q5wp8gk4kW4
* fix(inbox): cap inbound fan-out, flag a truncated mail history, and name a replaced transient row
Review pass on #2244: Superagent (bound the number of inboxes one mail can
fan out to: five), CodeRabbit (the history route now returns has_more past
200 rows and the panel says so instead of "every mail"), and the Swedish
accounting review (a redelivery that replaces a transient error row names
the replaced row on the InboundMailReceived record, so the replacement
leaves a trace). The migration comment states why the index swap is not
CONCURRENTLY: Supabase branching applies migrations in a transaction.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(inbox): resolve every addressed inbox and record the ones past the fan-out cap
CodeRabbit and the Swedish accounting review on #2244: slicing recipient
groups before the lookup let five unknown local parts starve a real inbox
and left companies past the cap with no trace. Every addressed inbox is
now resolved (one cheap lookup each), the first five are processed, and
the rest get their own InboundMailReceived record with outcome
fan_out_capped, shown in the panel as "not processed".
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* chore(inbox): move the inbound-mail migration past the parties versions merged tonight
Main moved party_decision_undo to 20260904000100 and added
20260904000200 (#2257, #2258). A version below prod's head is skipped by
Supabase branching, so 20260903190000 becomes 20260904001000 unchanged.
Staging re-tracked under the new version.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
