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.
On 2025-07-22 22:08:01 +0000, super70s said:
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.
Port 110 isn't liked by Unison. Leaving the port number blank defaults
to 119 which works fine.
On 2025-07-23 04:12:02 +0000, Your Name said:
On 2025-07-22 22:08:01 +0000, super70s said:
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.
Port 110 isn't liked by Unison. Leaving the port number blank defaults
to 119 which works fine.
That was a mistype, I'm using 119 for news.eternal-september.org.
On 23.07.25 10:18, super70s wrote:
On 2025-07-23 04:12:02 +0000, Your Name said:
On 2025-07-22 22:08:01 +0000, super70s said:
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.
Port 110 isn't liked by Unison. Leaving the port number blank defaults
to 119 which works fine.
That was a mistype, I'm using 119 for news.eternal-september.org.
Use Port 563 with SSL/TLS. To use Thunderbird instead of Unsion could
also help.
On 2025-07-23 08:31:04 +0000, Jörg Lorenz said:
On 23.07.25 10:18, super70s wrote:
On 2025-07-23 04:12:02 +0000, Your Name said:
On 2025-07-22 22:08:01 +0000, super70s said:
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.
Port 110 isn't liked by Unison. Leaving the port number blank defaults >>>> to 119 which works fine.
That was a mistype, I'm using 119 for news.eternal-september.org.
Use Port 563 with SSL/TLS. To use Thunderbird instead of Unsion could
also help.
I'm running Mojave on a 2014 iMac14,4. Unison does fine on it unless
it's some kind of settings problem like described above. I hear people saying it crashes a lot but it rarely does for me.
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.
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 1,064 |
Nodes: | 10 (0 / 10) |
Uptime: | 148:09:48 |
Calls: | 13,691 |
Calls today: | 1 |
Files: | 186,936 |
D/L today: |
33 files (6,120K bytes) |
Messages: | 2,410,932 |