1. Forum
  2. DOVE-Net
  3. Synchronet Programming

  • exec/nntpservice.js

    From Rob Swindell@VERT to Git commit to main/sbbs/master on Sun Feb 28 12:15:53 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/2679c059656dded5420202fb
    Modified Files:
    exec/nntpservice.js
    Log Message:
    Remove the auto-login feature

    from Tracker1: agree -auto should probably be removed

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to Git commit to main/sbbs/master on Sun Feb 28 14:33:05 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/6616ff691e4a0994d7ae7cc1
    Modified Files:
    exec/nntpservice.js
    Log Message:
    Respond with the (RFC3977) 480 response when authentication is required

    instead of the RFC977 502. Reportedly, this will trigger Thunderbird to prompt for or send client credentials. This should fix issue #208.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Tracker1@VERT/TRN to Rob Swindell on Sun Feb 28 19:02:13 2021
    On 2/28/2021 12:15 PM, Rob Swindell wrote:
    https://gitlab.synchro.net/main/sbbs/-/commit/2679c059656dded5420202fb Modified Files:
    exec/nntpservice.js
    Log Message:
    Remove the auto-login feature

    from Tracker1: agree -auto should probably be removed


    480, not 502
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    ï¿­ Synchronet ï¿­ Roughneck BBS - roughneckbbs.com
  • From Tracker1@VERT/TRN to Rob Swindell on Sun Feb 28 19:03:46 2021
    On 2/28/2021 2:33 PM, Rob Swindell wrote:
    https://gitlab.synchro.net/main/sbbs/-/commit/6616ff691e4a0994d7ae7cc1 Modified Files:
    exec/nntpservice.js
    Log Message:
    Respond with the (RFC3977) 480 response when authentication is required

    instead of the RFC977 502. Reportedly, this will trigger Thunderbird to prompt
    for or send client credentials. This should fix issue #208.

    Thank you.
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    ï¿­ Synchronet ï¿­ Roughneck BBS - roughneckbbs.com
  • From Rob Swindell@VERT to Git commit to main/sbbs/master on Thu Feb 3 20:29:00 2022
    https://gitlab.synchro.net/main/sbbs/-/commit/879c123ec4897cfbd5b53409
    Modified Files:
    exec/nntpservice.js
    Log Message:
    Add debug log lines to help root-cause issue #334

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to Git commit to main/sbbs/master on Thu Feb 3 22:50:08 2022
    https://gitlab.synchro.net/main/sbbs/-/commit/74db6a5340f68a174472ed78
    Modified Files:
    exec/nntpservice.js
    Log Message:
    Remove extra debug for Newsgroups heades, but log the internal code of sub

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Thu Sep 12 16:53:02 2024
    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
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Thu Sep 12 16:53:02 2024
    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
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Mon Sep 16 13:57:39 2024
    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
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Sat Nov 16 13:14:52 2024
    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
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Sat Nov 16 13:22:52 2024
    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
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Sat Nov 16 14:26:20 2024
    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
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Sat Nov 16 14:26:20 2024
    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
  • From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Sat Nov 30 22:38:54 2024
    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