1. Forum
  2. FidoNet
  3. SYNC PROGRAMMING

  • src/sbbs3/postmsg.cpp

    From rswindell@1:103/705 to CVS commit on Sun Sep 1 21:54:18 2019
    src/sbbs3 postmsg.cpp 1.127 1.128
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv26458

    Modified Files:
    postmsg.cpp
    Log Message:
    Don't create the security-related header fields if the assocated "client" object/struct doesn't have any meaningful data. Prevent this from happening:
    SenderTime 19700101000000Z
    SenderIpAddr
    SenderHostName
    SenderPort 0


    --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From rswindell@1:103/705 to CVS commit on Sun Sep 1 22:42:14 2019
    src/sbbs3 postmsg.cpp 1.128 1.129
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv2344

    Modified Files:
    postmsg.cpp
    Log Message:
    Automatic UTF-8 header field detection in savemsg(): if the to, from, or subject header fields are non-ASCII yet valid UTF-8, set the auxattr flag indicating that the msg header is in UTF-8.
    This function is used by JS MsgBase.save_msg(), so any scripts/services that use it (e.g. nntpservice, newslink, imapservice, etc.) to save messages with header fields that may be UTF-8 encoded will automatically benefit from this detection. Mixing CP437 (the default) with UTF-8 encoded header fields is not supported, so if one header field is valid UTF-8 (not plain US-ASCII), then they had better all be either plain US-ASCII or UTF-8 or there will be
    UTF-8 decoding issues when attempting to display or convert later.


    --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From rswindell@1:103/705 to CVS commit on Wed Apr 22 23:25:08 2020
    src/sbbs3 postmsg.cpp 1.131 1.132
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv26315

    Modified Files:
    postmsg.cpp
    Log Message:
    Don't try to signal an empty semaphore path if the netmail_sem is blank.

    --- SBBSecho 3.10-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From rswindell@1:103/705 to CVS commit on Sun May 24 17:41:52 2020
    src/sbbs3 postmsg.cpp 1.132 1.133
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv27907

    Modified Files:
    postmsg.cpp
    Log Message:
    Include a replied-to message's to field to be selected in the post-to history (arrow-up to choose strings from history).

    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to sbbs/master on Wed Sep 30 21:25:17 2020
    https://gitlab.synchro.net/sbbs/sbbs/-/commit/97bade44ebad5b431485e93c
    Modified Files:
    src/sbbs3/postmsg.cpp
    Log Message:
    Notify local recipients of locally-posted messages addressed to them.While SBBSecho would notify local users of imported messages addressed tothem (both EchoMail and NetMail) and QWK-imported messages recently gainedthe ability to notify local recipients of messages addressed to them, othermethods of posting messages (e.g. just using the normal terminal servermethod, e.g. the 'P' command) or using any JavaScript (e.g. web) methods ofposting messages lacked recipient notifications. So that's now fixed.And for JavaScript-saved local email messages too. I don't *think* this willresult in any duplicate notifications of received messages, but let me knowif you see excess/duplicate notifications.Anonymously posted messages are excluded.Messages posted to yourself are excluded (who does that?).
    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to sbbs/master on Wed Sep 30 21:26:58 2020
    https://gitlab.synchro.net/sbbs/sbbs/-/commit/f4ac7f3920abba7d3c717e3d
    Modified Files:
    src/sbbs3/postmsg.cpp
    Log Message:
    Resolve a gcc warning about signedness.
    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to sbbs/master on Sat Oct 3 12:16:52 2020
    https://gitlab.synchro.net/sbbs/sbbs/-/commit/c8193766c6b75abb18a2c257
    Modified Files:
    src/sbbs3/postmsg.cpp
    Log Message:
    Fix savemsg() bug introduced in 97bade44eb (Sep-30), returning false failure'i' is the return value of savemg(), used to determine success or failure(and what kind of failure) - so we can't use that for the usernumber ofthe recipient.
    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to sbbs/master on Wed Nov 11 17:55:49 2020
    https://gitlab.synchro.net/sbbs/sbbs/-/commit/a852cced25cbf1285825942f
    Modified Files:
    src/sbbs3/postmsg.cpp
    Log Message:
    Reduce unnecessary posted-to username searches. Auto-UTF8 in savemsg().When posting to "All" or replying to a message that was posted by networked (not local) user, don't attempt to search for that username in the local user base to inform them of the posted message to them.savemsg() is the underlying C function for saving a new message (mail or post) to a message base from several places, including JS modules. If there was no "charset" specified in the passed message header, check to see if the message body text is non-ASCII but valid UTF-8, and if it is, set the FIDO_CHARSET header field to the appropriate UTF-8 charset identifier string. This would *also* address Issue #177 reported by Michael J. Ryan. It's possible, but unlikely, that a message text would contain valid CP437 that *also* happened to be valid UTF-8. If that does happen to occur (e.g. in posted ANSI art?), we might want to revert this enhancement to savemsg() and leave to the caller's to detect/specify the charset, always.
    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to main/sbbs/master on Thu Mar 18 21:24:40 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/54c935707ff58e948fb0df2b
    Modified Files:
    src/sbbs3/postmsg.cpp
    Log Message:
    Move the tags prompt to *before* the locking of the message baseThanks Mr. Executive Chicken esq. for the telephone call and bug report.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to main/sbbs/master on Sun Apr 4 15:13:57 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/489267ade424d4f40cf8b752
    Modified Files:
    src/sbbs3/postmsg.cpp
    Log Message:
    mod_ar is no longer a pointer, it's an arrayCID 319077
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to main/sbbs/master on Tue Apr 13 20:20:22 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/908618c85f29a300acc7a500
    Modified Files:
    src/sbbs3/postmsg.cpp
    Log Message:
    Debug the "thread_back field missing" errorSome QWKnet vote messages are failing:evnt unpackREP <ENSEMBLE> !ERROR 2 (No such file or directory) in qwk.cpp line 1146 (qwk_vote) writing "/sbbs/data/subs/dove-gen" access=-105 info=smb_addvote thread_back field missingCatch this problem a little higher up (in votemsg()) and log the message's reply-IDs to help determine what's the root-cause here. Don't bother calling smb_addvote() if thread_back is 0.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to main/sbbs/master on Mon Oct 24 15:49:30 2022
    https://gitlab.synchro.net/main/sbbs/-/commit/33a8b69cfbbd8194e3519608
    Modified Files:
    src/sbbs3/postmsg.cpp
    Log Message:
    Strip control chars/ctrl-A sequences from msg subject in notify()We may want Ctrl-A sequences in the telegram subject, but not in the messagesubject
    --- SBBSecho 3.15-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)