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

  1. 28 Feb, 2021 2 commits
  2. 22 Feb, 2021 14 commits
  3. 21 Feb, 2021 4 commits
  4. 20 Feb, 2021 3 commits
  5. 19 Feb, 2021 5 commits
    • Rob Swindell's avatar
      Correct the parse_mail_address() argument order · e9329f6c
      Rob Swindell authored
      Issue introduced in previous commit to this file. The name arg(s) comes before the address arg(s).
    • Deucе's avatar
    • Deucе's avatar
      Fix CIDs 174500 and 174471 · 59b8829a
      Deucе authored
    • 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.
    • Rob Swindell's avatar
      Recognize DNB blacklist exempted email addresses in From fields · 27079b33
      Rob Swindell authored
      Previously, any DNS blacklist-exempt email addresses (in ctrl/dnsbl_exempt.cfg) had to be used in the mail-envelope (the "MAIL FROM:" address) - that doesn't work for all senders that use re-mailers or whatever where you end-up with some *bounce* address as the envelope-sender.
      So now, clear the DNSBL results when the From header field is parsed and the sender was in fact an exempt sender. Note: the Subject line will still contain the SPAM tag if the subject was parsed first (came earlier in the message header). May need to address this limitation in the future if it turns out to be a problem (!).
      Lowercase the [smtp|smtps]spy.txt log file.
  6. 18 Feb, 2021 6 commits
  7. 17 Feb, 2021 4 commits
  8. 16 Feb, 2021 2 commits
    • Rob Swindell's avatar
      Optional cap on TLS log message severity level · 113a9a56
      Rob Swindell authored
      Are you tired of getting TLS-related error log messages that you can't do anything about? e.g.
      web  0139 TLS ERROR 'Received TLS alert message: Unexpected message' (-15) setting session active
      The new sbbs.ini [web] TLSErrorLevel option (defaults to 0 / "Emergency") allows the sysop to set a cap (maximum severity) on TLS-related log messages in the web server (e.g. TLSErrorLevel=Warning).
    • Deucе's avatar
      Only patch I looked at in 68990cd8 was wrong. · 5a60ea6e
      Deucе authored
      x points to the terminating NUL in x64.  free()ing it would do wild
      and crazy things depending on how paranoid the free() implementation
      free(x64) instead... at least Coverity was happy though!