[Pidgin] #11590: Can't connect to jabber

[Pidgin]

#11590: Can't connect to jabber
-----------------------+----------------------------------------------------
 Reporter:  Shnurapet  |        Owner:  deryni 
     Type:  defect     |       Status:  closed 
Milestone:             |    Component:  XMPP   
  Version:  2.6.6      |   Resolution:  wontfix
 Keywords:             |  
-----------------------+----------------------------------------------------

Old description:

> So as I thought.

New description:

 Pidgin can't connect to an account at ya.ru (username at ya.ru) neither
 yandex.ru. Deselecting SSL/TLS, sending password in open form, specifying
 explicitly the server to connect or any other workarounds do not work.

 {{{
 pidgin-privacy-please-0.6.1-1.fc12.x86_64
 pidgin-musictracker-0.4.20-3.fc12.x86_64
 pidgin-2.6.6-2.fc12.x86_64
 pidgin-libnotify-0.14-3.fc12.x86_64
 libpurple-2.6.6-2.fc12.x86_64
 purple-msn-pecan-0.1.0-0.3.rc2.fc12.x86_64
 purple-facebookchat-1.64-1.fc12.x86_64
 }}}

--

Comment(by rekkanoryo):

 The specific issue in the debug logs you've posted here is that Pidgin
 isn't able to perform a DNS query for the SRV record _xmpp-
 client._tcp.ya.ru or the TXT record _xmppconnect.ya.ru to determine what
 server to connect to, and the XMPP service is not on the same machine that
 DNS says is ya.ru.  I am able to look up _xmpp-client.... successfully,
 which indicates that this is a problem on your network (likely a cheap
 home "router" with a broken DNS implementation).  To work around this, you
 can set a connect server of xmpp.yandex.ru on the account's "Advanced"
 tab, or you can fix the problem in its entirety by identifying and fixing
 the cause of the failed SRV record lookups.

 Also, you should not have changed the ticket's description; instead you
 should have used the comment box.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/11590#comment:7>
Pidgin <http://pidgin.im>
Pidgin