Parsing mime message using MimeMessage seems to do nothing.

Question

I've loaded a mime message into a string, and I'm trying to parse it into a MimeMessage object, but it doesn't appear to do anything useful with it - it doesn't fail, but it just doesn't do anything!
A segment of the code:
System.out.println( "String size: " + msgTxt.length() );
System.out.println( msgTxt );
msg = new MimeMessage( session, new ByteArrayInputStream( msgTxt.getBytes() ) );
System.out.println( "Class:" + msg.getContent().getClass().getName() );
System.out.println( "Sender: " + msg.getSender() );
System.out.println( "Content type: " + msg.getContentType() );
System.out.println( "Subject: " + msg.getSubject() );
System.out.println( "Lines: " + msg.getLineCount() );
produces the following:
String size: 1425
Return-Path: <[email protected]>
Received: from cs.ucl.ac.uk by lancaster.nexor.co.uk via JANET with NIFTP (XTPP) id
<[email protected]>; Thu, 5 Jan 1995 17:46:35 +0000
To: <IETF-Announce:;>
From: [email protected]
Subject: I-D ACTION:draft-ietf-mailext-pipeline-01.txt
Date: Thu, 05 Jan 95 10:53:24 -0500
Message-ID: <[email protected] I.Reston.VA.US>
Mime-Version: 1.0
Content-type: Multipart/Mixed; boundary="NextPart"
--NextPart
Content-type: text/plain; charset="us-ascii"
A Revised Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mail Extensions Working Group of the IETF.
Title : SMTP Service Extension for Command Pipelining
Author(s) : N. Freed, A. Cargille
Filename : draft-ietf-mailext-pipeline-01.txt
Pages : 9
Date : 01/04/1995
This memo defines an extension to the SMTP service whereby a server can indicate
the extent of its ability to accept multiple commands in a single TCP send operation.
Using a single TCP send operation for multiple commands can improve SMTP
performance significantly.
--NextPart
Content-type: Message/External-body;
name="draft-ietf-mailext-pipeline-01.txt";
site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts"
Content-Type: text/plain
Content-ID: <[email protected]>
--NextPart
Class:java.lang.String
Sender: null
Content type: text/plain
Subject: null
Lines: -1
Am I missing the point here, or should it have parsed a mutipart body?
Any suggestions as to what I'm doing wrongly would be greatly appreciated.
Thanks!

Answer 1

What chance did I have - my program was adding a blank line to the msgTxt string at the beginning, and then when I'd sorted that out, my sample mime message has blank lines after each separator so of course it didn't work.
Thanks for seeing that the problem actually was the "almost invisble", which is perhaps why I'd overlooked it so many times, and why something that should have been simple, seemed to be so excruciatingly difficult!