procmail
[Top] [All Lists]

Dealing with private Cc:s of list replies (was Re: Lockfile on $DEFAULT?)

1998-06-15 02:05:35
On Sun, 14 Jun 1998 01:37:51 -0400, Walter Dnes
<waltdnes(_at_)interlog(_dot_)com> wrote:
Step 2, have procmail dump the *PRIVATE* duplicate.  I don't
like the example in the manpages using formail and the message-Id
cache.  That one dumps the second copy that comes in.  99% of
the time, the private copy, going direct, gets to me before
the list copy, which has to detour via the list-server.  I want
the list-copy, so that if I reply to it, the reply goes to the
list.

What I do is actually stick a simple header on anything that lands in
my primary inbox which alerts me to the fact that it was also Cc:ed to
one of the lists I read. I make the header multi-line to make it stand
out. (I do the list filtering on the From_ line when I can, so
anything not From_ one of the lists I subscribe to basically lands in
my inbox.)

  ## Mark list Cc:s suitably

  NL="
"
  :0fhw
  * 
^TO_\/(procmail(_at_)informatik\(_dot_)rwth-aachen\(_dot_)de|spam-l(_at_)peach\(_dot_)ease\(_dot_)lsoft\(_dot_)com|\
        etc...)
  | formail -I"X-List-Cc: $NL   $MATCH"

My MUA selectively hides headers and so I've conveniently asked it to
hide To: and Cc: lines which match lists I subscribe to. Reduces
header clout on the screen and the X-List-Cc header is visible when
it's there, and alerts me suitably about Cc:ed mail.

/* era */

-- 
 Paparazzi of the Net: No matter what you do to protect your privacy,
  they'll hunt you down and spam you. <http://www.iki.fi/~era/spam/>

<Prev in Thread] Current Thread [Next in Thread>