On Tue, 1 Aug 2000, John Summerfield wrote:
While re-thinking about those leading spaces, it just occurred to me
that things could get dodgy if you have a list name that is a substring
of another list name. E.g. "redhat-list" and "hat-list" (there must
be one somewhere out there :) If that were a possibility, some tinkering
with the regex in the LISTS variable would be needed, and perhaps also
FOLDERS might best be changed to something like:
FOLDERS=",zoot-list,ZOOT-LIST,redhat-list,REDHAT-LIST,\
,redhat-announce-list,REDHAT-ANN,apollo-list,APOLLO-LIST,\
,hedwig-list,HEDWIG-LIST,cartman-list,CARTMAN-LIST"
If it mentions redhat in the headers, include a file to handle lists at
redhat. Hopefully, redhat will avoid the problem.
That is another good way to clean it up. I'm using includes
allready, I just never thought of it. I think though, in keeping
with your KISS rule, a better way would be to write a script
which generates the file for me, which gets included. My reason
for cleaning this stuff up is that looking in the files is
messy. I just want to plop in a line and go.. The script idea
will automate it for me.
Thanks again!
TTYL
--
Mike A. Harris Linux advocate
Computer Consultant GNU advocate
Capslock Consulting Open Source advocate
... Our continuing mission: To seek out knowledge of C, to explore
strange UNIX commands, and to boldly code where no one has man page 4.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail