On Mon, 31 Aug 1998, David W. Tamkin wrote:
programname: programname: cannot open
when procmail cannot execute programname, even though you'd logically expect
procmail: programname: cannot open
I had written privately to Jason that most likely xmessage is not in his
procmailrc's PATH (and he should fix the PATH, invoke xmessage by its
absolute path, or invoke xmessage by its relative path from $MAILDIR) or that
using it may require privileges that he has during his interactive logins but
which procmail processes started for him when he gets incoming mail do not
have. He did not reply.
Ack, sorry, been pretty busy.
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.
At one point I had procmail > filename and then tried to execute
xmessage -file filename, that did not work either. I am getting pretty
desperate here. 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.
==================================================================
Jason van Brecht
jvanbrec(_at_)uu(_dot_)net
==================================================================