On 26.08.11 15:21, Hylton Conacher (ZR1HPC) wrote:
If not, what are the bare minimum lines? A full listing of them would be
better as then I can add just the ones needed.
I would assume the following lines of code before the recipes:
Maildir
log
verbose
path
What else before the recipes start?
Do you have the three examples:
/usr/share/doc/procmail/examples/[1-3]procmailrc
on your host? I don't recall whether they came with the apt-get procmail
... yep seems so, since I don't see a procmail doc package.
You should be able to have some fun with them already.
I just now saw the package:
procmail-lib - procmail library of plug-in recipes
which might be worth a glance, once you're up and running.
It is many years since I've looked above the recipes, at the start of my
.procmailrc. Here's what I find:
# Avoid logging clashes. Separate log records.
MAILDIR=/home/erik/mail # Thanks to Bart Schaefer & Ruud H.G. van Tol:
LOGFILE=$MAILDIR/tmp_log.$$ # <- Each process uses a temporary log.
FINAL_LOG=$MAILDIR/log # <- Append here, via TRAP, at process exit:
TRAP='procmail -p DEFAULT=$FINAL_LOG /dev/null < $LOGFILE && rm -f $LOGFILE'
But that's been there so long that I can't be sure that it's still close
to optimal.
Erik
--
In a time of drastic change it is the learners who survive; the
'learned' find themselves fully equipped to live in a world that no
longer exists. - Eric Hoffer
____________________________________________________________
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