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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

super70s <[email protected]d> wrote:

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 name of the host has been reader80 for years.

There's also

reader443.eternal-september.org, port 443 for NNTPS using a modern TLS,
not SSL.

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

This is wrong. It's port 119.

For NNTPS using a modern TLS, use port 563.

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

This doesn't make any sense unless it's somehow saved a redirect to
reader80. Why not change it to the correct host?

and news.eternal-september.org, port 119.

Go figure.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 22 Jul 2025 22:48:43 -0000 (UTC), "Adam H. Kerman"
<[email protected]> wrote:

super70s <[email protected]d> wrote:

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 name of the host has been reader80 for years.

There's also

reader443.eternal-september.org, port 443 for NNTPS using a modern TLS,
not SSL.

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

This is wrong. It's port 119.

For NNTPS using a modern TLS, use port 563.

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

This doesn't make any sense unless it's somehow saved a redirect to
reader80. Why not change it to the correct host?

and news.eternal-september.org, port 119.

Go figure.

I experienced a similar problem and had to change my settings as well.
It happened without notice one day.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 22 Jul 2025 22:48:43 -0000 (UTC), "Adam H. Kerman"
<[email protected]> wrote;

super70s <[email protected]d> wrote:

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 name of the host has been reader80 for years.

Really? I was assuming it was a fairly new thing.

There's also

reader443.eternal-september.org, port 443 for NNTPS using a modern TLS,
not SSL.

I saw that on the site but I wasn't sure my newsreader could work with
TLS, it's graveyard software.

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

This is wrong. It's port 119.

Yeah that was a mistype, I meant 119.

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

This doesn't make any sense unless it's somehow saved a redirect to
reader80. Why not change it to the correct host?

I guess I should.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)