Neil Schneider wrote:
Lan Barnes wrote:
On Thu, March 13, 2008 5:50 pm, Neil Schneider wrote:
Or use the database that was already built for this purpose, namely LDAP.
But your going to use Postgres? Talk about overkill. Actually LDAP isn't that
bad and you can probably right a nice frontend similar to GQ to put data into
LDAP. There are probably already interface tools built in TCL/TK to help you.
I'm dealing with Postgres now and I don't care for it much (I like MySQL
better). I am configuring a Postfix server for my employer that will use
AVG+ASK+local RBL and then forward filtered mail to the qmail server. (I
am stuck with qmail for now, I like it less than I like Postgres). The
Postgres server contains all customer data, including e-mail account
info (user name, domain, password, anti-spam and anti-virus settings, etc.)
Having used LDAP in the past, I think I'd prefer that, but as I am with
qmail, I'm stuck with Postgres.
For that above scenario (calendaring), I'd probably select LDAP first,
MySQL second, and Postgres last. Also, LDAP can be tied into other
system services (or rather other services configured to use LDAP) easily
and several mail clients can use it as well.
PGA
--
Paul G. Allen, BSIT/SE
Owner, Sr. Engineer
Random Logic Consulting Services
www.randomlogic.com
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
