https://gitlab.synchro.net/main/sbbs/-/commit/fa91e9074a14a892557b7606
Modified Files:
src/sbbs3/qwktomsg.cpp
Log Message:
Default FTN charset to CP437 (not ASCII) for QWK-imported messages

A QWKnet tagline usually contains CP437 character 254 and if/when appended to
a message during export, would "convert" the message to CP437 thus making the "ASCII" charset advertisement incorrect.

If a FIDO CHARSET value was already specified (e.g. in HEADERS.DAT), that
value will (still) not be overridden. So the *original* import via QWK (before it gets exported to a QWKnet) is where this change will take effect.

Fix for issue #741
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/984c371ae383e19fcdb99cae
Modified Files:
src/sbbs3/qwktomsg.cpp
Log Message:
Don't use QWK reply message date unless time zone is also specified

For regular user QWK Relpy packet uploads only, if no timezone is specified (e.g. via @TZ kludge or HEADERS.DAT), then over-ride the message's "posted" date/time with the current date/time since we're going to set the message's timezone to the BBS's local timezone as well.

This is a fix for issue #783 reported by Chris Jacobs.

If/when we support user-specified timezones, then this likely would be a
place where we'd want to use the user's timezone.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)