At 11:45 2010-01-12 -0600, Christopher L. Barnard wrote:
which I already knew. Hence this email <grin>
Your post indicated that the last of the expressions parsed valid, or
something to that effect.
There are multiple tape libraries that identify themselves at the
beginning of the subject line. So "L700: Distribution list" and "L180:
Distribution List" and "Testlab: Distribution List" all go into the same
file.
Your regexp syntax wouldn't match that then. * will match zero or more of
the preceeding element. I figured you probably wanted to match the strings
somewhere in the subjects, which is why the .* is BEFORE the parentheticals
in the rewritten expression.
> Are these subject lines NEVER a reply form (Re: Fwd: and the like)? You
> probably really want to have a wildcard BEFORE the grouped list of text.
Nope. If anyone replies or forwards these messages I want them to not
be filtered but to into my main inbox. Besides, I have another rule
farther down that duplicates all Re: messages (like this one) into a
seperate responses folder.
If you have variable text before the specific string, you'll need to
identify replies then. One method would be to look for In-Reply-To: and
References: headers, though occassionally, someone will send a reply that
doesn't bear these markers.
You might try:
* ^Subject:[ ]*L[0-9]*:[ ]*(various string matches)
This would catch the original messages from the libraries, but not ones
bearing Re: and Fwd: at the front.
---
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 homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail