"Enable to" (TLS-related) error messages. This might help a little to
understand why these errors are happening and allow us to consider
lowering the log level(s) of commonly-occuring cases from LOG_ERR.

support though.

ESMTPS and ESMTPSA coming soon!

newsgroup property.

Note that any exascii is also illegal, but I don't feel like doing the
UTF-8 conversion thing today.  Also, you can manually stick in illegal
characters if you like... but then it's a feature, not a bug.

names from the Sync-JS object model (jsobjs.html) rather than from the
C/C++ source code (sbbsdefs.js). I got buy-in from mcmlxxix to make this
change, but any existing scripts which use the old names will need to be
changed or its likely that the .cnf record changes aren't going to be
made as intended (attn: CoA sysops).

struct field is not defined, write a zero-len string instead of 'undefined'.

Should fix possible issue with certificate being owned by root when
_THREAD_SUID_BROKEN is true (ie: Linux).

port number. This resolves the confusion that arises from multiple
identical "closing x Server socket on port n" lines in the log output.

(for subs and "all mail") and 4-digit message numbers. Subs with >9999 msgs
are not unheard of and its easy to accumulate that much mail in the mail base
these days. Just eliminated the ':' from the format line(s) to make room.

These waits could cause "bad" traffic (blocked, max client exceeded, etc)
to prevent/delay accept()ing "good" traffic on other services.

Ree (the author) said this old version should be removed from CVS.

Increase the verbosity of the "Log" checkbox label.

initialized (it's not).

I wasn't expecting to do this, since SFTP is often viewed as "better", but
SFTP doesn't have a specification, the implementations don't follow the
specification drafts that are out there, and the whole sharing a port between
file transfer and terminal server thing is irritating.

This has only been tested with lftp, but it seems to work.

created so graciously by Deuce, or as I like to call him: Mr. Crypto.

mail.sid corruption approximately around midnight (when delmail()) is
called as part of the "DAILY:" mail maintenance, I'm suspicious of this
function and while I haven't found any bugs, I did find (and now fixed)
lack of error checking in calls to smb_fsetlength() and smb_fwrite().

status.total_msgs value: if they don't match, don't add header & index
to the message base, it's apparently corrupted and we're only going to
make things worse as smb_putmsgidx() will fail (after we've stored the hdr)
with an "invalid index offset" error.

If caller doesn't zero-initialize smb_t, then the 'lock' member could've
been non-zero (garbage) and some functions would then not lock the SMB
header, used for protecting against corruption from multiple process or thread
modification of the same base.

for new TLS-related settings:
SubmissionsPort -> TLSSubmissionPort
POP3SPort -> TLSPOP3Port
USE_TLS_SUBMISSIONS_PORT -> TLS_SUBMISSION
USE_POP3S_PORT -> TLS_POP3
There was actuall a typo in the "USE_POP3S_PORT" string anyway. <shrug>

so that the smb_unlock() in main() doesn't fail and display the harmless
error:
Error -207 (smb_unlock 2 'No such file or directory' removing mail.lock)
unlocking mail