Comment 5 for bug 320528

Version: (using Devel)
OS: Linux
Installed from: Compiled sources

I tried to connect to GMX's jabber server and got the information that this is a unknown host. A quick check with PSI showed me that the server works fine and only kopete isn't able to connect.
My current version of kopete is Version 0.60.82

Further investigations showed that the first packet send to the server differs between kopete and PSI

PSI:
<?xml version="1.0"?>
<stream:stream xmlns:stream="http://etherx.jabber.org/streams" version="1.0" xmlns="jabber:client" to="gmx.de" xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace" >

Kopete:
<?xml version="1.0"?>
<stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" to="gmx.de" >

I tested it with `cat bad|nc jabber.gmx.net 5222` but both versions showed the same behavior and the server send only

<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='1839397057' from='dummyhost' xml:lang='en'><stream:error><host-unknown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error></stream:stream>

The next one was to check which server I connect to... and this seems to be the problem. Kopete connects to gmx.de (213.165.65.50) and PSI to xmpp-gmx.gmx.net

A quick check which DNS packets were send showed the really difference. Kopete asks for the ip of gmx.de and PSI asks about `host -t SRV -c IN _xmpp-client._tcp.gmx.de` (and maybe falls back if to kopetes behaviour when it fails).

See http://xmpp.org/rfcs/rfc3920.html#rfc.section.14.3 for more information about that.