From owner-freebsd-chat Wed Jul 23 06:59:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA18353 for chat-outgoing; Wed, 23 Jul 1997 06:59:09 -0700 (PDT) Received: from fly.HiWAAY.net (dkelly@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA18338; Wed, 23 Jul 1997 06:59:00 -0700 (PDT) Received: by fly.HiWAAY.net; (8.8.5/1.1.8.2/21Sep95-1003PM) id IAA32328; Wed, 23 Jul 1997 08:58:49 -0500 (CDT) Date: Wed, 23 Jul 1997 08:58:49 -0500 (CDT) From: David Kelly Message-Id: <199707231358.IAA32328@fly.HiWAAY.net> To: dkelly@HiWAAY.net, jmb@FreeBSD.ORG Subject: Re: What string to filter FreeBSD lists? Cc: chat@FreeBSD.ORG Sender: owner-freebsd-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > dkelly@hiwaay.net wrote: > > > > > Could anyone share with me what strings they use to filter their > > > FreeBSD lists. > > > I have tried a few things, but every now an then messages go > > > unfiltered.. > > > > As the other posting noted, they tend to flip-flop on the sender addresses. > > I filter with slocal and have decided to leave identical filters in place > > for owner-chat and owner-freebsd-chat, and similar for all the other > > if these tools (slocal, procmail, etc..) can handle regular > expressions, you can cover all cases by sorting on > owner-*. That's the One Big Failing of slocal, no regex. For now my CPU doesn't have much better to do than to read my entire .maildelivery for each and every incoming message. Slocal works. I sorta understand what I did to make it work. And one day will look into procmail and see if *this* time I can understand it. Not sure if nmh has been enhancing slocal. Maybe its time to look at that too. -- David Kelly N4HHE, dkelly@hiwaay.net (hm) ====================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.