To: Digital Man
Hey DM,

So I noticed it being quiet in Dovenet for a few days, so I checked my logs and discovered mail was not flowing to me.

I noticed this in the log:
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET No new messages.
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET Call-out: VERT
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qwk already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw0 already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw1 already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw2 already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw3 already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw4 already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw5 already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw6 already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw7 already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw8 already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw9 already exists
Jan 22 09:23:56 d-11-1 synchronet: evnt QNET Call-out to: VERT returned 1

And sure enough...

deon@d-11-1:/srv/docker/sbbs/data$ ls -al VERT.qw?
-rw------- 1 root root 0 Jun 28 2022 VERT.qw0
-rw------- 1 root root 0 Jan 15 07:13 VERT.qw1
-rw------- 1 root root 0 Jan 15 09:26 VERT.qw2
-rw------- 1 root root 0 Jan 17 16:41 VERT.qw3
-rw------- 1 root root 0 Jan 18 05:53 VERT.qw4
-rw------- 1 root root 0 Jan 18 09:03 VERT.qw5
-rw------- 1 root root 0 Jan 18 11:16 VERT.qw6
-rw------- 1 root root 0 Jan 18 13:30 VERT.qw7
-rw------- 1 root root 0 Jan 18 19:43 VERT.qw8
-rw------- 1 root root 0 Jan 18 21:56 VERT.qw9
-rw------- 1 root root 0 Apr 1 2022 VERT.qwk

After I deleted those, I got mail again :)

So that I understand, there can only be 10 qwk files in flight? And once all 10 are used, no more mail flows until there is a spare slot?

Not sure why I had zero sized files laying around - perhaps it would be good to detect those and delete them automatigically?

I went through my Jan 18 log to see if I could see why VERT.qw4 was left as a zero size file, and there was no errors that I could see.

Jan 18 04:53:39 d-11-1 synchronet: evnt QNET Downloading QWK Packet: VERT.qwk
Jan 18 04:53:52 d-11-1 synchronet: evnt QNET Downloaded VERT.qw4 (2.0KB) successfully
....
Jan 18 04:53:58 d-11-1 synchronet: evnt QNET Finished Importing QWK Network Packet from VERT: (2 msgs) in 1 seconds (2 msgs/sec), 0 errors
, 0 dupes

(The 1hr difference in the log and the file timestamp will be because of summer time).

Any other reason why they were left around?

....δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI
--- Synchronet 3.20a-Linux NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

To: deon
Re: No DOVENET for a few days...
By: deon to Digital Man on Sun Jan 22 2023 09:45 am

> Hey DM,
>
> So I noticed it being quiet in Dovenet for a few days, so I checked my logs
> and discovered mail was not flowing to me.
>
> I noticed this in the log:
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET No new messages.
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET Call-out: VERT
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qwk already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw0 already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw1 already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw2 already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw3 already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw4 already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw5 already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw6 already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw7 already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw8 already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET /opt/sbbs/data/VERT.qw9 already
> exists
> Jan 22 09:23:56 d-11-1 synchronet: evnt QNET Call-out to: VERT returned 1
>
> And sure enough...
>
> deon@d-11-1:/srv/docker/sbbs/data$ ls -al VERT.qw?
> -rw------- 1 root root 0 Jun 28 2022 VERT.qw0
> -rw------- 1 root root 0 Jan 15 07:13 VERT.qw1
> -rw------- 1 root root 0 Jan 15 09:26 VERT.qw2
> -rw------- 1 root root 0 Jan 17 16:41 VERT.qw3
> -rw------- 1 root root 0 Jan 18 05:53 VERT.qw4
> -rw------- 1 root root 0 Jan 18 09:03 VERT.qw5
> -rw------- 1 root root 0 Jan 18 11:16 VERT.qw6
> -rw------- 1 root root 0 Jan 18 13:30 VERT.qw7
> -rw------- 1 root root 0 Jan 18 19:43 VERT.qw8
> -rw------- 1 root root 0 Jan 18 21:56 VERT.qw9
> -rw------- 1 root root 0 Apr 1 2022 VERT.qwk
>
> After I deleted those, I got mail again :)
>
> So that I understand, there can only be 10 qwk files in flight? And once all
> 10 are used, no more mail flows until there is a spare slot?

That's the way qnet-ftp.js would work, yeah. It assumed that sbbs would import those QW* files, but SBBS just ignores 0-byte QW* files, so I see how that would be a problem.

> Not sure why I had zero sized files laying around - perhaps it would be good
> to detect those and delete them automatigically?

I just committed a change to qnet-ftp.js so it'll overwrite QW* files if they're 0-byte files.

> I went through my Jan 18 log to see if I could see why VERT.qw4 was left as
> a zero size file, and there was no errors that I could see.
>
> Jan 18 04:53:39 d-11-1 synchronet: evnt QNET Downloading QWK Packet:
> VERT.qwk Jan 18 04:53:52 d-11-1 synchronet: evnt QNET Downloaded VERT.qw4
> (2.0KB) successfully
> ...
> Jan 18 04:53:58 d-11-1 synchronet: evnt QNET Finished Importing QWK Network
> Packet from VERT: (2 msgs) in 1 seconds (2 msgs/sec), 0 errors
> , 0 dupes
>
> (The 1hr difference in the log and the file timestamp will be because of
> summer time).
>
> Any other reason why they were left around?

Not sure. Perhaps just timeouts (due to issues on the server side) while downloading. Likely there's another issue lingering as to why those 0 byte packets were left around in the first place.
--
digital man (rob)

Synchronet/BBS Terminology Definition #91:
UTF-8 = 8-bit Unicode Transformation Format
Norco, CA WX: 63.7°F, 27.0% humidity, 0 mph ESE wind, 0.00 inches rain/24hrs
--- Synchronet 3.20a-Linux NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

To: Digital Man
Re: No DOVENET for a few days...
By: Digital Man to deon on Sat Jan 21 2023 04:30 pm

Howdy,

> > Any other reason why they were left around?
>
> Not sure. Perhaps just timeouts (due to issues on the server side) while
> downloading. Likely there's another issue lingering as to why those 0 byte
> packets were left around in the first place.

So I suspect it's NAT64, given that you are on IPv6, and FTP. I havent done enough research to confirm it.

So I thought I'd try and get QWK packets via http and changed qnet-ftp to qnet-http.

It seems that's not working?

Jan 22 13:34:18 d-11-1 synchronet: evnt QNET Call-out: VERT
Jan 22 13:34:18 d-11-1 synchronet: evnt QNET QNET-HTTP 1.3 invoked with options: VERT dove.synchro.net xxxxx
Jan 22 13:34:19 d-11-1 synchronet: evnt QNET Getting /opt/sbbs/data/VERT.qwk
Jan 22 13:34:19 d-11-1 synchronet: evnt QNET GET /qwk.ssjs HTTP/1.0 Response: HTTP/1.1 404 Not Found
Jan 22 13:34:19 d-11-1 synchronet: evnt QNET Call-out to: VERT returned 1

I'm guessing that is your side? It should work right?

....δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI
--- Synchronet 3.20a-Linux NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

To: deon
Re: No DOVENET for a few days...
By: deon to Digital Man on Sun Jan 22 2023 01:38 pm

> Re: No DOVENET for a few days...
> By: Digital Man to deon on Sat Jan 21 2023 04:30 pm
>
> Howdy,
>
> > > Any other reason why they were left around?
>
> > Not sure. Perhaps just timeouts (due to issues on the server side) while downloading. Likely there's another issue lingering
> > as
> > to why those 0 byte packets were left around in the first place.
>
> So I suspect it's NAT64, given that you are on IPv6, and FTP. I havent done enough research to confirm it.

I don't have an Internet IPv6 address.

> So I thought I'd try and get QWK packets via http and changed qnet-ftp to qnet-http.
>
> It seems that's not working?

Correct, qnet-http is not supported today. Perhaps in the future.

> Jan 22 13:34:18 d-11-1 synchronet: evnt QNET Call-out: VERT
> Jan 22 13:34:18 d-11-1 synchronet: evnt QNET QNET-HTTP 1.3 invoked with options: VERT dove.synchro.net xxxxx
> Jan 22 13:34:19 d-11-1 synchronet: evnt QNET Getting /opt/sbbs/data/VERT.qwk Jan 22 13:34:19 d-11-1 synchronet: evnt QNET GET
> /qwk.ssjs HTTP/1.0 Response: HTTP/1.1 404 Not Found
> Jan 22 13:34:19 d-11-1 synchronet: evnt QNET Call-out to: VERT returned 1
>
> I'm guessing that is your side? It should work right?

No, it's purposely disabled on Vert.
--
digital man (rob)

Breaking Bad quote #31:
Feels like one of those cones put on dogs so they don't lick their own balls.
Norco, CA WX: 53.2°F, 45.0% humidity, 0 mph WSW wind, 0.00 inches rain/24hrs
--- Synchronet 3.20a-Linux NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

To: Digital Man
Re: No DOVENET for a few days...
By: Digital Man to deon on Sat Jan 21 2023 07:14 pm

> Correct, qnet-http is not supported today. Perhaps in the future.
>
> No, it's purposely disabled on Vert.

How come?

....δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI
--- Synchronet 3.20a-Linux NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

To: deon
Re: No DOVENET for a few days...
By: deon to Digital Man on Sun Jan 22 2023 04:09 pm

> Re: No DOVENET for a few days...
> By: Digital Man to deon on Sat Jan 21 2023 07:14 pm
>
> > Correct, qnet-http is not supported today. Perhaps in the future.
>
> > No, it's purposely disabled on Vert.
>
> How come?

Because it has known issues. If/when those issues are fixed, I'll re-enable that service.
--
digital man (rob)

Synchronet "Real Fact" #58:
The last version of Synchronet to run on MS-DOS and OS/2 was v2.30c (1999)
Norco, CA WX: 50.4°F, 51.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs
--- Synchronet 3.20a-Linux NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

To: Digital Man
Re: No DOVENET for a few days...
By: Digital Man to deon on Sat Jan 21 2023 09:50 pm

> Because it has known issues. If/when those issues are fixed, I'll re-enable
> that service.

Where are those known issues documented? If I get some free time, I'll happily have a look and see if I can fix them...

....δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI
--- Synchronet 3.20a-Linux NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

To: deon
Re: No DOVENET for a few days...
By: deon to Digital Man on Sun Jan 22 2023 08:47 pm

> Re: No DOVENET for a few days...
> By: Digital Man to deon on Sat Jan 21 2023 09:50 pm
>
> > Because it has known issues. If/when those issues are fixed, I'll
> > re-enable that service.
>
> Where are those known issues documented? If I get some free time, I'll
> happily have a look and see if I can fix them...

Here's an issue ticket that was created: https://gitlab.synchro.net/main/sbbs/-/issues/310

It's not clear if the cause of issues are in the client (qnet-http.js), the server (qwk.ssjs), or both.

You'd need to run both the client and server to debug and fix the issues.
--
digital man (rob)

Breaking Bad quote #46:
If I ever get anal polyps, at least I know what to name them. - Saul Goodman
Norco, CA WX: 53.3°F, 50.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- Synchronet 3.20a-Linux NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net