Skip to content
Snippets Groups Projects
  1. Dec 10, 2020
    • Rob Swindell's avatar
      Address GCC warning · 0cebd95a
      Rob Swindell authored
      ‘%s’ directive writing up to 255 bytes into a region of size between 103 and 128
      reported by Nelgin.
      0cebd95a
    • Rob Swindell's avatar
      Don't repeate mail "comment" headers in exported netmail msgs · 33568d12
      Rob Swindell authored
      smb_getmsgtxt() returns any "comment" headers as part of the message body text, and has since 2003.
      When I added mail->netmail (stored message) export support to SBBSecho v3, I duplicated this logic, so comment headers were added *twice* to exported netmail messages. Oops. I didn't notice until today when playing with forwarding-to-netmail (FTN).
      
      Also noticed and fixed: any comment headers in posted messages (unlikely/uncommon) would not be exported to EchoMail messages. Use the correct smb_getmsgtxt() mode flags ("NO_TAILS" instead of "BODY_ONLY") - I know, not great names.
      33568d12
    • Rob Swindell's avatar
      Updated Forwarded and ForwardedFrom text.dat lines. · cc60feec
      Rob Swindell authored
      User number is not always relevant (e.g. could be #0) when sending
      netmail, so don't show that. And the CRLF at in the Forwarded string
      appears extraneous.
      cc60feec
    • Rob Swindell's avatar
      03d0ca80
    • Rob Swindell's avatar
      Overhauled message forwarding, allow comments · 657ba52d
      Rob Swindell authored
      No longer derive the new message header from the original - too many problems. Simplified the forwarding support smblib (multiple SENDER* and RECIPIENT* header fields no longer expected/supported). Technically, the FORWARDED header field really serves no important purpose now.
      A comment can be passed into forwardmail() or (if NULL), will be prompted for. There is an issue where the added comment can be obscured by the receiving mail program if the original message is a multi-part MIME message. Not sure the best solution for that. Still a WIP in that regard.
      657ba52d
  2. Dec 09, 2020
  3. Dec 08, 2020
  4. Dec 07, 2020
  5. Dec 06, 2020
  6. Dec 05, 2020
  7. Dec 04, 2020
    • Rob Swindell's avatar
      Disable HAProxy support by default for now · 6a8a2b9b
      Rob Swindell authored
      This code does not currently work on WinXP:
      "The procedure entry point inet_pton could not be located in the dynamic link library WS2_32.dll"
      
      That could likely be addressed using GetProcAddress(), but for now, I want to get to the bottom of a *different* issue reported on a WinXP system, so need to this disabled.
      Define HAPROXY_SUPPORT in your build if you need this feature compiled in right now.
      6a8a2b9b
    • Rob Swindell's avatar
    • Rob Swindell's avatar
      a00a95a8
    • Rob Swindell's avatar
      ZMODEM Window Management support · 829627b9
      Rob Swindell authored
      The default is still full-streaming mode. The default can be changed by
      setting [ZMODEM] MaxWindowSize in sexyz.ini to a maximum window size to
      use by default (e.g. "100K"). Additionally, a [ZMODDEM] TargetWindowSize
      can be set to a duration (e.g. 60s) to dynamically adjust the maximum
      window size to match the through-put rate while keeping the outstanding data
      in-flight to an estimated "duration". When TargetWindowSize is used, the
      MaxWindowSize only specifies the *initial* maximum window size.
      
      The new '-w' command-line option can be used to control Window Management
      support (e.g. over-riding the .ini set default) - by using '-w' or '-w0',
      Window Management won't be used or by using '-w<max-size>', a maximum window
      size will be imposed (subject to the TargetWindowSize setting mentioned
      above). <max-size> can be specified in bytes or multiples (e.g. "-w100K").
      Ths option is similar to the [l]sz '-w' option except no space is expected
      between '-w' and the (optional) max-size value.
      
      Also new, when receiving [ZMODEM] FullDuplex can be set to FALSE to disable
      streaming mode: if the RecvBufSize is not set (0), the sender should use the
      subpacket data length (block size, e.g. 1K) as the segment size. Otherwise,
      setting FullDuplex=FALSE should produce the same behavior as setting the
      RecvBufSize would before (the result being the use of "segmented ZMODEM"
      instead of "streaming ZMODEM").
      
      All sexyz command-line options are case-sensitive now (not just the 'cmds').
      A lot of code clean-up in zmodem.c.
      
      Incremented zmodem.c rev to 2.0.
      Incremented sexyz version to 3.0.
      829627b9
    • Rob Swindell's avatar
      Change rev to 2.0. · 61b0bde8
      Rob Swindell authored
      61b0bde8
    • Deucе's avatar
      Fix this.sock is undefined error. · 3bdf0b9a
      Deucе authored
      Not sure how we get a successful shutdown after closing the socket,
      but the issue was reported by altere as happening in the wild.
      3bdf0b9a
Loading