On Mon, 2003-07-28 at 11:46, Joey Hess wrote: > Colin Watson wrote: > > > #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. Would multiple feeds poring into the bit bucket at the same time risk splash back and possible corruption of nearby memory from the spray? ;) -- Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP ML Kahnt New Markets Consulting Tel: (613) 531-8684 / (613) 539-0935 Email: kahnt@hosehead.dyndns.org
Attachment:
signature.asc
Description: This is a digitally signed message part