Bug 133097 - SRV records should be used to find the Jabber server
Summary: SRV records should be used to find the Jabber server
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 136229 162758 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-08-27 23:19 UTC by Bernhard Schmidt
Modified: 2009-10-04 00:11 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Schmidt 2006-08-27 23:19:46 UTC
Version:           0.12.2 (using KDE KDE 3.5.4)
Installed from:    Ubuntu Packages
OS:                Linux

Jabber clients should use SRV lookups to locate their servers. In my case my Jabber-ID is equal to my mailaddress (berni-at-birkenwald.de). birkenwald.de has no A/AAAA record (and even if it had, it would point to my webserver to support http://birkenwald.de, not to the jabber server). The standard way of a Jabber client would be to use the SRV record _xmpp-client._tcp.domain to locate the server

$ dig -t srv _xmpp-client._tcp.birkenwald.de +short
5 0 5222 vs02.svr02.mucip.net.

$ host vs02.svr02.mucip.net
vs02.svr02.mucip.net has address 83.170.6.69
vs02.svr02.mucip.net has IPv6 address 2001:1b10:1000:0:2aa:ff:fe00:202

At the current state of Kopete I have to override the default server information in Kopete. Similar issues arise when using Kopete with GoogleTalk, as they use the same method to find the chatserver. At the moment you have to enter talk.google.com manually.
Comment 1 Matt Rogers 2006-10-28 06:13:15 UTC
*** Bug 136229 has been marked as a duplicate of this bug. ***
Comment 2 Dennis P. Nikolaenko 2007-06-04 13:15:28 UTC
*** This bug has been confirmed by popular vote. ***
Comment 3 Matt Rogers 2008-07-11 04:33:00 UTC
*** Bug 162758 has been marked as a duplicate of this bug. ***
Comment 4 Marcel Schaal 2008-10-01 22:38:29 UTC
Come on guys. The bug is older than two years and haven't been fixed yet. It also affect kopete in kde 4.1.1 (0.60.2). Is any kopete-developer using Jabber?
Comment 5 Andreas Pietzowski 2008-10-02 01:18:35 UTC
You have my full agreement. It would really be nice to see that basic jabber feature implemented in the near future. Pleeeeaaaase :-)
Comment 6 Marek Siller 2008-12-17 22:50:52 UTC
Hi,

I've tried to fix this bug and implement an SRV DNS lookup for Jabber protocol in Kopete. However, for my implementation, I used an external library Ruli  (http://www.nongnu.org/ruli/). This way, the implementation is much simpler than to write a custom SRV lookup library; but I'm not sure, whether it is acceptable for Kopete being dependent on a external library. Could someone from Kopete developement team comment on this issue? In case, the implementation using Ruli is acceptable, I would paste my patch here (after running some tests), in other case, I would try to write a custom resolver (unfortunately QDns or Q3Dns class has been marked deprecated since Qt4).

Best regards,

Marek
Comment 7 Andreas Pietzowski 2008-12-18 00:24:31 UTC
Did you ask the author of Ruli for an integration? Maybe those developers are happy when someone integrates it into a real featured application like kopete...

Just an idea?
Comment 8 Detlev Casanova 2008-12-18 12:42:03 UTC
That's not a good idea as after the next update of our local copy of Iris, that will be directly supported by Iris. I think Olivier is currently working on that.
Comment 9 Igor Tarasov 2009-01-28 06:30:05 UTC
Why not using Q3Dns while Qt4 would get full dns functionality? PSI uses Q3Dns, and works well with SRV records.
Comment 10 radious 2009-08-07 21:56:40 UTC
After more than half of a year after last comment bug still exists. Do developers even plan adding the SRV lookup?
Comment 11 Detlev Casanova 2009-08-07 22:27:05 UTC
Kopete now supports SRV lookups.
Comment 12 Andreas Köhler 2009-10-04 00:11:42 UTC
Detlev, that sounds great. Thanks!
For reference, what version of kopete contains or will contain the fix?