Closed Bug 653320 Opened 15 years ago Closed 15 years ago

Linux ldap query fails: logging shows query issued for "mailNickNane" - typo?

Categories

(Thunderbird :: Address Book, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: proc.kmem, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.16) Gecko/20110322 Fedora/3.6.16-1.fc14 Firefox/3.6.16 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9 Running: Thunderbird 3.19, querying ldap for email address lookup. Identical config works fine on MS Windows platform. Ldap server query for email adddress returns "Ldap Server Search Problem" Turned on NSPR_LOG_MODULES="ldap:5,timestamp" Extract from log: 2011-04-28 01:15:13.525631 UTC - 118229376[7f7206e11040]: nsLDAPOperation::SearchExt(): called with aBaseDn = 'dc=<dc info removed>'; aFilter = '(&(&(objectclass=*)(mailNickNane=*))(|(cn=haes**)(mail=haes**)(sn=haes**)))', aAttrCounts = 2, aSizeLimit = 100 The correct LDAP attribute is "mailNickName"? Seems to be a straightforward typo. Reproducible: Always Steps to Reproduce: 1.Set up ldap query for email with correct dc, port numbers 2.Turn on logging 3.Create email to user not in the address book to generate an ldap query. Actual Results: Logging shows line above Expected Results: Returned an email address as part of an ldap query Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9 Fedora 14 x86-64
Have you checked your preferences? Especially the ldap_2 ones? We don't have anything starting mailNick in the code base which makes me think this is an issue in your preferences or with an extension that you have installed.
Hi Mark, thank you for your reply. You are entirely correct - I had a grep through the preferences and the ldap query string was bogus. Thanks for your time, and please close the ticket - it's a non issue.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.