Don't write your own API!!! Yes I know that you are adept with sockets and you can code like a mofo, but that ain't no reason to waste your time!
A coupla quick Google searches led me to these pages:
Download JavaMail straight from the Java dudes...
http://java.sun.com/products/javamail/
Then learn how to do it from the jGurus...
http://developer.java.sun.com/developer/onlineTraining/JavaMail/
See? Easy!
OK, I've played with it a little more. It works GREAT! The JavaScript problems that I was having yesterday were caused by actual JavaScript problems on our pages.
So, forget what I said about it only working with KISS pages: it works for all pages. If it errors, out, it's your fault. End of story.
I highly recommend this framework for anyone who wants to develop high-quality web applications.
One often neglected task of IT programmers is the implementation of systematic testing for their code. Oh, there can never be anything wrong with my code, the IT programmer would say. Nothing ever goes wrong.
......Except when things DO go wrong. Yep. That enhancement that you deployed last night for the accounting department has come back to bite you on the ass this morning. You got 2 hours to fix the problem or else you're fired. Oh, if you had only implemented jWebUnit Testing, you would never have been tricked into this bind!
Now, it ain't perfect as a tool: if you implement JavaScript widget-heavy GUI's, jWebUnit may not understand your pages. However, if you stick to the KISS principle when designing your pages, jWebUnit will save your ass time and time again. Given, of course, that you actually write the Java test scripts for your applications.
The version that I have just implemented is 3.8.1. It takes care of a lot of the annoying, behind-the-scenes things like making HTTP requests, submitting forms, following hyperlinks, etc. So, all you have to do is hand out simple instructions in nice OO Java. For those of us who work with a little too much PHP, it is nice to find an excuse to touch Java once in a while.
So, the verdict on jWebUnit? A+ if you develop web apps with simple GUI's, and a nice empty NULL for complex apps. The reason why I am holding back from passing judgement on it is because I wanna find out how hard is is to hack around its JavaScript illiteracy first.
Benefits:
Installing Movable Type was quite a moving experience. Everything works just fine if you follow the simple 6-step instruction.
All you need is Perl running on your webserver. If you have some required packages missing Movable Type even has downloadable resources on their site to help you eliminate your deficiencies.
Drawbacks:
It really is a publishing tool built for a small group of people: don't expect to run a self-growing community with it right out of the box. Also, due to the way UNIX security works, you have to open up some security holes.