Can you be more specific?
TIdIRC sends a QUIT command only when its own Disconnect() method is called by user code. TIdIRC does not call its own Disconnect() method for any reason (it calls the inherited TIdTCPClient.Disconnect() method instead). Certainly not when processing the server's 219 ENDOFSTATS message. Are you, by chance, calling Disconnect() yourself? Maybe in response to an error/exception?
TIdIRC does not currently process 210 status messages at all, they are simply ignored. In fact, I don't even see 210 defined in the original IRC protocol spec.
UPDATE: Oh wait, 210 is defined in a later update to the spec. But, it is defined as RPL_TRACERECONNECT, is marked as "unused", and is not listed as an allowed reply for the STATS command. So, I wonder why your IRC server is using 210 for its status infos?
Have you tried debugging TIdIRC's source code to see exactly what is failing while processing these messages?
TIdIRC sends a QUIT command only when its own Disconnect() method is called by user code. TIdIRC does not call its own Disconnect() method for any reason (it calls the inherited TIdTCPClient.Disconnect() method instead). Certainly not when processing the server's 219 ENDOFSTATS message. Are you, by chance, calling Disconnect() yourself? Maybe in response to an error/exception?
TIdIRC does not currently process 210 status messages at all, they are simply ignored. In fact, I don't even see 210 defined in the original IRC protocol spec.
UPDATE: Oh wait, 210 is defined in a later update to the spec. But, it is defined as RPL_TRACERECONNECT, is marked as "unused", and is not listed as an allowed reply for the STATS command. So, I wonder why your IRC server is using 210 for its status infos?
Have you tried debugging TIdIRC's source code to see exactly what is failing while processing these messages?