Re: mailfilter good mailreaver bad?

[email protected] Thu, 10 Feb 2011 15:07:17 -0500
Newsgroups gmane.mail.spam.crm114
Message-ID <[email protected]>
I've not been able to figure this one out.   Is it possible
that you don't have the other .crm files needed in the directory?
(IIRC, you will need maillib.crm, which is where load_cf_file
actually lives).

Can you check for that?

    - Bill Yerazunis
"Eric d'Alibut" <[email protected]> writes:

> I have been happily running an installation of crm114 with
> mailfilter.crm, maildrop, and mutt.
>
> Then I decided to switch in mailreaver and I get something like this
> while trying to test:
>
> rs@sixtiessurvivor:~/.crm-114$ ./mailreaver.crm
> now is the time for all good men to come to the aid
> now is the time for all good men to come to the aid
>
>  Aw, crud.  mailreaver.crm broke.  Here's the error: :\_nl:
> /usr/local/bin/crm: *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)
>
>  ERROR: mailreaver.crm broke.  Here's the error\:
> ERROR:
> /usr/local/bin/crm: *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)
> rs@sixtiessurvivor:~/.crm-114$
>
> Me again:
> mailfilter.cf is in the same dir as mailfilter.crm, namely the dir
> .crm-114 into which I change before running mailfilter.crm.
>
> crm lives in /usr/local/bin, I assume, because I built crm114 from src, to wit:
> crm114-20100106-BlameMichelson.src
>
> tia for any light shed on this experience.

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb