Bug 3729 - Use unicode instead of cp1251 in ldap queries
Summary: Use unicode instead of cp1251 in ldap queries
Status: NEW
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI/Address Book/LDAP (show other bugs)
Version: 3.14.1
Hardware: PC Windows 7
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2016-11-15 18:12 UTC by ilya-valeev
Modified: 2017-06-19 14:25 UTC (History)
1 user (show)

See Also:

Attachments
LDAP Query (88.44 KB, image/jpeg)
2017-06-19 14:17 UTC, Urfin 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description ilya-valeev 2016-11-15 18:12:26 UTC 
LDAP using fails in our network because Claws Mail uses cp1251 instead of unicode in LDAP queries. Searching in LDAP addressbook fails with error:
> Error searching LDAP
or some similar error. If it does matter, Thunderbird 45.4.0 and Seamonkey 2.40 interacts with LDAP server properly.

Windows 7 SP1 x64, Claws Mail 3.14.1 x64.
Comment 1 Urfin 2017-06-19 14:17:53 UTC 
Created attachment 1760 [details]
LDAP Query
Comment 2 Urfin 2017-06-19 14:21:44 UTC 
I have the same problem. I enclose a screenshot of the query. It is visible, that klavs mail tries to send windows-1251 request in the encoding utf-8.
Can I set the encoding of the LDAP query filter?
Comment 3 Urfin 2017-06-19 14:23:29 UTC 
I have the same problem. I enclose a screenshot of the query. It is visible, that klaws mail tries to send windows-1251 request in the encoding utf-8.
Can I set the encoding of the LDAP query filter?
Comment 4 Urfin 2017-06-19 14:25:54 UTC 
I have the same problem. I enclose a screenshot of the query. It is visible, that claws mail tries to send windows-1251 request in the encoding utf-8.
Can I set the encoding of the LDAP query filter?
Note You need to log in before you can comment on or make changes to this bug.