Jason van Brecht followed up,
| I did however create a path statement, did not work, in procmailrc I have
| XM=/usr/X11R6/bin/xmessage and in the recipre file itself I have tried
|
| | xmessage , | xmessage -, |$XM (I also tried | $XM -)
| none of those 4 have worked, I can use xmessage, works just great from an
| xterm or console.
Stan Ryckman is probably right: maybe your mail is being delivered on another
machine where xmessage is not installed or is not at that location.
Put this into your .procmailrc
LOG="$HOST
"
(note the trailing quote on the next line to enclose a literal newline
between the quotes) and see what it records in your logfile.
| Is there any other way to make procmail just execute a
| program rather then pipe the output to the program, say if a critical msg
| came in, instead of piping the body of the message to my screen, I could
| rather just say "xmessage go check your mail NOW" or something of the
| like.
You can trick procmail into limiting the input to a program that it runs,
but it still has to be able to find the program. The problem is not that
xmessage isn't accepting input, it's that procmail cannot invoke xmessage.