When issueing "smbclient -M somehost", the message is received by that host but
the username comes out as ______g__ or something equally unusable.
This can be confirmed by changing the message command line to something like:
message command = echo %f "@" %m "->" %s >> /tmp/messages
which results in lines such as:
____________________h @ pug -> /tmp/msg.uPZ2fb
where pug is the correct host but user is expected to be "jaco".
Additionally it doesn't look like smbclient honors the -n flag (if I do
"smbclient -M slowcoach -n testy" it still shows up as pug).
If Windows clients sends messages to this host then I get the correct values,
also samba 2.2.x works correctly.
I think this is fixed in 3.0.12
Probably earlier already - I just checked 3.0.10 and it's fixed there already.
I can't seem to get -n working but that may be due to other issues (I'm running
a WINS server).