message body is UTF-8 encoded. This works for either messages received via FTN
(with the "CHRS: UTF-8" control paragraph) or MIME-encoded messages (e.g.
Internet e-mail).

This is to be used by things to display messages. If the viewer (e.g. user's
terminal) supports UTF-8, just send through as-is. If not, translation (e.g. to
CP437) or filtering may be needed.

headers haven't been sent yet.

header, don't calculate either one and let the script shoot itself in the
foot.

Also, if a Location header is set, try an internal redirect rather than
forcing the client to handle it.

Now scripts can avoid chunked mode by specifying a correct content-length
if the content-length is wrong though, Bad Things will happen.

When importing QWK messages (e.g. from a QWKnet packet), the statistics logged:
  "Imported n QWK msgs in x seconds (y msgs/sec)"
would logged for all but the last conference (sub-board) being imported into.
Log the import statistics at the end of the import process if a sub-board is
currently open and messages were imported.
Also, log a message when importing QWK netmail.
Thanks to Mark Lewis' eagle-eye, noticing the total messages imported didn't
match all the stats log messages total.

of the bad MAC alerts.

This *should* fix LetSynchCrypt.js as well as other issues.

for additional headers and the final terminating CRLF.

Moved crc* and md5.* to src/hash

Removed v4upgrade from sbbs project.

crc* and md5.* was moved to src/hash
base64.* was moved to src/encode

You'll need to perform a clean rebuild.

You will need to perform a clean rebuild.

You will need to perform a clean rebuild.

You'll need to perform a clean build.

You'll need to perform a clean build.