[jdev] yahoo transport issues
Nathan J. Mehl
memory-jabber at blank.org
Fri Apr 23 10:39:44 CDT 2004
(Re-posting this from jadmin, where it produced no useful
suggestions.)
I'm having some weird issues with the yahoo transport, version 2.3.1,
running inside jabberd 1.4.2.
I can successfully register with the gateway with my Y! id
(memoryphd), and logging into the gateway via exodus appears to be
susccessful:
----------------------------------------------------------------------------
Tue Apr 20 16:27:19 2004 mio.c:760 MIO read from socket 7: <presence
from='nmehl at jabber.feedroom.com/Exodus' to='yahoo.feedroom.com/registered'><c
node='http://exodus.jabberstudio.org/caps' ver='0.9.0.0'
xmlns='http://jabber.org/protocol/caps'/><status>Away as a result of
idle.</status><show>away</show><priority>0</priority></presence>
Tue Apr 20 16:27:19 2004 base_connect.c:129 process XML: m:817A378 state:3,
arg:80C44F8, x:816B2F0
Tue Apr 20 16:27:19 2004 deliver.c:474 DELIVER 1:yahoo.feedroom.com <presence
from='nmehl at jabber.feedroom.com/Exodus' to='yahoo.feedroom.com/registered'><c
node='http://exodus.jabberstudio.org/caps' ver='0.9.0.0'
xmlns='http://jabber.org/protocol/caps'/><status>Away as a result of
idle.</status><show>away</show><priority>0</priority></presence>
Tue Apr 20 16:27:19 2004 deliver.c:678 delivering to instance
'yahoo.feedroom.com'
Tue Apr 20 16:27:19 2004 mio.c:607 mio while loop top
Tue Apr 20 16:27:19 2004 mtq 80C46E0 entering from pth
Tue Apr 20 16:27:19 2004 mtq 80C46E0 one call 816BC68
Tue Apr 20 16:27:19 2004 yahoo-phandler.c:335 [YAHOO] Packet type=2 subtype=12
iq=(null) iq_type=(null)
Tue Apr 20 16:27:19 2004 yahoo-phandler.c:336 [YAHOO] Packet to
'yahoo.feedroom.com/registered'
Tue Apr 20 16:27:19 2004 yahoo-phandler.c:337 [YAHOO] Packet from
'nmehl at jabber.feedroom.com/Exodus'
Tue Apr 20 16:27:19 2004 deliver.c:474 DELIVER 2:yahoo.feedroom.com <xdb
type='get' to='nmehl%jabber.feedroom.com at yahoo.feedroom.com'
from='yahoo.feedroom.com' ns='yahootrans:data' id='1'/>
Tue Apr 20 16:27:19 2004 deliver.c:678 delivering to instance 'yahoolinker'
Tue Apr 20 16:27:19 2004 mio.c:1054 mio_write called on x: 816C800 buffer:
(null)
Tue Apr 20 16:27:19 2004 xdb.c:212 xdb_get() waiting for
nmehl%jabber.feedroom.com at yahoo.feedroom.com yahootrans:data
Tue Apr 20 16:27:19 2004 mio.c:620 mio while loop, working
Tue Apr 20 16:27:19 2004 mio.c:279 write_dump writing data: <xdb type='get'
to='nmehl%jabber.feedroom.com at yahoo.feedroom.com' from='yahoo.feedroom.com'
ns='yahootrans:data' id='1'/>
Tue Apr 20 16:27:19 2004 mio.c:607 mio while loop top
Tue Apr 20 16:27:19 2004 mio.c:620 mio while loop, working
Tue Apr 20 16:27:19 2004 mio.c:760 MIO read from socket 7: <xdb type='result'
to='yahoo.feedroom.com' from='nmehl%jabber.feedroom.com at yahoo.feedroom.com'
ns='yahootrans:data' id='1'><query
xmlns='yahootrans:data'><username>memoryphd</username>
<password>********</password>
<key>***************************************</key></query></xdb>
Tue Apr 20 16:27:19 2004 base_connect.c:129 process XML: m:817A378 state:3,
arg:80C44F8, x:816D0E8
Tue Apr 20 16:27:19 2004 deliver.c:474 DELIVER 1:yahoo.feedroom.com <xdb
type='result' to='yahoo.feedroom.com'
from='nmehl%jabber.feedroom.com at yahoo.feedroom.com' ns='yahootrans:data'
id='1'><query
xmlns='yahootrans:data'><username>memoryphd</username>
<password>********</password>
<key>***************************************</key></query></xdb>
Tue Apr 20 16:27:19 2004 deliver.c:678 delivering to instance
'yahoo.feedroom.com'
Tue Apr 20 16:27:19 2004 xdb.c:52 xdb_results checking xdb packet <xdb
type='result' to='yahoo.feedroom.com'
from='nmehl%jabber.feedroom.com at yahoo.feedroom.com' ns='yahootrans:data'
id='1'><query
xmlns='yahootrans:data'>
<username>memoryphd</username><password>********</password>
<key>***************************************</key></query></xdb>
Tue Apr 20 16:27:19 2004 xdb.c:217 xdb_get() done waiting for
nmehl%jabber.feedroom.com at yahoo.feedroom.com yahootrans:data
Tue Apr 20 16:27:19 2004 yahoo-session.c:67 [YAHOO]: New session for
'nmehl at jabber.feedroom.com' from 'initial-check'
Tue Apr 20 16:27:19 2004 yahoo-session.c:76 [YAHOO]: New connection to
'scs.yahoo.com:5050' for 'nmehl at jabber.feedroom.com'
Tue Apr 20 16:27:19 2004 mio.c:527 calling the connect handler for mio object
81702B0
Tue Apr 20 16:27:19 2004 mio.c:607 mio while loop top
Tue Apr 20 16:27:19 2004 yahoo.c:1339 [YAHOO]:
'nmehl at jabber.feedroom.com/Exodus' connected to Yahoo! server. [memoryphd]
Tue Apr 20 16:27:19 2004 yahoo.c:327 [YAHOO]: Write Key: 1 Value:
memoryphd
Tue Apr 20 16:27:19 2004 yahoo.c:377 [YAHOO]: Writing 34 bytes to Yahoo!
(fd=8) state=1
Tue Apr 20 16:27:19 2004 mio.c:1054 mio_write called on x: 0 buffer: YMSG
Tue Apr 20 16:27:19 2004 mio.c:620 mio while loop, working
Tue Apr 20 16:27:19 2004 mio.c:678 socket 8 has been intialized with starting
karma 5
Tue Apr 20 16:27:19 2004 mio.c:279 write_dump writing data: YMSG
Tue Apr 20 16:27:19 2004 mio.c:607 mio while loop top
Tue Apr 20 16:27:19 2004 mio.c:620 mio while loop, working
Tue Apr 20 16:27:19 2004 mio.c:760 MIO read from socket 8: YMSG
Tue Apr 20 16:27:19 2004 yahoo.c:1366 [YAHOO]: Read 116 [0] bytes (fd=8) for
'nmehl at jabber.feedroom.com/Exodus'
Tue Apr 20 16:27:19 2004 yahoo.c:1385 [YAHOO]: 96 bytes to read, rxlen is 116
Tue Apr 20 16:27:19 2004 yahoo.c:1396 [YAHOO]: Service: 0x57 Status: 1
Tue Apr 20 16:27:19 2004 yahoo.c:302 [YAHOO]: Read Key: 1 Value:
memoryphd
Tue Apr 20 16:27:19 2004 yahoo.c:302 [YAHOO]: Read Key: 94 Value:
r-(o^n|p)&z%1&b-v-j-1%x+z%l+z+v|(e&8^y^l/5+t+8*l/d%(p|(j*4%l)/d&g*5))
Tue Apr 20 16:27:19 2004 yahoo.c:302 [YAHOO]: Read Key: 13 Value: 1
Tue Apr 20 16:27:19 2004 yahoo.c:1309 [YAHOO]: Process Auth
Tue Apr 20 16:27:21 2004 yahoo.c:327 [YAHOO]: Write Key: 0 Value:
memoryphd
Tue Apr 20 16:27:21 2004 yahoo.c:327 [YAHOO]: Write Key: 6 Value:
h=DE,R=0l,h=e1;E=al;E=iB;R=Ah,C=3D;h=c0;S=bE;T=Fl,
Tue Apr 20 16:27:21 2004 yahoo.c:327 [YAHOO]: Write Key: 96 Value:
w=mg,Q=mE;O=il,N=lB;D=nm,X=ok;E=2B;r=1l,W=9n;h=jg;
Tue Apr 20 16:27:21 2004 yahoo.c:327 [YAHOO]: Write Key: 1 Value:
memoryphd
Tue Apr 20 16:27:21 2004 yahoo.c:377 [YAHOO]: Writing 159 bytes to Yahoo!
(fd=8) state=1
Tue Apr 20 16:27:21 2004 mio.c:1054 mio_write called on x: 0 buffer: YMSG
Tue Apr 20 16:27:21 2004 mio.c:607 mio while loop top
Tue Apr 20 16:27:21 2004 mio.c:620 mio while loop, working
Tue Apr 20 16:27:21 2004 mio.c:279 write_dump writing data: YMSG
Tue Apr 20 16:27:21 2004 mio.c:760 MIO read from socket 7: <presence
from='nmehl at jabber.feedroom.com/Exodus' to='yahoo.feedroom.com/registered'><c
node='http://exodus.jabberstudio.org/caps' ver='0.9.0.0'
xmlns='http://jabber.org/protocol/caps'/>
<status>Available</status><priority>0</priority></presence>
Tue Apr 20 16:27:21 2004 base_connect.c:129 process XML: m:817A378 state:3,
arg:80C44F8, x:8171630
Tue Apr 20 16:27:21 2004 deliver.c:474 DELIVER 1:yahoo.feedroom.com <presence
from='nmehl at jabber.feedroom.com/Exodus' to='yahoo.feedroom.com/registered'><c
node='http://exodus.jabberstudio.org/caps' ver='0.9.0.0'
xmlns='http://jabber.org/protocol/caps'/>
<status>Available</status><priority>0</priority></presence>
Tue Apr 20 16:27:21 2004 deliver.c:678 delivering to instance
'yahoo.feedroom.com'
----------------------------------------------------------------------------
...and the transport certainly appears to be talking to yahoo, because it
tries to parse my buddylist:
----------------------------------------------------------------------------
Tue Apr 20 16:27:21 2004 yahoo-phandler.c:335 [YAHOO] Packet type=2 subtype=12
iq=(null) iq_type=(null)
Tue Apr 20 16:27:21 2004 yahoo-phandler.c:336 [YAHOO] Packet to
'yahoo.feedroom.com/registered'
Tue Apr 20 16:27:21 2004 yahoo-phandler.c:337 [YAHOO] Packet from
'nmehl at jabber.feedroom.com/Exodus'
Tue Apr 20 16:27:21 2004 mio.c:620 mio while loop, working
Tue Apr 20 16:27:21 2004 mio.c:760 MIO read from socket 8: YMSG
Tue Apr 20 16:27:21 2004 yahoo.c:1366 [YAHOO]: Read 500 [0] bytes (fd=8) for
'nmehl at jabber.feedroom.com/Exodus'
Tue Apr 20 16:27:21 2004 yahoo.c:1385 [YAHOO]: 834 bytes to read, rxlen is 500
Tue Apr 20 16:27:21 2004 mio.c:607 mio while loop top
Tue Apr 20 16:27:21 2004 mio.c:620 mio while loop, working
Tue Apr 20 16:27:21 2004 mio.c:760 MIO read from socket 8: ;
domain=.yahoo.com59T
z=NlYhABNrthAB2dlLbR69S28&a=QAE&sk=DAA98ycFRnRKvs&d=YQFRQUUBdGlwAVJ2UURTQgF6egFObFloQUJnV0E-;
expires=Thu, 15 Apr 2010 20:00:00 GMT; path=/; domain=.yahoo.com59C
mg=115319003memoryphd100010110293864001498f9D7nsFJLS2eqYsD1L.Pg--150AYydxt1zj1n1jhOQ_4zwrA--151_nkfgTAS3KcU69zKcqWOhA--
Tue Apr 20 16:27:21 2004 yahoo.c:1366 [YAHOO]: Read 354 [500] bytes (fd=8)
for 'nmehl at jabber.feedroom.com/Exodus'
Tue Apr 20 16:27:21 2004 yahoo.c:1385 [YAHOO]: 834 bytes to read, rxlen is 854
Tue Apr 20 16:27:21 2004 yahoo.c:1396 [YAHOO]: Service: 0x55 Status: 0
Tue Apr 20 16:27:21 2004 yahoo.c:302 [YAHOO]: Read Key: 87 Value:
Buddies:bendigegin,cecil_b_demental,dnwamadi,ihaveaboyfriend25,iwqs2000,ltgeller,nadian_blackstorm,not_a_nicegirl
Friends:deirdre_cusack,doktor_memory,nathan_j_mehl
jabber_yt:angellama2001,bouncing_soul_xxx,deirdre_cusack,doktor_memory,edyavno,kamela24,mabs_,mikey_kearns,nathan_j_mehl,peleron_2000,redragona,seattlgrrl,thagireb
----------------------------------------------------------------------------
...and yet, from the perspective of anyone actually using the real Yahoo
Messenger client, 'memoryphd' does not appear to be logged in, and I cannot
see any of my yahoo contacts as being logged in.
The behavior does not change if I change the Y! login host from scs.yahoo.com
to scs.msg.yahoo.com or vice versa.
Deleting my xdb spool file and re-registering with the transport does
not change the behavior.
Any insight that anyone could offer would be well appreciated. The full
transport log is available (slightly redacted) at
http://blank.org/memory/work/yahoot.txt.
-n
------------------------------------------------------------<memory at blank.org>
SENDING JUNK EMAIL TO MY ADDRESS CONSTITUTES YOUR LEGALLY-BINDING ACCEPTANCE
OF MY OFFER TO REMOVE BOTH OF YOUR NIPPLES WITH AN ORBITAL SANDER.
(--Andy Ihnatko)
<http://blank.org/memory/>----------------------------------------------------
More information about the JDev
mailing list