Hi How are you going to use the extra information you wish to store and how is it going to get into the database? Aren't you going to have to write a new application for this, be it James Mailets or more?
Assuming this is true, you would be best of creating your own DB tables for each use-case keyed off the same keys that the James' tables use for associated entities, such as user. This way, you are not tightly coupled to James' schemas which may change between versions. If your application requires access to both the data that James holds for an entity and the data that your custom table holds, create a view that encompasses data from both. When faced with this scenario, people often go for the hackier route of extending James' table definitions. This is not good practise, guaranteeing you upgrade pain and rework whenever James (or any other application) changes its schema definitions. If you step back a level from implementation to what you are trying to achieve, the group maybe able to advise on existing solutions that meet your requirements. Cheers -- Steve Hillel Bilman [mailto:[EMAIL PROTECTED] wrote on: 25 November 2008 00:28 > Hi, > > We are using Postgresql and require to store each of the > users details in > Postgresql. > From the URL http://james.apache.org/server/2.3.1/using_database.html > It shows how to store the spool and users' messages in a database. > > How do you store the user's details such as their username, > password and any > forwarders (in some cases we forward mail from one user to > another email > address) in the Postgresql database? > > Thanks > > > --------------------------------------------------------------------- > 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]