Just hasy guess, you asked: > Why hasn't the method updated the message
MimeMessages from MailImp are stored to stream repository by means of MimeMessageWrapper, while other content of MailImpl is stored to object repository. Check the AvalonMailRepository where "magic" happens. So when you modify MimeMessage (i.e. stream) your modifications may not be saved to storage (stream repository). Check how boolean variable "saveStream" variable is set in AvalonMailRepository around lines 180-190... Though I may be wrong. Best regards, Andrei PS would appreciate if someone will pay attention to my today's questions about James and TLS... ----- Original Message ----- From: "Samuel Sadek" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 14, 2002 10:40 PM Subject: Fwd: Re: Matcher/Mailet Library > I would appreciate it if anyone can provide some useful input into this > issue. > > Thanks, > > Sam. > > > >From: "Samuel Sadek" <[EMAIL PROTECTED]> > >Reply-To: "James Users List" <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Subject: Re: Matcher/Mailet Library > >Date: Tue, 14 May 2002 18:56:45 +0100 > > > >Noel, > > > >I have successfully reformatted the body attachment message, and have used > >the Mail.setMessage(MimeMessage) method to modify the original multipart > >message content. When I then referred to the actual file content it still > >had the body attachment line length of 60? Why hasn't the method updated > >the > >message content with the newly recreated version with the 76 line length > >reformat using the mentioned method? > > > >Please find the following mailet which does the actual reformatting: -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
