Closed
Bug 298396
Opened 20 years ago
Closed 19 years ago
LDAP address book not being searched during mail composition (ldap+autocomplete)
Categories
(SeaMonkey :: MailNews: Address Book & Contacts, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: david.hagood, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050620 MultiZilla/1.8.0.1m Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050620 MultiZilla/1.8.0.1m Having added an LDAP server as an address book, Mozilla is not attempting to access the server at all for any address completion or lookup actions. I have set the Prefs->Mail->Addressing->Directory server setting. I have confirmed the LDAP server is accessible using the same settings in GQ. I have confirmed that NO network traffic is being generated by Mozilla by watching with Ethereal. Reproducible: Always Steps to Reproduce: 1. Add LDAP server to Address book 2. Select LDAP server so added. 3. Attempt a lookup of a name known to be in the server Actual Results: No search results were returned. No network traffic to the LDAP server was generated. Expected Results: Mozilla should have contacted the LDAP server to attempt to perform the lookup.
Updated•20 years ago
|
Version: unspecified → Trunk
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050708 SeaMonkey/1.0a I've had a similar problem on Win XP for a few months. LDAP search in the address book stopped retrieving results; however, the address autocomplete does succcessfully search LDAP when composing a message.
| Reporter | ||
Comment 2•19 years ago
|
||
That is different than my results - neither completion nor address book lookup work. However, they work find in build 2005021712.
Thunderbird 1.5B1 (20050908) exhibits similar behaviour. I did not test with Ethereal, however using Tools, Options, Addressing, Address Auto-completion, the LDAP server was added (and checked off to be used). Look ups using Address Book are successful, however address auto-completion in the New Message composition window does not work. It also appears that if multiple Local Address Books are maintained, the only one Thunderbird appears to access for address autocompletion is the "Personal Address Book".
Comment 4•19 years ago
|
||
> Actual Results:
> No search results were returned. No network traffic to the LDAP server was
> generated.
>
> Expected Results:
> Mozilla should have contacted the LDAP server to attempt to perform the lookup.
>
Hmm, just a thought, you weren't in offline mode were you? (File->Work Offline/Online)| Reporter | ||
Comment 5•19 years ago
|
||
No, I never go offline, as I have an always-available connection, so there is no reason for me to use offline mode.
The address book search started working for me again in the SeaMonkey nightlies, a month or two ago.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051206 SeaMonkey/1.0b LDAP lookup is not working for me in either the Address Book module or the autocomplete feature in the Compose window. I have only been using SeaMonkey for a week or two, and I don't think this has worked in any of the builds I have tried yet. The same LDAp server settings are working correctly in Thunderbird. The reason the Autocomplete is not working may be related to problems in the Preferences dialog. My LDAP server is not showing up in the drop down list in the Addressing section. I've tried the "Edit Directories" button, and it also doesn't show up there. I can add directories there, and they will show up in the Address Book, but still not in the Preferences dialog.
Flags: blocking-seamonkey1.0b?
Just tested using 1.0b build 2005120805 on Win XP and LDAP is working for me both in addressbook and in autocomplete not tested on Linux though.
Have you tried creating a new profile and see if it happens there?
Comment 10•19 years ago
|
||
I got LDAP to work by copying the LDAP preferences from my Thunderbird prefs.js into my SeaMonkey prefs.js. I haven't had time to play around with settings since then to see if I can break it again.
Comment 11•19 years ago
|
||
(In reply to comment #10) > I got LDAP to work by copying the LDAP preferences from my Thunderbird prefs.js > into my SeaMonkey prefs.js. I haven't had time to play around with settings > since then to see if I can break it again. > If you've kept your old SeaMonkey prefs.js you'll be able to look at the differences - its the ldap_2.* settings that would be the interesting main ones to check for differences (and possibly any others with addrbook or address or something like that in).
Comment 12•19 years ago
|
||
This is a minor UI glitch that is even WFM for at least one developer here and might be caused by some wrong pref settings only, so not blocking Beta for this, esp. as Beta code is already frozen.
Flags: blocking-seamonkey1.0b? → blocking-seamonkey1.0b-
Comment 13•19 years ago
|
||
I think I need to make some things clear - the *original* bug is about LDAP address book *and* autocomplete not working. If it is just autocomplete refer to bug 317566 (which has a patch in progress). As it stands address book search WFM on yesterdays 1.8 trunk build: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051214 SeaMonkey/1.0b For the reporter, these are an example of my current settings, hopefully these may help in diagnosing your problem (please excuse me if you already know lots about ldap its hard to know peoples experience remotely): Name: anything Hostname: myserver.name Base DN: dc=intranet Port Number; 389 Bind DN: Advanced -> Search Filter: (objectclass=*) I'm not sure if the Advanced search filter is required, but I put it in for mine anyway. The dc=intranet is a subtree thats defined for some of my addresses. Bind DN I sometimes specify as cn=Manager,dc=intranet when I'm testing authenticated connections.
Comment 14•19 years ago
|
||
improved summary
Summary: LDAP address book not being searched → LDAP address book not being searched during mail composition (ldap+autocomplete)
Comment 15•19 years ago
|
||
Reporter, please check you have considered my comments from comment 13. In addition, we have now enabled LDAP logging on the trunk nightly builds (if its not in todays, it'll be in tomorrows). This will enable you to see what SeaMonkey is attempting to do over the LDAP connection. Information on how to enable it is here: http://wiki.mozilla.org/MailNews:LDAP_Address_Books
| Reporter | ||
Comment 16•19 years ago
|
||
It seems to have been a bad build - it is working now
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 17•19 years ago
|
||
(In reply to comment #16) > It seems to have been a bad build - it is working now Thanks, but we need to mark the bug as "Works for me", as we haven't changed anything to solve this particular problem. I'll do that now.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•19 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•