Benjamin Peikes <benp(_at_)npsa(_dot_)com> writes:
My .procmailrc file is the following
PATH=/bin:/usr/bin:/home/toggle
It would probably be preferable to just add /home/toggle to the front
of the default PATH, ala:
PATH = /home/toggle:$PATH
You usually want your personal directories before the system ones in
the PATH.
:0:
* ^From: Mailer-Daemon(_at_)vtt(_dot_)co(_dot_)za
/dev/null
:0:
* ^FROM_MAILER
| /home/toggle/parse_returned_mail
:0:
* ^FROM_DAEMON
| /home/toggle/parse_returned_mail
:0:
* MAILER-DAEMON
| /home/toggle/parse_returned_mail
:0:
*
! benp(_at_)npsa(_dot_)com
None of those recipes needs a locallockfile, so the second colon should
be removed from each of the ":0:" lines. Indeed, if you had a LOGFILE
defined, it would contain piles of warnings from procmail that it
couldn't determine what the lockfile should be named.
Also, since you've added /home/toggle to the PATH, there's no need to
include the path in the action. Just say
| parse_returned_mail
this account is at toggle(_at_)bozlo(_dot_)npsa(_dot_)com and is getting mail
forwarded to it from sender(_at_)togglethis(_dot_)com and
list-errors(_at_)togglethis(_dot_)com
The problem is that mail from MAILER-DAEMON is getting forwarded to
benp(_at_)npsa(_dot_)com
I suggest that you set a LOGFILE, then turn on VERBOSE, by putting the
following at the top of your .procmailrc:
LOGFILE = $HOME/procmail.log
VERBOSE = on
you can then examine $HOME/procmail.log to see what procmail thinks is
going on.
Philip Guenther