[Pidgin] #2638: "Message could not be sent because a connection error occurred:" (on MSN)

[Pidgin]

#2638: "Message could not be sent because a connection error occurred:" (on MSN)
---------------------------+------------------------------------------------
  Reporter:  ThorbjornTux  |       Owner:       
      Type:  defect        |      Status:  new  
  Priority:  minor         |   Milestone:       
 Component:  libpurple     |     Version:  2.1.0
Resolution:                |    Keywords:       
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by CZero):

 Okay, reading this thread and taking in all things mentioned I think some
 people here are being less then reasonable. Summing up the thread I come
 to this point:
 - MSN Protocol changed.
 - Some messengers (all? a lot?) experience the same troubles.
 - This is no -Pidin- bug, reading the first two points.
 - The fix mentioned: disable proxy, disable msn over http helps some
 people. It helped me for one day :S, afterwards it never worked again.
 - Most people posting in this thread complain it renders pidgin unworkable
 for people behind firewalls, not allowing anything beyond port 80. That's
 offcourse a given: If we weren't bound to these limitations at work we
 wouldn't have noticed the problem: there is no problem when you don't have
 to use port 80, you wouldn't use MSN over HTTP then right?

 So, what remains: I agree that there are probably indeed quite a lot of
 users with the same limitations as us (who are posting in this thread),
 who I'm betting all can't wait till this is fixed. The question to raise
 priority to this problem is valid to me, but I'm guessing the moderator
 will have to descide on the real figures: how big is the userbase that
 uses msn over http (bound to limitations at work). I sure hope this
 consideration will lead to bigger priority.

 Next to that: It is not a bug, but a change of protocol (digesting all
 information here) and I hope the coders will find a working solution soon!

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