Hi all,
I hope you can help me with the following, we are processing mails with james
and what we have experienced is that some (not all) mails expand wildly, by
that I mean:
A mail (a small one a few kbytes and text only) is sent and it is then
repeatedly written into the same file in spool, making this file explode to
several gigabytes in no time.
Now, we have traced this to happen at a ToProcessor shift (which makes sense
as mails are only written at that time).
Now, we are using several custom made mailets and some of these are using
constructs like:
service (Mail mail) {
MimeMessage msg = new MimeMessage(...);
...
mail.setMessage (msg);
}
That is a new MimeMessage instance is created and set on the existing Mail
instance, could this lead to the observed behaviour?. I have noticed that
none of the official mailets use this construct.
BTW this is on James 2.1.3.
regards
S�ren
--
S�ren Hilmer, M.Sc.
R&D manager Phone: +45 70 27 64 00
TietoEnator IT+ A/S Fax: +45 70 27 64 40
Ved Lunden 12 Direct: +45 87 46 64 57
DK-8230 �byh�j Email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
