On Sun, 28 Jul 2002, ProcMailER wrote:
* fleet(_at_)teachout(_dot_)org <fleet(_at_)teachout(_dot_)org> [07-28-02
17:53]:
On Sun, 28 Jul 2002, Professional Software Engineering wrote:
Why not try some of the profferred test filters, rather than using the
grep
tool, which procmail _doesn't_ use to resolve it's conditions?
I took "profferred test filters" to mean some utility that would work
something like grep only using whatever it is that procmail uses.
Is there, by the way, any such utility? Being able to run a test
condition against a specific message sample would, I should think, be very
handy not only for debugging an RC; but also for building them.
I *DON'T* use grep in the procmail RCs. I was using grep from the command
line to see if I could determine what got hit in that particular message
that caused it to be misrouted. I still don't know. I strongly suspect
it was the "bk.ru" matching with "brutal" - but from the log there's no
way to tell. (Unless this "MATCH" business will be helpful - it's now
been implemented - just waiting for a hit so I can see what the log says.)
Specifically:
See 'man procmailex', and the various FAQs linked from
Yes, I've read the man pages for procmailex (several times), also
procmailrc, and procmail. I've scanned the procmailsc man pages also.
I'm putting scoring off until I get more comfortable with the basic RCs.
<http://www.procmail.org>. Era, Nancy, and Jari all have excellent
examples in their various - and extensive - resources.
Have also been visiting the FAQs provided by these folks. All too often,
what I find starts out about two yards above my head and then gets higher.
I'll get there eventually.
- fleet -
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail