Path: nntp.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: super70s <super70s@super70s.invalid>
Newsgroups: rec.arts.tv
Subject: all you eternal-september users
Date: Tue, 22 Jul 2025 17:01:31 -0500
Organization: A noiseless patient Spider
Lines: 24
Message-ID: <105p1nr$45qr$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 22 Jul 2025 22:01:34 +0000 (UTC)
Injection-Info: dont-email.me; posting-host="3b1e6ae98babd4a73ebd9aa193b42805";
	logging-data="137051"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+KHaWD0Ekp8lEuVJraoF4j/vAO69Ro2VY="
User-Agent: Unison/2.2
Cancel-Lock: sha1:vDEvWdqVRexpF5fgXgTdzvvympA=
X-No-Archive: yes

On one of my newer systems I was suddenly having trouble getting 
eternal-september to refresh the messages the past couple of days.

So I went to eternal-september.org and checked the settings. Turns out 
they're different from the settings I had for 
reader-eternal-september.org and news.eternal-september.org -- they 
have been changed.

The correct server for reader.eternal-september.org is now 
reader80.eternal-september.org, port 80, no SSL.

The correct server for news.eternal-september.org is still 
news.eternal-september.org, but port 110, no SSL.

At least that's what works for me now. Maybe you should check your ES 
settings in case you run into trouble like I did.

Strangely, on my older system and newsreader (MT NewsWatcher) both of 
those servers work normally, without making any of the above changes. 
Which are reader.eternal-september.org, port 119 and 
news.eternal-september.org, port 119.

Go figure.