Thanks for the details on this problem.
The solution is for QMClient to be more sensitive to the incoming data in
the initial packet. As things stand, it expects the received data to be a
properly formed login packet, including a byte count. I suspect that what is
happening is that the position in which we expect to find this count is
occupied by text but gets interpretted as a (massive) count that causes the
We have modified the incoming end of a QMClient connection to sense that the
byte count is unreasonably large for a login packet and to disconnect. The
code already disconnected for invalid packet types.
Ladybridge Systems Ltd
17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB