On Sun, 5 Jan 1997, Timothy J Luoma wrote:
:0
* ? test -r $MATCH
|(formail -rt -I"From: Timothy Luoma <luomat(_at_)peak(_dot_)org>" ; \
/bin/cat "$file" )|$SENDMAIL -oi -t
:0E
|(formail -rt -I"From: Timothy Luoma <luomat(_at_)peak(_dot_)org>" \
-I"Subject: File not found ($MATCH)" ; \
/bin/cat "$PROCDIR/file_not_found" )|$SENDMAIL -oi -t
First, you'll need to name yourself as a recipient of the sendmail
command. Otherwise sendmail won't deliver to you if the original
message is from someone other than you.
|$SENDMAIL -oi -t , luomat(_at_)peak(_dot_)org
The ',' after -t may not be needed. I have used it and it works for
me.
I'd like to know if your E flag on the final recipe responds to
failures in the preceding pipe. If not, you might be able to just drop
the E flag, since the preceding recipe should deliver if successful,
and pass the message if unsuccessful. Either way, you open yourself up
to getting crank messages in the form of:
"send file /gimme.yer.password.or.the.os.gets.it!"
Re. your most recent mail re. MATCH:
* ^Subject:.send-ftp-uuencoded *\/[^ ].*
I think you are missing a dot before the "*\/". These regular
expressions can be tedious. I've been working on MATCH for the last
few days and it doesn't always seem to work as expected. I set up logs
to dump MATCHes to and sent mail to myself and watched the logs until
I began to have some sense of security in getting the MATCH var.
Regular expressions are very unforgiving when setting a MATCH var.
David