[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20031031005850.GS31048@sparky.finchhaven.net>
From: jsage at finchhaven.com (John Sage)
Subject: Shortcut...... may cause 100% cpu use!!!
Gregory, et al:
On Thu, Oct 30, 2003 at 02:07:23PM -0800, Gregory A. Gilliss wrote:
> Okay, I've enjoyed about as much of this as I can stand >-)
>
> Here's a new vulnerability: filtering out annoying peoples' postings
> on mailing lists. For purposes of example, we'll use FD and Bipin.
> (BTW, I did not come up with this, I'm just relaying it for educational
> purposes only etc):
>
> Let's say that I have concluded that any post from Bipin is a waste of
> bandwidth. The following course of action keeps the bandwidth wasters'
> postings to FD from showing up in my inbox:
>
> 1) install procmail (if you don't already use it)
> 2) touch ~/.procmailrc (see above)
> 3) include the following procmail rule in ~/.procmailrc:
>
> :0
> * ^X-BeenThere: .*full-disclosure@...ts\.netsys\.com
> * ? formail -x"From:" -x"From" -x"Sender:" | egrep -is -f $HOME/.mutt/blacklist.
> fd
> /dev/null
/* snip */
as with perl, there's more than one way to do it.
Here's what I've had in place for some time:
:0:
# Luz3rz L1zt
* ^From:.*(other_people_snipped_to_avoid_insulting_anyone_for_some_reason|visitbipin@...oo\.com|door_hUNT3R@...ckcodemail\.com)
Luz3rz_L1zt
I too get to see the replies where I want them, but anything from
Blipin (or whatever his name is..) and a few select others :-) goes
where I don't need to be bothered maybe more often than once a week,
say...
- John
--
"Most people don't type their own logfiles; but, what do I care?"
-
John Sage: InfoSec Groupie
-
ABCD, EFGH, IJKL, EmEnOh, Pplus+, Mminus-
-
ATTENTION: this entire message is privileged communication, intended
for the sole use of its recipients only. If you read it even though
you know you aren't supposed to, you're a poopy-head.
Powered by blists - more mailing lists