RF> I wasn't saying that to be flippant. A bog standard 112a36 64 bit linux
 RF> package installed both mis and mis2, and I was using mis2 because it
 RF> included ssh. I had no idea that it was unsupported. Standard mis looks
 RF> like the old mystic server.

If you have some copy of A36 that has mis and mis2 then you don't have a real
copy of A36.  Not sure if you knew that beforehand or not, but the legit copy
of A36 will only have the server and nothing else.  No mis2, no old looking
server.  Just mis (the server formally known as mis2).

You can download the A36 release at mysticbbs.com/downloads if you need it.

 RF> I can try to repro, I guess. It may be a minimal cost for me to rent
 RF> additional server space temporarily while we figure this out. I'll mull
 RF> that over tonight and more than likely will just pull the trigger on
 RF> getting another box.

Are you able to install another copy in a separate directory so you can do some
testing with the new version?  I'm not sure how your server works, but if its
by space then a fresh Mystic only takes 3 megabytes.  You could just use
different ports if you wanted to run any of the servers.

If you can do a side install we could use the latest in-progress A37 from
www.mysticbbs.com/downloads/prealpha, and we can work with that until we
resolve things with DOSEMU, etc.

 RF> I could've sworn the fsx hubs were Windows machines, but I could be
 RF> wrong. Like I said, I'll try to repro, something got into a funky state
 RF> and I'm not sure why. *shrug*

Yes the main hub is Windows but the mailer's logic and code doesn't change
between operating system versions.  The Linux version is probably more heavily
used than the Windows version in general.

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