Hi
Note: Maybe these messages enter in the system while the procmail is
busy, working in other messages (they may have large files attached). Is
it a problem?
A separate instance of procmail will be started for each message if more
than one arrives at once.
However, you don't use locking - is your perl script safe if more than
one instance is running at once?
VERBOSE=off
LOGFILE=/home/user1/procmail.log
Does the logfile tell you anything useful? If not, it would help for
you to include relevent parts of the log file here so that we can see
what is happening.
VERBOSE=off
Reduces the ammount of information that is written to the log file. If
you have a problem and don't understand what the problem is, set
VERBOSE=on
and check your logs again!
:0 H
*!^FROM_DAEMON
*!^X-Loop: Mail responder
Are any of the mails that are ending up in your mailbox from a daemon?
Or do they have that "X-Loop: Mail responder" header? That would seem
like the first thing to check. Your condition lines say "only use this
recipe if both those conditions are untrue". You can see whether that
is the case in your log file, especially if you turn VERBOSE on.
Additionally, although this won't be your problem, is there a good
reason why you set the SENDMAIL variable? It is usually safest to let
procmail use its default value.
Regards,
Martin
--
Martin McCarthy /</ PGP key available
marty(_at_)ancient-scotland(_dot_)co(_dot_)uk \>\
http://www.ancient-scotland.co.uk
/</ http://www.ehabitat.demon.co.uk
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail