Date: Thu, 20 Jun 2002 13:10:39 -0700 From: Matthew Hunt <mph@astro.caltech.edu> To: Bosko Milekic <bmilekic@unixdaemons.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Some small projects for mutt(1) Message-ID: <20020620131039.A7042@wopr.caltech.edu> In-Reply-To: <20020620152454.A23499@unixdaemons.com>; from bmilekic@unixdaemons.com on Thu, Jun 20, 2002 at 03:24:54PM -0400 References: <20020620152454.A23499@unixdaemons.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 20, 2002 at 03:24:54PM -0400, Bosko Milekic wrote: > cool if mutt did it). What this does is pretty straightforward: I see > a thread with subject "foo." I don't like it. I really don't like it. > I hit a key combination such as, I don't know, CTRL+B (or something not > bound yet), and not only is the entire thread instantly marked for > deletion, but a carefully crafted rule is also dropped into a sh*tlist > file (that can be handled by procmail?) which will ensure that all > _future_ mailings that are in response to said thread will immediately > be marked for deletion, or merely filtered. Hence, "persistent thread > suppression/deletion." This shouldn't be hard to glue together without modifying mutt itself. Make a little program, foo, that takes the message on stdin, passes it through "formail -x subject", massages it into a procmail rule, and appends it to some procmail rule file. The "massage" step should include escaping characters that have special meanings in procmail regexps, and adding something like (Re: *)? at the beginning of the subject when appropriate. Shouldn't be more than a screenful of Perl. -- Matthew Hunt <mph@astro.caltech.edu> * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020620131039.A7042>