Short version: I tested the new package and it fixes the bug. I will change the tag.
Adrien, thanks for creating the package and completing my initial bug report! Colin, thanks for the advice. This is what I did in detail: I reproduced the bug with ejabberd=2.1.10-2ubuntu1 (current precise version) and Pidgin 2.10.6. (Setup: jabber server with virtual hosts jabber.example.com and jabber.example.org. jabber.example.com SRV sends the XMPP client to jabber.example.com. jabber.example.org SRV sends the client to jabber.othername.com. Both jabber.example.com and jabber.othername.com go to the same jabber server. The bug was: Login with pidgin is possible for jabber.example.com, but not for jabber.example.org.) Then I installed ejabberd=2.1.10-2ubuntu1.1 from precise-testing. Login is now also possible for jabber.example.org if the newly introduced "fqdn" setting matches the SRV record (here: jabber.othername.com). As far as I can see, this is how the patch is supposed to work (cf. https://support.process-one.net/browse/EJAB-1529). Therefore, the bug is fixed by the new package. (The default value of the "fqdn" setting is the system hostname(1), which did not match jabber.othername.com in my case.) I did the following tests for regressions: Login to jabber.example.com (to which login was possible previously) works as before. It is not affected by the value of the new "fqdn" setting. Interaction with other Jabber servers (gmail.com, gmx.de) works as before. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048634 Title: Login issue with Pidgin using SRV records To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1048634/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
