'l' (list messages), 'x' (dump index), 'r' (read msgs), and 'v' (view msgs)
commands by "days old", by specifying a negative number (in days).
(e.g. "smbutil r-30" would read messages posted within the past 30 days).
This was added to test the smb_getmsgidx_by_time() function, but has some
value otherwise I suppose.

recvFrame() is being called in a loop and only breaking on specific
conditions or if recvFrame returned undefined. Problem is, on timeout,
recvFrame returns null (and when using === comparision, undefined !== null).
Also added more debug output around sends where I suspect there might be
another potential infinite loop.

I suspect that connect() may be blocking and causing Al's reported issue
(A BinkIT poll never returns from the script and goes into some kind of
infinite busy loop).

file already exists.
Also, insure all log messages are prefixed with "BinkIT:".

don't try to (re)lock it, just return SMB_SUCCESS.

I honestly don't recall why I made this change, but it makes sense, so I'm
committing it finally.

algorithm now. Also, now returns the index offset of the matched index
(if found), negative error value otherwise.

I was testing something and noticed that the old smb_getmsgidx_by_time()
implementation could sometimes return the index of a message posted before
the requested time. That was fixed by re-writing the binary search logic.

Also, I found it useful in my testing to have this function return the
offset of the matching index (in addition to the index record itself), so
checks of the return value need to compare >= SMB_SUCCESS, not just ==
or != SMB_SUCCESS.

userdatdupe() to match the passed login-id (username):
*  This allows more permissive username matching, e.g. if your user name
   is "Analog Kid", you could login with "analogkid", "analog.kid" or
   "analog_kid", which is handy when passing a user name on the command
   line (e.g. to an ssh client) for example.
*  This is the same function used for Telnet logins via exec/login.js

so that the current sub/group and dir/lib short name is displayed as
part of the prompt.

@-codes within them. Previously, only if the entire mnemonic string was
comprised of an @-code would it be expanded, now any @-codes within will expand
as well.

experimental 'U' (View Unread-Only toggle) command. The 'U' command from
the e-mail menu (e.g. email_sec.js) works better than the toggle approach and
is probably all that is needed.
Also, the user number lookup in the User Edit bit is better at finding the
proper user account (e.g. for received netmail).

settings (keys): mx, ip, ip6

This allows you to specify a long string (e.g. address) here without
exceeding the 63 char external program command-line limit.

command-line.

from the Chat menu would immediately clear the screen and redisplay the
menu after displaying the change in the node's state. This was due to the
enhancement in rev 1.77 of con_out.cpp whereby we no longer increment
lncntr if the first lines displayed after a key-press are blank (who
cares if blank lines scroll off the screen?). That's fine and all, but the
auto-pause check in outchar(FF) would only auto-pause if the line-counter
was greater than *one* (has been this way since forever). So with the
enhancement in 1.77, a single non-blank line displayed after a key-press
was now not enough to trigger the auto-pause ([Hit a Key] prompt).
So I've changed the line-counter trigger value to greater than *zero*,
which means we could have some new excessive auto-pauses, but other places
where auto-pause wasn't working, should again.

One new excessive auto-pause was after the system password was entered at
the SY: prompt, so that fix is included in this commit.

ever know. Make the max subject length 70 (like Synchronet).

default location to find !include'd baja (*.inc) files. If you use the '-I'
option, it will override the environment variable setting. For Nelgin.

using SSH: the output from the program (file transfer driver, door game)
would reach the SSH client, but input from the client (or user) would not
reach the external program:
passthru_output_thread() - responsible for SSH input from the client/user
to be sent to a "raw" pass-through socket used by the external program,
had a reversed logic bug added around rev 1.686.
Problem was introduced as part of the cryptlib update/SSH overhaul of
early 2018. Thanks to Thumper @ THEWASTE for the bug report!

We should try to keep this list current to assist new sysops, so feedback is
welcome.
Also read/saved using EchoCfg, so it added all the supported keys with default
values.
Updated the default Inbound directory
 (from /binkd/inbound to ../fido/nonsecure)
Updated the default Outbound directory
 (from /binkd/outbound to ../fido/outbound)

Version 1.17: For the message area chooser, added a new configuration file option, showDatesInSubBoardList, that specifies whether or not to show the date & time of the latest message in the sub-boards.

the sysop must now enable this feature in SCFG->Networks->FidoNet.
Also, widen the FidoNet configuration menu in SCFG, display more FTN
addresses and the default origin line (part of it, at least) in the menu.

the sysop must now enable this feature in SCFG->Networks->FidoNet.

Version 1.17 beta 62: Made another fix to avoid the "Unknown destination" error when forwarding a message to a QWK-style address (such as "sysop@DIGDIST")

Version 1.17 beta 61: Fixed a bug where it would report an "unknown destination" error when trying to forward a message to a FTN-style email address.

for DOS programs (part of the USE_DOSEMU patch).

flags set manually in SCFG.

(messages which contain the RESCANNED control line) to downlinks.

Also renamed pkt_to_pkt() to write_to_pkts().

"Conditional jump or move depends on uninitialised value(s)"
Thanks, Nelgin.

If there's no zone in the specified path, the default_zone is used and that zone
is a decimal number, not a hexadecimal string, so running parseInt(...,16)
on it errorneously generates an incorrect outbound/FLO dir.
This should fix the problem reported by Al @ TRMB.

If the ctrl/ssl.cert file did not exist, the various TLS/SSL services would
fail to create it and (sometimes) log the "creating SSL context" error.
This problem was introduced with rev 1.30 (Mar-9) and the fix/patch
provided by Deuce via irc. Thanks to Psi-Jack for the bug report.

(previuosly) silently fail - in the sendmail_negotiate() and pop3_thread().
If get_ssl_cert() can return -1 withOUT setting the estr argument to a
non-NULL value, then we could still have silent failures (TBD).

shells: default, wwiv, wildcat, pcboard).
- Added (U)n-read messages only command.
- Renamed (U)pload file to (A)ttach file.

shells with a new single/unified JS module (email_sec.js):
- New (U)n-read mail read command ('A' is now for sending file attachments)
- I didn't update to the renegade shell since it has a custom menu file
- This module will work with older Synchronet builds, without netmail file
  attachments
- The old Baja code still works, however... less Baja = rounder Earth

(out of disk space?).