what if the OUT message wasnt just blocked? maybe there is a following data packet specifying what kind of OUT it is.
the 'minimized window for 2 days' senario keeps me thinking.
maybe the MSN servers send a 'timeout' message to both clients, and after reciept, even though your window is minimized, a new connection is established seamlessly.
so.. since this setup, doesnt seem to quite work, or in any real way fixable, how about we do the reverse, and after every message sent, send an OUT message right after.
this way your contact would be inclined to disable that feature.
anyhoo, just a thought. remember to stay outside of the box
oh, just another thought.
maybe after each killed OUT message, you have an app send an 'IN' message back to MSN, doing kindof like a fake connection reistablish.
but it would use the same ports, and remember which TCP packet number was used last.
i was thinking that MSN might need actual typed data, before it opens a window. so that doing this wouldnt cause a loop, close the window, auto pops back open.
/ –
