Impossible to get working connection to MSN

It works fine for ICQ, but I can’'t make MSN connections working.

I tried using two differents MSN accounts, but it seams the connection does not work.

The administration console displays a green light in front of the MSN registration when the user connects using PSI, but the last login stays on “Never” and I cannot interact with MSN users in PSI.

Any idea ?

My configuration :

IM Gateway 1.0 Beta 3

Wildfire 3.1.0 Beta 3 (RPM install)

Linux / i386

1.5.0_08 Sun Microsystems Inc. – Java HotSpot™ Server VM

Message was edited by: sk_lionheart

Are you seeing anything in your error, info, or debug logs.

I’'ve got the same problem with MSN. There are no errors in my logs about the msn gateway. Only this when I attempt to login to the msn transport:

2006.09.30 19:56:57 An existing resource has changed status: obi_wan@jabber.blubb.net/Psi

2006.09.30 19:57:24 An existing resource has changed status: obi_wan@jabber.blubb.net/Psi

Hrm. I too am having some problems in MSN land at the moment. I recall that folk using Gaim had to update to a newer version to dodge issues with MSN. I wonder if these same issues are now affecting the transport. Will see what I can figure out.

I created an issue for it. GATE-77

Just this :

2006.10.01 01:00:42 Logging in to MSN gateway.

And nothing else in error, info or debug logs…

We tried using 3 different MSN accounts without any success.

It’'s strange because, in the registrations console, MSN sessions seam to be opened because the green light corresponding to the MSN connection is correctly displayed when the corresponding Jabber user is logged in. The “Last Login” column stays on “never”. I presume that it means that the connection is ever rejected.

It’'s a shame that nothing appears in the logs.

Message was edited by: sk_lionheart

MSN registration is definitely busted now. I deleted my registration and went to add it back in and got…

2006.09.30 16:11:52 org.jivesoftware.wildfire.gateway.BaseTransport.handleIQRegister(BaseTransport.j ava:610) Someone attempted to register with the gateway with an invalid username: xxxx@xxxxxx.com/Psi

Before I deleted the registration, presence and chat were working just fine though.

gtj wrote:

MSN registration is definitely busted now. I deleted my registration and went to add it back in and got…

2006.09.30 16:11:52 org.jivesoftware.wildfire.gateway.BaseTransport.handleIQRegister(BaseTransport.j ava:610) Someone attempted to register with the gateway with an invalid username: xxxx@xxxxxx.com/Psi

Before I deleted the registration, presence and chat were working just fine though.

That’‘s extremely bizarre. I just added my MSN accounts (all of my accounts) just fine and had no problems with that. May I ask what your entire MSN id is? (maybe send it via a private message or im or email to me?) It’'s entirely possible that I just am missing some possible characters.

No need. The Regex you’‘re using to validate MSN names doesn’'t include the period which is a valid character in an rfc822 address.

The only characters NOT allowed are…

()<>@,;:\"[]  and <space>

and control characters

Try…

username.matches("[^ \\p{Cntrl}()<>@,;:\\\\\"\\[\\]]+@[^ \\p{Cntrl}()<>@,;:\\\\\"\\[\\]]+");

My MSN ID would be Klaas_Tammling@hotmail.com… Maybe it’'s the same problem with the yim transport that there is a _ in the name?

I tried using these 2 MSN IDs :

richard_thibault@hotmail.com

lionheart@clansk.org

Same result each time : green light in the console, but no connection (“never” is still displayed in the registrations list and impossble to interact with MSN using a jabber client).

I confirm these two contacts work fine with MSN Messenger 7.5

If you are not able to reproduce, publish a beta 4 with much more debug logs

And some bugfixes maybe ^^

For information, I checked my linux firewall and temporarly disabled it in order to be sure it didn’'t come from a bad firewall rule : same result

I was able to reproduce the same beahvior using ICQ.

ICQ number 50852091 works fine, but impossible to login using ICQ number 384020496 (“Never” is still displayed)

50852091 is a very old icq account. 384020496 is a brand new one.

sk_lionheart wrote:

If you are not able to reproduce, publish a beta 4 with much more debug logs

You could always submit patches. I am doing this in my free time.

sk_lionheart wrote:

I was able to reproduce the same beahvior using ICQ.

ICQ number 50852091 works fine, but impossible to login using ICQ number 384020496 (“Never” is still displayed)

50852091 is a very old icq account. 384020496 is a brand new one.

I’‘m a tad confused with the issues you are running into. I have had no problems logging into ICQ. “Never” will occur if you have never properly logged into the legacy service. (ie it doesn’'t update until you are actually logged in) Another thing that -could- cause it is if the database schema is messed up.

The database schema has been created automatically on it’'s the embedded HSQL that is used

No problem to help in discovering the bug, give me access to the SVN, I can contribute as Java developer

You can check out a copy of the SVN tree from the developers link at the top of the page, it’'s amongst the wildfire source, and submit patches to me.