Siggy Brentrup writes:
Looks like a locking problem to me.
Try starting .procmailrc entries with
:0w:
the trailing colon enables locking
Ah. Oops! I overlooked this. Thanks.
But am I supposed to be getting:
procmail: Extraneous locallockfile ignored
In my LOGFILE file?
I've read the man page over several times
trying to figure out how I am supposed
to have procmail do file locking.
Below is a section of my .procmailrc.
Perhaps I have done something silly.
-- Todd T. Fries .. friest(_at_)acm(_dot_)org
# $Id: .procmailrc,v 1.2 1997/01/26 18:45:26 todd Exp $
DEFAULT=/var/spool/mail/todd
LD=/home/todd/Mail/log
MD=/home/todd/Mail
LOGFILE=$MD/mail.log
SUSPEND=60
NORESRETRY=600
LOCKSLEEP=5
LOCKEXT=.lock
COMSAT=no
:0w:
* ^X-Mailing-List:
{
:0w:
* ^X-Loop: debian
{
:0w:
* ^X-Loop: debian-user
$MD/news/linux.debian.user
:0w:
* ^X-Loop: debian-changes
$MD/news/linux.debian.changes
:0w:
* ^X-Loop: debian-announce
}
:0w:
* ^X-Loop: linux-ggi(_at_)eskimo(_dot_)com
$MD/news/linux.dev.ggi
:0w:
* ^X-Loop: jolt-list(_at_)redhat(_dot_)com
$MD/news/linux.dev.java.jolt
:0w:
* ^X-Loop: ROOTS-L(_at_)rootsweb(_dot_)com
$MD/news/lists.ROOTS-L
}
[...] (this part is similar to the above)
:0w:
* ^TO:(_dot_)*linux-afs(_at_)MIT(_dot_)EDU
$MD/news/linux.dev.afs
:0wch:
| gzip -9 >> $LD/headc.gz