ERROR 2 (No such file or directory) opening stray packet: /sbbs/temp/sbbsecho/577ab8e4.pkt

(35 chars). Use macros for maximum internal code length and echo tag lengths.

1. Reported by Accession and Rastus: when linking/unlinking echoes via AreaFix,
    all the linked node addresses (in the areas.bbs file) would be changed to a
    garbage address (e.g. "16720:17235/19521.19551").
    Bug introduced in sbbsecho.c rev 3.13 (May-9-2016).

2. Reported by Accession:
    Extraneous debug-level log output (a log line for each echo that exists in
    the area file): "Adding areas for <addr> to path/to/areas.bbs" and
    "Removnig areas for <addr> from path/to/areas.bbs".
    Introduced way back in sbbsecho.c rev 1.249 (Apr-17-2014).
    Now, a single debug-level log entries is added per areafix change request
    for all adds (area linking) and then all deletions (area unlinking) which
    makes much more sense.

3. Observed in the code:
    When using AreaFix to modify the area file (areas.bbs), if a modified
    echo's internal code was 16 characters, exaclty, then no space would be
    added between the internal code and the echotag.
    This bug has apparently been possible since the introduction of internal
    code prefixes in 2003.

the LogTimeFormat key in sbbsecho.ini. The default is "%Y-%m-%d %H:%M:%S".
If you want the old (v2) time-stamp format, set this value to
"%m/%d/%y %H:%M:%S". Any/all valid strftime() specifiers may be used.

this is not a totally unexpected occurrance. No need to fill up the error.log.

Windows build of addfiles, et al.

- "Configure" menus (not working since the IPv6 commit) - both IPv4 and IPv6
   addresses may be specified (comma-separated), or multiple IPv4 addresses!
- Added new "Temp Ban" settings to Properites->Security tab.
- Added context (tab) sensitive "Help" button to Properties page
  (links to section on relevant wiki page).
- Every log window has a new right-click pop-up menu with 2 options:
  1. Copy Selected
  2. Copy All
  Hopefully it's obvious what these menu options do. :-)

- Never ban the server's own address
- Log the login attempt and last name attempted
- Use a compressed version of the HH:MM:SS "time remaining" portion of the log
  message

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

of parse_byte_count() and parse_duration()) and use them in ini_file.c

size_t.

address (family and address value, ignoring ports and other fields).

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).