Mark Daring wrote:
> I think the problem is that JAMES doesnt use the ways around this problem.
Patches welcomed.
> There's no need to create a MimeMessage.
You do if you want to make any changes to the message, e.g., add a footer,
and until we integrate MIME4J, you need a MimeMessage anytime you want to
parse. Generally, we use our own MimeMessageWrapper, which doesn't load the
message unless necessary.
> if you add a custom header you dont have to load the entire
> message into memory by calling saveChanges() like in the
> LocalDelivery-Mailet.
If I recall correctly, that statement is demonstrably false, and was tested
to make sure.
> MySQL has (had) a problem with BLOBS and streams;
> 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.
That wouldn't when a database is used for clustering ...
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
