• SBBSEcho Send Notify List - No MSGID

    From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Sep 29 18:59:18 2026
    https://gitlab.synchro.net/main/sbbs/-/work_items/1257#note_10510

    SBBSecho has added a MSGID to the NetMail it creates itself (notify lists, AreaMgr replies) since 96712a1c35 (focuses-28-lives, 2021-11-12). A notify
    list generated by the current code (`sbbsecho -G`) starts with:

    ```
    ^AINTL 1:103/13 1:103/705
    ^ATZUTC: -0700
    ^AMSGID: 1:103/705 6abc6c3c
    ^APID: SBBSecho 3.37-Linux master/~01a7630c62 Sep 29 2026 GCC 14.2.0
    Following are the options set for your system and a list of areas
    ```

    Could you tell us which SBBSecho version sent the notify list (the `PID`
    line of the message, or `sbbsecho` run with no arguments), and where you
    found the MSGID missing: in the `.msg` file in the NetMail directory, in the outbound packet, or as seen on the receiving system?

    Testing this turned up a related problem, fixed and on master shortly: the MSGID
    serial was the current time in seconds, so NetMail messages created within
    the same second shared a MSGID. That happens with a notify or area list that
    is split into several messages to the same node, and a receiving tosser that checks NetMail for duplicates by MSGID could discard the later parts. Each generated message now gets a unique serial.

    -- *Authored by Claude (Claude Code), on behalf of @rswindell*
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Sep 29 19:01:35 2026
    https://gitlab.synchro.net/main/sbbs/-/work_items/1257#note_10510

    SBBSecho has added a MSGID to the NetMail it creates itself (notify lists, AreaMgr replies) since 96712a1c35 (focuses-28-lives, 2021-11-12). A notify
    list generated by the current code (`sbbsecho -G`) starts with:

    ```
    ^AINTL 1:103/13 1:103/705
    ^ATZUTC: -0700
    ^AMSGID: 1:103/705 6abc6c3c
    ^APID: SBBSecho 3.37-Linux master/~01a7630c62 Sep 29 2026 GCC 14.2.0
    Following are the options set for your system and a list of areas
    ```

    Could you tell us which SBBSecho version sent the notify list (the `PID`
    line of the message, or `sbbsecho` run with no arguments), and where you
    found the MSGID missing: in the `.msg` file in the NetMail directory, in the outbound packet, or as seen on the receiving system?

    Testing this turned up a related problem, fixed in 6c6d3dcbf9 (hepatitis-11-takes, 2026-09-29): the MSGID
    serial was the current time in seconds, so NetMail messages created within
    the same second shared a MSGID. That happens with a notify or area list that
    is split into several messages to the same node, and a receiving tosser that checks NetMail for duplicates by MSGID could discard the later parts. Each generated message now gets a unique serial.

    -- *Authored by Claude (Claude Code), on behalf of @rswindell*
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nick Boel@1:103/705 to GitLab issue in main/sbbs on Wed Sep 30 09:10:51 2026
    close https://gitlab.synchro.net/main/sbbs/-/work_items/1257
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nick Boel@1:103/705 to GitLab note in main/sbbs on Wed Sep 30 09:10:52 2026
    https://gitlab.synchro.net/main/sbbs/-/work_items/1257#note_10534

    My bad. I didn't even think to look at what version was sending me those netmails. PID was from v3.11 in 2020, as seen on the receiving system.

    At least you found a related problem, though!
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)