• src/sbbs3/msg_id.c postms

    From rswindell@VERT to CVS commit on Mon Nov 5 17:06:00 2018
    src/sbbs3 msg_id.c 1.9 1.10 postmsg.cpp 1.115 1.116 sbbsecho.c 3.97 3.98
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv31422

    Modified Files:
    msg_id.c postmsg.cpp sbbsecho.c
    Log Message:
    Don't generate FTN message-IDs for messages imported via FTN that are missing a message-ID (e.g. when exporting from SBBSecho).
    This addresses compliance with this [editorialized] clause in FTS-9:
    No system
    should ever add an MSGID and/or REPLY to, or modify an existing
    MSGID / REPLY contained in, a message not originating on that [FTN]
    system.

    Messages gated from other networks (technically coming from another system,
    but originating into an FTN from this system) will still have an FTN Message-ID generated/added.

    Since SBBSecho normally tosses to downlinks directly from packets, this adding of generated Message-IDs would no normally occur. However, if a downlink rescanned an area, any messages missing Message-IDs would get them generated automatically and they would appear to have originating on the local system. This was never the intention, so this is just a long standing but infrequently observed (and never reported) bug.


    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From rswindell@VERT to CVS commit on Sat Feb 16 14:30:00 2019
    src/sbbs3 msg_id.c 1.11 1.12 postmsg.cpp 1.118 1.119
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv2101

    Modified Files:
    msg_id.c postmsg.cpp
    Log Message:
    add_msg_ids() will now get the new/next message number if the msg.hdr.number
    is 0 (logic moved from sbbs_t::postmsg()).


    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net