Bug 118781

Summary:	I can't connect MSN with an exists passport.net acount (...@yahoo.es)
Product:	[Unmaintained] kopete	Reporter:	xeber <xeberlm>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	0.10.3
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description xeber 2005-12-21 11:21:13 UTC

Version:           0.10.3 (using KDE KDE 3.4.2)
Installed from:    SuSE RPMs
Compiler:          0.10.3 
OS:                Linux

My english isn't bery good.

I create passport.net acount with my yahoo e-mail account. I am connect with this account in very differents plataforms: Win98+MSN, WinXP+MSN, Fedora2+gaim, ubuntu+gaim, ubuntu+kopete.
Now in working on a new office, when we are configuring the new instalation of SuSE 10. All of others can connect to MSN, but with my account no. The other workers of office have ...@hotmail.com passport.net account.

NOTE: in other times, I use equal nickname to MSN account (...@yahoo.es), one day WinXP+MSN do not connect if the nickname is not changed. MSN server do not accept @. This is changed.

Comment 1 Thiago Macieira 2005-12-21 11:39:35 UTC


*** This bug has been marked as a duplicate of 118760 ***

Comment 2 xeber 2005-12-21 13:27:08 UTC

I do not undestand why is changed the status to resolved.

This is the error log:
$ kopete
kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (el servidor remoto cerró la conexión)

Comment 3 Matt Rogers 2005-12-21 14:26:23 UTC

this is a duplicate of bug 118760

*** This bug has been marked as a duplicate of 118760 ***

Comment 4 xeber 2005-12-21 16:55:45 UTC

The bug 118760 no resolve the problem.

In the machine when y executing kopete, do not problems other ...@hotmail.com msn account. The probles only have my account.

Comment 5 Thiago Macieira 2005-12-21 17:08:50 UTC

That's why bug 118760 isn't marked RESOLVED.

Comment 6 xeber 2005-12-26 16:37:49 UTC

The bug 118760 do not tell nothing relative to my problem after my comments.