To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=114760
                 Issue #|114760
                 Summary|LDAP - mailnews.js - no mapping
               Component|Database access
                 Version|OOo 3.2.1
                Platform|PC
                     URL|
              OS/Version|Windows XP
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|none
             Assigned to|dbaneedsconfirm
             Reported by|thomasjf





------- Additional comments from [email protected] Sun Sep 26 17:13:09 
+0000 2010 -------
Hi,

using OpenLDAP I can get access to LDAP adress book in OO. Because there are
only some fields filled in OO, I changed mailnews.js to map some fields from
inetorgPerson (server-schema) like this is possible in Thunderbird (about:config
or user.js). I.e.:

pref("ldap_2.servers.default.attrmap.WorkCountry", "c,countryname");

Every change in Thunderbird is successful, but no (!) change in OO.

Meanwhile I installed the downloadable "mozilla_op20.schema" at server side
(with a little change for the new mozillaUseHtmlMail). Because of this nearly
every field (attribute) is working. 

I would also like to have the 2 missing fields ("E-Mail(2)" and "WorkCountry")
in OO. But I cannot find any way (even not with a new and in TB working
attribute "SecondMail" at serverside) to map an existing attribute in OpenLDAP
to one of this two empty fields in OO...

Regards
Thomas

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to