--- Begin Message ---
In an earlier message today, I reported that I'm getting strange messages.
Now I found out that I'm getting these messages everytime the script is
executed that I'm using together with procmail.
This makes me think that procmail generates such messages -- I don't know
why.
Below, I'll add one of these messages, the script I'm using and my
.procmailrc. I'm a normal user on a cluster of HP9000/735 computers using HP/UX
9.03, I use elm (v. 1.147.109.14) and procmail 3.10.
Thanx...
-Michael
----------example message-------
From foo(_at_)bar Fri Jun 7 15:27:55 1996
Status: RO
-------end of message-----------
This message is copied straight out of my Mail/mbox file, there is no
additional header information.
------my script------------
# QSUB
while true ; do formail -s procmail < /usr/mail/mbelow && > /usr/mail/mbelow;
sleep 1200; done
------end of script--------
This script is running in the background, it's submitted as a batch request
to our Network Queuing System (NQS). When I had this running with sleep
600, the bogus messages came every 10 Minutes -- now I've changed it to
sleep 1200, and these messages come every 20 Minutes.
------my .procmailrc-------
# Please check if all the paths in PATH are reachable, remove the ones that
# are not.
PATH=$HOME/bin:/usr/bin:/bin:/usr/local/bin:.
MAILDIR=$HOME/Mail # You'd better make sure it exists
DEFAULT=$MAILDIR/mbox
LOGFILE=$MAILDIR/from
LOCKFILE=$HOME/.lockmail
:0 # Anything from thf
* ^Resent-From(_dot_)*debian-user(_at_)lists(_dot_)debian(_dot_)org
debian # will go to $MAILDIR/todd
:0
* ^Resent-From(_dot_)*procmail(_at_)Informatik(_dot_)RWTH-Aachen(_dot_)DE
procmail
:0
*
^Return-Path(_dot_)*basin-owner(_at_)yeti(_dot_)faveve(_dot_)uni-stuttgart(_dot_)de
basin
# Anything that has not been delivered by now will go to $DEFAULT
# using LOCKFILE=$DEFAULT$LOCKEXT
-------end of .procmailrc-------------
This is a modified version of procmail-3.10/examples/1procmailrc.
--- End Message ---