https://gitlab.synchro.net/main/sbbs/-/commit/c12c17399ec907f129a8417e
Modified Files:
exec/nntpservice.js
Log Message:
Use SMTP-routable Fido/QWK netmail addresses is From header fields

Use the Synchronet-supported FTN/QWKnet routable addressing in the from fields of messages posted via those network types. Using the mailutil.js fidoaddr_to_emailaddr() function that was apparently created for listserver.js but then made unnecessary (and thus unused for several years).

I think this addresses the concerns from issue #487. Reading a message via
NTTP (using the Synchronet NNTP service) in Thunderbird, one can now reply
to sender via email and it "just works" so long as the sysop has configured
the network support for those net-types correctly and Thunderbird is
configured with the Synchronet mail server as its SMTP server to use for that newsgroup folder. Whether the Synchronet mail server is configured to use direct delivery or relay is not relevant (though mentioned in the issue description).

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

https://gitlab.synchro.net/main/sbbs/-/commit/33cbf636365f3ed63d391d63
Modified Files:
exec/nntpservice.js
Log Message:
Check the DELETE attribute before the MODERATED/VALIDATED attributes

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

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/a67545b66e6d3e61ea35cf70
Modified Files:
exec/nntpservice.js
Log Message:
Fix issue with being able to read mail base as a newsgroup

... when using the -mail option, which probably no sysop is.

Just needed to set the 'can_read' property.

As reported via IRC by Accession

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

https://gitlab.synchro.net/main/sbbs/-/commit/3940ae18d33878a569d0587c
Modified Files:
exec/nntpservice.js
Log Message:
Add support for -utf8 option

To force conversion of non-ASCII message body text, assumed to CP437,
to UTF-8 encoded equivalent.

Use of the -ascii option or when exporting sub-boards that are configured (in SCFG)
to export ASCII only, defeats this option.

Fix for issue #917.

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

https://gitlab.synchro.net/main/sbbs/-/commit/19557fbbc0210ea91d4b52a0
Modified Files:
exec/nntpservice.js
Log Message:
The -mail option now allows user (non-Guest) access to their email

in the "mail" group, rather than sysop acccess to *all* email.

If any sysop actually wants the "all email" feature, that can be re-added
easy enough.

I *think* this is what Accession was asking for?

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

https://gitlab.synchro.net/main/sbbs/-/commit/583789f0df745abc7a1e8f04
Modified Files:
exec/nntpservice.js
Log Message:
Include sent mail messages in "mail" newsgroup too

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