Sprockets: Unfortunately, you're earlier assessment about aerize wifix not being able to handle any secured sockets is true. However, i don't think it's Wifix but rather Cricket that's cockblocking us. Cricket explicitly blocks important ports such as 25, 443, 995, 993, etc., and leaves some others open to be tunneled through port 8080. For example, with cricket Aerize WiFix won't work any apps like gmail, hotmail, yahoo, etc., and others that need those ports, however Shangmail works well on port 444 (secured sockets), is able to (incidentally, as a test I removed all of the extra hosts and left only en.shangmail.com:444, and it worked fine for me). I think that's why we're getting contradictory reports about gmail/logicmail, slacker, pandora, etc. working for some with wifix and other unable. Those that ARE able to are probably using wifi (802.11) on a blackberry like the Storm, and those that are NOT able to are probably just using the WAP2 transport (at which point Cricket castrates the needed ports). The true test would be for someone that has a wifi Blackberry (like the Storm) that is also flashed to cricket and has aerize WiFix, to first use the standard HTTP request format (with wifi), turn off the mobile connection and connect to a 802.11 wifi network, and try one of the apps like gmail IMAP port 995, etc. Then they could do the test in reverse using the WAP2 trans HTTP request format for gmail and disable wifi, connect cricket mobile connection, and test again. I'm betting that it'd work fine on the wifi test, and NOT on the cricket test, because people use ssh tunneling ports 444, 443, etc. through proxies on port 8080 all the time, but a lot of proxies explicitly block certain ports (Thanks, Cricket).