https://gitlab.synchro.net/main/sbbs/-/commit/24be3ec819079bac2bd3feca
Modified Files:
src/sbbs3/scfg/scfgmsg.c
Log Message:
Fix inverted default selection for Message Options->Purge Deleted E-mail

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

https://gitlab.synchro.net/main/sbbs/-/commit/742d71bf3ba6f42b37fe1592
Modified Files:
src/sbbs3/scfg/scfgmsg.c scfgsub.c scfgxfr2.c
Log Message:
Set cfg_changed flag (so msgbases are created/updated) when changing int-codes

When changing message or file area internal code prefixes or suffixes, the message base files need to be (re)created (e.g. in data/subs or data/dirs).
The 'cfg_changed' flag is the thing that indicates that we need to do that for each message or file area and we weren't setting that flag in these cases.

Note: this doesn't rename the message base files, so if they have content (messages or files), they'll just remain in the old internal code named files and require the sysop to deal with manually.

Reported in IRC by finglonger.

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

https://gitlab.synchro.net/main/sbbs/-/commit/8ff76ce4a4a33fce23cfded6
Modified Files:
src/sbbs3/scfg/scfgmsg.c
Log Message:
Add ability to change MailBase storage method from self-packing to fast alloc

This option has been built into the Synchronet runtime for 30+ years or so, but there was never a configuration menu provided to sysops to enable it. 99.9%
of sysops want a "self-packing" mail base, but any sysop that has recurring issues with mailbase corruption (Josh Renaud?) might want to try "fast allocation" as an option - though they will need to periodically pack the mail base to save disk space.

SMB Fast allocation storage is backwards compatible with self-packing, so a sysop can switch between the two storage methods without a problem.

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

https://gitlab.synchro.net/main/sbbs/-/commit/7e450dd10af20aa441ef0ce7
Modified Files:
src/sbbs3/scfg/scfgmsg.c
Log Message:
scfg: rich helpbuf for Message Areas > Message Options menu

Replace the three-line stub with per-option help for all 18 entries
(BBS ID, retry time, QWK packet limits, e-mail purging and dedup,
anonymous / quoting / upload / forward / kill-read toggles, real-name
delivery, signatures, deleted-message visibility, MailBase storage
method, guest scan depth).

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

https://gitlab.synchro.net/main/sbbs/-/commit/e75f7c0b8aca24046c1a5d0a
Modified Files:
src/sbbs3/scfg/scfgmsg.c
Log Message:
SCFG: apply the full sub record when importing *subs.ini

read_sub_ini_section() parses every field of a sub-board from the .ini
section, but the import copy-back only ran the generic identity-only path (code, names, newsgroup, area_tag, data_dir). So *subs.ini import
silently dropped the access-requirement strings, settings flags, print
modes, QWK conference number, max-message limits, taglines, post
semaphore, and FidoNet address - defeating the purpose of a format meant
to carry complete sub-board configuration between BBSes.

Introduced in reef-31-feed (cfb32e03f5), which added *subs.ini import but
never extended the copy-back to apply the fuller parsed record.

Route *subs.ini through the same field-by-field copy as subs.txt (added
in the previous commit), plus the fields the .ini format carries that the legacy text format can't: qwk_conf, print_mode, print_mode_neg, and
area_tag. ptridx stays preserved for both.

As a side effect, *subs.ini import no longer applies the "long name
contains 'sysop' and 'only' -> append SYSOP to the access requirements" heuristic; that inference is for formats with no ARS field, whereas
*subs.ini carries the access requirements explicitly.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

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