You can actually dispense with the wrapper if you use environment
variables to pass options to MHonArc, but I'm sure Achim has a good
reason for doing it his way. Just for the purposes of comparion,
here's how I do it:
eeeweb% cat .procmailrc
#Set on when debugging
#Replace `mail' with your mail directory (Pine uses mail, Elm uses Mail)
#Directory for storing procmail log and rc files
#Path and options for mhonarc
MHONARC='/dcs/packages/infosys/bin/mhonarc -add -quiet -umask 022 -idxfname inde
and then in the file .procmail/rc.classlists or rc.otherlists (depending
on the Originator: of the message), lots of the following:
# Procmail Entry for uci-www
|$MHONARC -rcfile $MHHOME/uci-www/0-rcfile.html -outdir $MHHOME/uci-www
Eric D. Friedman
"Detlef Ruschin" said:
On 13 Nov 96 at 12:42, Achim Bohnet wrote:
An (approximate) solution with not too much coding would be to use a
mail filter (like procmail). Each mail send to the list is archived
in an mbox on a ,e.g., monthly basis).
I use MHonArc with procmail and considered to do that but didn't know
how (not an experienced UNIX user). Could you give a hint how a
procmail recipe achieving this could look like?
Here is what I use in .procmailrc to archive the mhonarc list:
| /local/mail/mhonarc-1.2.2/mailarchive -add mhonarc "$NEWDATE"
Mailarchive is nothing more than a wrapper around mhonarc with my long.
list of options.
P.S. Procmail itself comes with an example manual page. It's worth
looking into it.