JID resource strings are case sensitive and should not be forced to lower case (patch supplied)
|Reported by:||logan@…||Owned by:|
|IRC client+version:||Client-independent||Operating System:||Public server|
Some jabber server implementations do case sensitive matches against the resource string at the end of a JID. The jabber_normalize function in jabber_util.c converts the entire JID including the resource string to lower case. The result being that with some jabber IM server implementations you can receive IMs with bitlbee but can't reply because the recipient resource string has been forced to all lower case.
I'm definitely not a jabber expert but it seems from a quick glance at the standards that the resource strings should be case sensitive. The jabber 2008 standards reference RFC3920 which in appendix D defers JID case sensitivity discussion to JEP/XEP-0029 "Definition of Jabber Identifiers (JIDs)". Section 2.4 of that document says "Resources identifiers are case-sensitive and are limited to 256 bytes."
If it saves any time, I've attached a patch (patch -p0 < jid_preserve_resource_case.diff) that fixes the problem for me.
Thanks for a very useful tool.