On Mon, May 28, 2001 at 07:35:47PM -0400, Russ Herrold wrote:
> Off the list, on Mon, 28 May 2001, user Watson wrote:
>
> > Other than just tweaking .procmailrc with a recipe every
> > time some idiot shows up, how would one go about setting
> > up a killfile?
>
> Watson, you know my methods ...
>
<snip>
> I use a two step variant variant of the above:
>
> :0 fhW: $HOME/.killfile.lock
> | egrep -i -f $HOME/.killfile | \
> formail -A "X-killfile: cheeseburger"
>
>
> ... that is the first is a unix filter rather than a
> delivering recipe -- I also allow for exemption from killfile
> screening by a 'passfile' which over-rides the killfile
> marker.
>
> and then later, I use:
>
> :0 h
> * ^X-killfile: cheseburger
> * !^X-passfile: olive
> | ~/$MAILDIR/killfile-dump.$DOM
>
If the last recipe is rewritten as:
:0 h
* ^X-killfile: cheeseburger
killfile-dump.$DOM
the _headers only_ of _all_ messages passed to it will end up in your
killfile folder.
I'm not quite sure why you're "piping" the output to a file and not a
process.
Any tips, Sherlock?
Paul
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:07:44 EDT