Spam Score plugin loads but never renders visible output

[ovizii]

Just so you know, after struggling to figure this out, I used an AI agent to help me summarize and analyse. Consider this AI-enabled post content ;-)

I'm running Stalwart v0.16.8 behind Traefik/Pangolin, with Bulwark Webmail v1.7.5. The Spam Score plugin activates successfully (I can see slots=1 in the activation log), but it never produces any visible output — no section appears in the email detail view, not even for emails that carry Stalwart's spam headers.

What I've verified so far:

1. Headers are present in JMAP responses. Inbound emails return X-Spam-Status, X-Spam-Score, and X-Spam-Result via Email/get. (Sent/outbound emails don't, which is expected.)

2. Headers reach the plugin pipeline. In Bulwarmail, parseEmailHeaders() in /lib/jmap/client.ts converts the raw JMAP array to a flat Record<string, string | string[]>. emailToReadView() in /lib/plugin-projection.ts passes headers through verbatim. The flat object is sent to the sandboxed iframe as extraProps.

3. Plugin source (spam-score/src/index.js): parseSpam() looks for X-Spam-Status and falls back to X-Spam-Score with toNumber(). There's Stalwart-specific fallback logic. shouldShow({ email, category }) returns true when category === null (the bottom section) by default, unless showWhenClean is explicitly false. The SpamScore component checks spamScore and spamVerdict to decide what to render.

4. The email-details-section slot is rendered in two places in email-viewer.tsx:
   Per-category rows inside the expanded details panel (passes a category string)
   A catch-all bottom section when category === null, gated by hasDetailsSlotOffers being > 0

What I haven't pinned down:

1. Whether hasDetailsSlotOffers is truthy — if the plugin offer doesn't register, the bottom section never mounts. The activation log showing slots=1 suggests it does register, but I'm not 100% sure.
2. Whether the plugin's shouldShow silently returns false due to some edge case in header parsing (e.g., header name casing, multiple values, or the Stalwart X-Spam-Status format not matching the SpamAssassin score= parser).
3. Whether the sandbox iframe fails to render (console errors are opaque since the plugin runs in an opaque-origin iframe).

To reproduce:

1. Install Spam Score plugin via the Plugins settings page.
2. Verify activation: you should see slots=1 in the plugin's activation log.
3. Open any inbound email that has been processed by Stalwart's spam filter (one that carries X-Spam-Status headers).
4. No spam score section appears in the email detail view, even with the details panel expanded.

Environment:

• Bulwark Webmail: v1.7.5
• Stalwart: v0.16.8
• Plugin version: latest from the Bulwark plugin registry
• Browser: Firefox 152, Chrome latest

[rathlinus]

please try beta

[ovizii]

I assume you mean the bulwark beta so Iwill give it a try over the weekend.

[rathlinus]

yes