Fixed: Content-Type on full message storage (RAW format)

We've fixed an issue where the Content-Type set on full message storage (RAW format) objects was inconsistent — it varied depending on the structure of each email (multipart/mixed, multipart/alternative, text/plain, and so on).

Every object stored in RAW format is a complete email — headers and body, exactly as received — so we now always set its Content-Type to message/rfc822, the correct MIME type for a stored email file. The original message's own Content-Type is still available, now included as body_content_type metadata on the stored object, alongside the existing from, to, remote_ip and helo_domain fields.

See our full message storage documentation for more on setting up storage providers.