Hello Jason, James has a modular design and you should be able to do that. I gave a presentation about James and maybe you can find more stuff there [1].
You should be able to write a Mailbox implementation (see James Mailbox [2] sub-project) that accesses your custom back-end. Then you can plug in your custom implementation inside James App [3] (Spring based app that assembles a full working server from all components). I think James App can give you a good overview of how components interact since all main components are exposed as beans. I'm working on making James available in Apache Karaf [4] but that's a long way from being usable right now. Good luck and please share more about your use-case. Cheers, [1] http://berlinbuzzwords.de/sessions/apache-james-more-emails-cloud [2] http://james.apache.org/mailbox/index.html [3] http://svn.apache.org/repos/asf/james/app/trunk/ [4] https://github.com/ieugen/james-karaf On Fri, Nov 30, 2012 at 12:51 AM, Trieu, Jason T <[email protected]> wrote: > Hi all, > > We have a custom message/mail repository that we need to provide IMAP4 access > to. From my research so far, James seems to be a good candidate for us to > use as the IMAP4 layer with us providing the implementation to handle > translation between IMAP4 and our repository. Is my understanding correct? > Can James be "customized" for this? > Also I am trying to understand the architecture of James 3.0 but I can't read > the current Technical Architecture diagram > (http://james.apache.org/server/3/dev.html). The font is just too small even > when I enlarge the diagram. Is there other sources where I can get this > document? Any other sources for information on James 3.0? I am trying to > get some good understanding of the design/architecture to figure out where to > drop in our custom classes. > > Thanks in advance. > > Jason. -- Ioan Eugen Stan / CTO / http://axemblr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
