Bug 181481 - Kopete cannot login to gmx-Jabber servers (and probably many other servers)
Summary: Kopete cannot login to gmx-Jabber servers (and probably many other servers)
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-21 10:44 UTC by Clara Gnos
Modified: 2013-06-05 18:31 UTC (History)
12 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.11


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Clara Gnos 2009-01-21 10:44:15 UTC
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.
Comment 1 Tobias Winchen 2009-01-21 22:06:34 UTC
I don' know if it is the same bug, but I can confirm that kopete can't connect to gmx.net in todays debian lenny version:

Qt: 3.3.8b
KDE: 3.5.10
Kopete: 0.12.7

and the version shipped today in KDE4 4.1.4 (Lenny backports)

I can connect to gmx.net with Pidgin 2.4.3 and to jabber.ccc.de with both kopete versions.

Comment 2 Chris 2009-01-22 23:37:38 UTC
I also experience connection problems (unknown host) with gmx.net with Kopete  0.60.82.
Comment 3 Bernhard Walle 2009-01-24 09:21:39 UTC
Has anybody found a workaround? That bug is quite annoying for me. :(
Comment 4 Clara Gnos 2009-01-24 09:50:21 UTC
I wrote about the workaround in the bug report. Just specify xmpp-gmx.gmx.net with port 5223 in your server and port editbox and enable "Override default server information".
Comment 5 Michael Greifeneder 2009-01-25 08:21:23 UTC
Workaround works for me, too. Thanks. 
Comment 6 entwanzer 2009-01-25 11:51:41 UTC
Tried the workaround, didn't work for me. I get the message "host not found"
Comment 7 Clara Gnos 2009-01-25 11:58:02 UTC
Did you use xmpp-gmx.gmx.net or xmpp-gmx.gmx.de? 

$ host -a xmpp-gmx.gmx.net                                                                                                                                                     
Trying "xmpp-gmx.gmx.net"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47849
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;xmpp-gmx.gmx.net.              IN      ANY

;; ANSWER SECTION:
xmpp-gmx.gmx.net.       1878    IN      A       213.165.65.40

Received 50 bytes from 192.168.1.1#53 in 86 ms


Are you using gmx, 1&1 or web.de?
$ host -t SRV -c IN _xmpp-client._tcp.gmx.de
_xmpp-client._tcp.gmx.de has SRV record 5 0 5222 xmpp-gmx.gmx.net

$ host -t SRV -c IN _xmpp-client._tcp.web.de
_xmpp-client._tcp.web.de has SRV record 5 0 5222 xmpp-webde.gmx.net

$ host -t SRV -c IN _xmpp-client._tcp.online.de
_xmpp-client._tcp.online.de has SRV record 5 0 5222 gmx.net
Comment 8 entwanzer 2009-01-25 12:19:21 UTC
(In reply to comment #7)

I used xmpp-gmx.gmx.net

host -a xmpp-gmx.gmx.net
Trying "xmpp-gmx.gmx.net"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12715
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;xmpp-gmx.gmx.net.              IN      ANY

;; ANSWER SECTION:
xmpp-gmx.gmx.net.       54752   IN      A       213.165.65.40

Received 50 bytes from 192.168.1.1#53 in 91 ms

I am using gmx.
host -t SRV -c IN _xmpp-client._tcp.gmx.de
_xmpp-client._tcp.gmx.de has SRV record 5 0 5222 xmpp-gmx.gmx.net.

host -t SRV -c IN _xmpp-client._tcp.web.de
_xmpp-client._tcp.web.de has SRV record 5 0 5222 xmpp-webde.gmx.net.

 host -t SRV -c IN _xmpp-client._tcp.online.de
_xmpp-client._tcp.online.de has SRV record 5 0 5222 gmx.net.

seems to be identical to your output.
Bu still, i get a popup from Kopete "Connection problem with Jabber server xmpp... There was a connection error: Host not found"
Comment 9 entwanzer 2009-01-25 12:33:31 UTC
Found the Problem: Trailing whitespace to the server-address :)

now it works
Comment 10 Frank Sagurna 2009-01-26 23:03:50 UTC
I have the same bug, tried xmpp-gmx.gmx.net , but still the same (No trailing Whitespace)
The strange thing is, that my 1und1 account still works with jabber.gmx.de
Comment 11 Frank Sagurna 2009-01-26 23:11:16 UTC
Ah, sorry, as i am on web.de with this second account, i had to use xmpp-webde.gmx.net , so now it works with this server.
Comment 12 Frank Sagurna 2009-01-26 23:38:28 UTC
Some additional info: I had to delete the account and reenterd it, according to the info i found here:

http://meinungen.web.de/forum-webde/post/771208  (german)
Comment 13 Clara Gnos 2009-01-27 11:15:26 UTC
> Some additional info: I had to delete the account and reenterd it, according to the info i found here:

This is "Quatsch". Kopete cannot resolve the SRV dns stuff and will not doing anything useful if you delete your account...
Comment 14 Frank Sagurna 2009-01-28 22:51:56 UTC
Robert: Thanks for your "kind" post. For me it was useful to delete the account.
Before deleting it did not connect.
Comment 15 Clara Gnos 2009-01-28 23:27:12 UTC
So, lets ask the other who had success in connecting to xmpp-gmx.gmx.net by deleting his account and then readd it to kopete 0.60.82 without manually overriding the connection information.
Comment 16 Manuel Mommertz 2009-04-12 09:59:47 UTC
Same here with kopete 0.70.2 (kde 4.2.2). Unknown host if i use gmx.de, but works with the workaround.
Comment 17 Manuel Mommertz 2009-04-12 10:00:47 UTC
*** This bug has been confirmed by popular vote. ***
Comment 18 Andreas Köhler 2009-10-04 00:07:47 UTC
Q: Is this a duplicate of bug 133097?
Comment 19 Robert Gerlach 2011-02-15 10:42:03 UTC
(In reply to comment #18)
> Q: Is this a duplicate of bug 133097?

Yes. It works well if your DNS supports SRV records. But there appears no error message if not (connection silently failed).
Comment 20 Paulo Fidalgo 2012-01-26 15:31:20 UTC
I've came across this through a google search, and at the moment I'm connected with Kopete to gmx.com server. So I think this could be closed.
Comment 21 Pali Rohár 2013-05-19 10:24:11 UTC
Kopete in svn has updated xmpp libiris library. Please test Kopete version from svn if this problem is fixed.