I'm not sure the cause, but if I RESCAN any of my uplinks (all Mystic)
I'm getting no messages after 2019. I'm on A44 latest release and have copied all the executables over the existing ones.
Please upgrade to the latest version and report back.
As far as the weird message thing, there was a bug in A43 only where if you did an echomail RESCAN it could import a funky message or two, so
that might explain any weirdness there.
Are you using the new reader or the old one? The new one is the M! menu command that has been available for testing, and it will be replacing
the old one in A45. I am not investigating anything with the old reader at this point.
As far as the weird message thing, there was a bug in A43 only where you did an echomail RESCAN it could import a funky message or two, so that might explain any weirdness there.
Ok, I'm on A44 latest, but I assume rescanning A43 uplinks will cause
them to not be able to send me anything past 12/30/2019? I am not receiving any message on the rescan past this date. I do get new
messages but everything between now and 2019 does not come through.
The weird message or two is a symptom of the Mystic A43 uplink then?
I was using the old one but changed to the new one and the problem persists:
If I hit enter on a message bases (with messages) that has a garbled message, it will not open it. I think the real problem is the garbled message is messing up the base data structure making it problematic to read. I think I'm going to try to manually edit the record (using some python code) and purge the message. Not going to be easy, I'll have to write a few lines of code to clean these.
What I would do is just backup the message base data files (just in
case), delete the weird messages, and then run message pack.
|Location:||Beaverton, Oregon, USA|
|Nodes:||16 (0 / 16)|