reached (connections with a successful login aren't counted).

- strListTruncateStrings()
- strListTruncateTrailingWhitespaces()
- strListTruncateTrailingLineEndings()

1. Randomize the last 3 characters of the internal code to generate a unique
   internal code.
2. Attempt to skip sub-directory names when generating long/short names from
   imported path, if no sub-dirs are in the path, then just right-justify the
   truncated path - trying to generate meaninful long/short names from long
   paths.
3. Do not allow duplicate paths to be imported into the same library.
4. Skip (do not import) directory entries that are > 63 chars in length.
5. Stop importing if/when total dirs >= MAX_DIRS (65534).

If anybody actually hit these limits I'd be impressed, but it's not impossible.
65535 (-1 as an int16_t) is a special value used to indicate an "invalid" item.

1. added option to import empty sub-directories (previously empty subdirs were
    always ignored).
2. attempt to generate a unique internal code when the auto-generated internal
    code (based on the characters in path) is not unique.
3. display "Scannnig Directories..." popup since this can take a while
    (especially on network drives and especially recurisvely).

Note: if you're importing lots of deeply nested subdirs, it's likely that a
unique internal code can't be generated (from the path) for all subdirs.
A randomly generated internal code might be an option if this is really
a problem for any sysops.

Also updated the brace style of this .c file, finally.

globally (using a new macro in sbbbsdefs.h: STR_UNKNOWN_USER). "<unknown>"
in some contexts was too vague (e.g. the 'c' command output from the sbbs
console).

   not daemonized: log output would be repeated (once with a timestamp in
   the log string, once without). Now direct calls to lputs/lprintf from
   sbbscon.c won't go to syslog (in this mode), but I think that's okay.
2. Change the prompt when terminating the servers: replace the ?=help and
   colon implying you can enter commands with just "Termianting..." since
   you can't actually type commands while a terminate is in progress.
3. Output the inactivity timeout values when waiting for servers to
   terminate (e.g. because they'res till in use).
4. Report IP addresses in square-brackes in the client ('c' command) output
   to differentiate from hostnames.

other things to detect/display the actual filename (when different than
what's stored in the database).

This should fix KK4QBN's problem with Windows->Linux migration of file bases
of Nighowl CDs (where the files.bbs contain lowercase filenames, but the files
themselves are uppercase).

and other improvements (filtering and stuff).

Version 1.17 beta 39: Made an adjustment for ANSI content detection for when to convert to Synchronet codes to make the message look okay in ANSI scrolling mode

Version 1.17 beta 38: When searching for messages (by text, from name, to name, or to you), it now uses the get_all_msg_headers() function if that function is available (otherwise, it will fall back to going through all messages one-by-one in the messagebase object).  With the get_all_msg_headers() function, it can get vote tally information so that information can be displayed when viewing the messages.

Version 1.17 beta 37: Added some more checking for ANSI content for certain messages to convert ANSI to Synchronet codes to prevent messages being displayed mangled in the ANSI scrolling interface.

Version 0.18 beta: Fixed a coloring issue when outputting who voted on a poll when more than 1 person voted on it.

Version 1.17 beta 36: Updated the newscan loop to wait 10ms at the end of the loop to avoid causing CPU usage to go high while the newscan loop is running (CPU usage was getting to 99% on my BBS system).  With the 10ms wait, CPU usage went down to 65-70% on my BBS system, so it seems this should help keep the CPU workload from getting so high.

Added (back) the '-d' command-line option to disable the deletion of processed
(e.g. imported) inbound netmail messages.
- This option has no effect if DeleteNetmail is set to "false" in sbbsecho.ini.
- This option *only* disables deletion of incoming netmail (no effect on
  outbound netmail deletion)
- In SBBSecho v2, the '-d' option disabled all netmail deletion, even though
  the help output only mentioned "netmail after import" (it was wrong).

Version 1.17 beta 35: Updated the threshold for the percentage of ANSI codes to convert to Synchronet (& strip out any ANSI that's difficult to convert) rather than display as ANSI (previous was 6%, now 7%), due to a message with ~6.4% ANSI codes.

update the file path in the message subject to point to the inbound directory
where the packet was found.

Version 1.17 beta 34: Updated the way it deals with rogue ANSI codes that seem to be added to certain messages (including cursor movement characters) which probably weren't intended to be there, which can mess up the display of messages when using the scrolling interface.

name(s) are zero-length strings.

attribute for netmail (both *.msg and in the mail base). This option should
*not* be used when the DeleteNetmail option is enabled (set to 'Yes').
A warning will be logged in this configuration as dupe netmail msgs may be
sent in that case.

by Bill McGarrity.

number is particularly interesting to me given the error's he reported seeing.

sbbsecho.h:186:7: warning: array æpktTypeStringListÆ assumed to have one element
Warning: size of symbol `pktTypeStringList' changed from 8 in .../rechocfg.o

For packet creation, the only difference (from Type-2+) is with packets created
from point nodes: the origNet field won't be set to 0xffff (as is the case with
FSC-48, Type-2+ packets). The auxNet field is now always set to the originating
net (ala Squish) when configured for Type-2+ packet generation.
When importing Type-2e (FSC-39) packets, the detected/logged packet type may be
reported as "2e" for valid "2+" packets. This is normal and expected when the
originating node is not a point and the auxNet field is 0.
The second set of orig/dest zone fields in a type 2e/2+ pkt header will
now be used when importing if the old/QM orig/dest zone fields are 0.
Also, the originating point field may now be imported even if the auxNet field
is not used (origNet != 0xffff).

New umask sbbsecho.ini configuration option (global), maybe used to over-ride
the default *nix file creation mode mask (077), similar to sbbs.ini.

Use more formal terminology (e.g. "Type-2", not "type 2.0").

Version 0.17 beta: Updated one of the error messages, and made a screen drawing optimization when viewing poll results

- %RESCAN returns a different failure result if the requested echo is a
pass-through area (cannot be rescanned)
- %UNLINKED will return only the unlinked echoes even when an "additional
echolist" is utliized and the linked areas are all pass-through (for Bill).

If what appears to be a QWKnet addressed was passed, but the QWK-ID portion was
exactly 9 characters, a 1-byte stack corruption would occur as the 10-char
local variable (node) could be written with 11 chars (9-char QWK-ID, colon,
null). The reported issue happend when attempting to send netmail to
"hemo@ujointbbs" which is neither a valid Internet email address or a valid
QWKnet address.

Version 0.16 beta: Added a main menu option to display poll stats - Lists the polls by highest number of votes (highest first), and for each one, lists the answer(s) with the highest number of votes (highest first).

Version 1.17 beta 33: Improved to better handle message text that starts with "By <name> to <name> on <date>" - Some of those messages have ANSI codes (such as cursor movement codes, etc.) in that part of the text, which can mess up the display of the message when using the scrolling interface.

findstr() and findstr_in_list().
This means that rather than listing an IP address range using the traditional
wildcard characters (e.g. "192.168.1.*"), you could specify a subnet range
using CIDR notation (e.g. "192.168.1.0/24").
The '!' prefix is supported for CIDR match lines (for negated match results),
but no other wildcard/match characters are (e.g. '^', '~', or '*').
You can mix and match traditional match lines and CIDR match lines in the same
filter file.
IPv6 CIDR notation is not yet supported.