Quote:
If you read RFC1459, it specifically states that all clients most respond with valid and accurate CTCP VERSION replies for the reasons I pointed out in my above posts. Don't argue with me. RTFM.

/me goes to read the RTFM (RFC1459). Searching RFC1459 for "CTCP" : Not found. Searching RFC1459 for "Client to Client Protocol" : Not found. Where does RFC1459 say anything about this? At the time RFC1459 was written, there was no such thing as CTCP. Now lets look at the CTCP specification. You say "valid and accurate" correct? Well, mIRC is neither. According to the CTCP specification, the format for a CTCP version reply is:
clientname:version:OS
for example:
mIRC:6.03:win32
Is that what your mIRC responds with? Because mine doesn't.

The general rule of thumb is a specific response, or even any response at all should NOT be required to any CTCP request. Any server that does require a CTCP response does not follow this. That is the IRC server's problem, not the client.