> From [EMAIL PROTECTED] Mon Jul 28 09:51:49 2003
>
>
> On Mon, Jul 28, 2003 at 11:46:11AM -0400, Joey Hess wrote:
> > Colin Watson wrote:
> [somebody broke attributions]
> > > > #Move flagged spam into the bottomless Unix pit.
> > > > :0:
> > > > * ^X-Spam-Flag: YES
> > > > /dev/null
> > >
> > > :0: says to use a locallockfile, which by default is the destination
> > > filename with $LOCKEXT appended, and you won't be able to write to
> > > /dev/null.lock. Try ':0:$HOME/.procmail.spam-lock' or something instead.
> >
> > Better yet don't lock it at all, /dev/null really does not care if two
> > processes write to it at once.
>
> Obviously I need more coffee :-)
>
> --
> Colin Watson [EMAIL PROTECTED]
>
I have heard that it is a bad idea to use lockfiles with /dev/null in procmail.
The source was more than credible but couldn't remember why....
Alan
--
For Linux/Bash users: Eliminate spam from your life
with the Mailbox-Sentry-Program. See the thread
MSP on comp.mail.misc for the latest version.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
