Hi Jerry,
It's a common need for big mail providers, and it make complete sense
to have cold/hot storage depending on the access pattern.
There are several solutions to that problem.
One is to implement your business logic (about what is hot or cold) in
your mailbox implementation and delegate t
Using James IMAP library, I had implemented a solution where I was showing
the mails from archive in mail clients like outlook and stuff. So yes, it
is pretty much possible to do that (composite or stuff, whatever you want
to call it.)
On Wed, May 9, 2018 at 12:39 PM Rami Ojares wrote:
> I remem
I remember at some point in James' codebase there was a set of interfaces.
And if you implemented them you could fully determine how James persists
data.
In this case storing to any amount of databases with your
organisation-specific criteria would be no problem.
You would just implement the st
