Jason <jvanbrec(_at_)UU(_dot_)NET> writes:
Okay, I tried it, but I get the same error wit the recipe you gave me, as
with all the ones I tried myself. (snippet of log file at the end for the
error)
...
:0
* ^Subject:.*Unauthorized*
{
:0c
Critical
:0b
| xmessage
}
...
procmail: Executing "xmessage"
procmail: [3942] Mon Aug 31 13:03:18 1998
procmail: Assigning "LASTFOLDER=xmessage"
From grim(_at_)shell1(_dot_)darkwing(_dot_)net Mon Aug 31 13:03:17 1998
Subject: test
Folder: xmessage
11
xmessage: xmessage: cannot open
The error message is being generated by xmessage, not procmail. I
would guess that xmessage expects a filename as an argument and
doesn't know to read stdin by default. You could try changing the
action to be:
| xmessage -
If that doesn't work but you're on a newish UNIX system that has /dev/fd
(Solaris 2.x and Linux both have this, I don't about others), then the
following may work:
| xmessage /dev/fd/0
Philip Guenther