Multipart/report - Missing Start Boundary - MultiPart.getContent()

Question

I am writing to you in regard to an issue that I have been facing recently, and I wanted to see if the JavaMail developers / community could provide any answers.
Does JavaMail support the multipart/report MIME specification (RFC 1892)?
The reason I ask, is that I have seen a strong correlation between errors in JavaMail and this content....
I am getting Missing Start Boundary exceptions when I execute this code on a message that has this Mime Type in it, (multipart/report)
mp = (Multipart)part.getContent();
count = mp.getCount(); // THIS IS WHAT THROWS THE ERROR
An example of this message header, would be
X-Atlas-MailScanner-From: [email protected]
Content-Type: multipart/report; report-type=delivery-status;
boundary="==IFJRGLKFGIR5607UHRUHIHD"
** NOTE HOW BOUNDARY IS SPECIFIED UNLIKE THE OTHER SECTIONS WHICH LEADS ME TO BELIEVE THE MISSING START BOUNDARY EXCEPTION **
--==IFJRGLKFGIR5607UHRUHIHD
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
--==IFJRGLKFGIR5607UHRUHIHD
Content-Type: message/rfc822
I have seen older posts that talk about other people's problem regarding this Exception; however, have not seen an abstract way for circumventing the issue.
Any insight/future development intentions/experience in dealing with this issue would be greatly appreciated.
RR

Answer 1

I'm getting the same exception on several "bounce" messages I try to access with JavaMail. I believe that some of them are flat-out wrong in their MIME encoding, as there truly is no start boundary. However, some appear to be OK and causing JavaMail to give an exception. Should this be logged as a bug?
Here's an example similar to yours (I didn't include all the received headers and several addresses are munged):
<blockquote><i>{noformat}Date: Sat, 19 Apr 2008 06:57:46 -0400
From: [email protected]
Subject: Undelivered mail
To: x
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="--TKFLZMMSbcaBDNCJdCBMaXGSRbVIAF"
--TKFLZMMSbcaBDNCJdCBMaXGSRbVIAF<br />
--> Error description:
Error-For: [email protected]
Error-Code: 5.1.1
Error-Text: No such list.
Error-End: One error reported.
--TKFLZMMSbcaBDNCJdCBMaXGSRbVIAF<br />
Content-Type: message/delivery-status
Reporting-MTA: dns; LISTS.NETSPACE.ORG
Final-Recipient: RFC822; [email protected]
Action: failed
Status: 5.1.1 (No such list)
--TKFLZMMSbcaBDNCJdCBMaXGSRbVIAF<br />
Content-Type: message/rfc822
Return-Path: <x>
X-Original-To: [email protected]
Received: from ppp91-122-170-233.pppoe.avangarddsl.ru (ppp91-122-170-233.pppoe.avangarddsl.ru [91.122.170.233]) by lists.netspace.org (Postfix) with ESMTP id 538527A53A for <[email protected]>; Sat, 19 Apr 2008 06:57:45 -0400 (EDT)
Received: from [91.122.170.233] by mx1.bne.server-mail.com; Sat, 19 Apr 2008 14:06:15 +0300
Message-ID: <01c8a226$87bfa580$e9aa7a5b@retentioncal53>
From: "x" <x>
To: <[email protected]>
Subject: The extracts of VPXL are Pueraria tuberose 75 mg, Mucuna pruriens 75 mg, Asteracantha longifolia 75 mg.
Date: Sat, 19 Apr 2008 14:06:15 +0300
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2741.2600
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2741.2600
TKFLZMMSbcaBDNCJdCBMaXGSRbVIAF{noformat}
</i></blockquote>