On Mon, Oct 06, 2003 at 04:31:46PM +0200, Ruud H.G. van Tol wrote:
Focus on these headers:
Sender: linux-kernel-owner(_at_)vger(_dot_)kernel(_dot_)org
Precedence: bulk
X-Mailing-List: linux-kernel(_at_)vger(_dot_)kernel(_dot_)org
That inspires
:0:
* ^X-Mailing-List: \/[^(_at_)]+
$MATCH
For a more complete recipe, see the recent entry by
Sean B. Straw / Professional Software Engineering
in the thread "general mail list rules".
I looked at the Generic listname identification recipe, and I was a bit
baffled by things there I did not understand at all. I opted to try
this, as a cobbled together approach from the note above and a piece of
the Generic listname recipe
:0:
* ^X-Mailing-List: \/[^(_at_)]+
{
LISTNAME=$MATCH
}
:0
* ! LISTNAME ?? ^^linux-kernel^^
linux-kernel
my resulting log file looked like this:
procmail: Extraneous locallockfile ignored
From sgates_sn(_at_)jakota(_dot_)de Tue Oct 21 16:08:34 2003
Subject: =?iso-8859-1?B?VGhlIGxpbmsgaXNudCA=?=opening
Folder: linux-kernel 3213
procmail: Extraneous locallockfile ignored
From htw4p471(_at_)htw-dresden(_dot_)de Tue Oct 21 16:08:35 2003
Subject: Such a Magnet32122
Folder: linux-kernel
I'm clearly nearly there, but these are procmail list messages that went into
my kernel list folder, so I obviously still don't understand what I have
wrought. :-)
I obviously don't need the : (lockfile) on the first line, since there is no
file to deliver to.
I'm not sure, but maybe I just need to match linux-kernel in htthe first
recipe, instead of the \/[^(_at_)]+ regexp?
This is what learning is all about...
-chuck
--
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail