"The following message could not be delivered"

[hilbert70]

Over at the pidgin there is the same problem, Mr laszlok debuged the problem and found out why it did not work,
Here it comes. I hope the coders can do something with it.

AGAIN I DID not find in, I am only the messenger to this forum to post a possible sollution, I hope I don't hurt someones feelings.

Hilbert

--> pidgin post -->
 
 I think I have solved it. This works perfectly for me behind a corporate
 firewall that only allows port 80 out.
 == Here is the issue: ==
 The default value for the msn server address is messenger.hotmail.com. You
 can see this is filled in beside "Server:" in the "Advanced" tab of the
 "Modify Account" dialog. However this server is only used for non-http
 connections. To use HTTP and bypass a corporate firewall, you must use
 gateway.messenger.hotmail.com. This address is hard-coded in the
 msn_httpconn_connect() function in libpurple/protocols/msn/httpconn.c. So
 no matter what host and port are given as arguments to
 msn_httpconn_connect(), it will always connect to
 gateway.messenger.hotmail.com on port 80.
 
 The problem arises when the msn server tells us to use another host. This
 only recently stopped working, so I am guessing up until then microsoft
 used the same server for everything. When you want to start chatting to
 someone, the client sends a switchboard request to the server:
 {{{
 XFR 12 SB
 }}}
 
 Then the server responds with the information on how to connect to the
 switchboard:
 {{{
 XFR 12 SB 65.54.171.30:1863 CKI 151986110.22113252.20218652
 }}}
 
 You can see there is a host and port given for the switchboard in
 "65.54.171.30:1863". The other two arguments are authentication method and
 session ID. Of course this was designed before the HTTP method was in use,
 because as you know we can't connect to port 1863 because of our corporate
 firewall; we have to use port 80. However the server still expects us to
 connect to the given host on port 80. So we need to connect to
 65.54.171.30:80.
 
 The pidgin code parses the host and port nicely, and requests a new
 connection to that server, but these arguments are ignored because both
 the host and port are hard-coded in msn_httpconn_connect(). It tried to
 connect to the switchboard at gateway.messenger.hotmail.com, but that
 server is not a switchboard, and sends HTTP 400 Bad Request. Pidgin then
 reports this to the user as "Message could not be sent because a
 connection error occurred".

[kakaroto]

Hi hilbert, this post is very interesting and gives us all the info we need, we can probably fix it now with the info you provided us..
heyyy, I'm back, it took me less than 2 minutes to fix it with the info you gave us, while I spent already hours going through a different solution which was so complicated and did not work!
Thanks a lot for this. Now, FINALLY, on SVN revision 9005, this aweful bug is fixed! and we can finally release the 0.97 final version, all thanks to you and of course the pidgin team who pinpointed the correct solution!
I must say, this is probably the most useful post anyone with only one post count in his profile has every written!

Thanks again!

[hilbert70]

Don't thank me, thank the pidgin team.

edit: Is the svn version ready for download from the site as dayly snv version? I'm not shure how I can get the to svn. Can I use the http://amsn.svn.sourceforge.net/viewcvs.cgi/amsn/trunk/amsn/ as check out address for amns:
svn co http://amsn.svn.sourceforge.net/viewcvs.cgi/amsn/trunk/amsn amsn
?

edit2:
I should have read the sf pages :oops: it is:
 svn co https://amsn.svn.sourceforge.net/svnroot/amsn amsn
 sorry my fault

[hilbert70]

I confirm, the new svn version is working.

Thanks amsn team, I am on msn again without the need to run squid on my machine, using squid as proxy localy worked somehow.

Thanks

[Locutus]

How do I update my windows version ?

Thx

[Phil]

Wait for 24h and download the development package on the website... Instructions to install it are on the wiki... http://amsn-project.net/wiki/Subversion#The_development_archive_way

[birgitA]

Hi Team,

Thanks for fixing it.
I got the latest svn and now I'm back on aMSN.
It's great!

Cheers, Birgit

[djviky]

Great !!! Now it works well !!!!
Thank's to all !!!    :wink:

[birgitA]

Hi all,

I installed 0.97RC1, SVN revision 9005 last week on my Suse 10.0 box when the problem was reported as fixed.
I can happily start a IM session with my contacts again, however, the other way round seems to fail.

A contact runs msn 8.1 on Win XP behind a firewall through port 80 proxy.
When he tries to IM me, he gets:
"Message couldn't be delivered to all recipients"
He doesn't have this problem with his other contacts.

We've tried this over several days, but unfortunately the problem remains.

Have any of you experienced the same?

Thanks, Birgit

[Gregamos]

I have the same problem, whenever the session closes, my contacts are unable to talk to me..

[yamiddu]

hi guys, sorry .. same problem here.
I installed revision 9044
tested, people can't contact me.

[djviky]

I have the same problem.
with the fix i resolved the problem to send message to my friends.
Now I can chat if I open a session.
But if someone try to send me a message, and I have not open a windows for conversation, the message did not arrive.
why?

[Locutus]

hi guys, sorry .. same problem here.
I installed revision 9044
tested, people can't contact me.

²

[kakaroto]

kakaroto% svn commit -m "This should fix proxy issues for when users open a chat to you (RNG instead of XFR)"
Sending        protocol.tcl
Transmitting file data ..
Committed revision 9054.

not tested, so please update and test and tell me if it fixed it.
thx

[yamiddu]

it works