- Ya
- 14 Agosti 2026, 08:26 UTC
- Mwandishi
- Kamo
- Ahadi ya
- f6e1bd8
remoteImagesAllowed was a primitive boolean, and only the three endpoints that fetch a whole message ever assign it. The folder listing does not — answering it per row would mean a consent lookup for every message in the page — so every envelope went out saying false. Not "external images are blocked for this member", but "nobody asked", encoded as a definite no and identical on the wire to a real one. Nothing downstream could tell those apart, and the reading pane acted on the wrong one: it paints a cached body before its message fetch resolves, built from the list row, so a member who had allowed images everywhere got the security prompt on every message they opened and watched it withdraw a split second later. The client-side fix that shipped alongside this stopped the pane trusting the row, which cured the symptom. This is the reason it was there to trust. Boxed, so null means not established. The three full-message paths still answer true or false and the client still acts only on an explicit false, so nothing changes for a message anyone has actually asked about. Bean is EmailService-local and had no getter callers, so the Lombok accessor rename reaches nothing. The test is trivial on purpose: un-box the field and the getter it calls stops existing, so the build fails before anyone has to notice the flicker again.