At 11:44 2003-04-18 -0400, Kenneth G. Goutal did say:
I have been running procmail for a few years now, mostly for spam control,
Please note that HTML email, esp in colour, isn't appropriate for email
discussion groups. Please reserve that for mailing friends and family or
coworkers locked into a dorky corporate mail system such as Notes or Exchange.
My .procmailrc file got hairier and hairier.
You should use INCLUDERC, and break the recipes out to a handful of
separate rc files instead of (as I suspect is the case here) one monolithic
.procmailrc. Doing so will make it easy to reliabily add something to the
"pre-spam" filters, because you always know that rcfile is included before
the spam checks (for instance).
I won't lay out my complete config, but it runs basically like so:
~/.procmailrc
Contains all initializations used globally throughout my procmail
config, including several variable extractions, such as SUBJECT, etc,
then INCLUDERC's boxes.rc, and lastly, includes a default delivery
rule.
~/.procmail/boxes.rc
The rcfile which organizes the other rcfiles. From here, I include
rcfiles for backups (usually commented out), administrative messages,
twit filtering, greenlisted "clean" discussion lists or one-way only
lists, where I can trust spam won't appear, then spam filtering,
regular lists, and other sorting. In all, I probably have about 40
rcfiles, comprising about 140KB of rules (and that DOES NOT include
greenlist/redlist content, which weights in at another 3.2MB).
To be effective, you need to keep things organized and
compartmentalized. It's a common approach for programming, and although
procmail isn't procedural in nature (it is linear), it is still a form of
programming, and benefits from an organized approach.
I'd like to run procmail on a file of mail messages.
These messages may have been accepted and stored by Elm,
or may in fact have already been processed by procmail with a previous set
of recipes.
Manual invocation of your procmail rcfile. see 'man procmail' and 'man
procmailex'.
*MOVE* your original mailbox to a new location. This is important - if you
don't, then each message which you tack onto the end will be there for
procmail to process again.
formail -s procmail < path/to/your/moved/mbx/file
Presuming that your procmailrc is supposed to deliver the messages to a
folder, you can figure that when you are done, you can delete that moved
mailbox file (since the messages should now be in another folder someplace).
Obviously, if you have multiple mailboxes, you need to repeat this command
for each one.
? Kenn Goutal ; <mailto:kenn dadum mv period com>mailto:kenn dadum mv
period com ; http://www poke mv poke com/users/kgg
Your URL is on 'ludes. Spaces are NOT legitimate separators within a
domain name.
---
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