• src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h

    From deuce@VERT to CVS commit on Wed Apr 20 22:29:35 2016
    src/sbbs3 echocfg.c 3.2 3.3 rechocfg.c 3.2 3.3 sbbsecho.c 3.6 3.7 sbbsecho.h 3.1 3.2
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv16078

    Modified Files:
    echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Initial support for new "UseFTNDomains" boolean INI option.

    With this option enabled, zone/domain mappings from ctrl/ftn_domains.ini are used to get the outbound directory name, and the orig/dest domains for type
    2.2 packets.

    This allows supporting 5D addressing in sbbsecho when zones do no overlap between domains (the normal case).




    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From deuce@VERT to CVS commit on Wed Apr 20 22:51:02 2016
    src/sbbs3 echocfg.c 3.3 3.4 rechocfg.c 3.3 3.4 sbbsecho.c 3.7 3.8 sbbsecho.h 3.2 3.3
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv17464

    Modified Files:
    echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Parse ctrl/ftn_domains.ini in a seaparate function in rechocfg.
    Back out echocfg.c changes.




    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From rswindell@VERT to CVS commit on Wed Mar 1 02:25:38 2017
    src/sbbs3 echocfg.c 3.7 3.8 rechocfg.c 3.12 3.13 sbbsecho.c 3.29 3.30 sbbsecho.h 3.9 3.10
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv8825

    Modified Files:
    echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Packet Type-2e (FSC-39.4) support:
    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.


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From rswindell@VERT to CVS commit on Mon Mar 6 19:58:09 2017
    src/sbbs3 echocfg.c 3.9 3.10 rechocfg.c 3.13 3.14 sbbsecho.c 3.31 3.32 sbbsecho.h 3.12 3.13
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv24612

    Modified Files:
    echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Added option (IgnoreNetmailSentAttr in sbbsecho.ini) to ignore the "Sent" attribute for netmail (both *.msg and in the mail base). This option should *not* be used when the DeleteNetmail option is enabled (set to 'Yes').
    A warning will be logged in this configuration as dupe netmail msgs may be
    sent in that case.


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From rswindell@VERT to CVS commit on Tue Sep 19 00:12:04 2017
    src/sbbs3 echocfg.c 3.13 3.14 rechocfg.c 3.16 3.17 sbbsecho.c 3.37 3.38 sbbsecho.h 3.14 3.15
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv17933

    Modified Files:
    echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Enhancement: don't allow inbox or outbox to configured for nodes with addresses that contains wildcards ("ALL") - prevents misconfiguration. Fileboxes are not for multiple-nodes (one node per in/outbox only).


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From rswindell@VERT to CVS commit on Thu Oct 19 02:56:52 2017
    src/sbbs3 echocfg.c 3.18 3.19 rechocfg.c 3.20 3.21 sbbsecho.c 3.40 3.41 sbbsecho.h 3.15 3.16
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv10955

    Modified Files:
    echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    At Nelgin's request, added TIC File Password management to sbbsecho.ini, 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).


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From rswindell@VERT to CVS commit on Mon Nov 6 03:43:22 2017
    src/sbbs3 echocfg.c 3.19 3.20 rechocfg.c 3.22 3.23 sbbsecho.c 3.50 3.51 sbbsecho.h 3.18 3.19
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv12113

    Modified Files:
    echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    SBBSecho v3.02:
    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)


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From rswindell@VERT to CVS commit on Tue Apr 30 00:33:47 2019
    src/sbbs3 echocfg.c 3.38 3.39 rechocfg.c 3.33 3.34 sbbsecho.c 3.112 3.113 sbbsecho.h 3.27 3.28
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv9078

    Modified Files:
    echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Add option to strip so-called "Soft CRs" (0x8D) from incoming messages.
    The default is off (no stripping). Previously, Soft-CRs were always stripped, but this behavior is now seen as an anachronism as CP437 char 141 is an important non-English laguage character and used as such in FidoNet msgs.


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Rampage@VERT/SESTAR to Digital Man on Tue Apr 30 05:43:52 2019
    Re: src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    By: rswindell to CVS commit on Mon Apr 29 2019 20:33:47

    Add option to strip so-called "Soft CRs" (0x8D) from incoming messages.

    it took me a minute to find this new option... i was looking for it in the Global Settings section instead of the Echomail Settings section... does it also apply to netmail? if not, it kinda really should ;)

    thanks for adding it, too! :)



    PS: i'm sorry for your loss... i just found out earlier yesterday... i'm still dealing with mine from august and i know it can be painful for a while :/


    )\/(ark

    ---
    ■ Synchronet ■ The SouthEast Star Mail HUB - SESTAR
  • From Digital Man@VERT to Rampage on Tue Apr 30 05:47:44 2019
    Re: src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    By: Rampage to Digital Man on Tue Apr 30 2019 01:43 am

    Re: src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    By: rswindell to CVS commit on Mon Apr 29 2019 20:33:47

    Add option to strip so-called "Soft CRs" (0x8D) from incoming messages.

    it took me a minute to find this new option... i was looking for it in the Global Settings section instead of the Echomail Settings section... does it also apply to netmail? if not, it kinda really should ;)

    As the online help says:

    Strip Soft CRs from Incoming Messages when set to Yes instructs
    SBBSecho to remove any so-called "Soft" Carriage Return (ASCII 141)
    characters from the text of imported EchoMail and NetMail messages.
    This setting defaults to No.

    ... it does also apply to NetMail. I'll probably move it to the global section since it really isn't EchoMail-specific.

    thanks for adding it, too! :)

    Sure. At first I was just going to remove the Soft-CR stripping, but thought I'd leave an option just in case someone really needs the old behavior.

    PS: i'm sorry for your loss... i just found out earlier yesterday... i'm still dealing with mine from august and i know it can be painful for a while

    Thanks. It's been ordeal for sure.

    digital man

    Synchronet/BBS Terminology Definition #17:
    DCE = Data Communications Equipment (or Deuce, Stephen Hurd)
    Norco, CA WX: 55.3°F, 88.0% humidity, 5 mph ESE wind, 0.00 inches rain/24hrs

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From mark lewis@VERT to Digital Man on Tue Apr 30 16:01:48 2019
    On 2019 Apr 30 01:47:44, you wrote to Rampage:

    it took me a minute to find this new option... i was looking for it in
    the Global Settings section instead of the Echomail Settings section...
    does it also apply to netmail? if not, it kinda really should ;)

    As the online help says:

    [...]

    ... it does also apply to NetMail.

    ummhummm... i read that and still wasn't sure so better to ask and find out than to assume and... well :lol:

    I'll probably move it to the global section since it really isn't EchoMail-specific.

    that would be cool...

    thanks for adding it, too! :)

    Sure. At first I was just going to remove the Soft-CR stripping, but thought I'd leave an option just in case someone really needs the old behavior.

    understandable...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Shoplifters with the runs take Clepto Bismol.
    ---
    * Origin: (1:3634/12.73)
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From rswindell@VERT to CVS commit on Wed Aug 21 21:15:07 2019
    src/sbbs3 echocfg.c 3.47 3.48 rechocfg.c 3.39 3.40 sbbsecho.c 3.135 3.136 sbbsecho.h 3.34 3.35
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv4325

    Modified Files:
    echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    SBBSecho should be able to run withOUT an area file (areas.bbs file).
    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 AutoAddToAreaFile=false.
    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.


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From rswindell@VERT to CVS commit on Tue Sep 17 07:29:35 2019
    src/sbbs3 echocfg.c 3.48 3.49 rechocfg.c 3.40 3.41 sbbsecho.c 3.140 3.141 sbbsecho.h 3.35 3.36
    Update of /cvsroot/sbbs/src/sbbs3
    In directory cvs:/tmp/cvs-serv6402

    Modified Files:
    echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Added support for auto-detection of incoming UTF-8 messages (default: enabled). 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.


    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to Git commit to main/sbbs/master on Thu Mar 18 19:44:44 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/8817d760e0c77e0959034a0e
    Modified Files:
    src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Build log rotation into SBBSecho, bump version to 3.14

    2 new configuration params: MaxLogSize (default: 10M) and MaxLogsKept (10)

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to Git commit to main/sbbs/master on Sun May 9 23:04:01 2021
    https://gitlab.synchro.net/main/sbbs/-/commit/9afeb9ea253ebad0b4e4b567
    Modified Files:
    src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Add option to control whether area-linked nodes must be configured

    This should address issue # 261.
    Before April 19, 2016, area-linked nodes were required to be listed as nodes in sbbsecho.ini:
    http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/sbbs3/sbbsecho.c?revision=3.6&view=markup
    I'm not sure why the change was made to only require that there be a wildmatch for each area-linked node. So just make it a configuration option. <shrug>

    Also removed the trailing "..." for every top level menu item in echocfg.

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows)@VERT to Git commit to main/sbbs/master on Fri Apr 14 20:37:52 2023
    https://gitlab.synchro.net/main/sbbs/-/commit/9a253736ae2ccfeb890efaa8
    Modified Files:
    src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    By default SBBSecho will now include the 'reason' in bad packet filenames

    When bad packets are detected and renamed to ".bad" files, include the reason in the new filename (e.g. "ff69453a.src-addr.bad" or "ff69453a.pkt-passwd.bad" instead of just "ff69453a.bad") to make it easier for a sysop to determine
    what to do with the bad packets without having to search through log files
    to discover the reason *why* SBBSecho considered the packet to be bad.
    This behavior can be disabled if desired by setting EchoCfg->Global->Verbose Bad Packet Names to "No". Note: the reason used is the *last* reason detected/logged for a packet to be considered bad; it's possible that there
    are multiple reasons that a packet may be considered bad. All reasons will be logged, but only the last reason is used in the new bad packet filename.

    Also added the missing "Delete Packets" option (to EchoCfg->Global). Though this setting was added in sbbsecho v3.0 (and settable via sbbsecho.ini), it
    was never exposed via EchoCfg; I don't think that was intentional. Normally, you'd always want to leave this set to Yes (the default) to delete processed packets, but when debugging, it may be desirable to leave the packet files
    in place. This what the old sbbbsecho v2 '-x' command-line option used to be used for (disable the deleting of processed packets).

    Moved the Global Settings, EchoMail Settings, and File Paths config menus to the upper left of the screen in EchoCfg. The placement seemed inconsistent
    and erratic, so this is a bit of a cosmetic improvement.

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows)@VERT to Git commit to main/sbbs/master on Fri Apr 14 21:16:58 2023
    https://gitlab.synchro.net/main/sbbs/-/commit/7914da93b6a0b64551317b1e
    Modified Files:
    src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Add option to delete bad incoming packets (not rename them)

    So a sysop now has 3 choices for SBBSecho's handling of incoming bad packets:
    - delete them
    - rename them *.bad
    - rename them *.reason.bad (the default)

    If SBBSecho is configured to rename bad packets, but the rename fails, the error is logged (as before) but the packet is not deleted (this is a change from previous behavior).

    Always log the *reason* a pkt was determined bad in the "Bad packet detected" log message.

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Mon Dec 4 22:21:51 2023
    https://gitlab.synchro.net/main/sbbs/-/commit/5e79f0550093a55dd0c8de70
    Modified Files:
    src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
    Log Message:
    Allow default packet type to be configurable

    Previously, any packets created for unlinked nodes, would always be Type-2 packets and the packet type for newly created nodes (in echocfg->Linked Nodes) would be Type-2+.

    The new DefaultPacketType setting default is 2+, so the only observed
    change in behavior will be that packets created for unlinked nodes will also
    be type 2+ (by default).

    Some additional log detail/adjustment around created/detected packet types.

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net