1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • Restore the BRE inter-bbs netmail attachment work-around from SBBSecho

    From Deucе@1:103/705 to GitLab note in main/sbbs on Wed Oct 22 00:52:30 2025
    https://gitlab.synchro.net/main/sbbs/-/commit/a3b2f9e2d2cf3494bf70f54f77ebdfb8fa49976b#note_7756

    So, this is actually likely not a bug...

    Per [FTS-5005](http://ftsc.org/docs/fts-5005.003), a ^ prefix requests that the mailer delete the file after it is sent. In The Clans, you can configure the mailer as "Binkley" or "Not Binkley".

    When it's Binkley, it prepends the ^ to the path, and when it's not Binkly, it adds a "FLAGS KFS" kludge line to the message.

    So while you do need to skip it to check if the file exists and potentially fix the case, it should also pass it through to the FLO file... characters that should pass through are '#', '^', '~', '-', '!', and '@', and '^'.
    --- SBBSecho 3.30-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Deuc¨ on Fri Oct 24 10:46:44 2025
    Re: Restore the BRE inter-bbs netmail attachment work-around from SBBSecho
    By: Deucе to GitLab note in main/sbbs on Wed Oct 22 2025 12:52 am

    So, this is actually likely not a bug...

    Per [FTS-5005](http://ftsc.org/docs/fts-5005.003), a ^ prefix requests that the mailer delete the file after it is sent. In The Clans, you can configure the mailer as "Binkley" or "Not Binkley".

    When it's Binkley, it prepends the ^ to the path, and when it's not Binkly, it adds a "FLAGS KFS" kludge line to the message.

    The "bug" that being referred to (and worked-around) was BRE's putting the FLO-filename-prefix in the *subject* of the netmail message. Nothing in FTS-5005 allows for that.
    --
    digital man (rob)

    Sling Blade quote #2:
    Karl (re: killing Doyle): I hit him two good whacks in the head with it.
    Norco, CA WX: 74.0°F, 57.0% humidity, 1 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.30-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)