Couple of suggestions: 1) Set the LOGFILE variable in your .procmailrc 2) Make the action of each rule be a pipe to a shell script that prints out all of it's arguments and make the argument be the name of the rule >>>>> "r" == rpgoldman <rpgoldman at real-time.com> writes: r> Does anyone have a bang-up approach for debugging .procmailrc files? r> I'd love something that would take a message file and step through the r> recipes, one after another, checking for matches and reporting them as r> they happen. r> I'm sure I'm dreaming, but it seemed worth asking.... r> R r> _______________________________________________ r> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota r> http://www.mn-linux.org tclug-list at mn-linux.org r> https://mailman.real-time.com/mailman/listinfo/tclug-list -- Jon Schewe | http://mtu.net/~jpschewe | jpschewe at mtu.net For I am convinced that neither death nor life, neither angels nor demons, neither the present nor the future, nor any powers, neither height nor depth, nor anything else in all creation, will be able to separate us from the love of God that is in Christ Jesus our Lord. - Romans 8:38-39 _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list