Hi Csányi! On Do, 15 Nov 2012, Csányi Pál wrote:
> Paul Hoffman <nkui...@nkuitse.com> writes: > > > On Wed, Nov 14, 2012 at 09:27:46PM +0100, Csányi Pál wrote: > >> David Champion <d...@bikeshed.us> writes: > >> > >> > * On 14 Nov 2012, Csányi Pál wrote: > >> >> > so export from clawsmail in ldif? :) > >> >> > >> >> I already did it, I exported from clawsmail into ldif file. > >> >> > >> >> However I can't add this resulting ldif file into ldap server, because I > >> >> get error message: ldap_bind: Invalid credentials (49) > >> >> when I enter the admin password. > >> > > >> > That seems like an LDAP problem. > >> > > >> > However, more the point, abook can import the LDIF to its own internal > >> > database. Why do you need to load it into LDAP at all? > >> > >> Because when I'm trying to do this in Abook, I get an error message: > >> > >> File does not seem to be a valid addressbook > > > > Maybe Clawsmail is producing invalid LDIF, or maybe abook can only > > handle a subset of LDIF. Send us a (sanitized) copy or excerpt to look > > at. > > OK, here it is in this mail as attachment. > ,---- | [...] | dn: uid=343637306,SomeTag | objectClass: inetOrgPerson | cn: AAAAAA BBBBBBBB | sn: Some SN | displayName: AAAAAA BBBBBBBB | mail: aaaaaaaa...@yahoo.com `---- Looks like a bug in abooks ldif parser, since it expects fieldnames to be lowercase. You need to convert the objectClass to objectclass and then abook imports it. regards, Christian --
