Have you tried logging in with your bot's account from MSN Messenger 6.2? Do you have any firewalls up that might be blocking the incoming or outgoing ports?
Have you tried logging in with your bot's account from MSN Messenger 6.2? Do you have any firewalls up that might be blocking the incoming or outgoing ports?
I have tried loggin in with MSN Messenger 7.0.0332, and on MSN Web Messenger, and there was no problem. I have a D-link router with firewall, but I there was no problem with MSN.pm 1.3.12 (the one that talha asad made)
Just comparing version 1.3 12 and 2.0... version 1.3.12 doesn't tell you if it fails on the first authentication server. It just plows right into the next bit of code, which is getting a list of passport urls. These are needed to complete authentication. I would expect 1.3.12 would fail also because even though it doesn't tell you it didn't hear from the first authentication server, it should be able to get the passport urls. Hmm...
You didn't tell me what version of MSN2.0 you have. It is usually printed as the first line of output. But if you have revision 76, you could try this: in MSN/Notification.pl, line 990, comment out return undef:
Code:
# return undef;
In other revisions, the line number will be different.
Anyhow, this will disregard whether we were able to connect to the first authentication server, in the same way that 1.3.12 does. See where that gets you.
LOL I didnt even think of comparing 2.0 with the old version that works. Good idea Mojave....considering that msn.pm's prior to 2.0 I never had a problem with. _________________ Check out Botworld! A dev resource for things bot.
Downloads, articles, news, fourm and more.
http://botworld.marzopolis.com
Notification.pm, line 992 is trying to split a value that is undefined, data it should get back from the authentication server, but doesn't, obviously.
And you're sure that 1.3.12 still works? Because, even if much of the other code is different between the two versions, the code that contacts the authentication server and gets the passport urls is the same. 1.3.12 should fail for the same reason.
When was the last time you successfully used 1.3.12?
Well, I have no idea. Here are the two blocks of code:
MSN 1.3.12
Code:
my $ua = new LWP::UserAgent;<br /> my $response = $ua->get('https://nexus.passport.com/rdr/pprdr.asp');<br /> my %passport_urls = map { split '=' }<br /> split(',',($response->headers->header('PassportURLs')));
MSN 2.0
Code:
my $ua = new LWP::UserAgent;<br /> my $response = $ua->get('https://nexus.passport.com/rdr/pprdr.asp');<br /> unless ($response->is_success) {<br /> $self->serverError( "Authentication Error: No response from Passport server" );<br /> return undef;<br /> }<br /> my %passport_urls = map { split '=' }<br /> split(',',($response->headers->header('PassportURLs')));
The only difference I see is that in 2.0 we are checking for success, which we had you comment out. How 1.3.12 gets the passport url data and 2.0 doesn't is beyond me.
No, it did work, it got the data... not sure how though.
I guess the is_success method might be a bit dubious - I'll have to look into that. Although, I never get the Authentication Error: No response from Passport server error.
No, it did work, it got the data... not sure how though.
I guess the is_success method might be a bit dubious - I'll have to look into that. Although, I never get the Authentication Error: No response from Passport server error.
User Control Panel
:unsure: