Writable Contact Lists With Outlook and LDAP?
Snafoo asks: "Ximian Evolution allows users to set up LDAP-based shared contact lists, to which multiple users can read and write. However, my company uses MS Outlook 2002, which doesn't support writing to LDAP directories. Currently, we use a kludgy PHP front-end to the LDAP directory for entering new addresses. Short of buying Exchange, is there anything we can do to share write-enabled contact lists with LDAP and Outlook?"
Can't you write a plugin for Outlook that synchronizes the local address book (or a subfolder of it) with the LDAP directory?
Disadvantage: the contacts are also present in the address book of Outlook.
Advantage: the contacts are always available, even when the LDAP directory is not accessible (interesting for travelling users).
why not change to evolution? It looks exactly like outlook, and if you don't use excange features anyway, then why not simply use the product that meets your demands instead of one that is made by microsoft?
I'm not trolling. I'm serious. Why do people choose to use MS products when there are alternatives out there, that will meet their demands?
I usually try to use the best tool for the job - not the "I have a hammer, therefore all my problems are a nail" solution.
Yeah, I admit that this is somewhat of a flamebait, (but so was the original /. question) but that's the problem with closed source and a abusive monopoly. If MS had been forced to open all API's and file formats like some of us were hoping, you wouldn't be having this problem.
For some strange reason, people think that Outlook is a stand-alone product. This is somewhat true, but you (like the poster found out) lose most of the compelling features if you fail to use Exchange. Look mom! I have a shirt with no pants!
Some people will probably point out that you may be able to use OpenMail or Insight Server (Insight Connector?), but these are also expensive products that don't fully integrate with Outlook either. If you are going to go high-end commercial, you might as well go with exchange (but put the damn thing behind a firewall / UNIX mail relay server fer christs sakes.)
Of course typing "shared outlook contact lists" in google comes up with a page with lots of info on the subject, but I didn't see anything that exactly matched the poster's requirements. Lot's of kludgy stuff, mostly commercial, all trying to make the closed source pile of crap a little more usable.
I'm guessing Evolution wasn't considered because Evolution only runs on Linux/UNIX.
(The original poster didn't make it clear which OS his company uses, but it seems pretty improbably that everyone at his company uses Outlook 2002 on WINE/Linux)
...using addressbook and OS X server.
--Mike
Mozilla Mail/Minotaur/Thunderbird has LDAP support, and the Mozilla LDAP SDK supports write access, so it might actually work. I have used Mozilla Mail as my primary email client since April of 2000 (M15 or so) but not with LDAP. Try it, it just might work.
I am not your blowing wind, I am the lightning.
I'm ignorant of Evolution's groupware capabilities so this is probably a silly question. Our Exchange users extensively use not only shared address books but also shared folders. There is gigabytes of information stored in the shared folders. Most of it contains email messages but much is also the other Outlook/Exchange objects, like appointments, address book entries(?), and little calendars.
What can these people use that is open source, from client to server? I'd like to hear an answer from someone who actually uses shared folders, shared address books with something like Evolution--none of this conjecture and hypothetical "what if" stories that don't help anyone.
Kriston
As I see it there are a two obvious solutions:
- Use a central locked-down PAB everyone has read-access to. Updates & additions are created by users as standard address book entries and sent to a designated in-house address. Every so often in the off hours all of those files are collected and dropped into the master file (can be scripted.) Benefits are the address-book entries contain all of the Outlook set of details, will work with 3rd-party add-ins.
- Or instead of using a "kludgy PHP front-end" use a better-quality one like Twiki or Horde. If with this you move your mailboxes over to IMAP you'll have also gotten a great remote-client solution. On their desktops they can use Outlook, away from them log into the webmail client, and also use it for those shared address-book updates.
By the way, a good utility for exporting from Outlook/Exchange to vCard and vCalendar files (individual files or multiple-entry files) is the free Outpod. Written for exporting to Apple iPods it is also an easy way to transfer around address books to many applications.I don't read ACs: If a post isn't worth so much as a nom de plume to its author then I wont bother either.
" aldap is designed as a groupware, Web-based, central contact manager. It can supplement end-users' personal address books or stand alone. It includes Perl scripts to create an empty LDAP tree ready for data entry, or if you have an existing Outlook contact database, import them easily. Its features include Add Organizational Units, Add entry, Search, View, Print, Modify, Delete, VCard export, Outlook conversion tools, plenty of end user help, and more."
As the creator of aldap I can tell you there's people using it on OSX, Windows, and Unix / GNU Linux systems. A live demo is available on the the project home page.
-- I've spent 30 min of company time trying to think of a good sig. You can imagine how good my passwords are.
and it has a corba application that sync contacts in outlook to your contacts on the openexchange server.
I don't suffer from insanity, I enjoy every minute of it.
This guy wrote an Ask Slashdot so we could help him with a technical problem, and that's what we should do. The fact that this problem is caused by an abusive software monopoly and closed-source programming is just not that useful or interesting, at least not in this context.
The answer to that is that they don't want to make all their users change email clients. But the answer to that is that Outlook has so many security issues, they need to change anyway.
Bynari's Insight Server/plugin does this.
Try HTMLize and look at the instructions. I think the process can be improved much, but here's a good start!
s x/ 17303
http://www.versiontracker.com/dyn/moreinfo/maco
We have had pretty good luck with this program.
You might want to check it out and see if it works for you.
(In no way affiliated, just a satisfied user)
http://www.dencom.co.nz/gab/gab.htm