Mail Management With Procmail - Tweaking The Engine (
Page 7 of 8 )
In the initial stages of setting up your procmail
recipes, you'll need to keep an eye on what's happening so that you don't
accidentally lose mail in case one of your recipes is a little off. To assist in
the process, procmail comes with powerful logging capabilities, which allow you
to see exactly what's happening with your mail messages.
This log is
activated via the special "LOGFILE" and "VERBOSE" variables in your
".procmailrc" file, which specify the name of the log and the extent of detail
in it, respectively. Consider the following example:
LOGFILE=$HOME/procmail.log
VERBOSE = yes
You can summarize the contents of this log file using the
"mailstat" command, which also ships with the procmail distribution - take a
look at the mailstat manual page for information on how to use the procmail logs
to build different types of reports.
Procmail typically looks for
mailboxes in your home directory. This doesn't usually work for me, since all my
mailboxes are in a folder named "mail" under my home directory. If your
situation is similar, consider telling procmail to adjust its default mailbox
search path via the "MAILDIR" variable.
MAILDIR=$HOME/mail
Finally, if you find it somewhat unsystematic to
keep all your recipes in a single file, you can even split them up into separate
files and merge them into your ".procmailrc" file via the "INCLUDERC" variable,
as below:
INCLUDERC = spam.procmailrc
INCLUDERC = lists.procmailrc
If you have a lot of recipes, modularizing
them in this manner makes them more manageable, and it also becomes easier to
selectively include or exclude them from your ".procmailrc" file.
