Re: procmail keeps running out of resources?

On 04/12/11 14:33, R A Lichtensteiger wrote:
> Jason Welsh wrote:
>
> <> well, the thing is, I DID have the size limiting but it didnt seem to
> <> have any affect, so i took it out just in case it was interfering somehow..
>
> Hah! I'm offended <grin>
>
> <> so I checked in the log and it seems that it chokes on smaller emails as
> <> well..
> <> 
> <> >From [email protected]  Tue Apr 12 07:09:28 2011
> <>  Subject: SignUpGenius.com Reminder for Book and a Bite Volunteering
> <>   Folder:
> <> /home/betty/Maildir/new/1302606568.20718_1.beast                  5433
> <> procmail: Program failure (-25) of "/usr/bin/crm"
> <> procmail: Rescue of unfiltered data succeeded
>
> What happens if you turn on debugging?  Save a message off to a file
> and then push it through crm at the command line:
>
>   % cat /tmp/crm.mbx | crm114 -t -u ~/.crm114 mailreaver.crm -stats_only
>
> That should tell us something about what crm114 and/or the filter you
> are using are doing when it goes <boom>
>
> Reto
ok, now we are cooking with gas!! ;)

ran it the first time and found out that my wife didnt have the 
mailreaver.crm
file in her .crm directory.. *ugh*  so
after i copied that over and ran it, I got

------=_Part_113781549_917494960.1302629253922--


Parsing line 680 :
 -->  output /:*:_nl: Aw, crud.  mailreaver.crm broke.  Here's the
error: :*:\_nl:/
       

Executing line 680 :
 Executing an OUTPUT statement
  filename >>><<<
  pre-IO seek to >>><<< --> 0
  and maximum length IO of >>><<< --> 8388608

 Aw, crud.  mailreaver.crm broke.  Here's the error: :\_nl:
Parsing line 681 :
 -->  output /:*:broken_program_message:/
       

Executing line 681 :
 Executing an OUTPUT statement
  filename >>><<<
  pre-IO seek to >>><<< --> 0
  and maximum length IO of >>><<< --> 8388608

crm114: *ERROR*
  Can't CALL the nonexistent label:  :load_cf_file:
 Sorry, but this program is very sick and probably should be killed off.
This happened at line 125 of file mailreaver.crm
(runtime system location: crm_exec_engine.c(701) in routine: crm_invoke)

Parsing line 682 :
 -->  output [stderr] /:*:_nl: ERROR: mailreaver.crm broke.  Here's the
error\: :*:_nl:/
       

Executing line 682 :
 Executing an OUTPUT statement
  filename >>>stderr<<<
  pre-IO seek to >>><<< --> 0
  and maximum length IO of >>><<< --> 8388608
Opening file stderr for I/O (writing)

 ERROR: mailreaver.crm broke.  Here's the error\:

Parsing line 683 :
 -->  output [stderr] /ERROR: :*:broken_program_message:/
   

Executing line 683 :
 Executing an OUTPUT statement
  filename >>>stderr<<<
  pre-IO seek to >>><<< --> 0
  and maximum length IO of >>><<< --> 8388608
Opening file stderr for I/O (writing)
ERROR:
crm114: *ERROR*
  Can't CALL the nonexistent label:  :load_cf_file:
 Sorry, but this program is very sick and probably should be killed off.
This happened at line 125 of file mailreaver.crm
(runtime system location: crm_exec_engine.c(701) in routine: crm_invoke)

Parsing line 684 :
 -->  }


Executing line 684 :
Statement 684 is a closebracket. depth now 0.

Parsing line 685 :
 -->  exit /:*:program_fault_exit_code:/


Executing line 685 :
Exiting at statement 685 with value 0



regards,
Jason



------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo