#871 closed enhancement (fixed)

Switch MSN implementation to XMPP

Reported by: anonymous Owned by: wilmer
Priority: wishlist Milestone:
Component: MSN Version:
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro:


Microsoft has announced their plans to make the Windows Live Messenger services available over XMPP.

It'd be extremely nice to see bitlbee support this.

Attachments (0)

Change History (8)

comment:1 Changed at 2011-12-16T22:14:08Z by anonymous

It looks like it uses a different authentication mechanism, also, it apparently lacks roster management.. so not really a suitable replacement for the reverse engineered MSN protocol backend.

comment:2 Changed at 2011-12-17T08:20:57Z by wilmer

Indeed it's stripped down, like Facebook's XMPP. I'll try to get the XMPP module to support the authentication scheme though, since for day-to-day things it's likely much nicer, and it'll always be a nice fallback when the native MSN module stops working.

comment:3 Changed at 2011-12-18T17:39:08Z by wilmer


18:34:21 <@root> jabber - Logging in: Server changed session resource string to 
18:34:21 <@root> jabber - Logging in: Authenticated, requesting buddy list
18:34:21 <@root> jabber - Logging in: Logged in
18:34:22 -!- _65fa8ab93184d611 [] has joined &bitlbee
18:34:22 -!- ServerMode/&bitlbee [+v _65fa8ab93184d611] by
18:34:22 -!- _2cf8192c9204b909 [] has joined &bitlbee
18:34:22 -!- ServerMode/&bitlbee [+v _2cf8192c9204b909] by

But the handles definitely suck. At least WHOIS helps:

18:34:27 -!- _65fa8ab93184d611 []
18:34:27 -!-  ircname  : Wilmer
18:34:27 -!-  server   : [jabber network]
18:34:27 -!- End of WHOIS
18:34:31 -!- _2cf8192c9204b909 []
18:34:31 -!-  ircname  : Sjoerd
18:34:31 -!-  server   : [jabber network]
18:34:31 -!- End of WHOIS

This is definitely not useful enough to drop native MSN support. Worst part is, it seems that there is no way to get a token that lasts for more than an hour, so you'll have to do the "authorize in browser, pass authentication code back to BitlBee" dance again every time you log in..

comment:4 Changed at 2011-12-18T19:30:33Z by wilmer

changeset:xmpp-oauth,815 should have this now. If you want to try it out:

19:39:21 <@wilmer> ac add jabber bla
19:39:21 <@root> Account successfully added with tag jabber
19:39:28 <@wilmer> ac jabber set oauth on
19:39:28 <@root> oauth = `on'

Something like that should work. Please let me know how that goes.

I think the nightly build bot will automatically pick up this branch within the next few hours.

comment:5 Changed at 2011-12-18T19:30:58Z by wilmer

Oh yes, you probably want to add a "ac jabber set nick_format %full_name" there too.

comment:6 Changed at 2012-02-11T17:09:05Z by wilmer

Resolution: fixed
Status: newclosed

Well, this stuff works. But it's not going to be ready for replacing the "native" MSN module any time soon.

Fixed for as much is reasonable.

comment:7 Changed at 2012-02-19T20:18:14Z by deferraz@…

I tried on 3.0.5 release and set oauth to on but i'm receiving this:

.:18:11:39:. @root: jabber - Logging in: Connecting .:18:11:39:. @root: jabber - Logging in: Connected to server, logging in .:18:11:39:. @root: jabber - Logging in: Converting stream to TLS .:18:11:39:. @root: jabber - Logging in: Connected to server, logging in .:18:11:40:. @root: jabber - Login error: BitlBee does not support any of the offered SASL authentication schemes:


There is some other thing to set?

comment:8 Changed at 2012-03-10T00:01:22Z by wilmer

That's fixed now.

Modify Ticket

as closed The owner will remain wilmer.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.