Alex Schroeder <alex(_at_)zool(_dot_)unizh(_dot_)ch> writes:
Everything seems to work with procmail, except for this strange
message in my log file. I have no idea what SYSPATH could mean.
SYSPATH: Undefined variable.
SYSPATH: Undefined variable.
From wschaly(_at_)platinum(_dot_)com Tue Nov 19 14:34:44 1996
Subject: Mojn Alex
Folder: /usr/spool/mail/alex 1705
SYSPATH: Undefined variable.
SYSPATH: Undefined variable.
From u2458(_at_)bwl(_dot_)uni-kiel(_dot_)de Tue Nov 19 17:11:33 1996
Subject: atlantis befehle
Folder: formail -r -k -b -A "Precedence: junk"\ 1609
SYSPATH: Undefined variable.
SYSPATH: Undefined variable.
From GuWolf(_at_)aol(_dot_)com Tue Nov 19 17:50:48 1996
Subject: Re: Bitter erklaehr mir mal...
Folder: /usr/spool/mail/alex 1839
This is most likely related to starting up a shell from your .procmailrc,
either via an action or via a backquote expansion. If your shell is of
the C-shell variety (csh or tcsh), then it will give this error if one
of the shell's startup scripts contains a reference to $SYSPATH without
it being defined, perhaps with the expectation that SYSPATH would be
passed in from login.
Solution: Put the following at the top of your .procmailrc:
SHELL = /bin/sh
By using the Bourne shell, which is much more suitable for scripting,
you'll avoid both this a other possible brokennesses.
Philip Guenther