Last time I used procmail is at least 5 years ago, so my approach to this is
like
a Newbie, I went to procmail.org and to some links from there and worked my way
thru some tutorials and examples, among them the very useful Quick Start at
Infinite Ink, one of the best primers to a complex program I've ever seen. All
of
what I tried worked with the first try, but there's something which produces
weird
results.
It's an example from man procmailex:
:0 fhw
| formail -k -X From: -X Subject:
I do get the desired result, but I also get a line of binary garbage logged to
procmail.log (see below, it's always the same). There doesn't seem to be a
difference with locking. (It's not clear to me, anyway, although I read some
sentences about it, when I need locking and when I don't.) When I use other
formail commands, like "formail -I" it works without that additional "benefit".
This is procmail 3.15.1 on Suse Linux 9.0.
It also seems that I have to use a final action which files to a folder when I
want to get the mail delivered after using formail. This is not the case with
other operations, including piping to other programs, they do get delivered to
the
default mailbox. I suppose I overlooked the explanation in one of the FAQs?
procmail: [15393] Sun May 16 15:42:54 2004
procmail: Assigning "MAILDIR=/-removed-"
procmail: Executing "formail,-k,-X,From:,-X,Subject:"
procmail: No match on "^Subject:.*Test"
procmail: Assigning "LASTFOLDER=default"
procmail: Opening "default"
procmail: Acquiring kernel-lock
\xD5[ \xA0\ 豐] \xF3^ \xCE\x94_ \xD5_`\x90\xEA}a \xB7?b\x90\xCC]c
\x99d\x90\xAE=e\x90\xB5f\x90\x90g\x90\x97\xE8g\x90r\xFDh\x90y\xC8i\x90T\xDDj\x90[\xA8k
q\xC6l\x90=\x88m
Folder: default 650
procmail: Notified comsat: "-removed-"
Kai
--
Kai Sch\xE4tzl, Berlin, Germany
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail