Hi! rick,

On 26 Oct 16 07:04, you wrote to me:

 PQ>> Something changed in the between-times? Some other program
 PQ>> changed the JAM-stored data?
 rc> The only program to access things is Golded and Crashmail

This is an extract from my other node's CM logfile for a toss run this
morning...

##==T=O=S=S=E=R====T=A=S=K==
- 27-Oct-16 07:06:00 CrashMail II 0.71 started successfully!
^ 27-Oct-16 07:06:00 Tossing files in /opt/ftn/fido/inbound...
= 27-Oct-16 07:06:00 Unarchiving /opt/ftn/fido/inbound/BD8F0F8C.THM using ZIP
^ 27-Oct-16 07:06:00 Tossing 70AB0983.PKT (6K) from 3:640/384.0 (27-Oct-16
07:05:17) / pw, 4d
= 27-Oct-16 07:06:00 Area ALLFIX_FILE -- 1 messages
= 27-Oct-16 07:06:00 Area FDN_ANNOUNCE -- 1 messages
= 27-Oct-16 07:06:00 Area FIDO-REQ -- 1 messages
= 27-Oct-16 07:06:00    Total ->     Read messages:      3     Written
messages:      4
= 27-Oct-16 07:06:00 Imported -> Imported messages:      3      Routed
netmails:      0
= 27-Oct-16 07:06:00      Bad ->      Bad messages:      0   Duplicate
messages:      0
^ 27-Oct-16 07:06:00 Scanning for orphan files
^ 27-Oct-16 07:06:00 Scanning for old packets
^ 27-Oct-16 07:06:00 Scanning for new files to pack
= 27-Oct-16 07:06:00 Packing 111ab800.pkt for 2:460/58.0 with ZIP
= 27-Oct-16 07:06:00 Sending 111ab801.pkt unpacked to 2:221/0.0
- 27-Oct-16 07:06:00 CrashMail end

You'll note straight up that there's no warning of bad things about the
headers.

 rc> I can read messages, BUT they have CORRUPT to and from headers, ie:
 rc> garbled names and node numbers.

Yep.  There's your problem.  You most likely have bad binaries.  I've seen
similar behaviour on my 'shadow' system, even with recent incarnations of later
version binaries.

I'll send you a copy of the original archive.  It'll just arrive unanounced in
your _insecure_ inbound.  The original binaries worked well in Puppy Linux 5.25
and Xubuntu 11.10, and still run nicely in the current Puppy 4.21 (yes, a
retrograde step for very good reasons).

To use the original binaries, you'll need to:

* stop your binkD;
* destroy your existing JAM messagebase (completely? see note, below);
* replace your current executables with the originals in the ZIP; and,
* restart binkD.

Your netmail area _may_ be okay?  Is it a *.Msg area?  Otherwise, trash it too.

No other changes needed... fingers crossed.  ;)  Just let CM re-create your
messagebase...

Cheers,
Paul.

... My toys!  My toys!  I can't do this job without my toys!
--- Paul's Win98SE VirtualBox