Well, this seems like a more complicated, but equally more useful approach.
It's probably not more complicated as much as unfamiliar.
<snip>So, I figure, I implement a transport.
Sound about right?
Yup.
Looking through the JavaMail docs, it seems the smtp settings are included in the MimeMail via session in Message. Now I'm guessing that session wont be stored if I use the writeTo method. So, the mail server config used for sending the messages will be lost?
True, you would need to store the envelope info somewhere (maybe just at top of text message). As for other session information, perhaps just stick with the same approach and store all session properties to the text file as well.
Another question: When I send mail, I am assuming that I will have to tell Session to use a different transport (going to mean messing with commons-sandbox-email because this is fixed to smtp). If I use the same session for sending mails, then I guess I will have to revert to smtp.
Hmm, I think I understand how you're thinking of doing this. I would probably just call the Sun SMTP impl directly, although by relaying on the transport rules, you could create layers of transports.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
