On Sun, 23 Oct 2016 22:43:50 GMT, rick christian
<rec9140@n377.r135.z1.fidonet.org> wrote:

 rc> I have gotten setup with a node, changed the crashmail.prefs to that node.

 rc> Did my Areafix, and added some echos.. but when importing them I get:

 rc> ! 23-Oct-16 22:09:37 Failed to read message #55 in JAM messagebase
 rc> "/home/rec9140/fido/jam/BINKD"
 rc> ! 23-Oct-16 22:09:37 Failed to read message #56 in JAM messagebase
 rc> "/home/rec9140/fido/jam/BINKD"
 rc> ! 23-Oct-16 22:09:37 Failed to read message #57 in JAM messagebase
 rc> "/home/rec9140/fido/jam/BINKD"

I have not ran crashmail but since it was developed by same person may
have this one issue that I ran into.

When I started trying to setup jamnntpd here I noticed that when
posting messages it would corrupt a message base or not see all the
messages.  I concluded it was an alignment error because the int's
used in the library are not of size specific.  the sizeof an int can
vary on architectures..  So when jamnntp's jamlib is built on a 64 bit
platform some of them are wrong size.

It wouldn't take much to go thru the code and fix this, or simply
build it with -m32 option (which I tested and works fine).

For jamnntpd, I just went with the smapi version (though it had bad
bugs too) which are now corrected.  It builds as a 64bit binary too...
no issues.  I used golded, hpt, and jamnntpd together.  I just need to
get off my butt and release what I have but there is one more thing I
want to correct before I do as well as test building on windows.

The state of fido software is that once someone gets something working
they tend to not share it outright.  Not out of malice - just out of
time constaints.  they also don't tend to make things "release grade"
such that a novice user can simply install them.  I do believe some
people want and would come back.  We need to figure out how to make
this great modern software more easy to use and understand.

---
 * Origin: The Byte Museum - news: news.bytemuseum.org (1:19/10)