At 12:20 2004-01-19 -0800, Gary Funck wrote:
Sean Straw replied:
>
> Since the problem posted involved the /etc/procmailrc file, it's a really
> good idea to set the logfile to something other than $HOME, and also to
> suspend logging at the end of the /etc/procmailrc.
I should continue that with ".. lest the USER not have VERBOSE logging, but
get stuffed with it when their own procmailrc handles messages, AND get
stuffed with the disk quota as well." Since the USER isn't responsible for
the processing in /etc/procmailrc, it's not nice to saddle them with the
logging from it.
When running procmail as a given user, in most common configurations,
procmail will look for its recipes in the user's $HOME/.procmailrc file,
and that's where you'd do your testing.
I still maintain that for _TESTING_, a sandbox configuration is superior -
you don't hose any messages that way, and autoreplies and the like are
trapped. Also, when you want to test for a specific condition, you just
edit a message to match the criteria and throw it at the sandbox setup,
instead of doing as some people do -- waiting for a message to arrive which
happens to meet the criteria.
A sandbox answers a lot of "what if" and "will this work" type questions as
well. If you code your scripts with a consistent style, you can take a
test script file right from your sandbox and drop it into your live
configuration without any further editing of the script (unlike manual
hack-n-test setups, where the post-test edit is what causes some subsequent
problem).
---
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