missing last character in away messages fetched by micq

[LeSpocky]

I'm using micq 0.5.4.1 and a friend of mine licq 1.3.4/SSL. If I fetch his away message the last character is missing. ICQ plugin 0.3.9.0 from Miranda is able to show the complete message though. This doesn't seem to happen always and in a short test not against licq 1.3.2/SSL. According to micq mailing list this could be a problem with LNTS (long null-terminated strings) which are in fact not correctly terminated by licq.

[emostar]

Works fine in the latest Licq:

     0040: 00 FF FF 0E 00 FF FF 00  00 00 00 00 00 00 00 00   ................
     0050: 00 00 00 E8 03 04 00 00  00 08 00 42 75 73 79 2E   ...........Busy.
     0060: 2E 2E 00 00 00 00 00 FF  FF FF 00                  ...........

The message is "Busy..." which is 7 characters, 8 if you include the terminating NULL. Which is what we are sending. By the way, I got micq 0.5.4.1 compiled to test, and it works fine with retrieving the message. Is the person sending non ASCII characters or something?

If you can provide a packet dump that would help this out.

[LeSpocky]

I tested this against my test account on Kubuntu feisty now. I set this account to DND and away message to "arbeit123". With direct connection this is truncated to "arbeit12", with messages through server the message is complete. I attach a packet dump from micq.

I set micq to log packages with "optconnection logstream on", triggered fetching away message with "getauto contactname" and set "optconnection logstream off" then.

Hope that helps.

[LeSpocky]

packet dump of broken away message

[LeSpocky]

The package dump posted before is not as useful as it could but behaviour could be reproduced by micq developer Rüdiger: http://micq.org/pipermail/micq-list/2007-June/001584.html You'll find a dump of a message packet there.

[emostar]

Hmm, I guess it has to do with multibyte characters. Will test it out with that...

[emostar]

OK, it only occurred in direct connections it looks like. Should be fixed with [4985]