Any comments on below? This is with "3.11pre4".
I pulled the included message out and tried it against 3.11pre7 and 3.10
without any problems. Stayed in the queue for an overly long time, but it
was still delivered without any problems (Solaris 2.5 and Linux 2.0.30).
I don't doubt that procmail has buffer overflow problems, but in this
case I'm guessing that it's either OS specific or the system actually
ran out of memory or procmail tried to do something funky via a
recipe.
Chris
----------------------------------------------------------------------
Looks like procmail has the same problem as the elm filter.
It core dumps on long lists. Most likely that the filter
buffer is not dynamic and can only grow so large.
Forwarded message:
From human(_at_)sparc(_dot_)sandiegoca(_dot_)ncr(_dot_)com Sun Aug 30
22:25:03 1998
Date: Sat, 29 Aug 1998 08:39:17 -0700 (PDT)
From: Mail Delivery Subsystem
<MAILER-DAEMON(_at_)sparc(_dot_)sandiegoca(_dot_)ncr(_dot_)com>
Message-Id:
<199808291539(_dot_)IAB17370(_at_)sparc(_dot_)SanDiegoCA(_dot_)NCR(_dot_)COM>
To: postmaster(_at_)sparc(_dot_)sandiegoca(_dot_)ncr(_dot_)com
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="IAB17370.904405157/sparc.SanDiegoCA.NCR.COM"
Content-Transfer-Encoding: 8bit
Subject: Postmaster notify: unknown mailer error 139
Auto-Submitted: auto-generated (postmaster-notification)
Sender: human(_at_)sparc(_dot_)sandiegoca(_dot_)ncr(_dot_)com
This is a MIME-encapsulated message
--IAB17370.904405157/sparc.SanDiegoCA.NCR.COM
The original message was received at Sat, 29 Aug 1998 08:26:33 -0700 (PDT)
from ncr-sd.SanDiegoCA.NCR.COM [153.64.251.18]
----- The following addresses had permanent fatal errors -----
"|/usr/local/bin/procmail"
(expanded from:
<bhoule(_at_)sparc(_dot_)SanDiegoCA(_dot_)NCR(_dot_)COM>)
----- Transcript of session follows -----
sh: 17374 Memory fault - core dumped
554 "|/usr/local/bin/procmail"... unknown mailer error 139