On Wed, Aug 25, 2004 at 09:19:37PM +0200, Michelle Konzack wrote:
Am 2004-08-25 13:28:48, schrieb Chuck Campbell:
Maybe:
* (^TO|^TO_|^Sender:|^X-list:|^FROM_DAEMON|^From\ ).*linux-xfs
{
:0 c:
list_ham
:0:
linux-xfs
}
The email in question has these headers present (also cut and pasted):
From linux-xfs-bounce(_at_)oss(_dot_)sgi(_dot_)com Wed Aug 25 00:01:10
2004
^
Der is noc "colon"
Return-Path: <linux-xfs-bounce(_at_)oss(_dot_)sgi(_dot_)com>
Message-Id: <200408250411(_dot_)i7P4BwKw017699(_at_)oss(_dot_)sgi(_dot_)com>
From: bugzilla-daemon(_at_)oss(_dot_)sgi(_dot_)com
To: xfs-master(_at_)oss(_dot_)sgi(_dot_)com
Sender: linux-xfs-bounce(_at_)oss(_dot_)sgi(_dot_)com
Errors-to: linux-xfs-bounce(_at_)oss(_dot_)sgi(_dot_)com
X-original-sender: bugzilla-daemon(_at_)oss(_dot_)sgi(_dot_)com
X-list: linux-xfs
Quesion: Why do you not filter normaly ?
What is normally?
______________________________________________________________________
/
| :0
| * ^X-list:.*linux-xfs
| {
| :0 c:
| list_ham
| :0:
| linux-xfs
| }
\______________________________________________________________________
is realy enough !
I'm trying to make a recipe to catch my mailing list emails and filter them
to the correct place, instead of having one recipe for each mailing list
and having to search headers for something unique in each individual list.
Also, if the scheme is generic enough, then when a list changes their address,
my recipe will still work correctly without changes.
-chuck
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail