Eeternal-september

Char Jackson wrote:
On Wed, 06 Sep 2017 03:05:31 -0400, Paul wrote:

# At the current time, the machine is ****ing up headers (it is posting
# the posting-host IP address), and I won't be using it until that is fixed.
# That means a filter on the posting part, isn't enabled yet. It replaces
# that part of the header, with an encrypted string.

In Message-ID: poster Mike Easter
says "In e-s support last nite Ray said 'oops' and restored the
encryption/hash."

So that part might be corrected now.

The news.eternal-september.org server is still acting up
for me. It's indicating "Connection Refused" at the moment.

And the number of sessions has dropped in the last couple hours.

http://www.eternal-september.org/ser...hp?language=en

The web server still works :-)

Paul

On Wed, 06 Sep 2017 09:46:22 -0500, in alt.comp.os.windows-10, Char
Jackson wrote:

# At the current time, the machine is ****ing up headers (it is posting
# the posting-host IP address), and I won't be using it until that is fixed.
# That means a filter on the posting part, isn't enabled yet. It replaces
# that part of the header, with an encrypted string.

Yeah, I saw that. If I was using E-S, I wouldn't be too happy about
that. There be stalkers in these waters who love information like that.

Just tried it out in alt.test. Doesn't seem to be doing that any more.

But I haven't been able to access NNTP over port 119 all day. Using port
80 with news.eternal-september.org right now.

I think the DNS is screwed up. Right now reader, news, and reader80 all
point to the same IP address on my network, which I'm guessing is the
web-port server.

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten

On Wed, 06 Sep 2017 12:41:11 -0400, in alt.comp.os.windows-10, Paul
wrote:

Char Jackson wrote:
On Wed, 06 Sep 2017 03:05:31 -0400, Paul wrote:

# At the current time, the machine is ****ing up headers (it is posting
# the posting-host IP address), and I won't be using it until that is fixed.
# That means a filter on the posting part, isn't enabled yet. It replaces
# that part of the header, with an encrypted string.

In Message-ID: poster Mike Easter
says "In e-s support last nite Ray said 'oops' and restored the
encryption/hash."

So that part might be corrected now.

The news.eternal-september.org server is still acting up
for me. It's indicating "Connection Refused" at the moment.

And the number of sessions has dropped in the last couple hours.

http://www.eternal-september.org/ser...hp?language=en

The web server still works :-)


I tried a DNS lookup for news.e-s.org and reader.e-s.org. They all appear
to point to the same IP address as reader80.e-s.org (at least on my
provider's DNS lookup).

DNS appears to have been fudged up.

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten

On Wed, 06 Sep 2017 13:10:27 -0500, Zaghadka
wrote:

I tried a DNS lookup for news.e-s.org and reader.e-s.org. They all appear
to point to the same IP address as reader80.e-s.org (at least on my
provider's DNS lookup).

DNS appears to have been fudged up.

That sounds normal to me. I expect all of those DNS entries to resolve
to the same IP. They don't have to, of course, but if it's a small
operation then that would be expected.

On 09/06/2017 05:30 PM, Char Jackson wrote:
On Wed, 06 Sep 2017 14:59:13 -0600, KenW
wrote:

On Wed, 06 Sep 2017 14:53:03 -0500, Char Jackson
wrote:

On Wed, 06 Sep 2017 13:10:27 -0500, Zaghadka
wrote:

I tried a DNS lookup for news.e-s.org and reader.e-s.org. They all appear
to point to the same IP address as reader80.e-s.org (at least on my
provider's DNS lookup).

DNS appears to have been fudged up.

That sounds normal to me. I expect all of those DNS entries to resolve
to the same IP. They don't have to, of course, but if it's a small
operation then that would be expected.

that site is being upgraded or something. found that on another group

The owner of the site put up a message he
http://www.eternal-september.org/ser...hp?language=en

Odd that they say it's working but both reader..... and news..... both
fail for me. port 119.

On 09/06/2017 05:37 PM, Big Al wrote:
On 09/06/2017 05:30 PM, Char Jackson wrote:
On Wed, 06 Sep 2017 14:59:13 -0600, KenW
wrote:

On Wed, 06 Sep 2017 14:53:03 -0500, Char Jackson
wrote:

On Wed, 06 Sep 2017 13:10:27 -0500, Zaghadka
wrote:

I tried a DNS lookup for news.e-s.org and reader.e-s.org. They all
appear
to point to the same IP address as reader80.e-s.org (at least on my
provider's DNS lookup).

DNS appears to have been fudged up.

That sounds normal to me. I expect all of those DNS entries to resolve
to the same IP. They don't have to, of course, but if it's a small
operation then that would be expected.

that site is being upgraded or something. found that on another group

The owner of the site put up a message he
http://www.eternal-september.org/ser...hp?language=en

Odd that they say it's working but both reader..... and news..... both
fail for me. port 119.

Yet I can ping both and they both resolve to the same IP. I've checked
everything in Thunderbird but can't find a single issue, and since
nothing changed, nothing should be wrong with TB settings. Oh well,
I'll wait for a while and see what happens.
Posting via aioe

On 9/6/2017 4:39 PM, Big Al wrote:
On 09/06/2017 05:37 PM, Big Al wrote:
On 09/06/2017 05:30 PM, Char Jackson wrote:
On Wed, 06 Sep 2017 14:59:13 -0600, KenW
wrote:

On Wed, 06 Sep 2017 14:53:03 -0500, Char Jackson
wrote:

On Wed, 06 Sep 2017 13:10:27 -0500, Zaghadka
wrote:

I tried a DNS lookup for news.e-s.org and reader.e-s.org. They all
appear
to point to the same IP address as reader80.e-s.org (at least on my
provider's DNS lookup).

DNS appears to have been fudged up.

That sounds normal to me. I expect all of those DNS entries to resolve
to the same IP. They don't have to, of course, but if it's a small
operation then that would be expected.

that site is being upgraded or something. found that on another group

The owner of the site put up a message he
http://www.eternal-september.org/ser...hp?language=en

Odd that they say it's working but both reader..... and news..... both
fail for me.Â*Â* port 119.

Yet I can ping both and they both resolve to the same IP.Â*Â* I've checked
everything in Thunderbird but can't find a single issue, and since
nothing changed, nothing should be wrong with TB settings.Â*Â* Oh well,
I'll wait for a while and see what happens.
Posting via aioe


Hi Al, same problem here, not working on news or reader But got it
working on Reader80 on port 80 which is what I am using now.

Rene

Rene Lamontagne actually wrote:

Hi Al, same problem here, not working on news or reader But got it
working on Reader80 on port 80 which is what I am using now.

TEST 1
telnet news.eternal-september.org 119
Connecting To news.eternal-september.org...Could not open connection to the
host, on port 119: Connect failed

TEST 2
telnet news.eternal-september.org 563
works (encrypted) I don't know how to test them using telnet though.

TEST 3
telnet reader80.eternal-september.org 80
200 news.eternal-september.org InterNetNews NNRP server INN 2.7.0 (20170224
snapshot) ready (posting ok)
help
post
340 Ok, recommended message-ID
GROUP alt.test
211 2653 3 3437 alt.test
POST
340 Send Article to be Posted
From:
Subject: Testing ET posting
Message-ID:
Newsgroups: alt.test

This is a test
..
next
body
quit

TEST 4
telnet reader443.eternal-september.org 443
works (encrypted) I don't know how to test encrypted connections

Roy Tremblay wrote:
TEST 2
telnet news.eternal-september.org 563
works (encrypted) I don't know how to test them using telnet though.

You need to use openssl

openssl s_client -connect news.eternal-september.org:563
CONNECTED(00000003)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify error:num=19:self signed certificate in certificate chain
verify return:0
---
Certificate chain
0 s:/CN=reader.eternal-september.org
i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
i:/O=Digital Signature Trust Co./CN=DST Root CA X3
2 s:/O=Digital Signature Trust Co./CN=DST Root CA X3
i:/O=Digital Signature Trust Co./CN=DST Root CA X3
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIFNzCCBB+gAwIBAgISAwULk/JCcqYNCCl92ocydzo2MA0GCSqGSIb3DQEBCwUA
MEoxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeX B0MSMwIQYDVQQD
ExpMZXQncyBFbmNyeXB0IEF1dGhvcml0eSBYMzAeFw0xNzA5MD UwMzQzMDBaFw0x
NzEyMDQwMzQzMDBaMCcxJTAjBgNVBAMTHHJlYWRlci5ldGVybm FsLXNlcHRlbWJl
ci5vcmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQ C4p84L+e2VOvGf
IfTvKag7WuhVHHkjOpmeaqen+lM9nmYgjDAS2hVlxvcylS3cDO VpFMD2nxRsxLUx
Yo8/O8FUU7STrE0BvVdIZLaTYaC/NjO3btmihnSqZzf9mlz1U919SwM8oj6HMsuQ
y+J+XR7qAxTuxKplbM6wzFh1lcJrjukR0BEvl3b2fzurJDPbTZ KHTIS0Rc5ahErj
VDZyEdyGOdETCtF8uTrTvk9CG5ENt0+qVt2WQfHgWGmt9eT52i ZFYBoB/BBGRQSr
EUxYW4Ri8nKERFJd91K+KCar1ZulOoHf2wqMr86ZTbRbYLAt1L hIfC+b7z1KhR/0
zovtXNIHAgMBAAGjggI4MIICNDAOBgNVHQ8BAf8EBAMCBaAwHQ YDVR0lBBYwFAYI
KwYBBQUHAwEGCCsGAQUFBwMCMAwGA1UdEwEB/wQCMAAwHQYDVR0OBBYEFMCBSD5H
SI4BtLY8c3RpNZYxmD7VMB8GA1UdIwQYMBaAFKhKamMEfd265t E5t6ZFZe/zqOyh
MG8GCCsGAQUFBwEBBGMwYTAuBggrBgEFBQcwAYYiaHR0cDovL2 9jc3AuaW50LXgz
LmxldHNlbmNyeXB0Lm9yZzAvBggrBgEFBQcwAoYjaHR0cDovL2 NlcnQuaW50LXgz
LmxldHNlbmNyeXB0Lm9yZy8wQwYDVR0RBDwwOoIabmV3cy5ldG VybmFsLXNlcHRl
bWJlci5vcmeCHHJlYWRlci5ldGVybmFsLXNlcHRlbWJlci5vcm cwgf4GA1UdIASB
9jCB8zAIBgZngQwBAgEwgeYGCysGAQQBgt8TAQEBMIHWMCYGCC sGAQUFBwIBFhpo
dHRwOi8vY3BzLmxldHNlbmNyeXB0Lm9yZzCBqwYIKwYBBQUHAg IwgZ4MgZtUaGlz
IENlcnRpZmljYXRlIG1heSBvbmx5IGJlIHJlbGllZCB1cG9uIG J5IFJlbHlpbmcg
UGFydGllcyBhbmQgb25seSBpbiBhY2NvcmRhbmNlIHdpdGggdG hlIENlcnRpZmlj
YXRlIFBvbGljeSBmb3VuZCBhdCBodHRwczovL2xldHNlbmNyeX B0Lm9yZy9yZXBv
c2l0b3J5LzANBgkqhkiG9w0BAQsFAAOCAQEAWQsi4zJUW75l9R lTHOjvzaMVbi1i
ee1kyDwKIr32OU6uHQczR+jFTsHg+BPt6wqryCYOS5kQRPpmpv QLhiTJH2fl5Nii
HsSwikTo9itFNz7yMxxOE83++nuQzyTK6ALaZWlfvAt42n0cU5 ZKP4iZ+cTIyJoY
OlIH1UTFTf8N1p/b7a81EbKgmP98wBup81IHHhnEC0jlZz5/CxGE/nEUKbaJdH4G
8LnIIZRsJu+aeRnNpck+CNLSOVDzTfIg6wRieHhcM4ndBkFwVy 18nzV6a1ApvVga
X4VCeWkS/3jf0R+ap73Y+02dJ2Hh1hQP3iVtw97uX8M5kYKH2amBgYFxxQ= =
-----END CERTIFICATE-----
subject=/CN=reader.eternal-september.org
issuer=/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
---
No client certificate CA names sent
---
SSL handshake has read 4024 bytes and written 421 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : TLSv1.2
Cipher : ECDHE-RSA-AES256-GCM-SHA384
Session-ID:
81843FBA365D9130CFB8CBC6C0C048F85A8B1FB529B4EE6885 928D10114BDE6C
Session-ID-ctx:
Master-Key:
C5CA7A58A1D1A71BE2C9A96225C29BAC44BB2C8FA917CC0E19 1A580441999ABE68A570BA648A66B598648D4E5EEFD191
Key-Arg : None
PSK identity: None
PSK identity hint: None
SRP username: None
TLS session ticket lifetime hint: 300 (seconds)
TLS session ticket:
0000 - 87 ac 97 55 4b 41 0e 32-44 17 f5 ff 26 3c 3c f8
....UKA.2D...&.
0010 - 51 f4 c5 14 c9 1a d0 17-53 ba 15 19 73 a7 77 b2
Q.......S...s.w.
0020 - 0c 06 ae 73 f6 72 29 1e-e0 37 6a 01 50 f0 9e d8
....s.r)..7j.P...
0030 - bf 7c 99 0a f0 85 93 39-c8 9b d6 05 8d 1e 29 e1
..|.....9......).
0040 - d8 93 ca 4b d9 a6 50 97-69 2e fe b6 93 50 e8 9b
....K..P.i....P..
0050 - 16 6a b3 b7 9c 87 4d f1-50 78 ee 67 2a 87 87 cf
..j....M.Px.g*...
0060 - 1f 28 27 8f 73 42 e6 ca-58 cf 9b 07 82 80 60 67
..('.sB..X.....`g
0070 - ed d8 9f 5e 74 7b 2b d4-36 11 42 91 55 54 2f f7
....^t{+.6.B.UT/.
0080 - 5d d6 68 72 7b f0 a9 c7-e2 b1 84 cf 32 e3 fe 6b
].hr{.......2..k
0090 - 6a 5c c1 25 8b fd ae a0-63 07 62 54 14 c9 95
j\.%....c.bT...
00a0 - SPACES/NULS

Start Time: 1504746753
Timeout : 300 (sec)
Verify return code: 19 (self signed certificate in certificate chain)
---
200 news.eternal-september.org InterNetNews NNRP server INN 2.7.0
(20170224 snapshot) ready (posting ok)
..
quit
205 Bye!
closed


Noticed port 119 stopped working today so switched to SSL 563 and it now
works...

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On 09/06/2017 07:39 PM, Roy Tremblay wrote:
Rene Lamontagne actually wrote:

Hi Al, same problem here, not working on news or reader But got it
working on Reader80 on port 80 which is what I am using now.

TEST 1
telnet news.eternal-september.org 119
Connecting To news.eternal-september.org...Could not open connection to the
host, on port 119: Connect failed

TEST 2
telnet news.eternal-september.org 563
works (encrypted) I don't know how to test them using telnet though.

TEST 3
telnet reader80.eternal-september.org 80
200 news.eternal-september.org InterNetNews NNRP server INN 2.7.0 (20170224
snapshot) ready (posting ok)
help
post
340 Ok, recommended message-ID
GROUP alt.test
211 2653 3 3437 alt.test
POST
340 Send Article to be Posted
From:
Subject: Testing ET posting
Message-ID:
Newsgroups: alt.test

This is a test
.
next
body
quit

TEST 4
telnet reader443.eternal-september.org 443
works (encrypted) I don't know how to test encrypted connections

If I use Test 2 port 563 do I use TLS/SSL or None for security?

If I use Test 2 port 563 do I use TLS/SSL or None for security?

Disregard!

On 05/09/2017 18:44, philo wrote:
On 09/05/2017 11:24 AM, Rene Lamontagne wrote:
On 9/5/2017 11:07 AM, Franklin wrote:
On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name
"news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.


https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by
new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under
the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.



Hi, thanks for the info, much appreciated.

Rene




Nice for it to be back now. I do have a few backup news servers though

Which one is your top backup of choice?

In alt.comp.os.windows-10, on Tue, 05 Sep 2017 09:07:15 -0700, Franklin
wrote:

On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.


https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by

This started working again yesterday, but last night or more likely this
morning, I could regtrieve but not post using it.

new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under

So I changed to reader... but it's the same situation.

Any suggestions? Or should I just wait. Wait!! I can't post this
question anyhow. ;-(

the usual name as soon as the DNS changes have fully propagated.
Currently, connections on port 80 and 443 are not available yet. These
will be available again soon. The new server has an SSL certificate
for both reader.eternal-september.org and news.eternal-september.org.
UUCP connectivity is currently not available, but will be
re-established tomorrow.

micky wrote:
In alt.comp.os.windows-10, on Tue, 05 Sep 2017 09:07:15 -0700, Franklin
wrote:

On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.

https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by

This started working again yesterday, but last night or more likely this
morning, I could regtrieve but not post using it.

new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under

So I changed to reader... but it's the same situation.

Any suggestions? Or should I just wait. Wait!! I can't post this
question anyhow. ;-(


By sheer force of will, you should be able to make it work.

Paul

In alt.comp.os.windows-10, on Fri, 08 Sep 2017 00:39:19 -0400, Paul
wrote:

micky wrote:
In alt.comp.os.windows-10, on Tue, 05 Sep 2017 09:07:15 -0700, Franklin
wrote:

On Tue, 5 Sep 2017 10:55:54 -0500, Rene Lamontagne
wrote:

Lost touch with 213-239-209-88 last night, news groups were all timing
out, this morning I changed back to the name "news.eternal-september.org
a now all back to normal.I was advised this may happen when I switched
to the numbers instead of name.

https://www.eternal-september.org/

2017-09-05 09:38:05 Server news.eternal-september.org replaced

The old reader server news.eternal-september.org had to be replaced by

This started working again yesterday, but last night or more likely this
morning, I could regtrieve but not post using it.

new hardware just before the scheduled replacement date. The new
server is up and running, DNS changes are underway. The new server is
called reader.eternal-september.org, but will also be available under

So I changed to reader... but it's the same situation.

Any suggestions? Or should I just wait. Wait!! I can't post this
question anyhow. ;-(


By sheer force of will, you should be able to make it work.

Paul

Yes, that must be it! I am so powerful.

Next, I will debug my software without leaving my bed.