XPost: alt.free.newsservers, news.software.readers

Before I bother the admin of a common free news server (who I promised if
he gave me a posting account, I wouldn't be any trouble) I would like to
figure out if the problem is his encrypted news server or if it's in mine.

It used to work but stopped working about a week ago with this "socket
error" of "Posting article failed. Socket error # 0".

I use 40TudeDialog with stunnel on Windows but I don't know what a "socket"
is nor if it's even related to stunnel or to the news server.

Stunnel has been running for years with other news servers and for months
with this news server (which I can't say what it is as it's not known to be available for posting unless you ask the news server admin to allow it).

How do I debug on my own?
What are the typical debug steps for testing an encrypted connection?

Thinking something might have used the port, I changed the port in both
40Tude Dialog and in the stunnel.conf file, but that arbitrary port change
made no difference (127.0.0.1:12345 => 127.0.0.1:54321) in the error.

[newsserver]
client = yes
accept = 127.0.0.1:54321
connect = news.newsserver.net:563
verify = 0
verifyChain = yes
CAfile = ca-certs.pem
checkHost = news.newsserver.net
OCSPaia = yes

How do I debug this error to see at least if the problem is me or him?

What's a "posting article failed socket error # 0" in 40tude dialog anyway?

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

XPost: alt.free.newsservers, news.software.readers

Am 29.11.2023 um 06:55:38 Uhr schrieb rocco portelli:

What are the typical debug steps for testing an encrypted connection?

ncat --ssl news.example.org 563

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

XPost: alt.free.newsservers, news.software.readers

rocco portelli <roccoportelli@nospam.it> wrote in news:uk78rq$3gr0h$1@paganini.bofh.team:

Before I bother the admin of a common free news server (who I promised
if he gave me a posting account, I wouldn't be any trouble) I would
like to figure out if the problem is his encrypted news server or if
it's in mine.

It used to work but stopped working about a week ago with this "socket
error" of "Posting article failed. Socket error # 0".

A connection already open failed.

Probably your provider unless you've picked up some malware.

Snag a copy of openSSL. Grab the 64 bit version.

https://indy.fulgan.com/SSL/openssl-1.0.2t-x64_86-win64.zip

openssl-1.0.2t-x64_86-win64>openssl s_client -connect news.eternal- september.org:563
200 news.eternal-september.org InterNetNews NNRP server INN 2.8.0
(20230917 snapshot) ready (posting ok)

Check and compare your server to those below.

openssl-1.0.2t-x64_86-win64>openssl s_client -connect news.neodome.net:563 openssl-1.0.2t-x64_86-win64>openssl s_client -connect news.blueworldhosting.com:563

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