I've just run across another hint on my problems with flist on linux
in my .mh_profile and was calling flist like:
flist +inbox -noshow -recurse
This would occasionally cause a segfault for a period of time until
*something* changes and it works again. After removing the flist
entry from my .mh_profile it started working again.
This seems to indicate that flist either doesn't like having the
-recurse flag twice or the segfault has something to do with reading