Kopete/MSN

Jump to: navigation, search
Other languages:
dansk • ‎English • ‎español • ‎italiano • ‎українська


Warning.png
 
Warning
Some of this information is old and may be obsolete. If you are a user of Kopete please either directly edit this page or add notes on the attached Discussion page



MSN logo

To know more about MSN protocol, see msnfanatic

In KDE 4.3

For sending files, nothing has changed, the old protocol is still used. But the new protocol has been partially implemented to be able to receive files. So you can now receive files from your contacts without problems.

In the full protocol, a few messages are exchanged to know the capabilities of each computer, and to know if the file transfer is possible with a direct connection or not. The direct connection has not been implemented yet in Kopete, so all our transfers are done through the chat sessions (the file is received in hidden messages).

Offline Messages

They work

Custom Emoticons

Kopete can receive custom emoticons sent by your contacts.

Exporting the emoticon theme is a planned feature but hasn't been implemented for KDE 3.4.

Display Pictures

It can send and receive them. If you find the picture appears too small in the toolbar, the full image appears in the tooltip. To have a bigger picture all the time (msn style) consider importing some theme from the configuration window.

Webcam Support

No support for now.

Winks and Nudges

Nudges implemented in KDE 3.5 Winks not implemented, plans?

Fixing MSN Error 715: Email Address not Verified

This error happens when the email address in your .net passport has not been confirmed to belong to you. Maybe you ignored the email they send out with a link to verify your email address? This is, unfortunately, not easy to fix (there appears to be no easy way to get that email resent), but there is a way to sort it out:

Method 1

The basic strategy we will follow is based on the observation that if we change the .NET Passport's primary email address, we get resent the confirmation email. So, if you change the primary email address to something else, then change it back, you will be given the opportunity to verify your email address again.

There's a caveat, however. Doing this may mess up MSN contacts in your contact list (though I didn't have any trouble), so make a backup copy of your contact list.xml file first, and if you're really nervous, write down your friends' Passport addresses first.

Here's how to change your primary email address:

  • Go to www.passport.net and log in with the passport you use for MSN Messenger.
  • Navigate to Member Services, then choose Edit my .NET Passport profile
  • Visit the link under your email address which says "I need to change this"
  • Enter your new desired email address and your password, hit the submit button
  • Wait for your confirmation email
  • Visit the link in the email. Click the Continue button, then log in.
Note-box-icon.png
 
Note
The logging in stage is vital; your email address is not verified if you do not log in here.


The first time through (changing your primary email address to something else) you don't need to verify, and can ignore the last two steps.

Method 2

There is supposedly an easier way. From Microsoft Newsgroups, I have discovered the following link: messenger which will begin the Email verification process.

You can also go through the "Contact Us" page and as you complete the form there is a specific option to request a new verification email address. A direct link to this is

http://support.live.com/eform.aspx?productKey=wlid&page=wlsupport_home_options_form_byemail&ct=eformts

Method 3

Even easier is the following: Go to your accounts page:

https://account.live.com/settingspage.aspx?mkt=en-us

If your email is not validated there is a highlighted message at the top of the page stating that your email isn't validated and a link to:

https://account.live.com/verifysi.aspx?mkt=en-us&rp=settingspage

Where a link/button is displayed to "Send me verification email".


This page was last modified on 30 October 2010, at 11:02. Content is available under Creative Commons License SA 4.0 unless otherwise noted.