Opened 10 years ago

Closed 2 years ago

#10281 closed defect (out of date)

remote msn client 'unable to deliver message' to pidgin

Reported by: rhduncan Owned by: khc
Milestone: Component: MSN
Version: 2.6.6 Keywords: msn proxy unable deliver message
Cc: Thasaidon, atilaw, sergiop, kerridge0, FlukeFan, marto, jebbis, jamie

Description

Using the msn protocol through a http proxy, remote buddy's get "The following message could not be delivered to all recipients" errors when sending me messages.

When initiating a chat, the first few message will get through OK. After waiting a short period of time and sending a message, the remote buddy will get the 'could not be delivered' error. The message are not also not actually delivered. After waiting a long time and sending a message, the message will come through OK and the remote buddy will not see any error.

Using the MSN/Windows live messenger client through the same proxy, remote buddy's can send messages fine, and do not get the 'could not be delivered' errors.

I do not believe this is a duplicate of #10049 or similar, as those are cases where pidgin fails to send, wheras in this case pidgin fails to receive (potentially due to premature closure of http connection, as seen in attached log). It is similar to #10206, which I think may be incorrectly marked as a duplicate.

Attachments (1)

pidgin_debug_log_output.txt (5.3 KB) - added by rhduncan 10 years ago.

Download all attachments as: .zip

Change History (25)

Changed 10 years ago by rhduncan

comment:1 Changed 10 years ago by rhduncan

Could this ticket have the same or similar resolution to #10144 - So perhaps something like not auto-closing MSN switchboard connections when using a http proxy?

comment:2 follow-up: Changed 10 years ago by Thasaidon

I'm using WinXP SP3 and Ubuntu Linux 8.04, both with Pidgin 2.6.2 And MSN users have reported the same problem to me while I'm using either OS. So it seems the problem is pidgin related, not OS related. Also, I do not get any errors what so ever. It's the MSN users who get the "The following message could not be delivered to all recipients" error.

Furthermore, the problem exists when connection to the internet via a proxy (at work), but also when connecting whithout a proxy (at home). However, with or without a proxy, there is always a NAT router/firewall between the host system and the Internet.

Changing my LAN ip to my actual public ip, does not help. Enabling/disabling "automatic router port forwards" does not help. Enabling/disabling "Use HTTP Method", does not help.

I am assuming that there is some kind of session time-out set in pidgin? If so, the most plausible reason would be that the NAT translations on the router/firewall will timeout resulting in a "loss of connection", because Pidgin is not keeping an open (active) connection.

The only thing I have not tried is: Manual specification of "range of ports to listen on", with the appropreate portforwarding on the router/firewall.

comment:3 in reply to: ↑ 2 Changed 10 years ago by Thasaidon

I forgot to mention, Other people using Pidgin report getting the same error when trying to communicate with me via the MSN protocol. They are also behind NAT routers/firewalls.

I also get the same error when communicating to them if they are using Pidgin.

comment:4 Changed 10 years ago by jcperez@…

The same problem is occuring to me in several different locations with different kinds of connections to Internet. I tried using msn-pecan instead of msn and the problem seems to disappear completely. JC.

comment:5 in reply to: ↑ description Changed 10 years ago by atilaw

I don't think this is a duplicate of the previous bugs either.

This exact problem occurs for me - I'm using Adium on a macbook pro (which uses libpurple). I've seen the same problem in pidgin on my windows machine a little while back too.

Happens on work network and my home connection, over ethernet/wifi at both places - problem shows itself as msn contacts complaining they get bounced messages. There is often no notification of messages not getting through either.

Tried using the mac client of msn recently and the fairly regular bounced messages my contacts get when I use adium and pidgin were gone, so it seems to be a library thing rather than an actual connection problem.

It never used to do this - I'm fairly certain these problems started maybe 4-6 months ago... before then I'd been using adium and pidgin with no complaints from any of my contacts about bounced messages.

I will add my own error logs from pidgin and adium soon to go with rhduncans.

comment:6 Changed 10 years ago by luixclid

just to add to the cause

i began having this problem after the last upgrade from ver 2.6.1 to ver 2.6.2

tried with msn-pecan but it didn't got better

now i had to stop using pidgin for msn

i have pidgin 2.6.2 over windows vista ultimate 32bit

comment:7 Changed 10 years ago by kerridge0

This is doing my nut - a critical bug for me and very frustrating! will try going back to 2.6.1?

comment:8 follow-up: Changed 10 years ago by kerridge0

had to go back to 2.5.8! seems to be working now at that version. vista business.

comment:9 in reply to: ↑ 8 Changed 10 years ago by Thasaidon

Replying to kerridge0:

had to go back to 2.5.8! seems to be working now at that version. vista business.

The reason for using Pidgin 2.6.x is because of a security issue http://www.pidgin.im/news/security/?id=34

comment:10 follow-up: Changed 10 years ago by kerridge0

bah! and I would have got away with it if it hadn't been for you pesky kids. OK I'm using http://code.google.com/p/msn-pecan/ and that seems to not have any problems...

comment:11 in reply to: ↑ 10 Changed 10 years ago by atilaw

Replying to kerridge0:

bah! and I would have got away with it if it hadn't been for you pesky kids. OK I'm using http://code.google.com/p/msn-pecan/ and that seems to not have any problems...

Thanks for pointing that out - I've basically stopped talking to my msn contacts because of this bug, I refused to use the official mac msn client too, it's a crime against IM... hopefully pecan will help until this bug is officially fixed!!

comment:12 Changed 10 years ago by marto

cc me

comment:13 Changed 9 years ago by rhduncan

  • Version changed from 2.6.2 to 2.6.4

This problem still persists in version 2.6.4!

Pidgin is 'destroying' the proxy connection after 60 seconds, and I'm assuming that either pidgin is not informing the msn gateway of the disconnection, or it is being ignored. Log extract below:

(12:18:29) proxy: HTTP proxy connection established ... (12:19:29) msn: destroy httpconn (01EEFE60)

Can the 60 second timeout please be removed, such as it was when resolving the msn chat problem in Ticket #10144

comment:14 Changed 9 years ago by downforce

I've been getting this with all of my MSN contacts messaging me, so tweaked some settings.

Primarily, I disabled "Use HTTP Method" and this SEEMS to have fixed it. It's been working fine for the last day and have asked my contacts to let me know if they get the message.

We don't run a proxy and I've set both Pidgin & MSN account to "No Proxy", running 2.6.4.

comment:15 Changed 9 years ago by rhduncan

Unfortunately, those of us behind corporate firewalls are forced to use a HTTP proxy, and also the 'Use HTTP method' for msn due to tight proxy restrictions.

Is there any response/acknowledgement/confirmation from the developer? Is there some more information I can/should provide in order to help? Am I wrong to assume it is a simple fix to solve the problem by (re)setting the connection timeout?

I am not a pidgin developer, but I'm gonna take a stab at a bit of a hack here ... but how about this ...

Somewhere in libpurple/protocols/msn/switchboard.c @@ msn_switchboard_add_user() method ...

if (swboard->servconn->session->http_method)
{
msn_servconn_set_idle_timeout(swboard->servconn, 0);
}

Or perhaps it may be better to set 0 timeout on both http_method and (purple_proxy_info_get_type(gpi) == PURPLE_PROXY_HTTP) conditions, but elsewhere in the code.

Any thoughts?

comment:16 Changed 9 years ago by jebbis

same issue here. testing now without "HTTP Method", and hopes it will work.

sitting behind a corporate firewall at work, so have to use HTTP Method.

comment:17 Changed 9 years ago by rhduncan

  • Keywords unable deliver message added; messages delivered removed
  • Milestone set to 2.7.0
  • Version changed from 2.6.4 to 2.6.6

This problem still exists in 2.6.6

Pidgin log still shows "msn: destroy httpconn" 60 seconds after the last chat message with a remote buddy, which I believe it too soon when using a http proxy.

I am only guessing the problem here: but I assume that at this 60sec instance, the msn gateway server is still connected to the http proxy and therefore thinks the connection to is still active, even though pidgin has closed it, and so when there is no acknowledgement of the message from pidgin, the remote buddy gets the error.

There seems to be no response/activity from pidgin developers, so I hope I am not stepping on any toes by setting the milestone for this to be fixed at 2.7.0

comment:18 Changed 9 years ago by rekkanoryo

  • Milestone 2.7.0 deleted

Do not touch the milestone on tickets. It is for my use only.

comment:19 Changed 9 years ago by BWJM

Can we please get this issue resolved? There are TONS of users affected by this (ie: users behind a corporate firewall for which the only real option is to use a different plugin or the core MSN IM client).

Thank you!

comment:20 Changed 9 years ago by Digian

Hello I am using win7 32-bit and pidgin 2.6.6

I have to use http proxy method at work and have noticed a lot of bounces, I was getting bounces at home until I realised this http proxy method is faulty.

I have turned http proxy off at home and no more bounces. :)

Please fix so we can use pidgin msn behind corporate firewall !!!

comment:21 Changed 9 years ago by rhduncan

There is still a problem with 2.7.3 and msn connections via http proxy - pidgin is destroying the connection,

(12:52:56) msn: destroy httpconn (031D6C80)

after which pidgin does not receive any of messages sent by a remote user.

The symptoms are now slightly different, as the 'could not be delivered' errors are no longer displayed on the remote user's client, but this possibly due to remote user's version of Windows Live messenger.

Should I open a new ticket for 2.7.3, or update the description of this one?

comment:22 Changed 8 years ago by jmanig

I'm using Pidgin 2.7.7 with MSNP15 forced on (to work around #13012).

I had the same issue, I've set the timeout to unlimited as per rhduncan and the problem goes away. The only thing is that the switchboard itself resets the connection after 5 minutes of inactivity. So I'll try to set it to 300 a bit later to see if it works.

comment:23 Changed 8 years ago by rhduncan

I am unable to test and confirm if this is still an issue in 2.7.10 due to #13012.

Pidgin is advertised as supporting the MSN chat network, and in my opinion should therefore work without needing any special plugins.

comment:24 Changed 2 years ago by dx

  • Resolution set to out of date
  • Status changed from new to closed

Closing all MSN tickets, since it has been removed in pidgin 2.12.0 after being broken for a couple of years (see http://ismsndeadyet.com/). The skypeweb plugin can be used as an alternative (yes, it supports MSN logins too)

If this issue is still present in any other protocols supported by pidgin, please leave a comment and we will reopen it.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!