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

  • SBBS MSGID

    From Chad Adams@1:19/40 to ALL on Thu Mar 2 11:15:37 2023
    MSGID: 1:19/40 2DCB0C0B
    PID: CyberBBS v1.0.10
    Hi,

    I just had a question about the MSGID used by Synchronet. Can you explain how sbbs creates the MSGID kludge?

    Thanks!

    -Nugax (cbbs)


    --- CyberBBS v1.0.10 2023/03/02 [Debian Linux/x64/x86_64]
    * Origin: CyberBBS WHQ BBS | http://www.cyberbbs.com (1:19/40)
  • From Digital Man to Chad Adams on Thu Mar 2 10:07:06 2023
    Re: SBBS MSGID
    By: Chad Adams to ALL on Thu Mar 02 2023 11:15 am

    MSGID: 1:19/40 2DCB0C0B
    PID: CyberBBS v1.0.10
    Hi,

    I just had a question about the MSGID used by Synchronet. Can you explain how sbbs creates the MSGID kludge?

    https://wiki.synchro.net/faq:misc#ftn_msgid
    --
    digital man (rob)

    Rush quote #42:
    Media messiahs preying on my fears, pop culture prophets playing in my ears Norco, CA WX: 49.1°F, 58.0% humidity, 1 mph E wind, 0.03 inches rain/24hrs
  • From Chad Adams@1:19/40 to Digital Man on Thu Mar 2 12:26:54 2023
    MSGID: 1:19/40 182A4278
    PID: CyberBBS v1.0.10
    Thank you! I agree with your article and was actually wondering how
    the MSGID 8 Char serial could even be assured to be unique with all of
    the echomail floating around.

    -Nugax (cbbs)


    --- CyberBBS v1.0.10 2023/03/02 [Debian Linux/x64/x86_64]
    * Origin: CyberBBS WHQ BBS | http://www.cyberbbs.com (1:19/40)
  • From Digital Man to Chad Adams on Thu Mar 2 11:07:04 2023
    Re: Re: SBBS MSGID
    By: Chad Adams to Digital Man on Thu Mar 02 2023 12:26 pm

    MSGID: 1:19/40 182A4278
    PID: CyberBBS v1.0.10
    Thank you! I agree with your article and was actually wondering how
    the MSGID 8 Char serial could even be assured to be unique with all of
    the echomail floating around.

    Well it's even more limited than "8 Char": it's 8 *hexadecimal* chars. FTS-9 is just a pretty bad idea, especially considering that RFC 822 had a much better/vetted Message-ID solution, was publicly availble for anyone to read/use, and existed 9 years before FTS-9 was published.
    --
    digital man (rob)

    Sling Blade quote #12:
    Karl (re hammer): I don't rightly know. I just kinda woke up holding it.
    Norco, CA WX: 54.3°F, 47.0% humidity, 2 mph ESE wind, 0.03 inches rain/24hrs
  • From Chad Adams@1:19/40 to Digital Man on Thu Mar 2 13:19:40 2023
    MSGID: 1:19/40 31718125
    PID: CyberBBS v1.0.10
    That's true. I wrote a routine that parsed your msgid before I knew what
    it was composed of. But, now that I know how you create it, I plan
    on also creating my MSGIDs a very similar way.

    Something like:

    msg_num.conf_identifier@node

    -Nugax (cbbs)


    --- CyberBBS v1.0.10 2023/03/02 [Debian Linux/x64/x86_64]
    * Origin: CyberBBS WHQ BBS | http://www.cyberbbs.com (1:19/40)
  • From Chad Adams@1:19/40 to Digital Man on Thu Mar 2 13:41:05 2023
    MSGID: 1:19/40 0FFE4D11
    PID: CyberBBS v1.0.10
    Do you write the REPLY kludge the same was as the BBS ID or the traditional way as onlined in FTSC?

    -Nugax (cbbs)


    --- CyberBBS v1.0.10 2023/03/02 [Debian Linux/x64/x86_64]
    * Origin: CyberBBS WHQ BBS | http://www.cyberbbs.com (1:19/40)
  • From Digital Man to Chad Adams on Thu Mar 2 11:53:00 2023
    Re: Re: Re: SBBS MSGID
    By: Chad Adams to Digital Man on Thu Mar 02 2023 01:19 pm

    MSGID: 1:19/40 31718125
    PID: CyberBBS v1.0.10

    Are you intentionaly sending those Kludge lines ^^^ without the proper Ctrl-A prefix?

    That's true. I wrote a routine that parsed your msgid before I knew what
    it was composed of.

    Message-IDs shouldn't be parsed. They should be stored or hashed as an opaque string of characters for message threading/reply-linking and dupe-detection, that's it.

    But, now that I know how you create it, I plan
    on also creating my MSGIDs a very similar way.

    Okay, but you shouldn't be parsing MSGIDs.
    --
    digital man (rob)

    Rush quote #3:
    The men who hold high places must be the ones who start... Closer to the Heart Norco, CA WX: 56.2°F, 47.0% humidity, 5 mph S wind, 0.02 inches rain/24hrs
  • From Digital Man to Chad Adams on Thu Mar 2 11:55:53 2023
    Re: Re: Re: SBBS MSGID
    By: Chad Adams to Digital Man on Thu Mar 02 2023 01:41 pm

    MSGID: 1:19/40 0FFE4D11
    PID: CyberBBS v1.0.10
    Do you write the REPLY kludge the same was as the BBS ID or the traditional way as onlined in FTSC?

    I'm not sure what you're asking. A REPLY kludge is just a copy of the original message's MSGID, as specified in FTS-9.
    --
    digital man (rob)

    Rush quote #57:
    He picks up scraps of information, he's adept at adaptation .. Digital Man Norco, CA WX: 56.2°F, 47.0% humidity, 5 mph S wind, 0.02 inches rain/24hrs
  • From Chad Adams@1:19/40 to Digital Man on Thu Mar 2 13:56:27 2023
    MSGID: 1:19/40 1C438055
    PID: CyberBBS v1.0.10
    Yea, I somehow removed the chr(1) character to the kludge. My next build will x that. I should clarify, I parsed msgid to obtain the node the msg came
    from. Thats more for my own display in the bbs. Still a work in progress.

    -Nugax (cbbs)


    --- CyberBBS v1.0.10 2023/03/02 [Debian Linux/x64/x86_64]
    * Origin: CyberBBS WHQ BBS | http://www.cyberbbs.com (1:19/40)
  • From Digital Man to Chad Adams on Thu Mar 2 12:04:51 2023
    Re: Re: Re: Re: SBBS MSGID
    By: Chad Adams to Digital Man on Thu Mar 02 2023 01:56 pm

    MSGID: 1:19/40 1C438055
    PID: CyberBBS v1.0.10
    Yea, I somehow removed the chr(1) character to the kludge. My next build will x that. I should clarify, I parsed msgid to obtain the node the msg came
    from. Thats more for my own display in the bbs. Still a work in progress.

    That correct place to obtain the node the msg came from is the origin line, not the MSGID.
    --
    digital man (rob)

    Rush quote #25:
    Throw off those chains of reason and your prison disappears
    Norco, CA WX: 56.2°F, 40.0% humidity, 2 mph E wind, 0.02 inches rain/24hrs
  • From Chad Adams@1:19/40 to Digital Man on Thu Mar 2 14:00:09 2023
    MSGID: 1:19/40 03B6CE4E
    PID: CyberBBS v1.0.10
    Got it. Thanks.

    -Nugax (cbbs)


    --- CyberBBS v1.0.10 2023/03/02 [Debian Linux/x64/x86_64]
    * Origin: CyberBBS WHQ BBS | http://www.cyberbbs.com (1:19/40)
  • From Chad Adams@1:19/40 to Digital Man on Thu Mar 2 14:14:22 2023
    MSGID: 1:19/40 1B3F941A
    PID: CyberBBS v1.0.10
    Wait, I am obtaining that from the origin line. I used to obtain from msgid
    but I chatted with you and you told me that previously. Sorry!
    Its running together!

    -Nugax (cbbs)


    --- CyberBBS v1.0.10 2023/03/02 [Debian Linux/x64/x86_64]
    * Origin: CyberBBS WHQ BBS | http://www.cyberbbs.com (1:19/40)
  • From Wilfred van Velzen@2:280/464 to Chad Adams on Thu Mar 2 21:43:28 2023
    Hi Chad,

    On 2023-03-02 12:26:54, you wrote to Digital Man:

    Thank you! I agree with your article and was actually wondering how
    the MSGID 8 Char serial could even be assured to be unique with all of
    the echomail floating around.

    To be precise: The combination of the 8 char serialno _plus_ the origaddr need to be unique! So since the originating system is in control of generating it, uniqueness can be assured!

    Bye, Wilfred.

    --- FMail-lnx64 2.2.0.0
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Chad Adams on Thu Mar 2 21:51:50 2023
    Hi Chad,

    On 2023-03-02 13:19:40, you wrote to Digital Man:

    That's true. I wrote a routine that parsed your msgid before I knew
    what it was composed of. But, now that I know how you create it, I
    plan on also creating my MSGIDs a very similar way.

    Something like:

    msg_num.conf_identifier@node

    That is a bad idea, please stick to the standard!


    Bye, Wilfred.

    --- FMail-lnx64 2.2.0.0
    * Origin: FMail development HQ (2:280/464)
  • From Digital Man to Wilfred van Velzen on Thu Mar 2 13:31:33 2023
    Re: Re: SBBS MSGID
    By: Wilfred van Velzen to Chad Adams on Thu Mar 02 2023 09:43 pm

    Hi Chad,

    On 2023-03-02 12:26:54, you wrote to Digital Man:

    Thank you! I agree with your article and was actually wondering how
    the MSGID 8 Char serial could even be assured to be unique with all of the echomail floating around.

    To be precise: The combination of the 8 char serialno _plus_ the origaddr need to be unique! So since the originating system is in control of generating it, uniqueness can be assured!

    That's how the spec *should* have been written, but alas, it was not:

    "The serial number may be any eight
    character hexadecimal number, as long as it is unique - no two
    messages from a given system may have the same serial number
    within a three years." FTS-9
    --
    digital man (rob)

    Breaking Bad quote #48:
    I am not in danger, Skyler. I am the danger. - Walter White
    Norco, CA WX: 59.3°F, 41.0% humidity, 1 mph SE wind, 0.02 inches rain/24hrs