Yes, the first version I put up would still work even though it had the wrong port. The reason is that now the VPLive error detection for bad connections works. First VPLive tries to send to rotate.aprs.net:14580, then if that fails it tries rotate.aprs.net:23 (this covers the case where some people's firewall blocks high numbered ports), and if that fails, it tries several of the tier 2 servers on port 14580.
So, even though I had the wrong port set (I put in 14850 instead of 14580), the program would use port 23 after the failure of port 14850.
14580 is the preferred port now for send only. Port 23 still works, but the core servers send back a bunch of data in response (which is unneeded and ignored by weather programs sending CWOP data), so it wastes some bandwidth.
I may change the order of servers VPLive tries in the future after this core server/tier 2 server debate gets resolved. But for now, the way I have it set up should be fairly reliable since it will fallback to tier 2 servers if the core servers get swamped and begin refusing some connections. The tier 2 servers are, for the time being back accepting weather data, but they've switched from using port 23 to using port 14580. They also may drop supporting the rotate.aprs2.net address, which is why I try specific individual servers in the tier 2 fallback code.
Steve