Testing yet another connection.
--
----Android NewsGroup Reader---- https://piaohong.s3-us-west-2.amazonaws.com/usenet/index.html*I* _can_ see this.
----Android NewsGroup Reader---- https://piaohong.s3-us-west-2.amazonaws.com/usenet/index.html
*I* _can_ see this.
On 15.10.2020 9.29, Brother Rabbit wrote:If successful, Theoretically I would have 6 connections to this
The item number #5 is interesting: "5. Added 56 bugs"----Android NewsGroup Reader---- CP>https://piaohong.s3-us-west-2.amazonaws.com/usenet/index.html *I*
_can_ see this.
The item number #5 is interesting:----Android NewsGroup Reader----
https://piaohong.s3-us-west-2.amazonaws.com/usenet/index.html
"5. Added 56 bugs"
rbb.fidonet.fi is an OS2 system, which doesn't support IPv6, which, if I understand correctly, HotdogEd requires, so my connection attempts fail, causing Tommi's system a crash report.
Jamnntpd is running at rbb.fidonet.fi under OS/2, true. It does not
support IPv6. Hotdoged works just fine with IPv4-only nntp servers.
But I have noticed that for some reason my Jamnntpd/OS2 crashes in
certain situations when accessing it with Hotdoged. I haven't got
time to investigate why it happens. Anyway, the server restarts
after a shorts period after the crash.
I had a similar problem with another connection.
So I guess it's more like HotdogEd doesn't like IPv4.
Not a big deal, just one of those quirks.
I had a similar problem with another connection. So I guess it'sI use hotdoged with IPv4 and it works as expected. I have found
more like HotdogEd doesn't like IPv4. Not a big deal, just one of
those quirks.
that hotdoged works with mailers that have a CRAM-MD5 handshake
but not with mailers that don't support it, like BBBS. I'm not
certain of that, that's just what appeared to be happening.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,063 |
Nodes: | 17 (1 / 16) |
Uptime: | 15:44:06 |
Calls: | 501,324 |
Calls today: | 3 |
Files: | 109,413 |
D/L today: |
1,068 files (98M bytes) |
Messages: | 301,992 |