Phil Temples asked,
| I can't seem to get "formail -l" to function properly. According to the
| man page, it should allow me to type,
|
| $ formail -l <folder>
|
| and generate a log summary in procmail-style.
Er, no. It generates a log *abstract* in procmail's style.
| The command "hangs" as though it is waiting for more input.
Yes, that's exactly what it is doing. It is expecting a message from
standard input.
| What am I doing wrong?
You're confusing it with the mailstat script included in the procmail
distribution.
| I read where this had been an undocumented option until recently.
It was a nonexistent option until recently. It's pretty new, coming with
3.22 I think.
formail -l string < message will output a logabstract, as Martin was
describing. Formail will take the From_ postmark line and Subject: line (if
they are present) and the byte count from the message and will use whatever
string you supplied as the name of the folder. I use it, for example, on a
system where IMAP folders are kept on a different server and procmail cannot
save messages directly into them: rather, procmail must invoke another
program to save the message on the IMAP server. Rather than see the name of
the other program in my logfile for every message, I do this:
LOGABSTRACT=off
TRAP='formail -l $IMAPFOLDER' # stdout and stderr of TRAP go to $LOGFILE
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail