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

  1. 04 Apr, 2021 2 commits
  2. 17 Jan, 2021 1 commit
    • Rob Swindell's avatar
      Don't include message number in origaddr portion of FTN NetMail MSGIDs · fca30919
      Rob Swindell authored
      Some old/unsupported FidoNet software (NetMgr? Squish?) reportedly parse addresses from MSGID control/kludge lines in NetMail messages to determine the source and/or destination address. This is clearly a bad idea for a lot of reasons, but to improve compatibility, let's not include the message number (or an '@') in the origaddr field for NetMail messages. This does slightly increase the chance of a duplicate MSGID being accidentally generated if the "mail" base is renumbered. No change for EchoMail MSGIDs (where dupe detection and threading still benefit from the additional entropy).
      For Watchman.
      fca30919
  3. 13 Dec, 2020 1 commit
  4. 12 Dec, 2020 1 commit
    • Rob Swindell's avatar
      Generate/use git_branch.h and git_hash.h for every make invocation · 221a860c
      Rob Swindell authored
      Allows reporting of branch/commit that was used to build the code.
      
      If for some reason building without 'git', you'll need these 2 files to
      already exist somehow - still need to work that out (e.g. for daily
      built-source archives).
      
      Need to update the Windows build to generate these files now.
      221a860c
  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/libsbbs.so 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 extdeps.mk 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.
      c6808b3f
  6. 16 Aug, 2020 1 commit
  7. 15 Jul, 2020 2 commits
    • rswindell's avatar
      Move nearest_sysfaddr() from fido.cpp to msg_id.c since it's needed by... · 4d87a354
      rswindell authored
      Move nearest_sysfaddr() from fido.cpp to msg_id.c since it's needed by anything that uses msg_id.c now (e.g. SBBSecho, which doesn't link fido.cpp).
      4d87a354
    • rswindell's avatar
      According to August Abolins (2:221/1.58): · 9798e647
      rswindell authored
      "Other systems produce [FTN MSG-IDs for NetMail messages) quite nicely: HotdogEd, BBBS, Mageia, Platinum
      Express, GED+LNX, and OpenXP.   I took it for granted that SBBS would be
      in the same league.   It makes it super easy to link up a netmail
      conversation or generate a graphical-tree when a msgid exists.
      
      I was spoiled into thinking that msgid was ubiquitous in netmail as well."
      
      Reviewing FTS-9, I see no restriction to only echomail, so sure, why not:
      add_msg_ids() now adds FTN Message-IDs to outbound NetMail messages too (not just FTN echomail). No configuration or SBBSecho change needed.
      9798e647
  8. 11 Apr, 2019 1 commit
  9. 17 Feb, 2019 3 commits
  10. 06 Nov, 2018 1 commit
    • rswindell's avatar
      Don't generate FTN message-IDs for messages imported via FTN that are missing a · b1692861
      rswindell authored
      message-ID (e.g. when exporting from SBBSecho).
      This addresses compliance with this [editorialized] clause in FTS-9:
           No system
           should ever add an MSGID and/or REPLY to,  or modify an existing
           MSGID / REPLY contained in,  a message not originating on that [FTN]
           system.
      
      Messages gated from other networks (technically coming from another system,
      but originating into an FTN from this system) will still have an FTN Message-ID
      generated/added.
      
      Since SBBSecho normally tosses to downlinks directly from packets, this adding
      of generated Message-IDs would no normally occur. However, if a downlink
      rescanned an area, any messages missing Message-IDs would get them generated
      automatically and they would appear to have originating on the local system.
      This was never the intention, so this is just a long standing but infrequently
      observed (and never reported) bug.
      b1692861
  11. 23 Nov, 2016 2 commits
  12. 20 Nov, 2016 2 commits
    • rswindell's avatar
      Solved the networked-voting "ordering problem". QWK/REP packets that contained · 3258eca3
      rswindell authored
      normal messages along with voting data (polls, ballots, etc.) would always be
      imported in this order: msgs, polls, ballots/votes, and then poll-closures.
      This could result in a confusing order of messages in the local msg base where
      there were messages in reply to a poll before the poll appears and other
      oddities. Anyway, this is now resolved by placing a msg "header block" for each
      vote-data item in the MESSAGES.DAT file. Since there is no body/text blocks,
      it should be ignored under normal circumstances, but these header blocks are
      only created if VOTING.DAT is enabled anyway.
      And now, the VOTING.DAT contains an extra line (empty .ini section) with the
      HEADERS.DAT offset associated with the chronology of the item. The format
      is still backwards compatible with the earlier builds that included VOTING.DAT
      support.
      
      Also, fixed the vote/poll/closure Message-IDs containing a msg number of 0
      (while not technically a problem, it wasn't the intention) with the use of the
      new function: get_new_msg_number().
      3258eca3
    • rswindell's avatar
      Automatic REPLY-ID fixup: · 396b931b
      rswindell authored
      If a message header has a thread_back value (it's a reply to another msg), but
      there is no Reply-ID header field, when converting QWK, look-up the
      original message-ID (to use for the relpy/vote Reply-ID value). If the original
      message doesn't have a message-ID, use the normal auto-generation scheme.
      This isn't normally necessary, but I posted a poll with a message-ID on
      DOVE-Net / Sysops and then voted on the poll, creating a vote with no Reply-ID
      which causes an SMB "writing" error (access=-105) on the QWKnet node BBSes
      (because the required header field is missing).
      396b931b
  13. 19 Oct, 2011 1 commit
  14. 25 Feb, 2008 1 commit
    • rswindell's avatar
      The Big Commit: · 73134a2c
      rswindell authored
      * Parses/consumes QWK headers.dat files
        - No more to/from/subj length limits
        - Extensive header details transferred for each message
        - IP/hostname filters (.can files) are applied to appropriate header fields
        - Code cleanup in the QWK functions
      * New functions to read/parse/search filter (.can) files as string lists
        - Performance boost - no need to open/read/close .can file for each message
      * More thread-safe Message-ID retrieval/generation (ftn_msgid and get_msgid)
      * Better Message-ID generation for misconfigured systems (e.g. no hostname)
      ! These changes require the latest smblib and xpdev libraries !
      73134a2c
  15. 02 Oct, 2005 1 commit
  16. 21 Oct, 2004 1 commit
  17. 08 Sep, 2004 1 commit
  18. 27 Jul, 2002 1 commit
  19. 27 Dec, 2001 1 commit
  20. 08 Nov, 2000 1 commit
  21. 10 Oct, 2000 1 commit