Getting email content

[osterday]

I've been looking through the JBoss Mail Server source, but haven't figured out how I can parse the content from the MailBody - I've got a listener working and can save the content into an eml file that I can see in Outlook Express. I didn't see any references to javax.mail or parsing functions in the JBoss mail classes.

I realize the "client" would parse the message, but if I'm doing things "server" side, does anyone have suggestions on this? I guess I need to create a javax.mail MimeMessage, but haven't figured out how to get this working. I looked at the Flex/Flash client code, but couldn't make heads or tails out of it.

Thanks! (So far JBoss Mail Server is working out great!)

[acoliver]

Yeah the GUI doesn't do more than display verbatim ATM. This is on the docket for the next relase but right now we store it a big contiguous blob o stuff. Jason & Co have some stuff for this that we may use:

http://fisheye.jboss.com/viewrep/JBoss/webservice/src/main/org/jboss/ws/soap/attachment/SimpleBoyerMoore.java?r=1.2
http://fisheye.jboss.com/viewrep/JBoss/webservice/src/main/org/jboss/ws/soap/attachment/BoundaryDelimitedInputStream.java

We don't use the JavaMail stuff for various reasons, some addressed in the beta that was just released to open source (it used to require reading the whole thing into memory) and some not (synchronization issues in the mime stuff related to the JAF crap).

[osterday]

Andrew,

I will keep an eye on the progress with the client and how you guys handle things.

I don't know how the javax.mail api stands up performance wise, but it's somewhat easy to deal with, so I've been playing around with that and got it working. I just needed to do this:

MimeMessage mm = new MimeMessage(null,message.getRawStream());

So I was able to create a javax.mail MimeMessage and then MimeMultipart after that to get the parts I needed.

Thanks again for all the work you and the JBoss crew do!

[acoliver]

The long and short of it is that JavaMail in its present production incarnation requires the whole mail in memory and does some needless thread syncronization. If you have a low volume system with small messages...who cares. If you have a high volume system with LARGE messages or variable size messages....you're going to start caring before too long.

-Andy

[acoliver]

but to be clear, I think that is a fine way to do it so long as it performs okay for you. Just load test first.

[osterday]

Yeah, the app will be low volume for now. I'll keep my eyes out for better ways to handle scaling up.

Thanks again... the more I play around with JBCS, the more ideas open up!

[acoliver]

Thanks! :-)

[osterday]

Actually after discussing what we want our app to do, we think were going to make use of JBCS more than just handing off the content and actually using the JBCS store as part of our app's repository and going to get the content from JBCS when needed.

Since JBCS is designed to scale, we're going to make use of that - still probably going to use javax.mail when we need to parse the content, but not as part of our listener. I'll keep the forum posted on how we make out!