omldapsync, change to user details via openldap

[buggycode]

Hi

My first post to this forum!

We, (our compnay), have managed to get out Scalix 11.x server going live today. Users sucessfully authenticate via and external LDAP server (OpenLDAP), and the same LDAP server is used to create mail box and basic user info for the Scalix server.
Inforatmation that is imported includes UID, Display Names and mail address.
Here is the issue I stumbled over today (and last year with version 10)
An entry in the LDAP server for person X was used to create an original mail box. After the mail box creation, a situation arose where the LDAP entry for person X had to be removed, and re-imported.
After performing and omldapsync (aggreement 13), the changes to the LDAP entry caused the scalix server to generate and error message to the effect the the user already existed and that no infomation about this person could be found with a Global ID of xxxxxxxx.
Apart form the entire LDAP entry have been re-imported, the only item I changed where the password and the SN field (mapped to Surname in Scalix).
Why is this particular entry being rejected?
How can i correct this without deleting the user mail box?
If I have to recreated the Mail box, how can I safe gaurd the mail within?

Thanks
Buggy.

[buggycode]

Any ideas Anybody?

Regards,
BuggyCode

[KevinAnderson]

can you pull the LDAP entry out with ldapsearch, and post it? I suspect there's a GUID in there that will have changed, though I am not 100% certain of that.

Thanks
Kev.

[buggycode]

Hi

I am sorry I just had to get the staff members, mail box going. I tried the following:
- omdelent -e "cn=X"
- omldapsynv -i <our.cfg> option 2.
This failed to reload the user X entry
- omdelu (the X authid) - this now deleted the mailbox
- Running omldapsync as above created the "new" mailbox successfully

The error messages (prior to the above) did complain about finding nothing about the user with GUID xxxxxx.
So, is the GUID based on LDAP entries?
By removing the LDAP entry and re- importing it, can that affect the GUID on the scalix server when the OpenLDAP entry is recreated?.
Based on this behavior, how can we associate and existing authid, mailbox GUID with an openLDAP entry that had to be recreated. The user DATA in this LDAP entry identical to the one just removed.

I could probably recreate the situation on a test server.

Thanks
Buggy

[buggycode]

Sorry,

A little concerned with this issue.
How would I get access to the Scalix ldap (ldapmapper?) directly
ldapsearch?
what would the base DN be?
Is the piece of documentation that poitn me in the right directions?

Thanks again,
Buggy

[carloscs]

What I have in my ldapbrowser entry is: o=Scalix

It's working here.