Thank you very much David. This helped immensely. And, of course, the
problem wasn't what I thought it was.
With the message I had exported from pine, I couldn't repeat the
"mismatch." Eventually it dawned on me that the binary that came with the
original was not attached. Saving the *complete* original message to a
unique pine folder and running the command line against that got me a hit!
A five-letter string included in the binary. "Matched: bkEru"
A REALLY good reason to include the escapes in the domain names (and ALL
of my recipes now are properly escaped)!
For me this has been a great learning experience and I really appreciate
the help I got. I'm sure I've been a pain to some on the list - so I'll
fade into the background and lurk some more. I'll probably resurface when
I'm ready to try the "scoring" bit! :)
Thank you all!
- fleet -
On Sun, 28 Jul 2002, David W. Tamkin wrote:
Procmail does not support having recipe code on the command line; it has to be
in a file. So you create a new rcfile -- let's call it .frogrc and put it
into $HOME. It should look something like this:
DEFAULT=$HOME/tadpoles # for messages that are not full-fledged frogs
Then, back at the shell prompt,
procmail .frogrc < message
and then you read $HOME/.froglog to see what text was assigned to MATCH.
procmail mailing list