• Changes in A39 - NNTP

    From Nugax@21:1/107 to All on Saturday, June 02, 2018 18:11:41
    There had to be some change to the NNTP server. I ahve a nttp client that did work, now when sending a message I get this error:

    + 2018.06.02 18:09:21 NNTP 1-S: 500 Unknown command
    + 2018.06.02 18:09:21 NNTP 1-Error 0: NNTP server exception


    Can you assist?



    -Nugax

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)
  • From Avon@21:1/101 to Nugax on Sunday, June 03, 2018 11:25:37
    On 06/02/18, Nugax pondered and said...

    There had to be some change to the NNTP server. I ahve a nttp client
    that did work, now when sending a message I get this error:

    + 2018.06.02 18:09:21 NNTP 1-S: 500 Unknown command
    + 2018.06.02 18:09:21 NNTP 1-Error 0: NNTP server exception

    A quick look at A39 whatsnew.txt reveals no new changes as far as I can tell.

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Nugax@21:1/107 to All on Saturday, June 02, 2018 18:55:56
    Well something seems broke - and all I did is upgrade the executables.

    On 06:25 03/06 , Avon wrote:
    On 06/02/18, Nugax pondered and said...

    There had to be some change to the NNTP server. I ahve a nttp client
    that did work, now when sending a message I get this error:

    + 2018.06.02 18:09:21 NNTP 1-S: 500 Unknown command
    + 2018.06.02 18:09:21 NNTP 1-Error 0: NNTP server exception

    A quick look at A39 whatsnew.txt reveals no new changes as far as I can tell.

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)


    --
    yrNews Usenet Reader for iOS
    http://appstore.com/yrNewsUsenetReader

    --- Mystic BBS/NNTP v1.12 A39 2018/04/21 (Linux/64)
    * Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)
  • From Nugax@21:1/107 to All on Sunday, June 03, 2018 09:36:01
    So, testing the NNTP with my client,

    Here’s the findings:

    - It worked no issues in A38

    - sometimes it works sometimes it gives the error I posted.

    - you have to try multiple times to pull the message sometimes.

    On 13:55 02/06 , Nugax wrote:
    Well something seems broke - and all I did is upgrade the executables.

    On 06:25 03/06 , Avon wrote:
    On 06/02/18, Nugax pondered and said...

    There had to be some change to the NNTP server. I ahve a nttp client
    that did work, now when sending a message I get this error:

    + 2018.06.02 18:09:21 NNTP 1-S: 500 Unknown command
    + 2018.06.02 18:09:21 NNTP 1-Error 0: NNTP server exception

    A quick look at A39 whatsnew.txt reveals no new changes as far as I can tell. >>
    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)


    --
    yrNews Usenet Reader for iOS
    http://appstore.com/yrNewsUsenetReader

    --- Mystic BBS/NNTP v1.12 A39 2018/04/21 (Linux/64)
    * Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)


    --
    yrNews Usenet Reader for iOS
    http://appstore.com/yrNewsUsenetReader

    --- Mystic BBS/NNTP v1.12 A39 2018/04/21 (Linux/64)
    * Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)