Synced messages only store a plain-text extract; HTML-only emails end up empty or truncated

[fcporto-nature]

Summary

Problem
The Message object stores only a single 'text' field. For emails that only have an HTML part (common for newsletters and automated notifications, observed on roughly 2-3% of synced messages in production), this text extract is sometimes empty or severely truncated, and there is no separate HTML/raw body field available through the API to fall back on.

Proposed solution
Store (or optionally expose via the API) the original HTML body alongside the plain-text extract, so client applications built on top of Twenty's message sync can render the full content instead of a blank or partial message for this subset of emails.

Additional context
Worked around, for the subset of mailboxes with IMAP access, by fetching the original message directly from the mail server via its Message-ID when the synced text looked suspiciously short. This only works for IMAP-accessible mailboxes, not for the primary Gmail-connected account, so a portion of affected messages remain unreadable in-app.

---

This feature idea was drafted with AI assistance as part of an internal improvement-tracking workflow. It is a suggestion only — no code changes are proposed or included.

[twenty-eng-sync[bot]]

Kind: Probably a feature request. Synced HTML-only emails expose only a derived plain-text body, which can be empty or truncated, while no original HTML body is available through the API.
Severity: UNDEFINED because this requests a currently unavailable storage/API capability rather than reporting a confirmed regression.
Root-cause hypothesis (high confidence): packages/twenty-server/src/modules/messaging/message-import-manager/drivers/gmail/utils/parse-and-format-gmail-message.util.ts converts HTML through extractMessageTextWithoutQuotedHistory and assigns only the result to text, discarding the original HTML from the imported message shape.
Missing: Twenty version, reproducible sample/raw MIME structure, exact truncation examples, and step-by-step reproduction.

[BOHEUS]

@neo773