You may have noticed a glitch in FSXNet in the last week or two (near the end of May). It caused .bsy flags for a week or so for me till I cleared it. Not sure what caused it, but look for busy flags if your having issues with that net and not RetroNet. RetroNet has worked fine, only fsxnet had an issue that seems to have caused .bsy flags for Mystic. In my case clearing them started
it working fine again.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Workpoint - You can't get here from there (80:603/0.3)

Hi bcw142!

05 Jun 2018 08:39, from bcw142 -> All:

fsxnet had an issue that seems to have caused .bsy flags for Mystic.

I have asked asked Paul to let his sane setup (binkd and fastecho) accept mails
for fsxnet.
He refused ... mentioning he wants to iron out bugs in the buggy Mystic alpha ...

CU, Ricsi

--- GoldED+/LNX
* Origin: Oxymoron: Authentic replica (80:774/18)