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

the number of decimal places in the resulting string.

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.

Created byte_estimate_to_str(), much like byte_count_to_str(), except the
byte count is rounded to the nearest tera/giga/mega/kilo-byte
(technically tebi/gibi/mebi/kibi-byte, but ugh, I'm old-sk00l!).

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.

Version 1.17 beta 63: Just before showing the message list or changing to another message area from the reader interface, it now writes "Loading..." in case there are a very large number of messages or sub-boards.

so remove 'errno' value (and corresponding error strings) from generated
/logged error messages. fseek(), read(), write(), open(), etc. do set errno
to a meaningful value, so we still log errno/strerror() in those failure
cases.

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

with smb_t.status.

log prefix solution.

can return false on error, which is >= 0, so this will just add 0 to the
length and keep on looping forever in that case.

not null on failure.

Also, is that some line ending weirdness?  *shrug*

'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.