At 08:14 2004-03-05 +0000, Paul Dean wrote:
The .procmailrc file only contains the following recipe but it doesn't
seem to be doing anything:
A logfile and VERBOSE would be informative. This should be the FIRST thing
you set up, so you can catch errors.
:0 hc
* !^FROM_DAEMON
* !^X-Loop: me(_at_)mydomain(_dot_)com
| (formail -r -I"Precedence: junk" \
-A"X-Loop: me(_at_)mydomain(_dot_)com " ; \
echo "Mail received - I'm away.")
| $SENDMAIL -t
Line before the pipe to sendmail doesn't have a continuation character, so
nothing is going to get sent along to sendmail, and the sendmail line
itself is going to generate an error, since it is invalid syntax as it's
own recipe or command.
Above all this, set:
LOGFILE=mylogfile.log
VERBOSE=ON
Then pump a message through it.
Another suggestion: set up a sandbox and toss messages at it from the
commandline -- of ALL the things to experiment with, autoreplies are the
worst, because if you screw up on them, OTHER people have to suffer.
You should also take a look at more of the "canned" autoreplies you've
received and try to make your text mimic them - this gives others an
opportnity to filter out these annoying messages.
Hit the list archives, there are several viable autoreply mechanisms which
have been written up here in the past.
Finally, take some time and read the following rant:
<http://www.professional.org/policy/autoreply.html>
As written, your autoreply will harrass mailing list participants, admins
of said mailing lists (as well as of outbound-only lists), and all manner
of things. Use it sparingly. You should record who you've already sent a
message to
---
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