PH> Check with the admin that your IP address has not ended up in badip.txt
 PH> in the data dir of Mystic. If it has he should remove it and restart his
 PH> MIS.

Yep, this sounds like a likely scenario.  If the SysOp has auto banning of IP's
on after a certain # of connections within a certain time frame, then Mystic
will simply print "BLOCKED" to the socket and disconnect.

How BBBS handles that is unknown to me, but that would absolutely explain it.

And BBBS does seem to have that issue where it endlessly pools according to
someone on FSXNET, so that would explain how the IP was banned to begin with
too.

--- Mystic BBS v1.12 A35 (Windows/32)