Handling of base64 encoded body for message/rfc822

Question

As I understand the mime spec allows only "7bit", "8bit", or "binary" for the body of a "message/rfc822" entity
However, it looks like Outlook is generating these under some circumstances (I have supplied a sample below). When attempting to read these via the JavaMail API the message content is empty and instead ends up in the header fields.
Is there a workaround or setting to handle these base64 RFC822 attachments in JavaMail?
Here's a stripped down sample of the message with the RFC822 attachment that I'm trying to handle:
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-Type: multipart/mixed; boundary=00235400e66249e8d9047d9b2ab3
--00235400e66249e8d9047d9b2ab3
Content-Type: multipart/alternative;
     boundary=00235400e66249e8cf047d9b2ab1
--00235400e66249e8cf047d9b2ab1
Content-Type: text/plain;
     charset=iso-8859-1
Content-Transfer-Encoding: 8bit
... [plain text version of message]
--00235400e66249e8cf047d9b2ab1
Content-Type: text/html;
     charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
... [html version of message]
--00235400e66249e8cf047d9b2ab1--
--00235400e66249e8d9047d9b2ab3
Content-Disposition: attachment
Content-Type: message/rfc822
Content-Transfer-Encoding: base64
UmVjZW...
--00235400e66249e8d9047d9b2ab3--

Answer 1

Thanks for the info and suggested workaround. Would be neat to have a configurable option in 1.4.4 since info on the web suggests there are other email systems generating this rubbish.
The customer who generated the emails is using Outlook 2007 with the Google Apps Sync for Outlook. I haven't been able to replicate in Outlook 2007 so might be related to the connector. I'll do some more testing before reporting the problem to the appropriate organization!