On 04/06/2006, at 6:44 PM, Stian B. Barmen wrote: > First thing is an issue that one of my users are reporting. > > "Sometimes when I use MSN transport on jabber.no I get a message like > this and It logs me off. (when I log in again it log me off and > I've to > wait 30 min or longer to try log) On aMSN client or somewhere MSN > works > correct. > > Disconnected from MSN servers: [Failure instance: Traceback (failure > with no frames): exceptions.UnicodeDecodeError: 'utf8' codec can't > decode byte 0xa9 in position 1: unexpected code byte > ]" > > I have enquired him for his passport name so I can search the log > files > for more evidence but I thought maybe I would just send it to you, > maybe > you already know what it is? Also I dont know which rev this was, > but I > guess 166 or 170. > > Number two is something that I noticed yesterday. I have used the new > MSN Live beta messenger, and so has a few of my friends. One of these > sent me an offline message the 22 of may and I have not been online > with > the MSN Live client in quite some time. Yesterday I logged on the Live > client and then I got the old offline message. So it seems the MSN > transport does not handle the MSN Live offline messages at all, it > just > does not get delivered. > > My guess would be that the Live client does some kind of discovery of > these messages, and pymsnt just listens for incoming events. > Support for > these offline messages would be good to implement before MS > releases the > new client or else jabber users will loose a lot of offline messages > from their contacts. > > Sorry for the lengthy mail :) > > Best regards > Stian B. Barmen
If you can grab me some log files, I'll be able to look into the first. Thanks. As for the second. Yes, I need to code support for offline messages. I will be doing it soonish. --- James
