This doesn't mean its corruption (although it could). It could be that
You're right, I suppose in most cases corrupt could likely lead to Mystic being completely unable to read the data files.
the message is marked as a private message or is twit filtered, search filtered, etc.
It could be also be a bug in A46 that was fixed in A47 but I can't remember off the top of my head if something like that was fixed! :)
Without having any real proof, I suspect the last one in this case. My only reasoning being that when new messages were received in an echomail area, the issue I had went away.
At any rate, I'm on A47 now so I'll just have to wait and see if I run into this again.
Thanks!
... The seminar on time travel will be held two weeks ago
--- Mystic BBS v1.12 A47 2021/08/29 (Raspberry Pi/32)
* Origin: New Mystic BBS (1:134/303)