LoginAttemptBanDuration value. Allows short-hand multipliers: YWDHMS
(year, week, day, hour, minute, second) and fractions (e.g. "2.5H").

size_t.

By default, after 20 consecutive (unique) failed login attempts, *or*
a failed login attempt wtih a name from the name.can filter file.
The default temporary ban duration is 10 minutes.
The temporary ban thershold is configurable via LoginAttemptTempBanThreshold
in sbbs.ini and the ban duration is configurable via LoginAttemptTempBanDuration
(in seconds).

prepend the text directory).

By default, after 20 consecutive (unique) failed login attempts, *or*
a failed login attempt wtih a name from the name.can filter file.
The default temporary ban duration is 10 minutes.
The temporary ban thershold is configurable via LoginAttemptTempBanThreshold
in sbbs.ini and the ban duration is configurable via LoginAttemptTempBanDuration
(in seconds).

calling Socket.bind() with an undefined hostname parameter would result in a
getaddrinfo() failure, e.g. on Windows, WSAHOST_NOT_FOUND 11001
The ircd.js passes the value of server.interface_ip_address to socket.bind()
and when run from jsexec, this property is not defined. So you couldn't run the
ircd from jsexec or you'd get "!Error 0 binding socket to TCP port xxx".
Also now setting the socket last_error value upon getaddrinfo() failure so
if there is a failure, the error message won't include the erroneous "Error 0".

underlying send() function is free to send a subset of the bytes, and
occasionally does (especially on non-blocking sockets).  The return value
was true if all bytes were sent or false if not all bytes were sent.

The new behaviour is to return the number of bytes sent or null on failure.

This is mostly compatible with existing code which appears to universally use
if (!sock.send(str))

Cases where it's not compatible are when a zero-length string is sent.  The
handling of errors is slightly different now too... previously, if you
retransmitted on failure, the stream would "stutter" now it will have
"holes".

StrictPacketPasswords (default is "true").
If you want SBBSecho v3 to behave like SBBSecho v2 with regards to packet
passwords for linked-nodes with *no* configured packet password, set this value
to "true" in your sbbsecho.ini file. I don't recommend doing this if you care
about the "security" of your echomail, but some sysops have been bitten by the
strict enforcement of the configured password in SBBSecho v3.

I also fixed some (but not all) of the signed/unsigned value comparison
warnings reported by msvc2013. Hopefully this didn't introduce any stupid bugs.

This has been broken (did not track consecutive failed login attempts from
the same client IP address) since the IPv6 commit of Aug-2015. I only noticed
this wasn't working when I was documenting the "auto-block hackers" feature
on the Wiki and noticed that every failed login (even those from the same IP)
was listed as a separate entry in the "Failed Logins" list (e.g.
sbbsctrl->View->Login Attempts). Ugh.

value (of "SYSOP") for the DefaultRecipient key. If it's blank (nobody)
just leave it blank.

(paraphrased) encountered when performing a echomail rescan for link(s):
When a packet reaches the configured "maximum packet size", finalize the
packet immediately (terminate the packet and close the file) rather than
waiting until the very end of all SBBSecho operations.

areafix responses to %LIST and %UNLINKED requests. If the same echo tag
was listed in multiple additional echolists, it was possible it would
appear multiple times in the areafix response list.

after the load(), throw an error.

load()s filename if propname is defined in scope (scope defaults to this.

Returns null if the file is not load()ed or the return value from load()
(last value of require()d file) if it is.

blowing up unexpectedly because of load() or a global hotkey event.

Don't free undefined variables.

Recipient using echocfg.

non-zero-length string, will touch/create that file if outgoing data has
been processed.

Intended to allow the mailer to scan as soon as outgoing data is available
rather than having it wait for the next normally scheduled scan.

Note, if using this feature as the *only* way to trigger a scan (not
reccomended), any other sources of outgoing data (such as hatching files,
interBBS doors, etc) will also need to touch this semaphore or they will
not be sent until sbbsecho processes outgoing data.

We can't pass a const char * to FREE_AND_NULL, so remove const qualifier
rather than not use FREE_AND_NULL() here.

Back out echocfg.c changes.

With this option enabled, zone/domain mappings from ctrl/ftn_domains.ini are
used to get the outbound directory name, and the orig/dest domains for type
2.2 packets.

This allows supporting 5D addressing in sbbsecho when zones do no overlap
between domains (the normal case).

longer used by SBBSecho (as of v3) and will just confuse sysops if left here.
If you're still using SBBSecho v2, just set the inbound directory in echocfg
(sbbsecho.cfg file) instead and all will be fine.

no longer uses it (as of v3).

separator (/ or \) before checking for mutex file.
Don't require an exact match [node:x] section in sbbsecho.ini for every link
in the area file (areas.bbs).

but it doesn't look like that's used here...

try to parse the link addresses.
Example invalid line (echo-tag cannot contain spaces):
VADA           Virtual Advanced BBS Support 1:261/38

toggle "EchomailNotify" setting in sbbsecho.ini.
Also changed "NetMail Options" menu to "NetMail Settings" and "EchoMail
Options" to "EchoMail Settings".

If one of the link addresses had a point specified (e.g. ".1") then all the
addresses would get that point appended to them.
Fixed atofaddr(): stop parsing the address at the *first* whitespace char.

Display parsed FTN addresss instead of string from AREAS.BBS file. Hopefully
this provides a better clue as to what is happening with his configuration.

anything in msgtoqwk() since in the case of packing REP packets for QWK
networking, there is no "current user" and this led to a bug where
(at least sometimes, in some scenarios) the REP packet would be created in
QWK Extended (QWKE) mode leading to other problems on the hub. QWKE mode
is not needed for Synchronet/QWKnet since we have the HEADERS.DAT file
which covers all the header fields otherwise "fixed" via QWKE kludge lines.
If the QWKnet account on the Synchronet hub was not configured for QWKE
mode, then QWKE kludge lines (e.g. "Subject:") could be interpretted as
body text and other kludge lines (e.g. @VIA, @TZ, etc.) would not be parsed
and removed from the imported body text, leading to extraneous metadata in
QWK-networked messages. As a work-around for QWKnet nodes using existing
versions of SBBS (without this fix), enable QWKE mode for your QWKnet acount
on the hub (e.g. VERT).

- If you are upgrading from SBBSecho v2.x, run "jsexec sbbsecho_upgrade.js"
  to convert your ctrl/sbbsecho.cfg to the new ctrl/sbbsecho.ini.
- Major code overhaul/re-write/modernization
- ArcMail/Attach/FD mode NOT TESTED: beware if you're using this style mailer!
- New features:
+ Easier to manage configuration file (sbbsecho.ini)
+ Multiple sysop aliases supported (for receiving netmail)
+ Mutual-exclusion-lock file (ctrl/sbbsecho.bsy) to prevent accidental
   concurrent invocations of SBBSecho
+ FileBoxes (optional inbox and outbox per node, only in BSO mode)
+ EchoList 4-char "flags" are now 25-char "keys" and much easier to deal with
+ Maximum msg age configurable for NetMail and EchoMail (separately)
+ Configurable "Area Manager" user name (default: SYSOP)
+ Configurable "Default Recipient" for netmail (default: SYSOP)
+ Far fewer command-line options, more settings in EchoCfg
+ Old command-lines will still work, but most of the legacy options are just
   ignored now. Run "sbbsecho -?" for command-line syntax and options.
Other improvements:
+ All Fido kludes, including PATH and SEEN-BY lines are stored in the
   Synchronet Message Base, always (can't be disabled)
+ Better security for inbound EchoMail (passwords are always enforced)
+ More comprehensive log output (the log output is more of a priority than the
  console output now)
+ Increased accuracy for recipient user name/alias matching
+ Higher-level of uniqueness to generated packet filenames
+ All temporary files (e.g. packets in process) are created in an
   SBBSecho-specific temporary file directory
+ No longer auto-terminates when any local key is pressed: use Ctrl-C/Break
   instead to initiate a graceful premature termination
+ Much more help text in echocfg
+ Better organization of settings in echocfg
+ Optional per-node "comments" for use in echocfg->Linked Nodes