Reinstated root directory variable, it actually helps in some cases.

I don't remember. Whisky. This thing is weird.

Don't delete non-property 'image' variable; set it to undefined instead.
Removed some convoluted and extraneous things I did years ago.
Various non-functional formatting things since I'm bored.

Spotted and fixed by Mark Lewis.

fixes the rendering of links like this one:
http://wiki.synchro.net/module:avatars

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

- no longer override the default send and receive socket buffers (limiting
  to 8Kbytes) - apparently modern TCP/IP stacks can use much larger buffers
  for sending large data more effeciently (quickly) over fast networks.
  Eliminating these 2 lines sped up the web server (e.g. wiki.synchro.net)
  page loads by a factor of 20+.
- enable TCP_NODELAY (disabling the Nagle algorithm) for *all* TCP sockets
  by default (not just telnet and rlogin servers).
  This helps performance of large data transfers a little bit too.

Big thanks to Deuce (!) for helping to debug and identify the cause of the
poor performance of the web server. I'm not sure why I/we were overriding
the default send/receive buffers but the old sockopts.cfg file introduced
in 2003 had 4Kbyte buffer sizes specified, and then when we switched to
sockopts.ini in 2005, the buffer sizes were increased to 8Kbytes. This might
have been the defaults for say, the Windows TCP/IP stack at the time, I
forget where I got those numbers from. Anyway, we shouldn't override them
without a good reason. And today, we definitely don't have a good reason
that I'm aware of. The default buffer sizes perform *much* better!

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.

Run addPoints against oroot (outbound) and any of its derivatives (outbound.002, etc.).
Should now find point directories in various outbounds.

in outbound dirs.
There remains a problem where only 'outbound.*' dirs will be scanned
for points, and points in 'outbound' (sans extension, ie. zone 1) will
not be found.

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

Not. Realize. That. - now fixed in the "LIST" and "NEWGROUPS" responses
(not that anyone actually uses the moderated message area feature of sbbs).

And just for Nelgin:
I added a -novotes experimental command-line option which if used, will
execute votes from the first & last message numbers included in the "LIST"
response. I'm curious if that makes any difference with tin (news reader) -
it will definitely slow down the response of the "LIST" command, so don't
use this "feature" without purpose.

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

always pretend otherwise.

Threw errors if 'val' was defined but non-string (no toUpperCase method).

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)

Handle 5D addresses (with or without point component).
Validate numeric address components and domains per FSP-1028.
Return value (if an object) now contains 'domain' property (if present).
Should fix processing of TICs with associated 5D addresses.
Introduces an unwieldy and overwrought regex.  Unf unf.
May break the entirety of fidomicrocyberchatnet.

"new message" detection (not the total number of articles) - so use the last
non-vote message number as the high water mark, not the msgbase.last_msg
value. For nelgin - Happy Turkey!

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.

The GROUP command reports the total number of articles in a group and we
were returning the total number of message indexes/headers, which includes
vote messages (not retrievable/viewable via NNTP) and messages flagged for
deletion (not retrievable/viewable via NNTP). So, count the actual
number of non-vote/deleted messages (index records) to use in the GROUP
response.

support active-users.json queries but don't report age and gender.

So I tested the following cases, which all pass:
cwd diralias -> 250 CWD command successful.
cwd /diralias -> 250 CWD command successful.
cwd /diralias/ -> 250 CWD command successful.
cwd /diralias/filename -> 550 filename: No such directory.
cwd /filealias -> 550 filealias: No such diretory.
cwd /filealias/ -> 550 : No such diretory.
retr filealias -> 150 Opening BINARY mode data connection for file transfer.
retr /filealias -> 150 Opening BINARY mode data connection for file transfer.

Hopefully is the end of the fixes for Chrome browser ftp weirdness
(tries to "CWD" to anything/everything to determine if it's a file or not).

- a CWD attempt to a /alias/filename would report 'success' to the client
  (Chrome web browser)
- the ftpalias.cfg file was left open in some instances

Version 1.62: Updated to save the message if the user disconnects, to support Synchronet's message draft feature that was added recently.