Closed Bug 105256 Opened 24 years ago Closed 24 years ago

LDAP server settings do absolutely nothing in Mozilla

Categories

(MailNews Core :: LDAP Integration, defect)

x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: bugz, Assigned: srilatha)

Details

I have set up an LDAP entry in the "Adressing" section of Mozilla's mail settings. This LDAP server is not consulted by the Mail client at any time. It doesn't show up in the "Address Books" either. Also, when "editing" the LDAP server entry, the "FIND" button is greyed out. Basically, the whole LDAP functionality of Mozilla's Mail portion does not seem to function. I have tried this in both Windows 98 and Linux versions. Same result. :(
Hi, Could you explain a little bit more detailed. What does not work 1) if you start the mozilla mail client - press New Msg and than type a part (at least 4 characters) of a recipient's name in the 'to' - field it does not get autocompleted ? 2) If you open the 'Address Book' client you don't see your server there? If it is 2) please have a look at http://mozdev.org/ftp/pub/sun/SummaryPatchII.txt . In addition to that please also have a look at bug http://bugzilla.mozilla.org/show_bug.cgi?id=100957 . I gave there some hints how you actually get back some results from the LDAP server. If it is 1) I think the 'find' function for the base dn isn't implemented yet. But can you re-check if you don't have any typos in your server name or base dn. If your problem is solved by one of my two possibilities, please close your bug. Cheers Roland
the only place where the LDAP setting currently in Mozilla is gonna show up, is when you're composing mails. so when you're composning a mail try to just type b and wait a few seconds. Then the LDAP search is gonna set in. so this bug is kind of invalid
Marking this bug as Invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
v
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.