I use getmail to grab mail from my ISP's IMAP server.  I filter it through crm114's mailreaver with this stanza:

[filter-1]
type = Filter_external
path = /home/josh/.crm114/mailreaver.crm
arguments = ("-u","/home/josh/.crm114")
exitcodes_drop = ()

Occasionally, mailreaver fails like this:

Filter error (filter Filter_external mailreaver.crm (allow_root_commands="False", arguments="('-u', '/home/josh/.crm114')", command="mailreaver.crm", exitcodes_drop="()", exitcodes_keep="('0',)", group="None", ignore_stderr="False", path="/home/josh/.crm114/mailreaver.crm", unixfrom="False", user="None") returned 1 (ERROR: mailreaver.crm broke.  Here's the error\:
ERROR:
/usr/bin/crm: *ERROR*
 For some reason, I was unable to read-open the file named  :*:fileprefix:priolist.mfp
 Sorry, but this program is very sick and probably should be killed off.
This happened at line 484 of file /home/josh/.crm114/mailreaver.crm
(runtime system location: crm_expr_file_io.c(151) function crm_expr_input))
)
  msg 343/801 (4419 bytes), filter error (filter Filter_external mailreaver.crm (allow_root_commands="False", arguments="('-u', '/home/josh/.crm114')", command="mailreaver.crm", exitcodes_drop="()", exitcodes_keep="('0',)", group="None", ignore_stderr="False", path="/home/josh/.crm114/mailreaver.crm", unixfrom="False", user="None") returned 1 (ERROR: mailreaver.crm broke.  Here's the error\:
ERROR:
/usr/bin/crm: *ERROR*
 For some reason, I was unable to read-open the file named  :*:fileprefix:priolist.mfp
 Sorry, but this program is very sick and probably should be killed off.
This happened at line 484 of file /home/josh/.crm114/mailreaver.crm
(runtime system location: crm_expr_file_io.c(151) function crm_expr_input))
)

However, ~/.crm114/priolist.mfp exists, and has no permission issues.
I don't know how or why this fails.

- Josh Triplett

[I'm sorry for the late answer, I was busy and hoped to handle your
report "the next day" each day.]

    JT> Occasionally, mailreaver fails like this:

I think it would help a lot if the problem was reproducible.  Is it
possible to store the incoming mails somewhere and to invoke the bug
systematically on some of the files?

Regards,

Milan Zamazal

Milan Zamazal wrote:

No, because re-running getmail again fetches those same mails and runs
them through mailreaver again with no issue.  So I don't think the bug
necessarily relates to mail content.

- Josh Triplett

    JT> No, because re-running getmail again fetches those same mails
    JT> and runs them through mailreaver again with no issue.  So I
    JT> don't think the bug necessarily relates to mail content.

Well, I googled a bit and found the following:

http://archive.netbsd.se/?ml=crm114-general&a=2007-07&t=4765896

Does it help to find out what's wrong?

Regards,

Milan Zamazal

I've been seeing this problem; it started for me over the past week or two.

I haven't changed my copy of crm114 in that time, but I have done a
regular regimin of apt-get updates for testing.  The only interesting
data point I have is that it happened after a kernel upgrade; the host
is Xen 3.0 and is running "2.6.18-53.1.13.el5xen" when it was previously
running "2.6.16.29-xen".  I cannot change the kernel.

I followed the suggestions at the end of the thread and see this when I place
the logging right around line 485 or so, before the comment "Not a learn, so
it's a CLASSIFY job.  Maybe full, maybe stats_only.":

  :add_extra_stuff:=-no-
  :automatic_training:=-no-
  :cache:=--
  :cachedir:=-:cachedir:-
  :cacheid:=-20080303_182124_861609_6DB5183E-
  :classifier_reason:=-no reason yet-
  :classify_status:=--
  :clf:=-osb unique microgroom-
  :decision_length:=-16000-
  :fail_blacklist_mail_to:=--
  :fail_priority_mail_to:=--
  :fail_SSM_mail_to:=--
  :fileprefix:=--
  :force:=-:force:-
  :general_fails_to:=--
  :learnfile:=-:learnfile:-
  :learnnonspam:=-:learnnonspam:-
  :learnspam:=-:learnspam:-
  :log_rejections:=-yes-
  :mailtrainer_output:=-:mailtrainer_output:-
  :msg_hash:=-6DB5183E-
  :nonspamcss:=-:nonspamcss:-
  :our_exit_code:=-0-
  :priolist:=-:priolist:-
  :reject_address:=--

Which doesn't tell me much.  The message that triggered this doesn't do so
repeatedly; my solution for the past few weeks has been to just run the mail
filter again.  This does not happen frequently; I would guess on the
order of once out of every 500 messages, which means a few times a day.

I am using version 20070810-3, and have been since shortly after it hit
testing; this one came out of nowhere.

Thank you, Alec, for an additional report.

Alec and Josh, I've just uploaded current snapshot of crm114
(20080315-1) to experimental.  Before I report the problem upstream,
would you please try the current version when it hits archives?

Regards,

Milan Zamazal

Milan Zamazal on 2008-03-15 10:38:54 +0100:

I'll give it a shot this weekend and let you know how it goes.

    AB> I'll give it a shot this weekend and let you know how it goes.

Thank you, perhaps you might help by talking to the upstream authors
now.  The issue has been opened today by another user on the crm114
mailing list and the upstream authors have no clue what might be wrong.

You may want to watch the thread starting with
http://article.gmane.org/gmane.mail.spam.crm114/8298

Regards,

Milan Zamazal

I don't know if upstream managed to fix this, but here appears to be a
fixed version:

http://hebbut.net/Public.Offerings/crm114.html
http://hebbut.net/Public.Offerings/crm114/20080525/index.html

Supposedly these versions work better in 64bit systems, though I don't
have tried them yet.

    AS> I don't know if upstream managed to fix this, but here appears
    AS> to be a fixed version:

Thanks for the pointer.  After lenny is out, I'll try to review what's
available and to make a newer version of the Debian package.

Regards,

Milan Zamazal

Is the bug still present in the current crm114 version in the Debian
archive (20090807)?

I no longer use crm114, and don't plan to change that, so I can't test
this issue.  Hopefully one of the other people who encountered this
problem can help.

- Josh Triplett