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).

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

https://gitlab.synchro.net/main/sbbs/-/commit/8c70994e75d4ba6960faca58
Modified Files:
src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h
Log Message:
Support SBBSecho robots that use .msg files directly

Each configured robot now has a "Uses MSG File" option (defaults to false) and if set to true, either the initial .msg file will be retained or if imported from a packet will be exported to .msg format, thus skipping the "mail base" phase.

Make the default robot attributes value 0x20 (In-transit) since that prevent repeated imports and exports of the same mail message.

I think this addresses issue #1001

With the robot attributes set to 0, I would've expected a .msg-using robot to still work (before this change) via the path: .pkt->mail base->.msg or even .msg->mail base->.msg. But now we don't need the mail base phase.

Increase SBBSecho version to 3.31

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