rw>  CM> My only other suggestion is to upgrade to a36 or a pre-alpha a37 whic
 rw>  CM> I know resolves this issue.
 rw> 
 rw> I believe this issue STARTED with A37, unless there was something
 rw> released very, very recently.

This was a known issue in an earlier version where the '.bsy' extension was
left off when deleting a BUSY semaphore, but its not a known issue now. You
would be the only one reporting it in current version (to my knowledge).

Of course if you kill 9 the servers, X out console windows, interrupt the
mailer or tosser process on your own, force shutdowns of the OS with stuff
still running (etc) you'll still end up seeing this issue... but those are all
operator errors.  If your server crashes that could cause it too.

Anyway, the point is that with typical operation its not a known issue, so let
me know if it is for you and lets get it resolved.  We're working hard to make
the new server stable as can be before official release, and fsxNet is pushing
it *hard* these days as you can see by this Status window of active concurrent
BINKP connections:

SERVER  USER             STATUS                 ORIGIN
──────  ───────────────  ─────────────────────  ────────────────────────────
 BINKP  21:1/154@fsxnet  Raiders Inc BBS        68.103.73.149
 BINKP  21:1/165@fsxnet  Miskatonic BBS         80.181.77.178
 BINKP  21:2/100@fsxnet  Tholian fsxHUB [NET2]  108.204.225.235
 BINKP  21:1/107@fsxnet  The ByteXchange BBS    204.12.198.27
 BINKP  21:1/141@fsxnet  Pie33                  107.170.38.150
 BINKP  21:1/189@fsxnet  Kernel Error Networks  2604:A880:0400:00D0::4BC4:10
 BINKP  21:1/111@fsxnet  Another Droid BBS      2.84.76.122
 BINKP  21:1/173@fsxnet  Sinclair Retro BBS     93.91.140.60
 BINKP  21:1/186@fsxNET  Castle Rock BBS        67.61.21.181
 BINKP  21:1/172@fsxnet  the facility bbs       173.170.129.51
 BINKP  21:1/166@fsxnet  DATANET                180.222.24.135
 BINKP  21:1/150@fsxnet  BadTaste-BBS           138.68.181.199
 BINKP  21:1/176@fsxnet  Radio Freqs & Geeks B  67.246.59.46

If there is a legit busy issue typically we'll see it pretty quickly on FSX
because of the crazy load it puts on Mystic! 

--- Mystic BBS v1.12 A37 2017/12/29 (Windows/32)
 * Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)