• exec/load/binkp.js

    From Rob Swindell (on Debian Linux)@VERT to Git commit to main/sbbs/master on Sat Jul 5 22:17:10 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/8533474761891eeb8d75eddd
    Modified Files:
    exec/load/binkp.js
    Log Message:
    Don't log BinkP errors in the error.log

    The sysop has no control over what misconfigured remote sysop connects to his BinkP service and sends whatever, so don't log received errors as errors, filling up the sysop's error log and potentially email inbox.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to Git commit to main/sbbs/master on Wed Dec 10 15:05:01 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/ff46f601780b4e933404ebb3
    Modified Files:
    exec/load/binkp.js
    Log Message:
    Also use a timeout if we have nothing to send.

    Fixes an infinite loop where there is nothing to send because the
    remote does not have the address you are calling to deliver a message
    for.

    For example if W6RAY just joined the BBSDev FTN, and was assigned
    885:1/99, and a netmail was created welcoming the BBS to the network,
    but they didn't add the new address to the AKA list in scfg, binkit
    would sit using 100% CPU.

    Now it sets the timeout, so sits at 0% CPU for 120s then fails.

    This is still likely wrong, but at least it's wrong in a much less
    harmful way.

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net