These are wrappers for the C++ function: sbbs::getnodetopage() and will
be used by the privatemsg.js (Ctrl-P handler) and possibly other node/user
interaction stuff in the future.

already with a call to getnodedat()).
When using the MSVC2017 CRTL, a lock() of a region that was previously
locked is a blocking call causing major slowness in the MSVC2017 build.
This just reverses the 1-line commit from 16 years ago in rev 1.10 of this file.

When using the MSVC2017 CRTL, an unlock() of a region that was not previously
locked is a blocking call causing major slowness in the MSVC2017 build.

not exist), set the user->number to 0 before returning as many callers of this
function do not check the return value, just the value of user->number after
it returns (ugh). This problem was discovered when running a fresh install,
typing "1" at the Login prompt and immediately getting a "Time's Up" message
and a disconnect - only happens when there's no data/user.dat file.

getnodedat() - don't try to unlock the node.dab file unless the read() fails.
When using the MSVC2017 CRTL, an unlock() of a region that was not previously
locked is a blocking call causing major slowness in the MSVC2017 build.

putmsgptrs() - cleans up obsolete sections in the data/user/*.subs files now.
So if you go from say 10,000 sub-boards to 2,000, it won't have to load and
search through the extra 8,000 invalid subs (once the file is re-written upon
log-off). This requires an updated xpdev build (for iniAppendSectionWithKeys)

fixmsgptrs() - if the msgbase index can't be opened or the last index record
cannot be read (e.g. there isn't one), insure the msg-scan pointer value is
set to 0 (not ~0).

destination addresses): this feature messed up the smeg@ address book
Baja module.
Use the email_sec.js module if you want this feature.

or else we may end up with user names in log msgs that don't apply.

removed.

("Node X", user alias, etc.) - so removing a lot of the redundancies.
Also, logging the current timed event code and other prefixes in the
event thread log messages - something I've wanted for a while now.
There might be some redundant "Node X" strings, so if you see some funny
looking log message, please let me know.

fix the resulting warnings.

debug log msg.

more (!) by removing the sections from the total file string list, once parsed.
Fixed a couple of minor and unlikely off-by-one errors with message ptrs
based on date/time.

option - the sysop chat availability is now controlled via semaphore
file (ctrl/sysavail.chat).

each section (sub-code) once. Should cut the search/parse algorithm by 66%
(since there's 3 keys/values we're searching for, per sub).

users) and adjusting scan ptrs by date or set to "Last msg" while online:
- speed (on my system, reduced from 12 to < 2 seconds)
  This involved 2 enhancements: check msgbase index file timestamp (fast)
  before opening any files. When opening the msgbase, just open the index
  file (no other msgbase files) - required new smblib function: smb_open_index.
- fixed off-by-one when setting by date (when setting the new-scan ptr to
  Jan-1-2018, you want that first message posted on/after Jan-1-2018 to be
  found as "new", not the first message posted *after* that date.
- re-added the fixmsgptrs() call in putmsgptrs(), inadvertently removed
  in the .ixb -> .ini ptr storage update in rev 1.192 of userdat.c.

Most of the copyright years in the source code were misleading (the date of
most recent publish was actually later) and all were unnecessary. I've been
removing copyright years piecemeal, for a long time, but I decided it was time
to just perform a bulk search and (mostly) replace. In some cases, I left
old copyright years on files that either are not used (and soon to be removed)
or obsolete and unlikely to ever be touched again (e.g. Win9x FOSSIL VXD). Some
of the runtime binaries still contain copyright years and those were updated to
2018.

output. Example:
File size        : 7,128,414 (6.8M) bytes

matches the search spec, the 'D' batch-flagging command would invoke the
downloadfile() method which confusingly, doesn't actually download (send)
the file, but instead performs all the post-download functions needed. So
the user would just see "<filename> sent." and possibly lose some credits
without actually receiving the file.

The "official" log line format is (as of right now at least):
"[socket] [protocol] [user/host-ID] [! if error]message"
Hopefully I can remember that when I add new log messages.

Also setting the protocol to SMTPS, POP3S, SEND/TLS, when appropriate and
passing it around to pretty much any function that can log a message.
Added debug-level log output when the mail sever is sending message body text
(every 100 lines).

The "max lines" parameter value passed to sockmsgtxt was using the cryptlib
session number - this would truncate sent email bodies to some seemingly
random number of lines. Introduced in rev 1.622.
Also added a couple of helpful log lines to let the log-reader know if/when
TLS was successfully negotiated for sendmail sessions.

(defaults to 10 megabytes, "10M").
When SBBSecho starts up, if this minimum amount of free space is not
available in any of the following directories, SBBSecho will display an
error and immediately exit:
- data directory (in SCFG)
- logs directory (in SCFG)
- netmail directory (in SCFG)
- outbound directory (from sbbsecho.ini)
- temp directory
- each linked-node's outbox, if configured

If the sysop runs out of disk space for some reason, at least SBBSecho
won't contribute to the problem.

prompts with the conditional beep enabled only with the '-b' option
(silent by default). Thanks to Nelgin.

with smb_t.status.