299968 - inline LDAP email search does not work, even though Address Book can find emails (subtree does not work?)

Status: RESOLVED DUPLICATE of bug 317566

(Thunderbird :: Address Book, defect)

Description

[Alexey N. Solofnenko]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050707 Firefox/1.0+
Build Identifier: version 1.0+ (20050705)

With Microsoft Exchange (5.5) LDAP directory, when BaseDN is empty AddressBook
can find emails, but inline suggestions cannot find anything.

Reproducible: Always

Steps to Reproduce:
1. point to an LDAP directory (works with Exchange 5.5)
2. leave BaseDN empty
3. search for emails in Address Book
4. start new message and start typing emails

Actual Results:  
no emails are suggested

Expected Results:  
the same emails as in address book should be suggested

Comment 1

[Mark Banner (:standard8)]

(In reply to comment #0)
> Build Identifier: version 1.0+ (20050705)
> 
> With Microsoft Exchange (5.5) LDAP directory, when BaseDN is empty AddressBook
> can find emails, but inline suggestions cannot find anything.

Reporter: do you mean BaseDN or BindDN? I have seen the problem when the BindDN is blank, if BaseDN is blank for me, nothing works at all.

Comment 2

[Alexey N. Solofnenko]

It is baseDN. Direct search in LDAP directory works, but inline - nothing is suggested.

Comment 3

[Rene Rask]

If I understand this bug correctly, I can confirm it.
Steps to reproduce:
1. Write a new email.
2. Start typing an email address into the To: field.
 type-ahead-find(if thats what its called) should now display a list of possible addresses.
3. The text turns red instead of displaying a dropdown with email.

This works with TB 1.0.7 on linux,mac and windows. It's broken on TB 1.5rc1 in linux and windows (haven't tested mac).
This was tested with a clean install of windows and TB.

Comment 4

[Mark Banner (:standard8)]

I think bug 317566 may be your problem, please can you have a look at the comments on that bug and see if they help you.

Comment 5

[George Hyman]

(In reply to comment #4)
> I think bug 317566 may be your problem, please can you have a look at the
> comments on that bug and see if they help you.
> 

I've checked the ldap_2.auoComplete and similar settings in prefs.js, reviewed 317566, and the behavior is the same.  Note that I was looking for a build with the proposed fix to 317566, but so far I don't think that fix has been accepted.

This bug may well be a duplicate of 317566

Comment 6

[Mark Banner (:standard8)]

(In reply to comment #5)
> (In reply to comment #4)
> > I think bug 317566 may be your problem, please can you have a look at the
> > comments on that bug and see if they help you.
> > 
> 
> I've checked the ldap_2.auoComplete and similar settings in prefs.js, reviewed
> 317566, and the behavior is the same.  Note that I was looking for a build with
> the proposed fix to 317566, but so far I don't think that fix has been
> accepted.

I'm going to close this as a duplicate of that bug then. I need to do a bit more work but that patch should be in by the new year hopefully. If it doesn't fix it, then please feel free to reopen this one afterwards.


*** This bug has been marked as a duplicate of 317566 ***

Comment 7

[Alexey N. Solofnenko]

Since the original bug is fixed, but the issue is still there, I am reopening this bug. The issue: address book can search by first or last name, but inline LDAP search searches only by one of them (maybe by display name).

Comment 8

[James Andrewartha]

(In reply to comment #7)
> Since the original bug is fixed, but the issue is still there, I am reopening
> this bug. The issue: address book can search by first or last name, but inline
> LDAP search searches only by one of them (maybe by display name).

This looks like bug 280219

Comment 9

[George Hyman]

The issue appears to be fixed in thunderbird 2.0 pre beta 1

Comment 10

[Mark Banner (:standard8)]

Comment 5, 6 & 9 confirm this is fixed/duplicate of bug 317566. Comment 7 & 8 are a duplicate of bug 280219. Therefore re-closing this as a duplicate of bug 317566.