So I just got off the phone with support at GoDaddy for one of my customers and was told "Sorry we can't do that", when asked to provide socket permissions to go out and hit a POP3 server. GoDaddy has the web.config locked down and so you can't override the originUrl="site" so my customer is dead in the water with this account.

This is a real bummer because he specifically checked asked for this (maybe not specifically for socket permission but external TCP/IP access) and was told that this was workable through this account.

I remember a long while back while talking about a related issue that some people have had better luck by leaning a bit harder on the tech support guys. I didn't have any luck though although the tech person I talked to spend about a half an hour researching the issue...

I'm wondering though - is anybody doing this with GoDaddy? Before I throw in the towel here (since some time went into getting the app over there and SQL setup) it would help if there's somebody around who might have gotten GD to buckle and give in and with some idea what GD had to do to make it happen on their end.

Anybody?

BTW, anybody have any hoster suggestions that are a little more lenient with their permission sets especially in regards to outbound/inbound external connections?

Source:http://www.west-wind.com