The "problem" is probably not the Javamail APIs but the SUN Javamail
implementation.
I think the problem is that JAMES doesnt use the ways around this problem.
Richs comment
(http://issues.apache.org/jira/browse/JAMES-134?page=comments#action_63254)
was absolutly right. There's no need to create a MimeMessage. And even if
you add a custom header
you dont have to load the entire message into memory by calling
saveChanges() like in the LocalDelivery-Mailet.
Another thing is that at MySQL has (had) a problem with BLOBS and streams;
this means
on loading the e-mail from the db the whole thing is in memory. So
rewritting the spool and MailImpl
to use the FileInputStream from the tmp-file the e-mail was stored in, can
solve this problem, especially
when all e-mails of a certain size are moved automatically into a FileStore
even if a database as MailStore
was specified.
Though this ideas are not new, maybe now is the best time to implement them.
MD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
