BTW, after running a bunch of regular mail through the discussed generic
list identifier, I came to realize that the X-Loop: expression doesn't seem
to be a good one to include (I hadn't paid particular attention to the
original expression so much as expanded it to handle the sample lists which
weren't being auto-identified). Surely, legitimate lists will have other
characteristics to match on. (Properly) Forwarded mail containing X-Loop
headers will result in false hits.
Of course, two other liabilities stick out about that generic list matching:
1. Case sensitivity -- using $MATCH as the filename means that if between
two copies of a message, the matched token differs (yea, it normally
shouldn't), your message may be stored to separate files.
2. No allowance for same-named lists on different services (webdesign and
webdev are two lists I recall seeing more than one of). Same would go for
vaguely-named lists.
Other than that, across a large crosssection of my own email, it seems to
do a reasonable job of identifying lists, so I'm putting the (now with
X-Loop removed) recipe into my mail config to simply emit logfile entries
to evaluate it over a longer term.
---
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