Setting up MSN with BitlBee

Upgrade required!

As of 2014-11-11, you will need to upgrade to the latest development version (bzr 1064)

Microsoft blocked the "ApplicationID" of windows live messenger 2008 (8.5), which happens to be used by several third party clients, including BitlBee and pidgin.

If you use debian/ubuntu, upgrading is easy: see Packages and use our APT repo.

If you use bitlbee-libpurple, you'll have to upgrade to libpurple 2.10.11.

Connection refused?

Try adding a line to your /etc/hosts like this (take the IP number from one of the working ones in http://ismsndeadyet.com/)

157.56.108.81 messenger.hotmail.com

Or install bitlbee libpurple and enable http method:

account msn set http_method on

Network status

Visit http://ismsndeadyet.com!

That page also lists a few other IP addresses and their status in case you get 'connection refused'.

Adding the account itself

To add a MSN account to BitlBee:

account add msn username@hotmail.com password
account msn on

This should be enough for most people.

You can also leave out the password and set it afterwards with /oper.

FAQ

Q: Why would I want MSN?

Q: Isn't it going to die?

Q: Doesn't MSN use the XMPP protocol?

Q: Is OAuth supported?

Versions

All current stable versions will fail to login, due to blocked ApplicationID - upgrade to bzr 1061 or patch the binary

The last important upgrade to MSN support in bitlbee was in 3.0.6, with MSNP18 support and multiple points of presence.

Troubleshooting

"Login error: Connection timeout" after "Authenticated, getting buddy list"

If you haven't upgraded yet, this is what the blocked ApplicationID error looks like.

<@root> msn - Logging in: Connecting
<@root> msn - Logging in: Connected to server, waiting for reply
<@root> msn - Logging in: Transferring to other server
<@root> msn - Logging in: Connected to server, waiting for reply
<@root> msn - Logging in: Authenticated, getting buddy list
<@root> msn - Login error: Connection timeout
<@root> msn - Logging in: Signing off..

"Error during Passport authentication: (null)"

The most common error, usually means "location blocked".

See HowtoFixMsn for a solution.

This error says "(null)" because bitlbee can't parse the error message to show something more meaningful. Because of this, it could also get shown for other error codes.

"Error reported by MSN server: Authentication failed"

This error can mean that the account is "temporarily blocked" and you need to verify it by providing a phone number.

It has also been seen when using a non-primary 'alias' address to log in to an account (just switch to the correct one).

Check your account recent activity page for more details, and see HowtoFixMsn.

"Error during Passport authentication: wsse:FailedAuthentication (Authentication Failure)"

This error almost always means that the password is incorrect.

"BitlBee - Received offline message. BitlBee can't show these"

You'll have to use a different client to fetch those messages (pidgin, amsn, emesene, etc)

The reason this message is shown is because the relevant code isn't implemented in bitlbee yet. Patches welcome

Server side support of offline messages has been disabled - if you actually get this message, let us know in #bitlbee!

A groupchat opens for individual conversations

MSN groupchats are weird. Your bitlbee is confused.

(known bug)

A note about outlook.com

Outlook.com is the new hotmail.com / msn.com / live.com. Some useful stuff you can do with it: