Open Bug 332169 Opened 19 years ago Updated 2 years ago

RFE: LDAP timeout should revert to offline address book

Categories

(MailNews Core :: LDAP Integration, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: rmeden, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 If a LDAP query times out (network connectivity, host down, whatever) revert to the offline address book for the query if not a period of time. Now it just returns no results. This should be used for both auto-complete and the address book. Reproducible: Always
Related to Core bug 259095?
nope.. that bug refers to specifying a search order for multiple address books. This is about treating an inaccessable LDAP server as offline.
Assignee: mscott → nobody
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
Component: Address Book → LDAP Integration
Product: Thunderbird → MailNews Core
QA Contact: address-book → ldap-integration
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: ldap timeout should revert to offline address book → RFE: LDAP timeout should revert to offline address book
I agree with this in spirit, if Thunderbird didn't hang when using "large" offline LDAP directories as listed in bug 153228.
Can we please fix this bug already? It has been there for 8 (!) years. If you download the LDAP contact data for offline use, it is only usable after you switch TB to "offline". Otherwise, it simply says that there are 0 contacts in the LDAP directory. 1) Differentiate between "I see 0 contacts in LDAP directory", "I am online but can't connect to LDAP server" and "I am offline and therefore cannot connect to LDAP server" 2) Implement periodical automatic download of the LDAP data: "Download for offline use every X hours" 3) Set a timeout for retrieving LDAP data: "switch to offline version after X seconds"
For goodness’ sake. This when is it going to be corrected? It does not look so hard to change.
The LDAP I connect to is behind a firewall (VPN access required) I rarely access. Names never resolve because I'm not in offline mode nor accessible to LDAP server. Being in offline mode would mean I can't send/receive any mail. If LDAP can't be reached then this should use offline db to resolve.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.