Forums mIRC Help zline/gline not reported correctly for ssl

depending on server, mirc reports

seems to be swallowing the cause and reporting the only ssl failure, which gives zero information, e.g.:

The SSL messages listed in your post are standard SSL errors that are reported when a server closes a connection.

The most common reason for the "SSL wrong version number" error is that the server is using an old version of SSL that is not secure and a suitable protocol cannot be negotiated.

The "SSL unexpected eof while reading" is due to an old/non-compliant server that is not sending a close notify event ie. calling SSL_shutdown(), when closing the connection. OpenSSL 3.x introduced a vulnerability fix relating to truncation attacks where if the server does not send a close notify event, this error is reported to prevent the vulnerability.

As far as I see, there isn't much a client can do in this situation. The server itself needs to be updated.

i understand about the ssl errors, however the actual cause in this case is zline/gline.
is there no way to detect this? the ssl error is extremely misleading, as this is not a ssl problem at all (not only barking up the wrong tree, but doing it in the wrong forest...)
*lines are of course reported correctly when there is no ssl involved.

In your case, it looks like the SSL connection is reporting these errors before mIRC receives anything else. It is possible for a client to not receive pending outgoing messages from a server if the server closes the connection incorrectly. See here and here for discussions on this topic. The odds are that this is due to the way the server closes the connection. The fact that the behaviour is different with/without SSL is likely down to SSL itself being stricter in how it handles connections, eg. as in the case of the truncation vulnerability.