Lock failure on "spamc.lock"

I'm seeing this in my procmail log in reference to locking with
spamassassin. I have seen the question posted in the usual places,
but I have found no hints as to why this is happening. Permissions
seem right. Anyone have any advice on this one?

Here is my procmailrc:

------------------------------------------------------------ ---------------------
LOGFILE=/var/log/procmail.log
DROPPRIVS=yes
VERBOSE=1

:0fw: spamc.lock
* < 256000
| /usr/bin/spamc

DATE=`/bin/date +%Y-%m-%d`
MAILBOX=/var/mail/spam

:0:
* ^X-Spam-Level: \*\*\*\*
$MAILBOX/$DATE

# Work around procmail bug:
:0
* ^^rom[ ]
{
LOG="*** Dropped F off From_ header! Fixing up. "

:0 fhw
| sed -e '1s/^/F/'
}

:0:
| /usr/sbin/sendmail -io "$@"
------------------------------------------------------------ -----------------------

Thanks.

Re: Lock failure on "spamc.lock"

On 11 Jul 2005, colonel wrote:
> I'm seeing this in my procmail log in reference to locking with
> spamassassin. I have seen the question posted in the usual places,
> but I have found no hints as to why this is happening. Permissions
> seem right. Anyone have any advice on this one?
>
> Here is my procmailrc:
>
> ------------------------------------------------------------ ---------------------
> LOGFILE=/var/log/procmail.log
> DROPPRIVS=yes
> VERBOSE=1
>
> :0fw: spamc.lock
> * < 256000
> | /usr/bin/spamc


You should not use a lock file when you pipe a message to spamc,
i.e., use this recipe instead of the one above:

:0 fw
* < 256000
| /usr/bin/spamc

I discuss this (including explanatory links) in the SpamAssassin
section of my Procmail Quick Start, which is here:



Nancy

--
Nancy McGough ~ ~
IMAP, pine, procmail, data deflexion, infinity, and more
> > > Please keep the discussion in the group < < <