08-03-2020, 07:21 PM
(08-01-2020, 11:50 AM)fearcry Wrote: thats true, i set the QuitMessage in Client A, so there must be a TIdIRC->Disconnect(MyQuitMessage); in my own Code . .
OK, so WHERE exactly in your code are you making that call?
(08-01-2020, 11:50 AM)fearcry Wrote: The only Chance to see this Issues is to be connected via SSL to admin the IRCD to get the Operator-Level to use the STATS Command
Since I can't test that myself to begin with, I don't care about that. That is just an implementation detail of the server.
(08-01-2020, 11:50 AM)fearcry Wrote: but it is responsible - just the receiving of [219 End of Stats] from Client A causes the TIdIRC->Disconnect(MyQuitMessage);
I can't help you if you don't show me EXACTLY what is being transmitted. I don't want to see logs. I want to see the RAW DATA going over the connection TCP (at least the IRC data, not the SSL data). Or, at least a call stack trace leading up to the call to Disconnect(). I'm ASSUMING there is an exception being raised that you are catching to call Disconnect(), yes? If so, I would need to know what function inside of TIdIRC is actually raising the exception, and what kind of exception it is.