Some threads just go on too long. Personally I think a troll has hijacked the main centos list again and is inducing food fight behaviours while that troll perfectly 'innocently' asserting that it is just respoding to all email.
see: http://video.google.com/videoplay?docid=-4216011961522818645 for a discussion of the problem of 'capture' in FOSS projects.
But if one loses interest in a thread, it is easy enough to tune them out:
1. Install procmail; yum knows how
2. Add a mark and drop ruleset
[herrold@new .procmail]$ cat ~/.procmail/killfilerc # # mark them :0fh ^ *List-Id:.*centos.centos.org ^ *Subject:.*CentOS Based Linux Firewall Document *!^X-brand | formail -A "X-brand: killfile "
# and dump them :0 w * ^X-brand: killfile /dev/null
3. Integrate it in mailhandling; a fragment from: /home/herrold/.procmailrc
# easy drops INCLUDERC=$HOME/.procmail/killfilerc
-----------------------------------
easy enough to save 'caught' pieces to a file, rather than devnull until you are certain collateral damage has not been induced; see the procmail manpage series for a full discussion.
-- Russ Herrold
Hi Russ,
Thanks for this hint. I have a couple of questions.
On 6/7/07, R P Herrold herrold@owlriver.com wrote:
:0fh
- ^List-Id:.*centos.centos.org
This is a handy way of filtering by the mailing list name. Thanks.
- ^Subject:.*Some subject line here
*!^X-brand | formail -A "X-brand: killfile "
# and dump them :0 w
- ^X-brand: killfile /dev/null
Could you explain why you are going through killfile here? For example, can't you just do:
:0: * ^(From|Sender|Received):.*Perrin /dev/null
if you do not want anything from a person named Perrin? I have lines like that in my filter (not with 'Perrin' by the way) and it seems to be working. As you can tell, I am not very familiar with procmail filter format.
Akemi
-- Russ Herrold
On Fri, 8 Jun 2007, Akemi Yagi wrote:
Could you explain why you are going through killfile here? For example, can't you just do:
:0:
- ^(From|Sender|Received):.*Perrin /dev/null
It _is_ certainly possible to do it all in one step, but I do LOTS of marking (with the 'f' filter operator) in my procmail rules [I have about 10,000 lines of procmailrc marking, re-writes, redirects, and so forth], and it helps me to debug matters this way, when I save up the actual drop to one place.
I actually will turn on logging markers around a rule when I am 'tuneing' it up (procmail rules are not quite regex's and I still consult the man pages, after probably a decade building my ruleset). For the mailing list, I simplified my example, as in production, the marking for a killfile and the actual drop are done in differing files.
from my ~/.procmailrc:
# at the start, whitelist certain senders # and RPH personal stuff # INCLUDERC=$HOME/.procmail/friendbrandrc # LOG="after friendbrandrc # " INCLUDERC=$HOME/.procmail/logbrandrc # LOG="after logbrandrc # " INCLUDERC=$HOME/.procmail/clientbrandrc # LOG="after clientbrandrc # "
I have fuzzed the names of some of the rules for some rules.
[herrold@new herrold]$ wc .procmailrc ; cd .procmail ; wc -l *rc 758 2418 17979 .procmailrc 164 antispamrc 140 bugzillarc 18 caosityrc 17 centosrc 133 clientbrandrc 114 devnullrc 9 diskwarningrc 13 dsblcleanuprc 44 ecommercerc 38 elaaarc 345 embbbrc 40 epcccrc 24 flipfloprc 492 friendbrandrc 18 ibdddrc 18 infectedrc 38 iweeerc 15 killfilerc 6013 listbrandrc 15 logbrandrc 20 mailbouncerc 11 mailinglistmgtrc 51 mirrorlistrc 71 monitoringrc 2 monitorrc 59 nagiosrc 169 old-spam-handlerrc 2 ORCmailHUPrc 68 ORCStatusrc 42 parcelrc 1 qnrc 11 registrarrc 22 replylooprc 3 spamassassin-default.rc 125 spamtraprc 30 tegggrc 38 templaterc 339 twitbrandrc 18 ubhhhrc 49 vendorrc 32 virusbrandrc 311 whitelistrc 36 wiiiirc 9 wingsrc 159 zz_filingrc 9386 total [herrold@new .procmail]$
-- Russ Herrold
-
Akemi Yagi -
R P Herrold