sending im via libpurple causes microsofts msn messenger to quit

[Duncan Berriman]

Just built with V2.7.8 and same issue with libpurple and msn.

Done some testing with other networks.

Yahoo - works fine
Google - works fine
Using Yahoo library to talk to MSN account - works fine (except it would
appear incoming messages are only received at the libpurple end when an
outgoing message is sent) and of course there is quite a lag in messages
being received in MSN messenger.
AIM - works fine.

Anyone any idea why libpurple client keeps causing msn messenger of buddy to
crash?

Thanks
Duncan

-----Original Message-----
From: devel-bounces at pidgin.im [mailto:devel-bounces at pidgin.im] On Behalf Of
Duncan Berriman
Sent: 20 December 2010 10:09
To: devel at pidgin.im
Subject: sending im via libpurple causes microsofts msn messenger to quit

Following on from previous message to the list I have now built my own
libpurple having removed the problematic request_input call and instead just
hard coded the call to finish_auth_request.

My code can now successfully add an msn buddy and it is saved in MSN (which
is verified by logging on using msn messenger).

Now a further problem.

If I send messages via my client  using libpurple to the MSN contact it
causes the contact using MSN messenger to logout.

Any ideas why libpurple is causing MSN Messenger to quit? Slightly worrying
it causes MSN's current  messenger to fail.

Debug log below up to the point msn messenger fails.

(09:58:47) msn: send IM {Hello} to xxx at hotmail.co.uk
(09:58:47) msn: prepare to send online Message
(09:58:47) msn: send via switchboard
(09:58:47) msn: switchboard send msg..
(09:58:47) msn: C: SB 004: MSG 7 A 148
 (09:58:47) msn: S: SB 004: ACK 7
(09:59:16) msn: C: NS 000: PNG
(09:59:16) msn: S: NS 000: QNG 48
(09:59:46) msn: C: NS 000: PNG
(09:59:46) msn: S: NS 000: QNG 47
(09:59:47) msn: destroy httpconn (0x91d4b08)
 (09:59:48) msn: send IM {Hello} to xxx at hotmail.co.uk
(09:59:48) msn: prepare to send online Message
(09:59:48) msn: send via switchboard
(09:59:48) msn: new httpconn (0x9209818)
(09:59:48) msn: C: NS 000: XFR 26 SB
(09:59:48) msn: switchboard send msg..
(09:59:48) msn: Appending message to queue.
(09:59:48) msn: S: NS 000: XFR 26 SB 64.4.44.26:1863 CKI
1165210067.24521976.210101249 U messenger.msn.com 1
(09:59:48) msn: Switchboard:auth:{1165210067.24521976.210101249}
socket:{64.4.44.26:1863}
(09:59:48) dns: DNS query for '64.4.44.26' queued
(09:59:48) dnsquery: IP resolved for 64.4.44.26
(09:59:48) proxy: Attempting connection to 64.4.44.26
(09:59:48) proxy: Connecting to 64.4.44.26:1863 with no proxy
(09:59:48) proxy: Connection in progress
(09:59:49) proxy: Connecting to 64.4.44.26:1863.
(09:59:49) proxy: Connected to 64.4.44.26:1863.
(09:59:49) msn: C: SB 005: USR 1
yyy at hotmail.co.uk;{1BE99E6D-1C6E-4BEA-8B3E-9C464006A774}
1165210067.24521976.210101249
(09:59:49) msn: S: SB 005: USR 1 OK
yyy at hotmail.co.uk;{1be99e6d-1c6e-4bea-8b3e-9c464006a774} yyy
(09:59:49) msn: C: SB 005: CAL 2 xxx at hotmail.co.uk
(09:59:49) msn: S: SB 005: CAL 2 RINGING 1165210067
(09:59:49) msn: S: SB 005: JOI
xxx at hotmail.co.uk;{33fe9a67-6013-4498-b079-c38e04d0746b} xxx
3055849760:2609258384
(09:59:49) msn: Processing queue
(09:59:49) msn: Sending message
(09:59:49) msn: C: SB 005: MSG 3 A 148
(09:59:49) msn: switchboard send msg..
(09:59:49) msn: C: SB 005: MSG 4 U 98
(09:59:49) msn: S: SB 005: JOI xxx at hotmail.co.uk xxx 3055849760:2609258384
(09:59:49) msn: Processing queue
(09:59:49) msn: switchboard send msg..
(09:59:49) msn: C: SB 005: MSG 5 U 98
(09:59:49) msn: S: SB 005: ACK 3
 (10:00:24) msn: S: SB 005: BYE
xxx at hotmail.co.uk;{33fe9a67-6013-4498-b079-c38e04d0746b}
(10:00:24) msn: destroy httpconn (0x9209818)
(10:00:24) msn: S: NS 000: FLN xxx at hotmail.co.uk 1 0:0
(10:00:24) blist: Updating buddy status for xxx at hotmail.co.uk (MSN) Buddy
"xxx at hotmail.co.uk" (prpl-msn) signed off

Duncan

_______________________________________________
Devel mailing list
Devel at pidgin.im
http://pidgin.im/cgi-bin/mailman/listinfo/devel

--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.