Hi All, Thank you very much. I have already passed the first hurdle..... Now i can start with the web interface. 1. How do i create more users ? How do i integrate it with my application ? 2. What happens if i decide not to use the database and go ahead with the folder structure to store the mails ? 3. Can any one help me out in deciding the steps involved in this ? Thanks again !!! With warm regards Hrishikesh ------------- Original Message -------------- Oki DZ <[EMAIL PROTECTED]> wrote: To:[EMAIL PROTECTED] From:Oki DZ <[EMAIL PROTECTED]> Date:Fri, 22 Jun 2001 08:08:10 +0700 Subject:Re: Mailstore Stefan Wagner wrote: > On the one hand you're perfectly right, but that's nothing special as it > would be if it is really integrated with James. Additionally you've got the > problem that you've got to store the mails after fetching them via POP3 so > you have to write them in a database or something like that. Yes, that's a problem. > So why not getting alle the mails via JDBC? It's a good idea. It would be a solution to the currently existing James POP server's performance (which I think that needs to be improved). Besides, I think that if you have a web mail that uses James' POP, it'd be a bit overboard; too much overheads: the JDBC connection, POP connection, and the storage for storing the fetched messages (where would you put them, back on the database? That'd be yet another JDBC connection). > I'm currently developing a webbased mail-client on Jetspeed and I'm also > thinking of integration with James. Make sure that the column names (well, the db schema) are not hardwired. James 1.3 would have different column names in the tables (it would be incompatible with the current James). >So I've already thought quite some time > about that. What my biggest problem is, is that James doesn't support virtual > hosts. Not every email server installation would need the virtual host feature. It's not really an issue, I think. > By the way if somebody is interested in my code, I want to release it under > the Apache Licence in a few weeks. Just let me know. That would be great. Why "a few weeks?". _Right_now_ is the right time. I already have quite many users complaining about the performance of the mail server; POP time-outs, SMTP connections that seemingly "hang". A JDBC-direct web mail application would really be a cure for the existing James POP server's implementation problems (I use 1.2.1rc2). The web app could make the migration to James 1.3 smoother; say, you have the latest version of the mail server, then you could connect the web app to the 1.2's database and let the users read their email from the previous version's database. Their POP connections, would be set to connect to the new James POP server. By doing so, all the messages could be retrieved. If the 1.2's mailboxes are empty, then the web app would be set to connect to the new database. Oki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _____________________________________________________ Buy Lagaan & Yaadein music for 30% less. Avail this special offer at http://shopping.rediff.com/shopping/music/offerrediffmailer.htm --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
