Quote:
The problem I experienced is caused by the following PING command, which mIRC occasionally sends to the server:

Code:
  -> irc.inet.tele.dk PING :TIMEOUTCHECK
  <- :irc.inet.tele.dk PONG irc.inet.tele.dk :heidel

Why mIRC sends these I have no idea, I can only speculate.

See item 28 in versions.txt regarding the new connect timeout option in the connection/options dialog.

If mIRC sends a PING with a parameter, it expects a PONG response with that parameter. This is meant to be standard PING/PONG behaviour. If your bouncer is intercepting the message and is not replying correctly, then mIRC will not work.

This also affects the flood protection feature which uses the same method in mIRC 6.17, and explains why users are saying the flood protection is not working.

mIRC only sends a PING timeout check when there has been no activity for some time.

mIRC hides PINGs sent to you from the server, not PONGs that are due to you sending a PING to the server (where you would expect to see a reply). These are different messages entirely.