Closed Bug 195325 Opened 23 years ago Closed 20 years ago

LDAP autocomplete using remote server) erratic

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bugzilla_account, Assigned: racham)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202 Build Identifier: Mozilla 5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030119 the autocomplete/search for a remote LDAP server works, but erratically. for the following examples, assume that there are two users in the remote directory whose particulars are: First = Foo, Last = Bar, email = foo.bar@mozilla.org First = Foofee, Last = Fum, email = foofee.fum@netscape.com and that the sender's account is: First = Joe, Last = Smith, email = jsmith@xyz.com 1) autocomplete partially works in the compose window To: field. -- typing "Foo" or "foo" sometimes does no autocomplete at all; sometimes shows "foo@xyz.com" on the first line followed by both matching users in the pulldown menu, as expected; and sometimes shows "foo@xyz.com" followed by a folder icon with a red checkmark labelled "LDAP server search problem". if i help it along by typing another letter or two, it usually wakes up and autocompletes correctly. -- typing "foo." (with the period) gives either the correct autocomplete or the server error. behavior varies. -- typing "Foo B" (trying to match by name instead of email) either gives the server error or BOTH entries. so it appears to be looking at the start of the email address no matter what. 2) in the Address Book window, both the Personal Address Book and the Collected Addresses can be searched by any part of Name or Email. For example, a search on "org" finds all addresses whose emails end in ".org", as expected. But for the LDAP server (which appears with a folder icon alongside the other two books in the left-hand pane), the search only matches on first name, last name, or the *beginning* of an email address. So if the user Joseph Bloggs (joe.bloggs@xyz.com) is in the LDAP directory, searching on "joseph", "bloggs", or "joe" will find him, but "joe.bloggs", "xyz", and "com" will not. 3) highlighting either Personal Address Book or Collected Addresses gives a full list of contents in the right-hand pane. user can then narrow down that list by typing stuff in the search box. but if user selects the LDAP server, nothing at all appears on the right until at least one character is typed in the search box. Reproducible: Always Steps to Reproduce: 1. set up a remote LDAP server in mail 2. fire up a Compose window 3. try using address autocomplete on some known addresses in the remote directory
Product: Browser → Seamonkey
dup of bug 194305?
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.