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.

--- SBBSecho 3.09-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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.

--- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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.142 new configuration params: MaxLogSize (default: 10M) and MaxLogsKept (10)
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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 configuredThis 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=markupI'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.
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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 filenamesWhen bad packets are detected and renamed to ".bad" files, include the reasonin 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 determinewhat to do with the bad packets without having to search through log filesto discover the reason *why* SBBSecho considered the packet to be bad.This behavior can be disabled if desired by setting EchoCfg->Global->VerboseBad Packet Names to "No". Note: the reason used is the *last* reasondetected/logged for a packet to be considered bad; it's possible that thereare multiple reasons that a packet may be considered bad. All reasons will belogged, but only the last reason is used in the new bad packet filename.Also added the missing "Delete Packets" option (to EchoCfg->Global). Thoughthis setting was added in sbbsecho v3.0 (and settable via sbbsecho.ini), itwas 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 processedpackets, but when debugging, it may be desirable to leave the packet filesin place. This what the old sbbbsecho v2 '-x' command-line option used to beused for (disable the deleting of processed packets).Moved the Global Settings, EchoMail Settings, and File Paths config menus tothe upper left of the screen in EchoCfg. The placement seemed inconsistentand erratic, so this is a bit of a cosmetic improvement.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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, theerror is logged (as before) but the packet is not deleted (this is a changefrom previous behavior).Always log the *reason* a pkt was determined bad in the "Bad packet detected"log message.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)