Post Reply 
Windows Live Messenger & live.com ; required exceptions
May. 20, 2009, 05:21 PM
Post: #1
Windows Live Messenger & live.com ; required exceptions
Hello everyone,

As you might know, if you use Windows Live Messenger and live.com, they don't work properly through Prox+Sidki (maybe indeed through any other config too).
For some time, I've had the following entries in the bypass list, but I don't think I've ever had it set ideally; specifically regarding how to filter (or block?) rad.msn.com whilst still allowing other bits of msn.com. rad.msn.com seems to deliver the ads in Messenger, some of which are very intrusive including on-mouse-over 'popouts'.

*live.*
*.hotmail.*
*.msn.*

(Note: login.live.com may be sufficient as an exception just for Messenger, but various parts of live.com itself break through Prox+Sidki)

I based the above on looking at this page :-

Network ports and urls required for Windows Live Messenger 2009, by Microsoft

Can anyone suggest a better/correct/more efficient set of bypass or exception entries, for both Windows Live Messenger and live.com?
(whilst still trying to tame ad delivery from rad.msn.com)

Thanks for any wisdom,
Lee
Add Thank You Quote this message in a reply
Post Reply 


Messages In This Thread
Windows Live Messenger & live.com ; required exceptions - leecovuk - May. 20, 2009 05:21 PM

Forum Jump: