Closed Bug 240551 Opened 20 years ago Closed 19 years ago

Does not recgonize schemas (neither the unofficial mozillaOrgPerson_v0.6 or inetOrgPerson)

Categories

(Thunderbird :: Address Book, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 116692

People

(Reporter: richard.gray, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

Experimenting with the best design for an automated address book entry system,
and have been trying to work out the schema that thunderbird recognises. 

The standard inetOrgPerson populates some data (work city, phone number, display
name) but not others, (home info, work street, etc)

I found and d/led the unofficial schema
(http://bugzilla.mozilla.org/attachment.cgi?id=142856&action=view)

While it matches the fields correctly, the data still does not populate through
to the address cards displayed in thunderbird. 

So, could be a schema problem, or could be that the mappings have changed. I
trawled the forums to find any listing of the mappings, but to no avail.

see http://forums.mozillazine.org/viewtopic.php?t=52406&highlight=ldap+schema
for a further note on the inconsistencies

Reproducible: Always
Steps to Reproduce:
(In reply to comment #0)

> The standard inetOrgPerson populates some data (work city, phone number, display
> name) but not others, (home info, work street, etc)

Indeed, all fields from inetOrgPerson should be filled in.

And in particular, it would be nice to have support for multiple email adresses
in the 'mail' field of inetOrgPerson. Now it only displays the first.
Neither the inetorgperson or mozilla .6 schema populate for me either.  I think
its also important to stress that it should work with the inetorgperson schema.
 I have a directory that I query from windows, mac, and linux.  The built it mac
and windows address book use the standard inetorgperson schema.  Why should
mozilla use a proprietary one?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
The LDAP fields names are now customisable and can therefore be set up to the
schema you require. I'm therefore marking this a duplicate of bug 116692 which
implemented the change.

*** This bug has been marked as a duplicate of 116692 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.