| Summary: | Use unicode instead of cp1251 in ldap queries | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Claws Mail (GTK 2) | Reporter: | ilya-valeev | ||||
| Component: | UI/Address Book/LDAP | Assignee: | users | ||||
| Status: | NEW --- | ||||||
| Severity: | normal | CC: | ilya-valeev | ||||
| Priority: | P3 | ||||||
| Version: | 3.14.1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Attachments: |
|
||||||
Created attachment 1760 [details]
LDAP Query
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? 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? 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? |
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.