From owner-freebsd-chat  Wed Jul 23 21:14:52 1997
Return-Path: <owner-freebsd-chat>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA06406
          for chat-outgoing; Wed, 23 Jul 1997 21:14:52 -0700 (PDT)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06373
          for <chat@FreeBSD.ORG>; Wed, 23 Jul 1997 21:14:10 -0700 (PDT)
Received: from localhost (jfieber@localhost)
	by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id XAA06669;
	Wed, 23 Jul 1997 23:13:50 -0500 (EST)
Date: Wed, 23 Jul 1997 23:13:49 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Francisco Reyes <francisco@natserv.com>
cc: FreeBSd Chat list <chat@FreeBSD.ORG>
Subject: Re: What string to filter FreeBSD lists?
In-Reply-To: <199707240133.VAA14312@federation.addy.com>
Message-ID: <Pine.BSF.3.96.970723230931.5701S-100000@fallout.campusview.indiana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-chat@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 23 Jul 1997, Francisco Reyes wrote:

> On Wed, 23 Jul 1997 06:19:41 -0700 (PDT), Jonathan M. Bresler wrote:
> 
> >	the only two possilbilities are owner-freebsd-<listname> and
> >	owner-<listname>
> 
> Should we send you emails that are not filtered by any of these two.
> :-)
> 
> On second thought those two strings will not do what I want. I want
> messages sent "to me" to go somewhere separate from the messages sent
> "to the list". I have never had a problem filtering the list, but if I
> used the strings you suggest I would get dups in each folder I have for
> each list.

In my procmail filter, the first thing that happens is that dups
are zapped.  This is done by keeping a cache of message-id's.

# Weed out duplicate messages
:0 Wh: msgid.lock
| formail -D 8192 msgid.cache


Then for the freebsd lists, I have a two level filter rule.
Anything from an "owner" at freebsd.org gets in the first level
and the second level splits things up appropriately.  I've never
had any problems with things landing in the wrong places.

# Messages from any of the freebsd mailing lists...
:0
* ^Sender:.*owner.*@.*freebsd.org$
{
  :0
  * ^Sender:.*www
  www

  :0
  * ^Sender:.*bugs
  bugs

  :0
  * ^Sender:.*doc
  doc

  :0
  * ^Sender:.*CVS-committers
  cvs

  :0
  * ^Sender:.*questions
  questions

  :0
  bsd
}


-john