Niepo74's fix works fine for me, thanks.

Yes, I didn't realize that... it seems that the only way to make it asynchronous is by using -command, so be careful

Lol, at least you fixed the typo x)

Oh, I was talking about the two files thing and I forgot that I didn't sent the post yesterday... maybe you'll find it useful:

The issue seems to happen when sending more than one file over the SB. This is what I tried:

- Sending one file using a direct connection: works.
- Sending two files using a direct connection: works.
- Sending one file using the SB: works.
- Sending two files using the SB: error.
- Sending two files using a direct connection and a third using the SB: seems to work*

* The first two transfers didn't cancel, but both files had 1k missing when they arrived. Don't know if it could be aMSN related.

Bad news, now it's worse than before when sending two files :S

The first file goes fine, but the second one stops almost instantly. It just sends 2 or 10k.

Finally!!

After some hours of coding (it was my first time with tcl/tk  :oops:) I've found the problem, which was, of course, pretty lame ;p

Just open proxy.tcl and change this:

Code:

after 0 "catch {::http::geturl [list https://nexus.passport.com/rdr/pprdr.asp] -timeout 5000 -command {globalGotNexusReply $self}}"

for this:

Code:

if { [catch {set token [::http::geturl [list https://nexus.passport.com/rdr/pprdr.asp] -timeout 5000]}] } {
return -1
}

globalGotNexusReply $self $token
return ok

The tcl/tk documentation says that catch returns 1 when there's an error, but this proc must return -1. Take a look at protocol.tcl:

Code:

if { [$proxy authInit] < 0 } {

Sometimes ::http::geturl throws an exception (or whatever it's called in tcl/tk), and that's where it hanged, 'cause the execution continued as if globalGotNexusReply was called, but it wasn't

And finally, the reason why I don't call globalGotNexusReply using -command is 'cause it seems that when the request times out, -command is not executed, so it should hang too (I couldn't test this enough, so I'm not 100% sure)

A warning or something when the exception is catched would be nice, too, so the user can now that there has been a problem and must reconnect

WTF, I was about to send you the dump after testing several things xDDD

I'll try it tomorrow and see if it works

Bad news, it happened again.

This time in a different scenario... I was sending three files to the same contact, and the transfer failed with the second and third.

I have a problem with my router and those too ports were closed, so the issue may be caused by one of the following:

- There's some message you don't know that is sent when using the SB and aMSN doesn't ACK it.
- There's a problem when sending more than one file, maybe the ACKs going nuts and being sent to one of the others connections or something like that.
- It has something to do with having the ports closed, but I don't think that would be the cause.

I'm pretty sure that the problem is the SSL authentication thing. Here's what Ethereal's trace says when aMSN can't connect:

1. Begins handshake with *.gateway.edge.messenger.live.com (let's call it Gateway), and connects.
2. Begins handshake with Nexus, but it never receives the SYN/ACK, so there's no SSL authentication!
3. Sends MSN commands through Gateway and then hangs at USR 3 TWN S because there is no SSL auth.


Here's what it does when the connection is successful:

1. Begins handshake with Gateway and connects.
2. Begins handshake with Nexus and connects.
3. Sends MSN commands through Gateway and SSL commands through Nexus.
4. Continues with the login process.


So, could it be possible to make sure that the connection with Nexus is established before connecting with Gateway?
Probably that's the problem

I can email you the traces if you want

PS: It's essentially what you said before about the Nexus server no responding... just making sure it connects before sending the other commands should do it.

Ok, I've got the traces and have found something.

The first time it tried to log in without SSL authentication, and failed. The second time it authenticated and loged in successfully.

Could that be the problem?

It's me who cancelled at USR 3 TWN S, there's not timeout as far as I know (if I don't cancell it just hangs there forever)

So, the problem is that aMSN doesn't send a USR 4 TWN S (in this example)... that would be logical if it never received the USR 3 TWN S, but it does, so it's strange. I assume it sends it to the same server it's already connected, so it should have nothing to do with what I was saying in the other post...

I'll try to trace it with Ethereal (or whatever it's called now) and see what happens. I'll have to wait untill it decides not to connect (today it connected at the first attempt), so it may take a while.

Anyway, here's the status log, just in case:

Code:

[04:45:18] Catch in proc trans (title ): can't read "lang(title)": no such variable
[04:45:18] Catch in proc trans (followtext ): can't read "lang(followtext)": no such variable
[04:45:18] Catch in proc trans (filters ): can't read "lang(filters)": no such variable
[04:45:18] Catch in proc trans (savetofile ): can't read "lang(savetofile)": no such variable
[04:45:18] Catch in proc trans (clear ): can't read "lang(clear)": no such variable
[04:45:18] Catch in proc trans (close ): can't read "lang(close)": no such variable
[04:45:18] No LANG environment variable. Using en
[04:45:18] LoadLoginList: starting
[04:45:18] LoadLoginList: HOME=*******/amsn, HOME2=*******/amsn, HOMEE=*******/amsn
[04:45:18] LoadLoginList: adding profile ******@hotmail.com with lock num 0
[04:45:18] LoadLoginList: adding profile ******@msn.com with lock num 63695
[04:45:18] LoadLoginList: getting an initial profile
[04:45:18] CheckLock: LoginList getlock called. Lock=63695
[04:45:18] CheckLock: Port 63695 is free!!
[04:45:18] LockProfile: Locking ******@msn.com
[04:45:18] LockProfile: Got random port 65094
[04:45:18] LoadLoginList: profile ******@msn.com is free, locking
[04:45:18] LoadLoginList: we found a free profile: ******@msn.com
[04:45:18] load_config: Started. HOME=*******, config(login)=******@msn.com
[04:45:18] load_config: loading file *******/config.xml
[04:45:18] load_config: Config loaded
[04:45:18] PLUGIN : Nudge
[04:45:18] load_lang called from a plugin
[04:45:18] load_lang called from a plugin
[04:45:18] PLUGIN : Cam Shooter
[04:45:18] load_lang called from a plugin
[04:45:18] load_lang called from a plugin
[04:45:18] PLUGIN : Inkdraw
[04:45:18] PLUGIN : ColoredNicks
[04:45:18] ColoredNicks loaded
[04:45:18] load_lang called from a plugin
[04:45:18] load_lang called from a plugin
[04:45:18] PLUGIN : Winks
[04:45:18] Loading Winks plugin...
[04:45:18] load_lang called from a plugin
[04:45:18] load_lang called from a plugin
[04:45:18] utils/windows/gnash/gnash.exe
[04:45:18] Winks Loaded OK.
[04:45:18] load_my_pic: Trying to set display picture *******/displaypic/Thriller.png
[04:45:18] skin custom 's scrollbar loaded
[04:45:18] Themes ERR: AddClass with incomplete option list
[04:45:18] Themes ERR: AddClass with incomplete option list
[04:45:18] Themes ERR: AddClass with incomplete option list
[04:45:18] logging out, creating loginscreen : show_login_screen
[04:45:19] LoadLoginList: starting
[04:45:19] LoadLoginList: getting profiles
[04:45:19] LoadLoginList: HOME=*******, HOME2=*******/amsn, HOMEE=*******/amsn
[04:45:19] LoadLoginList: adding profile ******@hotmail.com with lock num 0
[04:45:19] LoadLoginList: adding profile ******@msn.com with lock num 65094
[04:45:19] ConfigChange: ******@msn.com
[04:45:19] ConfigChange: Valid email
[04:45:19] logging in, destroying loginscreen : loggingIn
[04:45:34] cmsn_auth starting, stat=a
[04:45:34] check_web_ver: status=timeout ncode=
[04:45:34] cmsn_auth starting, stat=v
[04:45:34] cmsn_auth starting, stat=i
[04:45:34] cmsn_auth starting, stat=u
[04:45:34] cmsn_auth: Nexus didn't reply yet...
[04:46:27] Read EOF in ::NS::Connection1, closing
[04:46:27] ::MSN::CloseSB ::ns Called
[04:46:27] ::MSN::ClearSB ::ns called
[04:46:27] clearing sb ::ns. oldstat=u
[04:48:19] ::DirectConnectin::Write: SB ns problem when writing to the socket: can not find channel named ""...
[04:48:19] ::MSN::CloseSB ns Called
[04:48:19] ::MSN::ClearSB ns called
[04:48:19] clearing sb ns. oldstat=d
[04:48:19] ::MSN::CloseSB ns Called
[04:48:19] ::MSN::ClearSB ns called
[04:48:19] clearing sb ns. oldstat=d
[04:48:19] Loging out
[04:48:19] logging out, creating loginscreen : loggedOut
[04:48:19] LoadLoginList: starting
[04:48:19] LoadLoginList: getting profiles
[04:48:19] LoadLoginList: HOME=*******, HOME2=*******/amsn, HOMEE=*******/amsn
[04:48:19] LoadLoginList: adding profile ******@hotmail.com with lock num 0
[04:48:19] LoadLoginList: adding profile ******@msn.com with lock num 65094
[04:48:19] logging out, creating loginscreen : show_login_screen
[04:48:19] ConfigChange: ******@msn.com
[04:48:19] ConfigChange: Valid email
[04:48:20] logging in, destroying loginscreen : loggingIn
[04:48:20] cmsn_auth starting, stat=a
[04:48:20] cmsn_auth starting, stat=v
[04:48:21] cmsn_auth starting, stat=i
[04:48:21] cmsn_auth starting, stat=u
[04:48:21] cmsn_auth: Nexus didn't reply yet...
[04:48:21] gotNexusReply: loginurl=https://loginnet.passport.com/login2.srf
[04:48:21] gotNexusReply: authentication was waiting for me, so I'll do it
[04:48:21] ::DirectConnection::authenticate: Getting https://loginnet.passport.com/login2.srf
[04:48:22] ::DirectConnection::GotAuthReply 302: Forward to https://msnialogin.passport.com/login2.srf
[04:48:22] ::DirectConnection::authenticate: Getting https://msnialogin.passport.com/login2.srf
[04:48:23] ::DirectConnection::GotAuthReply 200 Ticket= t=9nVaVWGWZAlpMV4P16rzNDKkUmn*KzBev9wRN5PKNzNtMIX9HXmjpdeSckyxRq2gA7EqyX48W2glMNjGQj2xwuLnqPBoZsXs*4!B2VFsDWcD12U3Hid4gbuw$$&p=99svTWVJfF0dbfXZ05Ib2x8H2qJvjlj3CUSHTTNGuZmf5BEhvgBnHO*haGIgrimgEhiWb1DGWSu8g8nRB10x*o!dlKbk*zJg2Zclrb1nhn6vZrJnljf9V1bDilfL*J2qOzPKdPF0gFItNNdscQqLt6t*PFD3bcmcrNOk9nD3ZYh!CS1FhyjXRLgQ$$
[04:48:23] cmsn_auth starting, stat=us
[04:48:23] save_config: saving config for user ******@msn.com in *******]
[04:48:23] save_config: saving config_file. Opening of file returned : file2136a50
[04:48:23] save_config: Config saved
[04:48:23] Loading address book data...

PS: Take a look at [04:46:27]... it seems that it do times out after all.

Hi,

I'm having this problem for a couple of weeks, so I've investigated a bit. First of all, here's the protocol log:

Code:

[04:45:19] ::Proxy::ProxyDirect1
[04:45:19] < Connected to: 207.46.107.67 1863 >
[04:45:34] ->ns-sock460 VER 1 MSNP12 CVR0


[04:45:34] ->ns-sock460 CVR 2 0x0409 winnt 5.1 i386 MSNMSGR 8.0.0812 msmsgs *******@msn.com


[04:45:34] ->ns-sock460 USR 3 TWN I *******@msn.com


[04:45:34] <-ns-sock460 VER 1 MSNP12 CVR0
[04:45:34] <-ns-sock460 CVR 2 8.1.0178 8.1.0178 8.1.0178 http://msgruser.dlservice.microsoft.com/download/1/A/4/1A4FEB1A-18E0-423A-B898-F697402E4F7F/Install_Messenger.exe http://get.live.com
[04:45:34] <-ns-sock460 USR 3 TWN S ct=1200800720,rver=5.0.3270.0,wp=FS_40SEC_0_COMPACT,lc=1033,id=507,ru=http:%2F%2Fmessenger.msn.com,tw=0,kpp=1,kv=4,ver=2.1.6000.1,rn=1lgjBfIL,tpf=b0735e3a873dfb5e75054465196398e0
[04:48:19] ->ns FAILED: OUT


[04:48:20] ::Proxy::ProxyDirect3
[04:48:20] < Connected to: 207.46.107.67 1863 >
[04:48:20] ->ns-sock408 VER 4 MSNP12 CVR0


[04:48:20] ->ns-sock408 CVR 5 0x0409 winnt 5.1 i386 MSNMSGR 8.0.0812 msmsgs *******@msn.com


[04:48:20] ->ns-sock408 USR 6 TWN I *******@msn.com


[04:48:20] <-ns-sock408 VER 4 MSNP12 CVR0
[04:48:21] <-ns-sock408 CVR 5 8.1.0178 8.1.0178 8.1.0178 http://msgruser.dlservice.microsoft.com/download/1/A/4/1A4FEB1A-18E0-423A-B898-F697402E4F7F/Install_Messenger.exe http://get.live.com
[04:48:21] <-ns-sock408 USR 6 TWN S ct=1200800887,rver=5.0.3270.0,wp=FS_40SEC_0_COMPACT,lc=1033,id=507,ru=http:%2F%2Fmessenger.msn.com,tw=0,kpp=1,kv=4,ver=2.1.6000.1,rn=1lgjBfIL,tpf=b0735e3a873dfb5e75054465196398e0
[04:48:23] ->ns-sock408 USR 7 TWN S t=9nVaVWGWZAlpMV4P16rzNDKkUmn*KzBev9wRN5PKNzNtMIX9HXmjpdeSckyxRq2gA7EqyX48W2glMNjGQj2xwuLnqPBoZsXs*4!B2VFsDWcD12U3Hid4gbuw$$&p=99svTWVJfF0dbfXZ05Ib2x8H2qJvjlj3CUSHTTNGuZmf5BEhvgBnHO*haGIgrimgEhiWb1DGWSu8g8nRB10x*o!dlKbk*zJg2Zclrb1nhn6vZrJnljf9V1bDilfL*J2qOzPKdPF0gFItNNdscQqLt6t*PFD3bcmcrNOk9nD3ZYh!CS1FhyjXRLgQ$$


[04:48:23] <-ns-sock408 USR 7 OK *******@msn.com 1 0

As you can see, the only difference is between "::Proxy::ProxyDirect1" and "::Proxy::ProxyDirect3". I don't know why $self returns the 1 and the 3 (I have no knowledge of tcl/tk), but the method is the same in both cases (authInit)

The weird thing is that the issue only happens the first time I try to connect. After a successful connection it always works the first time when reconnecting, even after restarting aMSN, so that makes me think that the key could be something about cached data, like when you try to resolve a DNS and the first time it's slow or times out, but the rest works fine 'cause it's cached.

If that's the case, it could be some server issue as you said before (assuming the data is cached on the server) or maybe somehing related with aMSN, assuming we store the data.

I hope this will give you a hint to solve the problem. Maybe it has nothing to do with it, but it's an idea

By the way, I have the status log too, if you want it

Lol, don't worry, just keep up the good work

Thanks, I've tried twice with the same file and it works, I guess it's fixed now

Check your mail

Sure, that would be kakaroto (at) sourceforge.net ?