-- ssh is still blocked. Maybe I can tunnel ssh-over-SSL? For that I need another port. How about 993 (IMAPS)? Turns out that one's blocked too. I can't even call a legit IMAPS server on a system where I have a guest account, and which works over normal networks. Good thing I use POP3 for my personal mail, but I'm surprised no corporate customer has given them grief over this.

Really feels like cargo-cult security: rules invented sans understanding. #BoringTravel #StupidNetworkTricks

Banging a bit more on #Amtrak #ChicagoUnionStation WiFi. It's rather a Mrs Presky's Prize:
-- I had used a self-signed TLS cert for my home POP3S/SMTPS, and their gateway refused to allow calls. I've now got a real cert from #LetsEncrypt and it works.
-- Well, except SMTPS. Port 465 is a non-no. Run the same service on port 587 and all is well. I am not sure this is what the standards say. #BoringTravel #StupidNetworkTricks ...
Arrived Chicago 3h50 late. Amtrak held the Capitol Limited for connecting passengers; no need to hold my train. Sitting in the Metropolitan Lounge waiting for it, and discovering that the stupid network lets me call my pop3s server now that I have a real SSL certificate, but still blocks all calls to smtps (465). Maybe I'll try 587. #BoringTravel #StupidNetworkTricks