Home/ Questions/Q 6685137
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T05:01:26+00:00

I’m not writing a mail application, so I don’t have access to all the

  • 0

I’m not writing a mail application, so I don’t have access to all the headers and such. All I have is something like the block at the end of this question. I’ve tried using the JavaMail API to parse this, using something like

Session s = Session.getDefaultInstance(new Properties());
InputStream is = new ByteArrayInputStream(<< String to parse >>);
MimeMessage message = new MimeMessage(s, is);
Multipart multipart = (Multipart) message.getContent();

But, it just tells me that message.getContent is a String, not a Multipart or MimeMultipart. Plus, I don’t really need all the overhead of the whole JavaMail API, I just need to parse the text into it’s parts. Here’s an example:

This is a multi-part message in MIME format.\n\n------=_NextPart_000_005D_01CC73D5.3BA43FB0\nContent-Type: text/plain;\n\tcharset="iso-8859-1"\nContent-Transfer-Encoding: quoted-printable\n\nStuff:\n\n            Please read this stuff at the beginning of each week.  =\nFeel free to discuss it throughout the week.\n\n\n--=20\n\nMrs. Suzy M. Smith\n555-555-5555\nsuzy@suzy.com\n------=_NextPart_000_005D_01CC73D5.3BA43FB0\nContent-Type: text/html;\n\tcharset="iso-8859-1"\nContent-Transfer-Encoding: quoted-printable\n\n\n\n\n\n\n\n\n\nStuff:
\n           =20\nPlease read this stuff at the beginning of each =\nweek.  Feel=20\nfree to discuss it throughout the week.
\n
-- 

Mrs. Suzy M. Smith
555-555-5555
suzy@suzy.com\n\n------=_NextPart_000_005D_01CC73D5.3BA43FB0--\n\n
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are a few things wrong with the text you posted.

    It is not a valid multi-part mime. Check out wikipedia reference which, while non-normative, is still correct.

    The mime boundary is not defined. From the wikipedia example: Content-Type: multipart/mixed; boundary="frontier" shows that the boundary is “frontier”. In your example, “—-=_NextPart_000_005D_01CC73D5.3BA43FB0” is the boundary, but that can only be determined by scanning the text (i.e. the mime is malformed). You need to instruct the goofball that is passing you the mime content that you also need to know the mime boundary value, which is not defined in a message header. If you get the entire body of the message you will have enough because the body of the message starts with MIME-Version: 1.0 followed by Content-Type: multipart/mixed; boundary="frontier" where frontier will be replaced with the value of the boundary for the encoded mime.

    If the person who is sending the body is a goofball (changed from monkey because monkey is too judgemental – my bad DwB), and will not (more likely does not know how to) send the full body, you can derive the boundary by scanning the text for a line that starts and ends with “–” (i.e. –boundary–). Note that I mentioned a “line”. The terminal boundary is actually “–boundary–\n”.

    Finally, the stuff you posted has 2 parts. The first part appears to define substitutions to take place in the second part. If this is true, the Content-Type: of the first part should probably be something other than “text/plain”. Perhaps “companyname/substitution-definition” or something like that. This will allow for multiple (as in future enhancements) substitution formats.

    • 0