Set the client protocol to "FTPS" upon successful TLS startup in the control connection (response to the AUTH TLS command from the client). Log some messages indicating FTPS was attempted or successful.

This seems to be misguided and would only increase the chances of a DoS-type attack on TCP session resources.

A second 3-second delay upon malloc failure is also removed.

Also, disable the QWK packet creation timeout edit when QWK packet
download support is disabled.

Support optional limit on concurrent connections from the same IP address to the FTP server by setting MaxConcurrentConnections in the [ftp] section of sbbs.ini. Unlike the mail server and the terminal server, this concurrent-connection count is not discounted by the number of authenticated logins. The default value is 0 (unlimited).

This closes issue #156

Each list mutex is destroyed in the call to listFree() in cleanup(). Without a call to listInit(), the mutex is not recreated and thus the lists are no longer mutex-protected after a recycle. No negative consequences were observed from this issue, but a potential issue it is (was).

This project morphed into SEXYZ a long, long time ago.

Don't search more than 1500 days in the future for a next-run date match. This handles erroneous or just bizarre timed event configurations such as February-29 (once ever leap year) or April-31 (never).

Don't set to 0xff to begin with, in SCFG.

Introduced with "use strict" commit (unsurprisingly).

Set sysop_available and/or sysop_unavailable in the [logon] section of your
modopts.ini to a comma-separated list of strings to pick at random and replace
the default text.dat LiSysopAvailable and LiSysopNotAvailable strings during
logon (displayed as part of the "logon info" block near the end of the
hard-coded logon sequence).

Inspired by the SYSAVAIL.C modification that I used to use with my own
custom ("INHOUSE") build of Synchronet, this is now available for all sysops
to replace "Available" or "Not Available" with a random funny/smart phrase of
your choosing (but without commas; a separate delimeter could be used if that
is a problem).

Print the Mbyte estimate.

.. when packing a QWK packet (on Win32, was always reported 0 messages per second).

A bit of redundant code cleanup, no expected functional change.

Leave it to new users to do weird stuff and define a mail-forward loop. Outsmart them and don't allow forwarding when the destination is a local address (QWKnet, FidoNet, or Internet).

Exposes the FTN BBSID value from the message header (if there is one).

This repetition would happen when the hub's address was the same as their
'fido' key value.

Update to previous commit.

Advertise the system's QWK-ID (a.k.a. BBS ID) in exported echomail messages. This will allow correlation of avatars that were imported via SYNCDATA carried via QWKnet (e.g. DOVE-Net) with messages imported from those same BBSes via FTN.

The alternative was to have SYNCDATA Avatar messages include all the AKAs of each BBS (in the body text), but that was looking like a rather complicated solution. This approach (the BBSID kludge) seems a much simpler solution.

I still need to implement the JS side of this solution however (for avatar lookups using the FTN BBSID), but this was the first important step.

Chasing down the cause of:
term Node 2 <Guest> Error: invalid y coordinate: 0

As was observed by David Westphalen on Facebook:

The call numbers are messed up on the main menu. Says "Calls 8702 of 1615".
Is there a way to fix this? Shouldn't it say "Calls 1615 of 8702"?

The numbers were just from different statistics. They should have more
correlation to each other now.

Not sure how Zharvek triggers this error using the module, but he managed to
do it twice, so add a bit of paranoia-check.

The days of browsers rendering HTML served-up via FTP are over, so remove this feature. This also removes all JavaScript support from the FTP server and that is a bit odd as it was one of the first Synchronet components for which I added JS support.

Removing this feature was pretty painless; much easier than adding it was. The main motivation was less cruft to port to the file base in the works. There should be no more references to 00index.html anywhere at this point. Bye bye cool feature, we'll miss you.

A couple of stragglers here, the isalnum() call caught by an MSVC exception.

Jump the time forward (in 24-hour chunks) to find the next date/time the event will run rather than just adding 24-hours and assuming it's an event that runs every day (of the week or month) at a specific time.

Also, expose the next-run-date/time for an event as a new `next_run` property for `xtrn_area.event[]` (in `time_t` format) for easier debugging of these kinds of issues.
Also expose the error log level as a new property: `error_level` while we're here.

We only use NSPR to build libmozjs, not to build sbbs. So define our own MIN and MAX macros if they're not already defined (e.g. from sys/param.h on *nix). Such a simple can o' worms, but wormful can it was.