public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Paulo Marques <pmarques@grupopie.com>
Cc: Lukasz Stelmach <stlman@poczta.fm>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [OT] mailing list management
Date: Fri, 03 Jun 2005 02:11:05 +1000	[thread overview]
Message-ID: <4889.1117728665@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 01 Jun 2005 11:49:08 +0100." <429D92A4.1060103@grupopie.com>

On Wed, 01 Jun 2005 11:49:08 +0100, 
Paulo Marques <pmarques@grupopie.com> wrote:
>The thing is, this list has a lot of traffic (as you might have noticed 
>:), and sometimes people don't have time to go through all the emails, 
>and just take special attention at mails directed at them personally.

"There is always more than one way to do things".

~/.procmailrc

#################################################################
# If my address appears in To:, Cc: or Bcc: then add X-To-Me: YES
#################################################################

:0 Whc
| formail -c -x to -x cc -x bcc | egrep -i 'some expression' > /dev/null
:0 aWhf
| formail -A 'X-Personal: YES'

Replace some expression with a grep expression that matches all email
addresses that you consider personal.  Such mail on any list gets the
line 'X-Personal: YES' added, which makes it trivial to file or index
them separately.

To suppress duplicate messages, also in .procmailrc

:0 Wh: msgid.lock
| formail -D 20000 msgid.cache


  parent reply	other threads:[~2005-06-02 16:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 10:13 [OT] mailing list management Lukasz Stelmach
2005-06-01 10:22 ` Jan-Benedict Glaw
2005-06-01 10:27   ` Christoph Hellwig
2005-06-01 10:34     ` Lukasz Stelmach
2005-06-01 10:43       ` Bernd Petrovitsch
2005-06-01 10:31   ` Lukasz Stelmach
2005-06-01 10:45     ` Bernd Petrovitsch
2005-06-01 11:02       ` Lukasz Stelmach
2005-06-01 17:37         ` Stefan Smietanowski
2005-06-02  9:45           ` Lukasz Stelmach
2005-06-01 10:46     ` Jan-Benedict Glaw
2005-06-01 10:49     ` Paulo Marques
2005-06-01 11:10       ` Lukasz Stelmach
2005-06-02 16:11       ` Keith Owens [this message]
2005-06-03 12:03         ` Lukasz Stelmach
2005-06-03 12:37           ` Jochen Striepe
2005-06-01 11:41     ` Paul Jakma
2005-06-01 12:44       ` Lukasz Stelmach
2005-06-01 13:01         ` Måns Rullgård
2005-06-02  9:50           ` Lukasz Stelmach
2005-06-02 12:34             ` Måns Rullgård
2005-06-03 11:42               ` Lukasz Stelmach
2005-06-03 11:46                 ` Måns Rullgård
2005-06-01 13:25         ` Paul Jakma
2005-06-02 10:05           ` Lukasz Stelmach
2005-06-02 21:31     ` Michelle Konzack
2005-06-01 10:30 ` Måns Rullgård
2005-06-01 10:53   ` Lukasz Stelmach
2005-06-01 11:01     ` MadMike
2005-06-01 11:06       ` MadMike
2005-06-01 11:09     ` Matthias Andree
2005-06-01 11:14     ` Bernd Petrovitsch
2005-06-01 11:16 ` Jesper Juhl
2005-06-03 12:53 ` Matti Aarnio
     [not found] <4ayEi-52j-23@gated-at.bofh.it>
     [not found] ` <4ayNT-58e-27@gated-at.bofh.it>
     [not found]   ` <4az7m-5lG-31@gated-at.bofh.it>
2005-06-01 13:02     ` Bodo Eggert

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=4889.1117728665@ocs3.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    --cc=stlman@poczta.fm \
    /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