Hi,
I downloaded anh installed LinPopUp. I also add to samba file smb.conf:
message command = /usr/local/bin/LinPopUp "%f" "%m" %s; rm %s

After that, I lauch LinPopUp end send message to a Windows 2000 machine. It's successful. But I cannot receive message from the Windows 2000 machine.
Help me!
Thanks!

I have the same problem and its buggen the $#!+ out of me, any suggestions?

I have the same line in my smb.conf, samba restarts normally but still it will not execute the LinPopUp program upon incoming messages from anywhere, even the localmachine.

check if linpopup is in /usr/local.
If not specify its location in global section of smb.conf

I've been working on the problem with isoaga, and this is not the problem i'm afraid. Here is the standard line from our samba distribution; the first thing we tried:

message command = /usr/bin/LinPopUp "%f" "%m" %s; rm %s &

LinPopUp is definitely at the path specified.

I've tried other things, some as simple as attempting to redirect the file to somewhere where I can see it:

message command = /bin/bash -c 'cat %s > /message; rm %s' &

This dosen't work either - no file called message appears, however the sender gets a "message sucessfully set" conformation from smbd... Mabey it's something to do with permissions... does anyone know what user the message command is run under?

Thanks,
c42f

Well... it's seems that everibody has the same problem. I can't receive messages either.

For the ones who had the same problems like i did, this is what worked for me:

I downloaded the LinPopUp-1.2.0-3.src.rpm from http://www.chez.com/littleigloo/file...2.0.src.tar.gz and i installed. After that i modified the smb.conf file ( in redhat 9 this file is located in /etc/samba ) by writing in the Global section the line:
message command = /usr/local/bin/LinPopUp "%f" "%m" %s; rm %s
I was assured that i must spell EXACTLY as above, or strage problems might ocure.
After that i saved the smb.conf file and RESTARTED the service. And finally, i turned off the firewall (in my case i stopped the "iptables" service).

So... now you should be able to send messages to a target computer ( but not to the all network at one time - like in the "net send * message" command from win ), and you can "fool" the others windows machines that you are receiveing messages, when in fact you don't.

That's it 'till now. If i will find the answer i will post it here, but, it would be so much nicer if the answer will be posted by someone else, so i could read it
Ain't that a newbie's dream?