At 08:26 2002-11-26 -0800, Professional Software Engineering did say:
.* is crossling header newlines in an attempt to match, and it does so on
the first two lines. Mentally walk through the match process:
Self-correction: \>* would have been doing that, so yes, the specific
header explanation offered by Don is most likely. Running it with verbose
confirms this:
procmail: Assigning "MATCH="
procmail: Matched "sourceforge.net [66.35.250.206]) by mail.crtman.com
(Postfix) with SMTP id 74A06AA6C1 for <lists(_dot_)netsaint(_dot_)wfitzgerald(_at_)crtman(_dot_)com"
procmail: Match on "lists\.\/(_dot_)*(_dot_)wfitzgerald(_at_)crtman(_dot_)com"
procmail: Matched "sourceforge"
procmail: Match on "^^\/[^.]+"
With my suggested change:
procmail: Assigning "MATCH="
procmail: Matched "netsaint(_dot_)wfitzgerald(_at_)crtman(_dot_)com"
procmail: Match on
"lists\.\/[-_a-z0-9]*\(_dot_)wfitzgerald(_at_)crtman\(_dot_)com"
procmail: Matched "netsaint"
procmail: Match on "^^\/[^.]+"
Oh, and I neglected to correct the unescaped dots in your original recipe,
so the corrected recipe is something more like:
:0:
* lists\.\/[-_a-z0-9]*\(_dot_)wfitzgerald(_at_)crtman\(_dot_)com
* MATCH ?? ^^\/[^.]+
MailingLists/$MATCH
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail