You can look at this more as a difficulty in the current behavior of mIRC, or possibly a bug. This idea or problem is with Perform on connect, and being set per network and server. The perform on connect command I have entered is for "networkx" and it uses networkx.com to connect, however networkx discontinued service and is now forwarding traffic to "networka" - in this case networkx is no longer advertised as the network and networkx.com is no longer the server name, however mIRC still sends the perform on connect commands as if it were connecting to networkx. This is sort of a security problem actually, as one might send passwords and other information to the new server and that information can be intercepted by untrusted people. It would be a good idea that mIRC only perform the on connect commands if the server it connects to has the proper identification the server connect process (network name and irc server names).
What say you?