After working fine for several years, some of the delivery statements
in my .procmailrc that invoke formail have stopped working. It looks
like this occurred after a recent upgrade. I've put the version info,
some relevent bits from my .procmailrc, and the verbose log comments
below. Does anyone know what might have changed, and how I can fix it?
I've been relying on the tags inserted into the mail to sort it once I've
downloaded it to my local machine (running Eudora light) None-delivering
recipes that invoke formail simply to insert comment lines continue to
work just fine.
Thanks in advance,
Dave Stone
PROCMAIL VERSION:
procmail v3.21 2001/06/29
Copyright (c) 1990-1999, Stephen R. van den Berg <srb(_at_)cuci(_dot_)nl>
Copyright (c) 1997-2001, Philip A. Guenther
<guenther(_at_)sendmail(_dot_)com>
[snip]
Locking strategies: dotlocking, lockf()
Default rcfile: $HOME/.procmailrc
It may be writable by your primary group
Your system mailbox: /var/spool/mail/dstone
FROM .procmailrc:
SHELL=/bin/sh # user shell - csh not recommended
LINEBUF=8192 # gives procmail room to work
MAILDIR=/var/spool/mail/$LOGNAME # !!! location of mail folders
PATH=$PATH:/$HOME/bin:/usr/lib
[snip]
:0:
* [some match condition]
| formail -A "X-Sorted: IN_MAIL_TAG" >> $MAILDIR
FROM log FILE:
procmail: Locking "..lock"
procmail: Executing " formail -A "X-Sorted: IN_MAIL_TAG" >> $MAILDIR"
/bin/sh: .: Is a directory
procmail: Error while writing to " formail -A "X-Sorted: IN_MAIL_TAG" >>
$MAILDI
R"
procmail: Non-zero exitcode (1) from " formail -A "X-Sorted: IN_MAIL_TAG"
$MA
ILDIR"
procmail: Assigning "LASTFOLDER= formail -A "X-Sorted: IN_MAIL_TAG" >>
$MAILDIR"
procmail: Unlocking "..lock"
procmail: Locking "/var/spool/mail/dstone.lock"
procmail: Assigning "LASTFOLDER=/var/spool/mail/dstone"
procmail: Opening "/var/spool/mail/dstone"
procmail: Acquiring kernel-lock
[snip]
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail