Yeah, I am doing that. Looking at the source for MimeMessageWrapper however, saveChanges loads the message cache if it hasn't already and calls saveChanges on that. As the header cache is never updated, the save makes no difference...
-----Original Message----- From: Steve Brewin [mailto:[EMAIL PROTECTED] Sent: 26 November 2003 09:54 To: James Users List Subject: RE: LOTS of MimeMessageWrapper issues... bugs? Neill Robbins wrote: > > However, my original point still remains. The MimeMessageWrapper > appears to be inconsistent with respect to which functions it updates > the internal header cache for and which it doesn't. I don't see that > there is any particular reason why there should be a difference > between the set functions which do update the header cache and those > that don't... Are you calling MimeMessageWrapper.saveChanges()? This is a requirement of the JavaMail API to write everything back to the message. -- Steve - - - - - - - - - - - - - - - - - - This private and confidential e-mail has been sent to you by Synergy Systems Limited. It may not represent the views of Synergy Systems Limited. If you are not the intended recipient of this e-mail and have received it in error, please notify the sender by replying with "received in error" as the subject and then delete it from your mailbox. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
