contains a message hdr with a block length less than 2. Some versions of
Mystic apparently generate these REP packets and the errors are annoying
and there's really nothing the sysop can do about it but report back to
the user (or QWKnet node) that their packets contained some invalid
message headers.

is the likely cause of missing lines or "Aborted" messages upon saving
with the internal editor.

fancy structure initalization syntax here.

- separate sections with a blank line (when adding a section)
- place spaces around '=' in value assignments ("key = value").

this idea (web-server parsed html files with embedded JS) was never implemented
and made obsolete by web handlers (e.g. xjs).

anyway (here) and never implemented in the web server.

Oddly, the Identity Lookup checkbox was obscurring (hiding) the Hostname
Lookup checkbox, so that becomes visible/available again.

section of the sockopts.ini (if there is one) rather than the [tcp] or
[udp] sections. This resolves the errors:
      term xxxx !ERROR 95 setting socket option (TCP_NODELAY, 1) to 1
which started appearing after the TCP_NODELAY option was added to the
[tcp] section.

TCP connection actually failed. This bug only appeared to affect *nix
systems. This bug appears to be very old, introduced in rev 1.74 of
this file (Mar-2003) by yours truly.
From the Linux 'connect' man page:
EINPROGRESS
              The  socket  is  nonblocking  and the connection cannot be i
              completed immediately.  It is possible to select(2) or poll(2)
              for completion by selecting the socket for writing.  After
              select(2) indicates writability, use getsockopt(2) to read the
              SO_ERROR option at level SOL_SOCKET to determine whether
              connect() completed successfully (SO_ERROR is zero) or
              unsuccessfully (SO_ERROR is one of the usual error codes listed
              here, explaining the reason for the failure).

We weren't doing the 'getsockopt(SO_ERROR)' part.

Wrap all read_*_cfg() and write_*_cfg() calls with simple functions that
display popup messages that the Reading or Writing is being performed.
There was already copy/pasta everywhere for the Reading ... cnf files, but
nothing for writing.

getfname() on a path that ends in a slash, returns an empty string pointer.
Fixed-up some logging output around listing creations.

- use GLOB_MARK to eliminate calls to isdir() in loops
- use stat() rather than calls to flength() and fdate()
- don't call getfiledat() if getfileixb() failed
- profiling info-level log msgs added for index/listing generation, e.g.
  "detailed listing (3459 bytes) of /main/SBBS (45 files) created in 2 seconds"

Fixed bug with indexes generated for directories with the
"Access Files Not In Database" option enabled, files not in database were
excluded from the generated index (e.g. 00index, 00index.html).

rather than calling both flength() and fdate() (which both call stat()), just
call stat() once and use the result for both file size and date/time.

the beginning of a SAUCE record and the end of very old MS-DOS text files.
Added support for ESC[1;1f/H (home cursor) and ESC[0J (clear to EOS) sequences
(converted to the equivalent in Ctrl-A codes).
Output Ctrl-A characters in uppercase, as they were documented and as is
common practice.
Covert ESC[xB and ESC[xD to the appropriate Ctrl-A sequences rather than
converting to ASCII ctrl chars (CR, LF, BS).

Ctrl-AJ (clear to EOS)
Ctrl-A` (home cursor)

Oct-14-2018:
It turns out, PabloDraw actually inserts a Ctrl-AZ sequence at the end of .msg
(and presumably Synchronet .asc) files it edits - before the SAUCE record.
This resulted in a printed Ctrl-Z character (arrow pointing right) in most
terminals when viewing text/menu files created or edited with PabloDraw. :-(
So, now Ctrl-AZ (uppercase) will revert to the previous definition:
premature end-of-file (EOF)
and a Ctrl-Az (lowercase) will output a Ctrl-Z (substitute) character.
I'm not a big fan of case-sensitive Ctrl-A codes, but frankly, running out of
chars and I already started this pattern with the Ctrl-AF/f sequences.
Hopefully there's no existing software that is/was putting Ctrl-Az (lowercase)
in files, expecting that to trigger a premature EOF. I certainly was not.

when sending the "ANSI" output to stdout (and not a file).

WITH_SDL are not defined. This should fix JSDCOS builds for those without
libsdl1.2-dev installed - but really, you want SDL installed to get the
full docs, I think.

warning: ISO C++ forbids converting a string constant to 'char*'
and comparision between signed/unsigned int.
This does *not* address the reported build issue:
In function `_start':
(.text+0x20): undefined reference to `main'

this should fix the missing/misaligned 'bbs' property descriptions in
jsobjs.html

when a host-name lookup (getaddrinfo call) failed.

if the current user did not meet the access requirements, the corresponding
element if these associative arrays would be a random JS value, not the
actual program/section object.

(i.e. *nix) - I guess nobody really uses this utility.
Incremented version to 1.02.

<useron alias>, so we need to include it in the log message here if we
want the current user's alias included in event related log messages
(e.g. unpacking QWK-REP packages).

error messages.

251 response which was made optional in RFC2821 - to address privacy
concerns.

Incremented copyright year to 2019.

Incremented copyright year to 2019.

change the errormsg() call to just a debug-level log message. These failures
are expected if the local system (QWKnet node) didn't get the original poll
message, for example.
Continue to log these errors when encountered on a QWKhub (where they are
less expected since a hub should normally have a deeper history of
messages/polls than nodes will).