31 Oct 16 16:33, you wrote to Nicholas Boel:

 NB>> I believe you were already told that CM v1.5's deb package includes
 NB>> broken binaries. Your better bet is probably to compile the original
 NB>> (.71?) or have someone (I believe Paul Quinn already offered you
 NB>> binaries of the original version) give you some binaries to try out.

 RC> I don't think it matters what version it is...

 RC> I've managed to some how compile

 RC> 1.5 0.75

 RC> and *ALL* exhibit the same behavior... error reading ....

in my experiance, those using crashmail have been extremely lucky that it works
 for them... why and how is another story... i've seen both sides but i've
never tried to run it myself... why? specifically because of the problems you
are seeing... for my tastes, it was never stable enough for me to consider...
other's mileage has obviously varied...

i won't even mention that the original author has been gone for over a decade
and that they completely abandoned all their software when they left... they
were at least kind enough to release it for others to play with but that
doesn't mean it was working software at that time...

i also won't mention the couple of message based libraries that also came out
that had their own, sometimes erroneously, ways of handling message bases...
MAPI and SMAPI are two that i recall... the history leaves /much/ to be
desired... you really need to consider that a lot was also hobby stuff written
bt teenagers and twenty-somethings that did the code for grades in school and
left it at that...

i'm sorry to say that you seem to be expecting much too much of the software
that you are choosing to test... descent linux based FTN stuff hasn't been
around all that long... it has been a long and hard fought battle to get what
little bit of fTN software available for anyone to use...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Cheese is senior citizen milk.
---
 * Origin:  (1:3634/12.73)