i have a problem with smbclient -M and a message with this format:
the message have 2 lines and 126 characters. this messages is saves in a file for testing. i test it with lines with different lenght, but this makes no change.
if i send this message with smbclient -M host<messagefile, i get no message popup at the host.
i use ethereal to log transfer and found the packets, which smbclient is sending with the message.
a message with same character count and 3 lines make no problems or one character more or less works also. only with 2 lines and 126 characters (count with wc) is not displayed.
i change some characters or all, but this have no effect.
i send this message to a host with winxp and win2000, but none of them display the message or log it to systemlog.
i don't know, if this is a problem from windows or samba, but it is not good!
Tried it with a cut&paste from the bug report, works for me.
Please re-open with more info like the file that fails for you as an attachement and a sniff of the failed attempt.
Created attachment 2097 [details]
you know, that with copy and past more then 126 characters are copied while there are some spaces at the end of the first line ?
to reproduce this error, you must create a text-file (like the test-file) which have a size of 126 bytes and 2 lines with text.
Ok, got it reproduced. The trick is to use it against XP and not NT4. NT4 can cope with that 2-liner you sent. Weird one.
i can it only test with xp and win2000 because i have no running nt4 at the moment.
and with both it don't work with this message and i don't know why.
Understood. I just wanted to ack that I could reproduce it. The problem is that right now I'm busy with other stuff.
I've found out, that the problem is reproducable with messages sent from 'smbclient -M' to Windows 2k or XP with a transfer length of multiples of 127 bytes and multiples of 127 bytes plus 1 byte. That means for example messages with length of 127, 128, 254, 255 etc. bytes are not displayed under Windows!
Created attachment 2924 [details]
I've checked in the attached patch as r25169, it fixes the bug for me.
The patch fixes it for me, please re-open if it doesn't for you.