• NNTP server message-id field

    From Static@21:2/140 to g00r00 on Mon Feb 3 05:03:58 2020
    Any way the message-id the NNTP server sends to the client could be made
    unique server-wide?

    I've noticed an issue with some clients (eg: Thunderbird) that behave unexpectedly because they assume message-ids are globally unique (RFC822/1036)

    For example if I first view post#1 in FSX_GEN I get the proper message, which has message-id 1. But then if I go over to FSX_MYS and try to bring up the first post there I get the one from FSX_GEN again instead. Basically the
    client sees that I'm trying to view msgid 1 and just displays what it already has without even attempting to download the one from the latter area.

    It'd probably be sufficient to just add the area name to the message_id field: MSGAREA.MSGNUM
    Or more like RFC822 spec in case inter-BBS msgid collisions are also a thing: <MSGAREA.MSGNUM@BBSNAME>

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Subcarrier BBS (21:2/140)
  • From g00r00@21:1/108 to Static on Mon Feb 3 14:51:37 2020
    Or more like RFC822 spec in case inter-BBS msgid collisions are also a thing: <MSGAREA.MSGNUM@BBSNAME>

    Sure its on the TODO list to finish it but since someone is actually using the server I will make it a higher priority. Using the message number at all is not long term solution since they are not unique (packing for example can change message numbers) but I already have the format in my notes its just
    not finished.

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Static@21:2/140 to g00r00 on Mon Feb 3 16:45:26 2020
    On 03 Feb 2020, g00r00 said the following...
    Sure its on the TODO list to finish it but since someone is actually
    using the server I will make it a higher priority. Using the message number at all is not long term solution since they are not unique
    (packing for example can change message numbers) but I already have the format in my notes its just not finished.

    All right, that's good to hear. Especially that you've already got a more complete approach in mind. The news server can be handy on mobile.

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Subcarrier BBS (21:2/140)
  • From g00r00@21:1/108 to Static on Tue Feb 4 16:59:18 2020
    All right, that's good to hear. Especially that you've already got a more complete approach in mind. The news server can be handy on mobile.

    It'll be good to have someone to test it! I will take a look at this in A45
    I don't want to start it now because its too close to A44.

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Embalmed@21:4/166 to g00r00 on Sun Feb 23 19:29:38 2020
    On 04 Feb 2020, g00r00 said the following...

    All right, that's good to hear. Especially that you've already got a complete approach in mind. The news server can be handy on mobile.

    It'll be good to have someone to test it! I will take a look at this in A45 I don't want to start it now because its too close to A44.
    I started playing around with thunderbird and the NNTP server but i'm having all kinds of problems. The groups on SciNET subscribe, and then the next
    time i come into thunderbird they are orphaned and say the message area
    doesn't exist on the server. I wonder if this is because I havea : in the name of the SciNet areas so the groups are named scinet:.Sysops.only and such fsx areas kinda work, but i can't reply to anything i get a message like
    'Would you like to subscribe to 8023? if i say ok thunderbird crashes.

    I can at least read some of the bases in fsx, but a lot of them i can only
    see subject lines but not the messages. I think possibly these ones have / character in the name somewhere.
    chat works, cryptographic works,
    but fsxnet.BBS.Support/DEV no good.

    I'm guessing there are some forbidden characters for newsgroup names?

    |07E|10m|07b|10a|07l|10m|07e|10d |12-----------------------------------------------------
    |09Black Lodge Research BBS |11blacklodgeresearch.org:4022
    |11fsx|08Net: |0721:4/166 |11sci|08Net: |0777:1/133

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: Black Lodge Research BBS (21:4/166)
  • From Netsurge@21:4/154 to Embalmed on Mon Feb 24 00:42:50 2020
    message area doesn't exist on the server. I wonder if this is because I havea : in the name of the SciNet areas so the groups are named scinet:.Sysops.only and such fsx areas kinda work, but i can't reply to anything i get a message like 'Would you like to subscribe to 8023? if
    i say ok thunderbird crashes.

    Yes. Your newgroups names in mystic must not contain spaces and apart from alphanumeric characters can only contain a '.'.

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)