public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [TOOL] matchreply: make procmail aware of threads and dups
Date: Thu, 03 Sep 2009 17:58:10 +0900	[thread overview]
Message-ID: <4A9F8522.1010900@kernel.org> (raw)
In-Reply-To: <4A9F847C.60606@kernel.org>

Tejun Heo wrote:
> Hello,
> 
> I've been reading the rather unfortunate LAK stuff on this week's LWN
> and it seems like other people are having similar problems with
> duplicated messages from different mailing lists.  Here's a program
> I've been using for a couple of years now to solve the issue.  It
> builds index of Maildir folders and can match for duplicates or a
> thread a message belongs to and very easy to use with procmail.
> 
> With proper procmailrc rules, this allows me not to worry about dups
> (there's race window and some might escape from time to time but no
> biggie) and easily follow the threads I'm interested in by simply
> moving the thread to one of the folders I keep closer eye on
> regardless of the actual target delivery addresses.
> 
> The attached tarball contains README but it's outdated and doesn't
> explain the -d option which matches for duplicates.
> 
> Here's my .procmailrc with some explanations which I grew over the
> years and am sure can be made much prettier somehow but it should show
> how it can be used.

Ooh.. right, one more thing.  To make the messages I wrote to be
filtered the same way, I disable the MUA from storing sent messages
directly and instead make it bcc myself, so that those end up in the
same folders as the threads they belong to.

Thanks.

-- 
tejun

      reply	other threads:[~2009-09-03  8:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03  8:55 [TOOL] matchreply: make procmail aware of threads and dups Tejun Heo
2009-09-03  8:58 ` Tejun Heo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A9F8522.1010900@kernel.org \
    --to=tj@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox