https://gitlab.synchro.net/main/sbbs/-/commit/04340d911b1e7282cdb74119
Modified Files:
exec/nntpservice.js
Log Message:
Close any open message base after input timeout (5 minutes)

As Nelgin pointed out, the nntpservice can leave a message bases open while
a client is idle. Normally, an inactive client would be disconnected after 5 minutes of inactivity, so that wouldn't be much of an issue. However, if authenticated as a user with the H-exemption, no auto-disconnection after
input timeout would happen. So let's close any open message base for good measure.

The input/receive timeout probably should be configurable and lowered to
a smaller duration (one minute?). I'll leave that for another commit.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/3f0bbb17b52485874e2fba2d
Modified Files:
exec/nntpservice.js
Log Message:
Close an open message base after just 10 seconds of client inactivity

... and log a debug-level log message when doing so.

The current input/receive timeout duration (5 minutes) might be a bit long to leave a message base open (though, there's no known issue with doing so). For example, when users read message bases using the terminal server, they can sit for much longer than 5 minutes reading an open message base.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/8c6589b017d070d1cb8f4bda
Modified Files:
exec/nntpservice.js
Log Message:
Re-open closed message base for commands to use selected/open base

Should fix issue #790

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/d4692e0a5cf643b67928ec8e
Modified Files:
exec/nntpservice.js
Log Message:
Look up referenced FTN MSGID of messages being POSTed and use in FTN-REPLY

... for Acccession

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/a7f1a24a2ce7e67a87d067a8
Modified Files:
exec/nntpservice.js
Log Message:
Don't overwrite the posted-reply FTN REPLY ID if it was provided by the client

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/6b08ef0f8657d966606e72ce
Modified Files:
exec/nntpservice.js
Log Message:
Revert "Don't overwrite the posted-reply FTN REPLY ID if it was provided by the client"

This reverts commit a7f1a24a2ce7e67a87d067a89450a18108b8965d.

Not the fix we're looking for.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/ca6360b60d63f68471164682
Modified Files:
exec/nntpservice.js
Log Message:
Revert "Look up referenced FTN MSGID of messages being POSTed and use in FTN-REPLY"

This reverts commit d4692e0a5cf643b67928ec8e2cdf9b333c1ab2d0.

Not the fix we're looking for.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/5fc54d290be58774dc7a597c
Modified Files:
exec/nntpservice.js
Log Message:
More RFC (3977) conformance

Some of the NNTP commands (e.g. LIST) aren't supposed to change the "currently selected newsgroup". Had to use a different variable name (e.g. mb versus msgbase) since these message base variables share the function scope).

GROUP and LISTGROUP commands are supposed to set the "current article number" to the first article in the group. We weren't doing this.

The HEAD, BODY, STAT, and ARTICLE commands aren't *required* to have arguments and yet, we required they had at least one argument (an article number). Now fixed.

Enabled "strict mode" even though that didn't catch the colliding 'msgbase' variable definitions.

Incremented the revision to 1.2

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net