Closed
Description
The BODYSTRUCTURE response for MIME messages is missing the extension parameters (body parameters), and most notably thus missing the MIME part boundaries of multipart messages.
Example:
Given a simple multipart message:
From: <noreply@apple.com>
Content-type: multipart/alternative;
boundary="47969A3F-1F13-4D6C-83F5-695D4B116B14"
MIME-version: 1.0
Subject: B
Message-id: <97E2B701-346B-410C-A575-0F73CFAA2F31@apple.com>
Date: Thu, 26 Sep 2024 10:03:22 +0200
To: mail-app-test@strnmn.me
--47969A3F-1F13-4D6C-83F5-695D4B116B14
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=us-ascii
b
--47969A3F-1F13-4D6C-83F5-695D4B116B14
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
charset=us-ascii
<html><body>b</body></html>
--47969A3F-1F13-4D6C-83F5-695D4B116B14--
the server should return this BODYSTRUCTURE
4 FETCH (UID 6 BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "us-ascii") NIL NIL "7BIT" 9 2 NIL NIL NIL NIL)("TEXT" "HTML" ("CHARSET" "us-ascii") NIL NIL "7BIT" 228 0 NIL NIL NIL NIL) "ALTERNATIVE" ("BOUNDARY" "47969A3F-1F13-4D6C-83F5-695D4B116B14") NIL NIL NIL))
Note the ("BOUNDARY" "47969A3F-1F13-4D6C-83F5-695D4B116B14") part.
But mox currently returns this BODYSTRUCTURE:
* 4 FETCH (UID 6 BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "us-ascii") NIL NIL "7BIT" 9 2)("TEXT" "HTML" ("CHARSET" "us-ascii") NIL NIL "7BIT" 228 1) "ALTERNATIVE"))
Note: This boundary information should be included for all multi-part MIME parts, not just the main part’s boundary. If another multipart is nested inside the main message’s multipart, that part’s boundary information must also be present in the BODYSTRUCTURE.
Metadata
Metadata
Assignees
Labels
No labels