I don't understand this issue. You can only press M when you're reading a message, and if there are no messages in a sub-board, then you can't get into the reader mode (since there are no messages to read). And if there are no messages in a message area, there would also not be any messages to list (it should tell you the sub-board is empty). If you have a list of "nobody" and bad dates, I have a feeling that particular messagebase may be corrupt on your system.
I would recommend running chksmb , where is the name of that messagebase .SHD file. If it finds any problems, you can then run fixsmb and hopefully it will fix any issues the messagebase may have. I think you can even run fixsmb without using chksmb first.
I can reproduce that and will look into it.
It seems it only happens when you change to an empty sub-board from within DDMsgReader. If you change to an empty sub-board from the BBS and try to read it with DDMsgReader, DDMsgReader will tell you there are no messages in the sub-board.
Did a little more testing this morning. It's unique to DDMsgReader because of the ability to jump areas direct from the message list. It's populating from getBogusMsgHdr, which is used often, but I suspect you're creating headers when the number of messages in the message list is zero.
I'd say this is pretty low priority to fix, but the issue is real.