IMHO the current MailRepository should become a MessageRepository and only store Messages (without the Mail envelope and other informations from the Mail object not already in the MimeMessage object).
We could then add a JavamailStoreMessageRepository that allow you to use any Javamail Store as a message repository for james. We should also add a MailMessageRepository that allow you to see a MessageRepository on top of our current MailRepositories (for backward compatibility) PS: I already have done some of this work (removed MailRepository, added MessageRepository) in the 3.0 "hacked" james I currently use. Stefano > We should further distinguish between message and mail, where > message is the actual content and mail refers to the JAMES > content that includes a reference to the message. We already > do this to some extent, but if we are going to revisit the > mail repository, we might as well learn from our experiences > and clean things up. One thing that the separation of > message and mail clears up is that we can store many copies > of the mail in different user mailboxes, and one message. > When/if that message would be changed > (POP3 does not permit, but IIRC IMAP allows), then we would > copy the message and update the associated mail item. This > would also clear things up for mailet programmers, so that > they have a more clearly defined behavior, as well as improve > resource utilization in both memory and storage. > > --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
