234666 - LDAP streetAddress should default to street

Status: RESOLVED EXPIRED

(MailNews Core :: LDAP Integration, defect)

Description

[Douglas Hammond]

User-Agent:       
Build Identifier: Mozilla Thunderbird 0.5 (20040207)

LDAP streetAddress should default to street if not present.  street and 
streetAddress are the same attribute. inetorgperson street is used instead of 
streetAddress.



Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Che Wang]

Mozilla 1.2-1.6/Thunder 0.5
openldap

I'm having the same problem where the 'streetaddress' -> 'street' =
inetorgperson.schema does not show up when querying an entry in the ldapserver.
Mozilla is asking for 'streetaddress' in the ldap logs, 'street' and 'street
address' are the same attribute with information, but Mozilla Addressbook fails
to use the information. 

I've changed attributes in the schema to reflect 'streetaddress' but that also
has not worked.

I had this error since Mozilla 1.2, revisited Mozilla 1.6/ldap hoping it would
be fixed, but hasn't yet.

Comment 2

[Stefan]

OS: WinXP
Mozilla Thunderbird 0.6a (20040419)

Have same Problem

Comment 3

[Rafael]

(In reply to comment #0)
> User-Agent:       
> Build Identifier: Mozilla Thunderbird 0.5 (20040207)
> 
> LDAP streetAddress should default to street if not present.  street and 
> streetAddress are the same attribute. inetorgperson street is used instead of 
> streetAddress.
> 
> 
> 
> Reproducible: Always
> Steps to Reproduce:
> 1.
> 2.
> 3.

We have the same problem with openldap and thunderbird 0.7.1

Comment 4

[Rafael]

I can view the workaddress field in Thunderbird using the postofficebox
atributte from ldap server.

Comment 5

[Doug Wright]

-> Core:MailNews:LDAP Integration

Comment 6

[James Lick]

The current changes proposed in
https://bugzilla.mozilla.org/show_bug.cgi?id=157925 would fix this bug.

Comment 7

[Gervase Markham [:gerv]]

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/

Comment 8

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.