Skip to content
Snippets Groups Projects
  1. Nov 13, 2017
    • rswindell's avatar
      Fix build issue: new usage of getmail() · b4b7b43b
      rswindell authored
      b4b7b43b
    • rswindell's avatar
      Fixed build issue: getmail() usage. · f804eb0d
      rswindell authored
      f804eb0d
    • rswindell's avatar
      Fix inadvertent commit of changes to jsexec.c · d058e6a4
      rswindell authored
      d058e6a4
    • rswindell's avatar
      *** empty log message *** · f51297f6
      rswindell authored
      f51297f6
    • rswindell's avatar
      Fixed build issue: getmail() usage · fd7315b5
      rswindell authored
      fd7315b5
    • rswindell's avatar
      New feature: control of SPAM visibility when reading mail on the Terminal · 824c499d
      rswindell authored
      Server via the new 'V' command from the Reading Mail prompt allows you to
      toggle between all mail (including SPAM, the default), SPAM only, or HAM only.
      Also added a new '/' (search text) command from the reading mail prompts.
      824c499d
    • rswindell's avatar
      Squash a couple of new GCC warnings. · f3a56088
      rswindell authored
      f3a56088
    • 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
        password
      - 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
        NULL-terminated)
      * 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 :-(
      d0013bd7
    • rswindell's avatar
      New feature: control of SPAM visibility when reading mail on the Terminal · d18bd3bd
      rswindell authored
      Server via the new 'V' command from the Reading Mail prompt allows you to
      toggle between all mail (including SPAM, the default), SPAM only, or HAM only.
      Also added a new '/' (search text) command from the reading mail prompts.
      Mail imported before the mailsrvr added support (recently) for the MSG_SPAM
      attribute flag will not be counted/filtered as SPAM.
      SBBSecho will have a commit (next) to support the new loadmail() usage, it
      will not compile until then.
      d18bd3bd
    • rswindell's avatar
      Fix long-standing bug with routed (re-packed) netmail messages: · 6cdb6d6a
      rswindell authored
      The orig address in the packed msg header is (and still is) the proper
      local system address (this may be correct behavior, still checking), but
      no INTL control line (FSC-0004) was added, so the packed message header
      ends up defining the originating system address. So, now we include an
      INTL control line in packed netmail messages which reflects the actual
      origin address of the message. Thanks to Nigel Reed for helping to identify
      and test this problem over the past week or so.
      6cdb6d6a
  2. Nov 12, 2017
  3. Nov 11, 2017
  4. Nov 09, 2017
    • rswindell's avatar
      Fix long-standing bug (since forever): · dc7ef25b
      rswindell authored
      When packetizing netmail, the "origin" address in the created packet header
      was copied from the netmail (*.msg) message file. This is fine for locally
      created netmail, but nof for forwarded netmail (!). This would end up creating
      outbound packets with a foreign source/origin address which may or may not
      be deliverable.
      
      Sort of related, if there are stray packets in the outbound directory with a
      foreign source/origin address - don't packetize them! Just log a msg and ignore
      these foreign outbound packets.
      
      This explains at least part of the problem Nelgin reported where a routed
      netmail was delivered to him (on Vert) from a hop running SBBSecho v3.01 and
      I saw this packet header oddity. Now, why the actual netmail message itself
      had the wrong origin address has not been identified.
      
      If your system routes netmail messages (e.g. your hub), you'll want his update!
      dc7ef25b
    • rswindell's avatar
      Fix for BSO/FLO mode: when packing netmail, if the netmail message has the · ec30d79d
      rswindell authored
      "Hold" attribute set, don't route to the configured uplink. Just like the last
      commit, but now we actually create the proper cut/hut/out filename based on the
      status as well.
      Turns out, Crash and Hold NetMail was handled correctly in v2.x and was an
      un-reported regression (new bug) in v3.0.
      ec30d79d
    • rswindell's avatar
      Fix for BSO/FLO mode: when packing netmail, if the netmail message has the · c3882eb6
      rswindell authored
      "Crash" attribute set, don't route to the configured uplink.
      We really should do something similar for the "DIR" FLAGS kludge line, but
      that's more work (and isn't easily set on a per-msg basis, like crash is), so
      I'll revisit that later.
      c3882eb6
  5. Nov 08, 2017
  6. Nov 07, 2017
Loading