if it should be replaced.  It's common on FidoNet for replaces to have a
wildcard in it.

Also, add support for a new Handler key in tickit.ini.  This defines a file
which defines a Handle_TIC function and whose last statement isn't null.
The parsed TIC file is passed to this function and, if it returns true, the
file is assumed to be handled.

Version 1.13 beta 1.  Bug fix: Message number error when a new user starts reading messages.  Now checks for a seemily special value for the message number to avoid an error.

This will only import tic files from the secure inbound.  This is intended to
be used with IgnorePassword to limit the attack surface.

TIC passwords and not care if they match the packet password or not.

This imports *ALL* TIC files into the local file base, possibly overriding
existing files, so could be dangerous if you accept incoming TIC files from
anybody (which is the normal Fido setup).

Despite what fsp-1039.001 says, ALLFIX uses multiple Desc lines for long
descriptions, so Desc is *not* "A one line description of the file to be
distributed." and actually matches the Ldesc description.

Support both, but use the longest one.

has no password.

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

disconnect them (with a message) and log a notice.

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

instead of a string argument.  They perform the send/recv themselves using
a buffer.

This allows taking advantage of non-blocking sockets (in new Synchronet
builds) to be much more responsive.

This should still be compatible with the old socket.send implementation.
The *first* send it does in blocking mode and detects if it's the new or
old socket.send implementation and sets a global variable.  Future sends
know if it's the old or new API and treats them accordingly.

This may make new ircd running on an old build slightly less responsive
when a new user joins or when a new link is established since it blocks
all other ircd activity until the entire send queue has been transmitted (or
the connection is terminated).

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

Synchronet builds).  Use multiple send()s when needed.

correctly now though.

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

1) Don't use socket.recvline() on non-blocking sockets.  Instead, have
   the recvq object parse lines and receive 64k at a time.
2) Pass all received data through the recvq object rather than attempt
   to process one command per recv().
3) Pass all data sent on established connections through the sendq
   object rather than only use it if send() fails.
4) Move client throttling completely into ircd_user.js and out of
   the queue processing function so we don't accidentally throttle
   server connections.
5) send() the entire sendq contents as a single send() rather than one
   line per main loop.
6) Parse the entire recvq each time through the main loop.  This
   requires tracking when an unregistered connection is replaced by
   either a client or a server connection.