> I agree with your observation about the extra load from using MimeMessage. > But where/how do you want to remove the usage of MimeMessage, and what > alternate approach would you use? Maybe add an extra method on > MailImpl to > retrieve the message header/body data as a stream? I don't understand why any of the core features of James need to access any of the Mime information fo the messages, surely headers and body are all that James shoudl be interested in? If someone can help me understand what parts, and why, then I could perhaps suggest how to avoid it, I'll take a look later. d --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
- [VOTE] Remove model attribute from MailRepositories Charles Benett
- Re: [VOTE] Remove model attribute from MailRepositor... Serge Knystautas
- Re: [VOTE] Remove model attribute from MailRepositor... Harmeet
- RE: [VOTE] Remove model attribute from MailRepositor... Danny Angus
- Re: [VOTE] Remove model attribute from MailRepositor... Serge Knystautas
- Re: [VOTE] Remove model attribute from MailRepositor... Harmeet
- Re: [VOTE] Remove model attribute from MailRepositor... Peter Donald
- RE: [VOTE] Remove model attribute from MailRepositor... Danny Angus
- Re: [VOTE] Remove model attribute from MailRepositor... Danny Angus
- Re: [VOTE] Remove model attribute from MailRepositor... Serge Knystautas
- RE: [VOTE] Remove model attribute from MailRepositor... Danny Angus
- Re: [VOTE] Remove model attribute from MailRepositor... Serge Knystautas
- Re: [VOTE] Remove model attribute from MailRepositor... Harmeet
- Re: [VOTE] Remove model attribute from MailRepositor... Charles Benett
