[Pidgin] #1377: QQ no longer connects; appears blocked (2007.05.22 at 18:30:40 CST)

[Pidgin]

#1377: QQ no longer connects; appears blocked (2007.05.22 at 18:30:40 CST)
--------------------------+-------------------------------------------------
 Reporter:  dsobodash     |       Type:  defect
   Status:  new           |   Priority:  minor 
Component:  pidgin (gtk)  |    Version:  2.0.1 
 Keywords:                |    Pending:  0     
--------------------------+-------------------------------------------------
 Hello. There appears to be a problem with the QQ protocol plugin. QQ is
 detecting it as an old version of the software and killing it. This just
 began today, but the bug appeared in the QQ protocol plugin before when
 Pidgin was still Gaim.

 Below is the output from the debug log. I only included the relevant QQ
 section:

 {{{
 QQ: ==> [33703] QQ_CMD_REQUEST_LOGIN_TOKEN, from (QQ2006 Spring Festival
 build)
 QQ: ack [33703] QQ_CMD_REQUEST_LOGIN_TOKEN, remove from sendqueue
 QQ: <<< got a token with 24 bytes -> [default] decrypt and dump
 0000:  41 66 E9 A4 67 43 0F B7 2D A7 B8 95 2D 63 E4 9D  Afi$gC.7-'8.-cd.
 0016:  15 5F 0D FE AD 98 0C 25                          ._.~-..%
 QQ: ==> [33704] QQ_CMD_LOGIN, from (QQ2006 Spring Festival build)
 QQ: ack [33704] QQ_CMD_LOGIN, remove from sendqueue
 QQ: Decrypt login reply packet with inikey, 99 bytes
 QQ: Unknown reply code: 6
 QQ: >>> 112 bytes -> [default] decrypt and dump
 0000:  06 C4 FA B5 C4 BA C5 C2 EB D4 DD CA B1 B2 BB C4  .Dz5D:EBkT]J12;D
 0016:  DC CA B9 D3 C3 B5 CD B0 E6 B1 BE B5 C4 51 51 A3  \J9SC5M0f1>5DQQ#
 0032:  AC C7 EB B5 BD A3 BA 68 74 74 70 3A 2F 2F 69 6D  ,Gk5=#:http://im
 0048:  2E 71 71 2E 63 6F 6D 2F CF C2 D4 D8 B0 B2 D7 B0  .qq.com/OBTX02W0
 0064:  D7 EE D0 C2 B0 E6 B5 C4 51 51 A3 AC B8 D0 D0 BB  WnPB0f5DQQ#,8PP;
 0080:  C4 FA B6 D4 51 51 B5 C4 D6 A7 B3 D6 BA CD CA B9  Dz6TQQ5DV'3V:MJ9
 0096:  D3 C3 00                                         SC.
 QQ: Try extract GB msg:
 您的号码暂时不能使用低版本的QQ，请到：http://im.qq.com/下载安装最新版的QQ，感谢您对QQ的支持和使用
 account: Disconnecting account 0x8161dd0
 connection: Disconnecting connection 0x886f488
 QQ: 0 packets in sendqueue are freed!
 QQ: 0 group packets are freed!
 QQ: 0 groups are freed
 QQ: 0 add buddy requests are freed!
 QQ: 0 info queries are freed!
 QQ: 0 qq_buddy structures are freed!
 connection: Destroying connection 0x886f488
 }}}

 To be sure this wasn't simply a single server lockout, I attempted
 connecting to the following servers with Pidgin. All of the returned the
 same output as above:

 {{{
 219.133.48.103
 219.133.60.173
 219.133.49.211
 219.133.40.157
 219.133.51.160
 219.133.40.130
 219.133.38.230
 219.133.38.5
 218.17.209.42
 }}}

 Please advise.

 (Apologies for resubmitting. I did not know that Trac would interpret line
 breaks as '''not''' line breaks, and my previous log ended up unreadable)

-- 
Ticket URL: <http://developer.pidgin.im/ticket/1377>
Pidgin <http://pidgin.im>
Pidgin