Hi Martin,
----
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?
----
The perl script works well with two or more instances. Anyway, an error
with this script must be logged (and it not happens). The question is
that some messages ignore the script and don't give a chance to my
perlscript to log anything.
----
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.
----
The log have only lines like...
From john(_at_)isp(_dot_)com Wed May 23 08:11:35 2001
Subject: Hi!
Folder: /home/user1/getmessage.pl 1499
----
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!
----
Done... But now I'm waiting for a message that reproduce the error.
----
: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.
----
The system sends mails and these rules avoid loopbacks. I have some
messages that matches these conditions in a regular way, but I have
messages too that don't matches these conditions but has redirected to
same place (my local inbox).
Here is a example header of a message that was ignored...
From mike(_at_)myemail(_dot_)com Tue May 22 15:40:23 2001
From: "Mike" <mike(_at_)myemail(_dot_)com>
To: "John" <jj(_at_)internet(_dot_)net>
Subject: Examples
Date: Tue, 22 May 2001 16:41:49 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0005_01C0E2DE.18DC9420"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
----
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.
----
It was for an old server... The actual is ok. I don't have this line
anymore. ;)
Thanks!
Regards,
Marcos
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail