Synchronet now requires the libarchive development package (e.g. libarchive-dev on Debian-based Linux distros, for more info) to build successfully.

  1. 10 May, 2021 1 commit
  2. 19 Mar, 2021 1 commit
  3. 19 Feb, 2021 1 commit
    • Rob Swindell's avatar
      Automatically route in-transit mail to points to boss nodes · 45ced2a3
      Rob Swindell authored
      If the destination point node is not a linked node (does not exist in sbbsecho.ini), but the boss node is linked, automatically route to the boss node. The log entries look like this when this happens:
      "Routing packet (%s) to boss-node %s"
      "Routing NetMail (%s) to boss-node %s"
      For poindexter FORTRAN (REALITY) - test results appreciated.
      Incremented SBBSecho version to 3.13.
  4. 25 Dec, 2020 1 commit
  5. 23 Nov, 2020 1 commit
    • Rob Swindell's avatar
      The great C function dependency refactor of 2020 · c6808b3f
      Rob Swindell authored
      The goal of this commit is that: only modules that either are part-of sbbs.dll/ or need to link with/use that library, will #include "sbbs.h" and thus be dependent on its subsequent includes (e.g. cryptlib.h, jsapi.h). This should mean can be trimmed way down.
      I also removed CVS keyword/comments and trimmed up the boilerplate copyright notice in modified and added source/header files in this commit.
      There is no functional change in behavior in this comment.
  6. 16 Aug, 2020 1 commit
  7. 12 Jun, 2020 1 commit
  8. 27 Apr, 2020 1 commit
    • rswindell's avatar
      Don't export SMB->.msg NetMail messages that have the "in-transit" attribute · 446ab0ef
      rswindell authored
      flag set.
      Allow robot configurations in to include attribute values to
      add (or-into) the message header, thus allowing for robot-netmail messages
      that remain in SMB and are handled by robots (e.g. tickfix.js). Without
      the in-transit attribute flag set, the messages will be subsequently
      exported out to netmail/*.msg files for potential processing by other
      FTN utils.
  9. 26 Apr, 2020 1 commit
    • rswindell's avatar
      Add support for "robots": Right now, robots are for receiving netmail messages · 8df3c6b7
      rswindell authored
      only (e.g. areamgr requests or whatever). In the future, they could be extended
      to echomail areas too, if that's desirable.
      For now, it's really intended for ticket-FileFix.
      Anyway, NetMail can be received for the robot-name@<your-ftn-address> and
      the mail message will be stored in the Synchronet "mail" base. The recipient
      extension will be absent since there is no valid user account associated with
      the robot. Robot names supercede other user names/aliases for received netmail.
      If one or more netmail messages were imported for a robot and that robot has
      a semaphore path/filename specified (e.g. to trigger a timed event), then that
      semaphore will be "touched" before SBBSecho exits.
      One weird anomly with this is if attached files are received for robots, those
      files will be stored in data/user/ The altnerative is to just ignore
      file attachments sent to robots.
      The echofg supprot for robots is still yet to be added. In the mean time, you
      can add robots to your sbbsecho.ini like so:
      Incremented version to 3.11.
  10. 03 Apr, 2020 2 commits
  11. 13 Dec, 2019 1 commit
  12. 17 Sep, 2019 1 commit
    • rswindell's avatar
      Added support for auto-detection of incoming UTF-8 messages (default: enabled). · 6942ba6b
      rswindell authored
      If an incoming message contains no CHRS/CHARSET control line *and* the message
      text contains valid UTF-8 character encodings, set the FTN charset value to
      UTF-8 so the message will be displayed/handled accordingly.
      I did not add checks for header fields (to/from/subject) - we should probably
      auto-detect UTF-8 in those as well, but for now, I don't see messages coming
      into FidoNet echoes with UTF-8 in the header fields.
      Incremented SBBSecho/EchoCfg version to 3.10.
  13. 22 Aug, 2019 1 commit
    • rswindell's avatar
      SBBSecho should be able to run withOUT an area file (areas.bbs file). · 5fd5ae24
      rswindell authored
      This requires that the AutoAddSubs=true in sbbsecho.ini (the default) and if
      you don't want an area file created/updated with new subs, just set new option
      Both of these options default to true which is the same as the previous
      behavior: if you have a link that configured to hub for a msg group, any subs
      not already in the area list/file will be considered new and added dynamically.
      So what's new here is that you can set SBBSecho not to create or update an
      area file and SBBSecho will run just fine if no area file exists or contains no
      area definitions.
      Incremented version to 3.09.
  14. 25 Jul, 2019 1 commit
  15. 23 Jul, 2019 1 commit
    • rswindell's avatar
      New option for SBBSecho to basically ignore any configured outboxes for · 55a2e1e4
      rswindell authored
      linked nodes: UseOutboxes (default: true)
      BinkIT will continue to outboxes even when this option is set to false, but
      SBBSecho won't place any mail files in the outboxes when this option is set to
      For PSI-Jack who was surprised that SBBSecho put mail files into outboxes.
      Since it appears BinkD supports both outboxes and normal outbound directories
      for linked nodes and BinkIT does as well, this shouldn't really make any
      difference - just a sysop preference.
  16. 22 Jul, 2019 1 commit
  17. 17 Jun, 2019 2 commits
  18. 27 May, 2019 1 commit
  19. 30 Apr, 2019 1 commit
  20. 19 Mar, 2019 1 commit
    • rswindell's avatar
      Export/import the original message editor column width (when known) as a new · 3a1923d8
      rswindell authored
      FidoNet "Kludge line" (control line): "\1COLS: <columns>\r" where <columns>
      is a value between 0 and 255 and a value of 0 is special, meaning "unknown"
      and not normally specified (this is the default assumption when there is no
      "columns"/COLS header field). When a message editor column width is unknown,
      is is normally assumed to have been 80 columns for word-wrapping/re-wrapping
      purposes when displaying the message text.
      This feature has worked well for Synchronet's QWK networking (i.e. there are
      far fewer instances of word-wrapping/re-wrapping issues when viewing messages
      on DOVE-Net), so I decided to support this message header field over FTN
      (SBBSecho) as well. Hopefully other FidoNet software authors will notice and
      support this header field in the future as there are still numerous examples
      of word-wrap issues when viewing FidoNet messages. At least Synchronet <->
      Synchronet systems over FidoNet should be able to re-wrap and display all
      message text nicely when both ends support this kludge line.
      Incremented SBBSecho version number to 3.07.
  21. 08 Sep, 2018 1 commit
    • rswindell's avatar
      Added the BinkP/BinkIT "PlainAuthOnly" toggle setting/option. It's a bit · dd66956f
      rswindell authored
      confusing with 3 bool settings (in the sbbsecho.ini) to represent 4 valid
      security requirement levels, so I attempted to simply the menu options to
      make it easy for sysops.
      BinkpAllowPlainText now defaults to true since the supported encryption method
      isn't even an official FidoNet standard, yet.
      I also added/updated some online help (F1) help text.
      Added an "Exiting" popup (like SCFG) when exiting.
  22. 07 Aug, 2018 1 commit
    • rswindell's avatar
      Incremented version to 3.06 · 9eaf77be
      rswindell authored
      Added version for Bill McGarrity: for each linked-node, a preferred
      local address (AKA) can be specified to be used as the source address
      when creating packets destined for that linked-node. If no local address
      is specified, the previous (best match) logic is used: find an AKA that
      has the same zone and net as the destination address, if none found, use
      the first address with the same zone.
  23. 19 Jul, 2018 1 commit
    • rswindell's avatar
      Added a "MinFreeDiskSpace" setting to the root section of sbbsecho.ini · bad50ed8
      rswindell authored
      (defaults to 10 megabytes, "10M").
      When SBBSecho starts up, if this minimum amount of free space is not
      available in any of the following directories, SBBSecho will display an
      error and immediately exit:
      - data directory (in SCFG)
      - logs directory (in SCFG)
      - netmail directory (in SCFG)
      - outbound directory (from sbbsecho.ini)
      - temp directory
      - each linked-node's outbox, if configured
      If the sysop runs out of disk space for some reason, at least SBBSecho
      won't contribute to the problem.
  24. 04 Jun, 2018 1 commit
  25. 31 Mar, 2018 1 commit
    • rswindell's avatar
      SBBSecho/EchoCfg v3.04 - uses the newly merged sbbsecho/binkit/ftn_domains.ini · 3bdfbd61
      rswindell authored
      If you're not using BinkIT (you're using some other FidoNet mailer), you can
      safely ignore all the settings/options.
      A lot of the online help for the new settings/menus needs to be written
      still and the wiki now needs a lot of update to reflect the changes.
      The "title" of this program was changed, again, from "SBBSecho Config" to
      "[Synchronet] FidoNet Config" since it configures more than just SBBSecho
  26. 24 Nov, 2017 1 commit
    • rswindell's avatar
      EchoCfg -> Linked Nodes: · 308fa038
      rswindell authored
      - Expose the node's "name" property to be edited
      - Expose the node's "areafix support" property to be toggled
      - Renamed "AreaFix Keys" to "EchoList" keys (these are keys to EchoLists)
      - Display the node number's 8-char hexadecimal value, helpful for filename
      EchoCfg->NetMail Settings:
      - New optino: Ignore NetMail 'KillSent' Attribute
        when set, sent netmails with the "KillSent" flag won't be deleted by SBBSecho
      - The name (destination) of forwarded AreaFix requests is now configurable
        (no longer hard-coded to "AreaFix")
      Enforce the SM_DELREADM option.
      Use smb_storage_mode().
  27. 13 Nov, 2017 1 commit
    • rswindell's avatar
      SBBS v3.03: · d0013bd7
      rswindell authored
      * AreaFix updates:
      - No longer accepts AreaFix requests to "SBBSecho", since we send mail from
        that name, accepting mail to the same name can create a bot-loop
      - Each linked node has a configurable "name" now, where to send notifications
        (not always "sysop")
      - AreaFix support for a node can be toggled without clearing their AreaMgr
      - Area listings now include the echo descriptions (when available)
      - Fix: the badecho is not included in area lists returned via netmail
      - Improved log output around AreaFix requests/operations
      - %echostats [echo] command now supported to request most recents stats for
        an area
      - Notifications can now be toggled by AreaFix sysops using %NOTIFY On/Off
      - Notification mail to the local Area Manager (sysop) now have the correct date
        time/zone in the message header (not copied from the AreaFix request)
      * Added support for auto-responding to PING NetMail requests
      * When exporting EchoMail, if the date/time written or imported exceeds the
        configured maximum age for EchoMail, don't export it (rescan exempted)
      * The -g (generate notification messages) works with a passed address now
      * Better grunged packet detection (e.g. NULL-terminated header fields must be
      * Avoid bot-loop by refusing to send netmail from "SBBSecho" to "SBBSecho"
        If you setup an echolist to forward areafix requests to your hub a loop could
        occur :-(
  28. 06 Nov, 2017 1 commit
    • rswindell's avatar
      SBBSecho v3.02: · 4f84221d
      rswindell authored
      Most of the changes are in EchoCfg:
      - SBBSecho and EchoCfg will now maintain auto-backups of the sbbsecho.ini file
      - AutoAddSubs now defaults to true/enabled: this setting is harmless without
        further configuring linked nodes (Uplink for Groups / GroupHub)
      - Global Settings are now a separate sub-menu in EchoCfg
      - EchoCfg remembers current selection on (more) sub-menus
      - Sub-menus have been rearranged and resized
      - Numerous Online Help text updates in EchoCfg
      - Adding missing/new settings to EchoCfg:
        Log Timestamp Format
        Strict Packet Passwords
        Use FTN Domain/Zone Map
        BSY Mutex File Timeout
        BSO Lock Attempt Delay
        BSO Lock Attempt Limit
        Config File Backups
        Linked Nodes->Uplink for Message Groups
        Echo Statistics File
        Outgoing Semaphore File
        Automatically Add New Subs to Area File
        Maximum Backups to Maintain of Area File
        Relay Filtered Messages
        (everything you can set in sbbsecho.ini should now be editable via EchoCfg)
  29. 28 Oct, 2017 1 commit
    • rswindell's avatar
      EchoStats filename (data/echostats.ini) is now configurable. · 884c19fb
      rswindell authored
      EchoStats now contain message timezones (when written) and a "known" flag
      (bad echoes have known = false).
      EchoStats are now sorted before being written to the EchoStats file.
      Fixed bug in getfmsg(): trailing ex-ASCII chars of the message body would be
      chopped-off - go back to using a uchar.
      Re-worked packed-msg import parsing and grunged message detection a bit to
      log more msg details for all EchoStats.
      Added "AutoAddSubs" feature (set to true in sbbsecho.ini to enable):
      - If sub-boards are created (e.g. with SCFG) in one or more message groups, the
        areas can be automatically added to your Area File (areas.bbs)
      - The hub must be first configured in EchoCfg->Linked Nodes and then you set
        the GroupHub key in sbbsecho.ini to the name of the message group that this
        link is the hub for (e.g. "FidoNet"). You can specify multiple groups, if
        necessary, by comma-separating the names.
  30. 26 Oct, 2017 1 commit
  31. 19 Oct, 2017 1 commit
    • rswindell's avatar
      At Nelgin's request, added TIC File Password management to sbbsecho.ini, · aeb367c2
      rswindell authored
      echocfg, and SBBSecho (for AreaFix management of the pwd). SBBSecho doesn't
      use the password itself, but it allows it to be managed via the %TICPWD AreaFix
      command. EchoCfg will read the (new) TicFilePwd key from the node sections
      of the sbbsecho.ini and allow them to be modified/saved. Max TicFilePwd length
      is 8 chars (same as Packet Passwords).
  32. 19 Sep, 2017 1 commit
  33. 09 Jun, 2017 1 commit
    • rswindell's avatar
      The beginnings of auto-echo-add: · f4fedac6
      rswindell authored
      - SBBSecho will now maintain a file called the Bad Area File
        (default name is data/badarea.lst), in BACKBONE.NA format
      - This file is suitable for importing in SCFG->Message Areas now, but expect
        some automation in the near future
      - To get area descriptions (not just echo tags) in the Bad Area File, be sure
        to configure at least one "Additional EchoList" to point a comprehensive echo
        list (e.g. BACKBONE.NA or similar)
      - SBBSecho will automatically add new areas (when new messages are received for
        msg areas you don't carry) or remove areas that you start to carry - no sysop
        maintenance of this file should be needed. And the file does not have to be
        deleted after being imported (e.g. with SCFG).
      - SBBSecho does not (and may never) actually modify your Synchronet Message
        Areas configuration directly, that is yet to be determined
      Another new feature: Area File (areas.bbs) backups:
      - Whenever the Area File is modified via AreaFix, the current file is backed
        up  (e.g. areas.0.bbs, etc.)
      - This feature can be tweaked or disabled via the AreaFileBackups key in
        sbbsecho.ini (not yet in echocfg), default backup level is 100
      * Numerous EchoCfg help text updates.
      * Some minor terminology updates (e.g. AREAS.BBS->areas.bbs, Areafix->AreaFix).
      * Incremented SBBSecho version from 3.00 to 3.01.
  34. 06 Mar, 2017 1 commit
  35. 01 Mar, 2017 3 commits
    • rswindell's avatar
      +1 for NULL terminator. · 097a0825
      rswindell authored
    • rswindell's avatar
      Fix GCC warnings: · e95e0dae
      rswindell authored
      sbbsecho.h:186:7: warning: array æpktTypeStringListÆ assumed to have one element
      Warning: size of symbol `pktTypeStringList' changed from 8 in .../rechocfg.o
    • rswindell's avatar
      Packet Type-2e (FSC-39.4) support: · aace645d
      rswindell authored
      For packet creation, the only difference (from Type-2+) is with packets created
      from point nodes: the origNet field won't be set to 0xffff (as is the case with
      FSC-48, Type-2+ packets). The auxNet field is now always set to the originating
      net (ala Squish) when configured for Type-2+ packet generation.
      When importing Type-2e (FSC-39) packets, the detected/logged packet type may be
      reported as "2e" for valid "2+" packets. This is normal and expected when the
      originating node is not a point and the auxNet field is 0.
      The second set of orig/dest zone fields in a type 2e/2+ pkt header will
      now be used when importing if the old/QM orig/dest zone fields are 0.
      Also, the originating point field may now be imported even if the auxNet field
      is not used (origNet != 0xffff).
      New umask sbbsecho.ini configuration option (global), maybe used to over-ride
      the default *nix file creation mode mask (077), similar to sbbs.ini.
  36. 03 Aug, 2016 1 commit
    • rswindell's avatar
      AreaFix overhaul a bit. · 11d74039
      rswindell authored
      Added support for "%RESCAN <echo-tag>" at the request of Al Prunty, because he
      asked for this "new feature".