If using xtrn_head, display section name/header as well

See merge request !67

The following properties would only reflect the status at the time the file_area object was initialized:
    - can_access
    - can_upload
    - can_download
    - is_operator
    - is_exempt

 ... so if changes were made the user while online, for example, these property values would *not* also change to reflect the current state.

The lib[] and lib_list[] 'can_access' properties still have this flaw.

Also: Add a new "files" property to the dir[] and dir_list[] objects to report the current number of files in each directory database.

can_access/upload/download and is_operator
similar to what we already had defined for sub-boards

If you aren't using a custom xtrn menu head per section, then you might fall back on a global one...but the prior logic would not display the actual section heading if it used a global (xtrn_head) file. If you are using xtrn_head, you don't have anything in there with a section name, so display the section name from code again

The following properties would only reflect the status at the time the
msg_area object was initialized:
- can_access
- can_read
- can_post
- is_operator
- is_moderated

... so if changes were made the user while online, for example, these
property values would *not* also change to reflect the current state.

The grp[] and grp_list[] 'can_access' properties still have this flaw.

Also: Add a new "posts" property to the sub[] and sub_list[] objects to
report the current number of posted messages (quicker than opening a MsgBase
instance).

This is a really stupid way of drawing the highlight, but fixing it
this way is trivial vs. refactoring all the ugly.

Fixes #192

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