Hi there, I would advice you to have a look at the mailbox-api or mailbox-store libraries which are used by the upcoming james release. We already havea lot of implementations in trunk so you can have a look how you can implement your own mailbox storage.
The mailbox-api can be seen as low-level api for building up custom mailboxes. The mailbox-store library is more like a high-level api. Most times the mailbox-store is the way to start of (its just easier and works out well for most needs). Have a look here: https://svn.apache.org/repos/asf/james/imap/trunk/ Feel free to come back to use if you have questions. Bye, Norman 2010/9/30 Eric Charles <[email protected]>: > Hi, > > You can implement your own mail/user repository. This is introduced in > http://james.apache.org/server/2.3.1/repositories.html for James 2.3. > > For James 3, you can implement your own mailbox store. > Because of IMAP, the implementation in James 3 is more complex than in James > 2.3. > > An alternative would be to implement your store in the James 2.3 way, and > migrate it to James 3 (when the migration tool will be available). > Or another alternative would be to migrate your database schema to the James > 3 schema. > > Tks, > > Eric > > > On 30/09/2010 17:46, iceball12 wrote: >> >> We have an application with email embedded without using any standard >> email >> server or protocol (pop3/imap). >> >> However we now do need these email boxes to be accessible true imap/pop3 >> for >> mobile phones and standard web mail clients. >> >> Is it possible to create extention to james to expose these boxes (which >> are >> on different email domains) on the existing oracle backend? >> > > > --------------------------------------------------------------------- > 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]
