Support STARTTLS in SMTP and STLS in POP3.  This includes the sendmail
thread.  Clients can now be configured to use STARTTLS with Synchronet
mail services, and Synchronet will attempt to deliver securely when
possible (though it will fall back to plain text delivery when necessary.)

This touches a *lot* of mail server stuff, so some instability is not
unlikely.

Of course, RFC8314 (Jan, 2018) officially recommends implicit TLS on the TLS
ports now, so support for that should be next.

iniGetValue() boolean parsing (by passing a default value of 'false').

line 359: ReferenceError: typeoof is not defined

TypeError: this.node[sec].poll.toUpperCase is not a function

it's TLS (SSL).

This will get replaced with actualy config things once we ascertain that
it works properly and stuff.

TLS servers without all of them needing to separately load the ssl certificate.

It's destroyed in free_scfg(), and the config *must* be prepped both to
destroy the certificate and to load it.  This is because the "no cert"
value is -1, not 0, so the prepped flag is all we really have to indicate
if it's zero because it's a valid certificate or zero because no certificate
has been loaded.

the ZYZ BinkP value (e.g. with the sysop's real name instead of alias).

in your accepted syntax.

certificate is generated.

Added an "install" command: "jsexec binkit install"

saving changes.

mark the session as secure.  Works around Radius/4.010/21.01.2005,13:56(Final-Release)/Win32
not sending the reccomended M_OK argument.

Nov-28-2017 (don't save .ini files with every change of log-levels), it was
quite easy for the visible log level controls and the actual log level (in the
startup structures) to get out-of-sync.

I'm pondering saving the selected log-level when recycling or something else,
but for now at least the visible controls match the real log level.

May fix infinite M_EOB ping-pong on some v1.1 connections.

paths end in a path separator since the calling scripts (e.g. binkit.js)
assume they do. This apparently is not a problem if you're still using
SBBSecho v2/sbbsecho.cfg however.

use sbbslist.js instead.

This allows using --import again later if something goes wrong.

and import certificate chains.

This supports two commands and one option:
--csr
	Supports multiple --domain example.com options (defaults to system.inet_addr)
	Generates a csr on stdout.
	jsexec certtool --domain example.com --domain www.example.com --csr > csr.pem

--import <file>
	Imports a certificate chain.  A certificate chain is two or more
	PEM certificates in a file... ie:
	-----BEGIN CERTIFICATE-----
        MIIFNzCCBB+gAwIBAgISA/+MFKRHU5G75Qe5a0tI9p2rMA0GCSqGSIb3DQEBCwUA
        -----END CERTIFICATE-----
        -----BEGIN CERTIFICATE-----
        MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/
        -----END CERTIFICATE-----
        If the entire chain isn't present, it will be imported, but the TLS
	server won't validate properly.

This should be usable with Let's Encrypt stuff today.

it's true.  Log an error with the URL if it's not true and account creation
fails.

All of this as LOG_DEBUG.

(e.g. when downloading syncterm-src.tgz)

A second fix for the recursive make issue in src/sbbs3/targets.mk
(build of scfg, uedit, and umonitor).

recursive make of scfg, uedit, and umonitor.