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)

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.

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.

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.

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.

https://gitlab.synchro.net/main/sbbs/-/commit/f2e46f3dc5c7d31badc23c94
Modified Files:
src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
Log Message:
Replace almost all references to AreaFix with AreaMgr or AreaManager

"AreaFix" is a proper product name. Though it's been defunct and unsupported for decades, we still should not confuse sysops and historians: the general term for what AreaFix did/does is Area Management, aka Conference Management.

The sbbsecho.ini key names are unchanged and the destination netmail address for AreaManager requests can still be "AreaFix" (though "SBBSecho" is still supported as well).