Moving Outlook/vCards to an LDAP Address Book? 55
T-Suit asks: "I'm looking for a way to move 1000+ vCards (the result of painful consolidation after going through our sales' team personal Outlook contacts) into OpenLDAP, so that we can access them from all plaftorms. I've looked at Dawn, but its LDIF export is too crufty for ldapadd and it doesn't solve the issue of how to update those records easily, so I'd also need some kind of 'master GU' to edit them remotely. Along the way, I must say I am amazed at the lack of good LDAP-only contact manager apps for Windows, Linux and Mac OS X. Besides Evolution (which behaves strangely for me and doesn't show all the fields Outlook entries have), all 'nice' 'shared address book' tools I see are limited, web-based or rely on a SQL database. LDAP Management apps (such as diradmin) allow me to edit all fields, but are not for casual users (or available on Windows). Any suggestions on how to both import and maintain this data?"
Outlook 2003 Business Contacts Manager (Score:5, Interesting)
Sadly, you will have to wait a month or two and fork over a couple hundred bucks-- but it seems like you have those kind of resources.
Re:Outlook 2003 Business Contacts Manager (Score:2)
Re:Outlook 2003 Business Contacts Manager (Score:2)
Re:Outlook 2003 Business Contacts Manager (Score:2)
I didn't say it was easy, but it works.
Solution (Score:3, Funny)
Re:Solution (Score:1)
Also (Score:2, Informative)
Re:Also (Score:2, Insightful)
My own experience with GroupWise's LDAP tools, are the the server will abend under any kind of load above around 10 computers hitting the LDAP daemon at the same time.
About GroupWise itself:
- They lock everything up in proprietary encrypted databases, and provide only Win32 tools for administring it.
- Their email client (which is required for accessing the databa
Re:Also (Score:2)
Re:Also (Score:2)
Let's just hope they let the Ximian guys take care of it. Evolution's user interface is braindead on it's own, mostly due to religiously following MS Outlook, but at least there is a fair chance of getting work done with it.
Re:Also (Score:2)
Re:Also (Score:2)
Re:Also (Score:2)
Re:Also (Score:2)
Re:Also (Score:1)
They're moving all the client stuff onto Java, but the admin stuff is moving to web based...
GW is pretty bad but the file serving still rocks...
Re:Also (Score:2)
No (Score:2)
GroupWise can be extremely buggy, and you'll spend a lot of time retraining your Outlook users. And none of them will like the switch.
Hmmmm (Score:3, Insightful)
Even Better, (Score:3, Interesting)
SunOne vs. openldap (Score:3, Insightful)
SunOne/IPlanet/Netscape directory server has a nice gooey GUI for adding/searching/modifying. Searches can be done via web-browser...
So, just make an OU for contacts, dump the contacts in with Perl, create accounts for your salesy people and give them admin privilege of the contacts ou. It'll take a little time to get all the bugs worked out and lusers trained, but it will be functional from the start. I think.
Then you hire someone to come in and write a couple of little Perl CGI's using the PerlDap module or the variety of others available. I've been messing around with one that allows lusers to update a few of their records via Apache (perl modules CGI, PerLdap; Apache module mod_auth_ldap). Not too hard.
Re:SunOne vs. openldap (Score:2)
I spent a couple of weekends in June trying to move my family's outlook contacts to an OpenLDAP server. . . I finally gave up. There is no solution that I could find; unless I am willing to become way more conversant in LDAP than I have time to invest.
What the poster was asking for, and what I too would love to see, is a simple install-and-run solution that allows Outlook contacts
A little perl ought to do the trick (Score:2, Interesting)
use Text::vCard;
use Net::LDAP;
# remainder left as an exercise for the poster.
Ruby-Solution (Score:2, Interesting)
I made a little ruby-script (my first!), which achieves something like that.
It's far from perfect, but works for me.
download it here [fh-sw.de]
The archive containt a procmailrc, because i'm invoking it via an extra email-address. you will need ripmime
The script uses the vcard-Class from ruby-lang.org [ruby-lang.org], which is included in the archive.
LDAP Browser/Editor and LDAPExplorer (Score:2, Informative)
LDAP Explorer [unimelb.edu.au] is a decent web interface.
Re:LDAP Browser/Editor and LDAPExplorer (Score:1, Flamebait)
The way java is build, it cant match the normal windows api before the hardware is like 2x faster (my system is 2ghz). And thus one cannot expect people to use java applications yet on windows, unless one forces employees to do it.
that's simple to fix... (Score:1, Troll)
Re:that's simple to fix... (Score:1)
Been there... (Score:3, Informative)
To manage, phpLDAPadmin [sourceforge.net] is the best tool I've found so far.
Outlook, Mozilla, etc. can all access as clients.
I also recommend LDAP System Administration [oreilly.com] by Gerald Carter, though with some reservations. It provides a decent grounding in LDAP, but won't be an end-all-be-all definitive resource.
heh (Score:2)
Now away from opinion: Outlook, like most windows apps allows for COM interfaces. Perl, PHP, or heaven forbid Visual Basic have COM interfaces. It's pretty simple to use MS's helpful documentation of the Outlook COM functions to write up your own contact extraction utility. Once you have the data, it's pretty trivial to format it and/or toss it into another DB.
eGuide (Score:1)
It's a free (as in $), java servlet based white pages that works against LDAP, and all the display is done in XSLT so its very customizable.
Evolution (Score:2)
Outsource it to India (Score:3, Funny)
Of course then we have your entire contact database which we can either use for our own personal profits (legal or otherwise) or maybe we just sell it to all your competitors for a nice tidy profit. Then you will be fuxored pretty bad, but hey - at least it only cost you $10.
Re:Outsource it to India - With Real English Docs (Score:2)
Here in the US, the education
Re:Outsource it to India - With Real English Docs (Score:2)
They are not technological wizards that have backgrounds of 10 years plus diagnosing hardware / network issues and immediately recognize that 8 beeps means your motherboard is complaining abo
AddressMagic (Score:4, Informative)
We used a program called AddressMagic to convert the 7000 or so Outlook "Contacts Folder" contacts to LDIF in an attempt to get them into OpenLDAP. Much like you our efforts were in vain. Outlook's got too much crap in there that's just plain undocumented but our office staff use (categories being the biggest one).
I've been playing with Exchange4Linux [sourceforge.net] -- Crappy name but some really nifty software. Everything is stored in PostgreSQL -- everything -- This is both a good thing and a bad thing; Postgres is well up to the task, but the E4L server software is quite slow at the moment. They've written it in Python, and it talks to the proprietary Outlook connector via CORBA. Why CORBA? I dunno; it doesn't talk through firewalls worth a shit. :-(
I've successfully imported our 4000 contacts without even blinking. I also imported an additional 3.2GB of email, journals, notes and schedule data. Postgres just took it in and asked for more. This is on a server with an UW3 disk subsystem and 1G of memory.
Looking at the DB any "pure" MAPI object is stored in plain english, both by parameter name and value. Any Outlook-specific crap is stored with MAPIhexstringhere names and whatever data format Outlook uses for the data. It would be dead simple trivial to convert that into LDAP, but why bother when PostgreSQL has an LDAP frontend you can probably get working.
The nicest thing about E4L is that the Outlook guys lose zero functionality and (when completed) the IMAP, LDAP and iCAP frontends will give full connectivity to the entire OSS crowd. E4L is planning on making money selling Outlook connector licenses (which aren't that dear, really) but as I mentioned earlier, the server is 100% OSS and free (beer and libre). I realize that oGo is out there but to be honest, oGo looks enormously complex and it's written in a hideous language. I'd rather spend my time learning Python than Objective-C any day, thank you very much. E4L's got a single unified backend (PostgreSQL) which is scalable and solid, and with some more work (moving more into stored procedures, using the LDAP frontend, etc.) it will be an Exchange killer. It already works flawlessly with Outlook, as I mentioned.
Re:AddressMagic (Score:2)
This cursed limit is killing us where I work.
Thanks.
Re:AddressMagic (Score:1)
What 2G limit for email? We don't have a single email over about a couple dozen meg. Postgres stores mail attachments as large objects, which are individual files on disk. Mail headers and bodies are (this is from memory now, I may be mistaken) in a bunch of MAPI attributes.
I imagine you could get around the 2G limit by using fseek64(); you will likely have to recompile the apps you're using to make sure they use the proper seek/stat calls, and are using long longs for storing the file offsets.
Re:AddressMagic (Score:2)
Check out Turba (Score:2)
You should check out the Horde Project's Turba module. It provides contact management services that integrate with Horde's other services (such as IMP, the webmail component). Check out the page for Turba here:
http://www.horde.org/turba/
Turba can use several backends, including LDAP (which is how I have it configured). I've never tried to set Turba up standalone (I have
Re:I'm not doing your job for me. (Score:2)
OpenLDAP (Score:2, Informative)
We regularly receive a corporate address list of some 150,000 addresses.
The Exchange GAL was slowing down, so a decision was made to move these addresses to OpenLDAP.
It does the trick alright, but mapping the fields was like trial and error. The OpenLDAP forums and Google helped a lot there.
Now Outlook clients add a directory service and point it to the LDAP server. Remember to install the MS patch/registry hack else resolving addresses from the To: box will
the dodgy way (Score:3, Informative)
Export the suckers as csv/Excel
import into new favorite address app
retain users
long way but should work
Convert to an intermediate format first? (Score:3, Informative)
This should be trivial (maybe 5 lines) in perl if you know the format of the cards (spec available at http://www.imc.org/pdi/, assuming MS followed the spec
Then, you could import the one file into your new ldap database, and use whatever you want to manage it after that.
Re:Convert to an intermediate format first? (Score:2)
Re:Convert to an intermediate format first? (Score:2)
If it's running a standard database (mysql, postgresql, oracle, whatever), you could import the data directly using the db's tools.
I looked briefly at the vcard modules for perl, and at the vcard spec; it should only take a few hours to write a program to extract the data f
Ldap Tools..... (Score:2, Informative)
http://rolodap.sourceforge.net/
http://ldap-abook.sourceforge.net/
http://sourceforge.net/projects/directorymanage
vCard to LDIF (Score:1)