07-17-2012 11:18:26 AM
I've been an Easynews.com Usenet user for a bit over 10 years, and have been using their SSL NNTP server for at least two years, maybe more. I signed up to AT&T U-verse in August of 2011, and had been using my identical, unchanged NNTP client configuration, set to connect to the Easynews SSL NNTP server (secure-us.news.easynews.com) successfully from the time I signed on to AT&T U-verse last August until about June 24 of this year. Since that time, attempts to connect to secure-us.news.easynews.com have been unsuccessful. This server listens on ports 21, 22, 23, 25, 53, 80, 110, 119, 443, 563, 8000, and 8080. I tried all of these to no avail. I am able to successfully connect to their non-SSL server, which listens on port 119, but I would much prefer to use the SSL server due to security concerns. I have tried this connection on my normal NNTP client (Usenet Explorer), as well as Thunderbird and have even attempted to Telnet to the server, with no luck. I brought up this issue on the Easynews support newsgroup, and one other user is having the same problem, but it is by no means widespread. I have spoken to Easynews tech support, but they are able to connect to the server just fine.
Is AT&T blocking SSL access to third party Usenet servers?