Re: killthread script

2004-01-07 Thread Florian Ernst
Hello there!

On Wed, Jan 07, 2004 at 02:39:10PM -0700, s. keeling wrote:
You could add a sub-clause to your Debian lists recipe which greps a
file containing a list of subjects you don't want to see.  I think
Karsten mentioned "| formail ... >> bad_subject" or some such to seed
such a file.  It'll be in the archive somewhere (or was that in
comp.mail.mutt?).
It was here on the list, see
http://lists.debian.org/debian-user-0312/msg04461.html
(Just had it at hand...)

Cheers,
Flo


signature.asc
Description: Digital signature


Re: killthread script

2004-01-07 Thread R. Wood
On Wed, Jan 07, 2004 at 05:24:33PM -0500, Matt Price imagined:
> On Wed, Jan 07, 2004 at 02:03:04PM -0700, s. keeling wrote:
> > Incoming from Matt Price:
> > > I have pretty good spamfilters up now, but I still find
> > > there's a bit too much info for me.  How does one
> > > implement a "killthread script"?
> > 
> > In mutt, type "?"  That shows ^D is mapped to delete thread
> > (at least here it is).
> > 
> ahh... I sort of thought that what was meant by "killthread"
> was a way to pre-emptively kill messages from a particular
> thread before they appear (ideally), this would either be done
> after procmail delivers the mail, or through some kind of
> dynamic addition to .procmailrc).  
> 
> Deleting threads is a good start, but with some of the
> super-active threads on this list or (say)
> [EMAIL PROTECTED], deleting a thread just lets it show up
> again later on.
> 
> does anyone have some kind of script they've developed for htis
> purpose?
> 
> m

I just use a procmail recipe for any thread I want to kill, e.g.

:0 D :
* ^Subject.*empty boot log
/dev/null  # will go to /dev/null


I also have an alias to 'vim ~/.procmailrc' so that I can invoke
my procmail filter file quickly when I need to.

HTH,
Raymond
-- 
"What difference does it make to the dead, the orphans, and the
homeless, whether the mad destruction is brought under the name
of totalitarianism or the holy name of liberty and democracy?"
(Gandhi)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: killthread script

2004-01-07 Thread s. keeling
Incoming from Matt Price:
> On Wed, Jan 07, 2004 at 02:03:04PM -0700, s. keeling wrote:
> > Incoming from Matt Price:
> > > On Wed, Jan 07, 2004 at 02:49:18AM -0600, Jesse Meyer wrote:
> > > > 
> > > > First of all, a good email client, aliases, and a killthread script is
> > > 
> > > I have pretty good spamfilters up now, but I still find there's a bit
> > > too much info for me.  How does one implement a "killthread script"?
> > 
> > In mutt, type "?"  That shows ^D is mapped to delete thread (at least
> > here it is).
> > 
> ahh... I sort of thought that what was meant by "killthread" was a way
> to pre-emptively kill messages from a particular thread before they
> appear (ideally), this would either be done after procmail delivers
> the mail, or through some kind of dynamic addition to .procmailrc).  

You could add a sub-clause to your Debian lists recipe which greps a
file containing a list of subjects you don't want to see.  I think
Karsten mentioned "| formail ... >> bad_subject" or some such to seed
such a file.  It'll be in the archive somewhere (or was that in
comp.mail.mutt?).


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)   http://www.spots.ab.ca/~keeling 
- -


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: killthread script

2004-01-07 Thread Matt Price
On Wed, Jan 07, 2004 at 02:03:04PM -0700, s. keeling wrote:
> Incoming from Matt Price:
> > On Wed, Jan 07, 2004 at 02:49:18AM -0600, Jesse Meyer wrote:
> > > 
> > > First of all, a good email client, aliases, and a killthread script is
> > 
> > I have pretty good spamfilters up now, but I still find there's a bit
> > too much info for me.  How does one implement a "killthread script"?
> 
> In mutt, type "?"  That shows ^D is mapped to delete thread (at least
> here it is).
> 
> 
ahh... I sort of thought that what was meant by "killthread" was a way
to pre-emptively kill messages from a particular thread before they
appear (ideally), this would either be done after procmail delivers
the mail, or through some kind of dynamic addition to .procmailrc).  

Deleting threads is a good start, but with some of the super-active
threads on this list or (say) [EMAIL PROTECTED], deleting a thread
just lets it show up again later on.

does anyone have some kind of script they've developed for htis
purpose?

m


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: killthread script

2004-01-07 Thread s. keeling
Incoming from Matt Price:
> On Wed, Jan 07, 2004 at 02:49:18AM -0600, Jesse Meyer wrote:
> > 
> > First of all, a good email client, aliases, and a killthread script is
> 
> I have pretty good spamfilters up now, but I still find there's a bit
> too much info for me.  How does one implement a "killthread script"?

In mutt, type "?"  That shows ^D is mapped to delete thread (at least
here it is).


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)   http://www.spots.ab.ca/~keeling 
- -


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



killthread script

2004-01-07 Thread Matt Price
On Wed, Jan 07, 2004 at 02:49:18AM -0600, Jesse Meyer wrote:
> On Wed, 07 Jan 2004, Justin Ellison wrote:
> 
> > I'm a linux user of 3 years who manages 10-15 RedHat servers at work,
> > and I've run Gentoo on my laptop since 1.2.
> 
> > The mailing list is great, but the noise floor is too much for me.  
> 
> First of all, a good email client, aliases, and a killthread script is
> your friend.  Impliment one using your email-client-of-choice and your
> scripting-language-of-choice.  Procmail + Mutt + common shell tools can
> do it.  debian-user is a flood of information.

I have pretty good spamfilters up now, but I still find there's a bit
too much info for me.  How does one implement a "killthread script"?
any pointers? 

matt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]