<useron alias>, so we need to include it in the log message here if we
want the current user's alias included in event related log messages
(e.g. unpacking QWK-REP packages).

error messages.

251 response which was made optional in RFC2821 - to address privacy
concerns.

Incremented copyright year to 2019.

Incremented copyright year to 2019.

change the errormsg() call to just a debug-level log message. These failures
are expected if the local system (QWKnet node) didn't get the original poll
message, for example.
Continue to log these errors when encountered on a QWKhub (where they are
less expected since a hub should normally have a deeper history of
messages/polls than nodes will).

has type 'size_t'

Mail.*LstHdr text strings.

decide that.

data-type and API. This works better for terminals < 80 cols in width and has
some other improvements with inserting/deleting lines using the arrow keys,
but still not great.
No longer does tab-expansion on text read from a file - may want to add that
back in <shrug>.

Added a command key (!) to reverse the mail list sort order.

normal (chronological) order of the returned mail indexes.

quote files (ain't nobody got time for that!).

requests sent to "SBBSecho" again. SBBSecho used to allow this back in
v3.02 (Nov-2017) and earlier versions, but was removed for loop-safety
since AreaMgr notifications and responses are sent from "SBBSecho", but
we have bot-loop protection built in, so that should be okay.

skip any spaces before parsing the value (for CGI supplied headers).

If we get one of these statuses from via a CGI, assume we have good headers.

the file.can. Log a message when receiving or filtering files received via
QWK/REP.

timeout) when opening the mail base for statistics purposes. This should
solve the problem of long delays during logon or sbbsctrl shutdown while
mail base maintenance is being performed.

line endings (sole-LF) instead of CR/LF line endings.
Thanks to Mark Lewis (wkitty42) for the bug report!

- include errno description (strerror output)
- exclude (redundant) node number

created) before this funciton is called, so we can't *always* delete
the quote file. Delete it if restoring a draft or if quoting is disabled
only.

going to recover a draft message or quote a source message or whatever.
Lingering QUOTES.TXT files interferred with recovering draft messages.

in GET responses when Connection: Keep-Alive is not enabled.

HTTP-Version value we send (no functional change). My intepretation is we
should be sending either nothing or "HTTP/1.1" here, never "HTTP/1.0". This
interpretation appears to match the behavior of other web servers
(e.g. Apache httpd).

expands to "on" or "off" based on user's split-screen private chat setting.

PAGER (expands to "on" or "off" to indicate chat page enable status)
ALERTS (expands to "on or "off" to indicate activity alert enable status)

description/documentation more closely. That is, if there is an INTL kludge
line in the incoming netmail message, there will be no "fuzzy" zone matching.
This means that Fuzzy Zone operation will only apply to netmail messages that
do *not* have an INTL kludge line (which specifies the source and destination
zones already). This solves the problem reported by Mark Lewis with
unexpected Fuzzy Zone behavior (when enabled), it was over-riding the
source zone number even though it was specified (via INTL kludge) in the
original netmail message body.

CPU utilization to get a large file copy completed quicker.