At 14:35 2004-05-19 -0500, Jack L. Stone wrote:
Also, added the catch recipe at the top of the procmailrc as suggested by
Sean. However, this does the same as the "redirect" recipe I stuck in last
night that sent to another account. Just didn't have it right at the top
before the dups recipe.
uh, the point is to store a copy BEFORE anything else is done, so that you
know how many times it was passed to procmail.
if you suspect issues with procmail, taking action AFTER a bunch of other
things has taken place does NOT isolate the problem.
Additionally, don't dig out OLD verbose logs - generate new ones for the
current messages and *CURRENT* rcfile contents. Correlating old logs to
stuff that ISN'T in your rcfile is a mammoth waste of time.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail