I'm thinking of setting up an address-book on my server, but I'm not sure whether to use LDAP or MySQL.
As I see it, LDAP is actually designed for this, and seems to have a more-or-less standard address-book format. On the other hand, I'm already using MySQL for several things, eg gallery2.
But there doesn't seem to be any standard address-book format for SQL. Another thing, kmail and other mail clients seem to have standard LDAP interfaces.
I don't really like LDAP, but it seems the way to go. Is that right ... ? I'd be interested to hear your views.
I just installed a ldap address book last week, I will no go into the detail of how pain fule the configuration was, information in a simple human way is difficult to find but I would definetly recommend LDAP, since it is more (easy) to integrate into a email reader, by putting easy in brackets I do mean in brackets, evolution is not to bad but it does things in a really stupid way, I.E it don't remember the Manager password so the user that needs access to writing into the ldap needs to know it, do I suspect that you could get around it by creating a ldap user with write access to your tables, I have never tried mysql for only a address book but I would not recommend it since mysql is generally after my opinion slower and the email readers don't really support it, if you need some pointer let me know I am going to write my little how to at some stage now on how to set it up.
Kind regards Per Qvindesland
Timothy Murphy wrote:
I'm thinking of setting up an address-book on my server, but I'm not sure whether to use LDAP or MySQL.
As I see it, LDAP is actually designed for this, and seems to have a more-or-less standard address-book format. On the other hand, I'm already using MySQL for several things, eg gallery2.
But there doesn't seem to be any standard address-book format for SQL. Another thing, kmail and other mail clients seem to have standard LDAP interfaces.
I don't really like LDAP, but it seems the way to go. Is that right ... ? I'd be interested to hear your views.
Per Qvindesland wrote:
I just installed a ldap address book last week, I will no go into the detail of how pain fule the configuration was, information in a simple human way is difficult to find but I would definetly recommend LDAP, since it is more (easy) to integrate into a email reader, by putting easy in brackets I do mean in brackets, evolution is not to bad but it does things in a really stupid way, I.E it don't remember the Manager password so the user that needs access to writing into the ldap needs to know it, do I suspect that you could get around it by creating a ldap user with write access to your tables, I have never tried mysql for only a address book but I would not recommend it since mysql is generally after my opinion slower and the email readers don't really support it, if you need some pointer let me know I am going to write my little how to at some stage now on how to set it up.
Thanks for your reply. I think I will follow your advice, and go with LDAP.
I've been reading chapter 20 of "Linux Home Server HOWTO", "Shared Address Book (LDAP)", by Miles Brennan <brennan.id.au>, at http://www.brennan.id.au/. This seems to contain fairly explicit instructions for setting up LDAP and adding an address book.
I'll contact you if I do meet any problems, thanks.
Timothy Murphy wrote:
I'm thinking of setting up an address-book on my server, but I'm not sure whether to use LDAP or MySQL.
As I see it, LDAP is actually designed for this, and seems to have a more-or-less standard address-book format. On the other hand, I'm already using MySQL for several things, eg gallery2.
But there doesn't seem to be any standard address-book format for SQL. Another thing, kmail and other mail clients seem to have standard LDAP interfaces.
I don't really like LDAP, but it seems the way to go. Is that right ... ? I'd be interested to hear your views.