Thanks for the response. Yeah I do want it for myself so will probably start the project regardless, as I would want to share it with other people who might need something like this too.
On the adding a complete groupware solution to DBMail that is def *not* what I had in mind. I was just asking for DBMail developer input wether it might be something of interest. Not so much for development, but to have your project integrated into another this way. It seems that there are a lot of people out there looking to completely replace Exchange these days. Many of them are familiar with Linux but not at a level where they want to devote TONs of time to getting an open mail solution working. I mention Kolab because it installs perfect in under 20 mins on a Debian system. It's really a joke. I was just thinking that an installer for a complete solution with that sort of easy might improve the DBMail install base. While DBMail is amazing, I love it, it is not a complete mail solution, and obviously not a complete groupware solution. And of course that is not the goal of the project so it makes sense. But for the same reasons the people who dont' want to take the time to piece together a system are missing out. Anyway, I have a busy month, but think I'll look into possibly starting a SF project for this if the DBMail team has no objections. Again a seperate project that just integrates DBMail with some other server software for a complete turn-key groupware solution. Thanks again for your response Arron, Kevin > I think you have two main ideas in here: > > - You want a decent groupware solution for yourself. > - You're proposing that DBMail make integration a part of > the project. > > On the first count, go for it! Any web groupware system > that supports IMAP > authentication will work out of the box with DBMail. Done. > > On the second count, I would rather not begin tying DBMail > to a single web > frontend. I am a developer of TWIG, I eat my own dogfood, > I'd rather not > have my own system become out of tree. I'm sure others out > there are using > IMP, SquirrelMail, and others -- not to mention webDBMail! > > I'm not a fan of the big cross platform (well, > cross-linux-distribution) > installers that some of these projects require. We could > contrive an > idealized set of packages that compose a DBMail > installation, but I don't > see the need for that. > > Aaron > > > On Wed, Jun 29, 2005, ""Kevin Baker"" > <[EMAIL PROTECTED]> said: > >> So this is just a idea, but thought I'd put it out >> there. >> >> Has anyone considered working on integrating DBMail + >> Postfix with egroupware? >> >> (http://www.egroupware.org/user-manual-english) >> >> Right now my primary installs are using Kolab with >> Horde. >> This makes it pretty much a complete turn-key >> email/groupware solution. Works great, but dependant on >> LDAP and Cyrus.... which are ok but not the direction I >> want. >> >> I've been looking to replace Kolab/Cyrus with >> DBMail/Custom for some time now. I just like the RDBMS >> backend concept a lot, mostly for its replication >> possibities. >> >> Anyway, eGroupware seems like a logical choice for a >> pairing in the same way that Kolab Paired with Horde. >> It >> uses MySQL/PgSQL for a backend, has webmail, calendar, >> todos, content system, about 15 apps... even palm >> syncing. >> All it is lacking is a standard email and database >> server. >> With the common db backend it seems to make sense. >> >> Anyway, if there is interest, it might be good to spin >> out >> a seperate sf project to integrate the two... with a >> simple installer like Kolab. >> >> >> Goals: >> - provide a complete groupware solution using >> application that use MySQL/Postgres as a data store. >> - focus *only* on integrating existing projects with >> no development on actual projects to keep focus. >> - make easy commandline installer >> - compat with multiple platforms (RH, Fedora, Debian...) >> >> >> Features: >> - dbmail + postfix + spamassassin + clamav >> - egroupware >> - Mysql/Pg Backend >> - custom installer (model after kolab) >> - compile dbmail >> - download install egroupware >> - maybe an apt-get type thing >> - configure replication to second server >> for hot backup >> >> Why: >> 1. The easier and more feature rich a solution including >> dbmail is, the larger the user base would be. This is >> why >> I went with Kolab in the first place. >> >> 2. The large the user base, larger the potential pool of >> developers. >> >> 3. A seperate project would also help to keep the DBMail >> focus from being deluted, while helping support for the >> project increase. >> >> >> Ok, so it's a brain dump... but I've been thinking of >> ways >> to maybe help the project. Since I am not a C developer >> I >> thought this would be a way, until I actually kick >> myself >> and actually start coding. >> >> >> Thoughts? Feel free to tell me I'm nuts, and I'll move >> onto other thoughts ;) >> >> Kev >> >> >> >> >> _______________________________________________ >> Dbmail-dev mailing list >> Dbmail-dev@dbmail.org >> http://twister.fastxs.net/mailman/listinfo/dbmail-dev >> > > -- > > > > _______________________________________________ > Dbmail-dev mailing list > Dbmail-dev@dbmail.org > http://twister.fastxs.net/mailman/listinfo/dbmail-dev >
