Lock the mail base while backing it up as part of the daily maintenance.

is ever written to disk, it'll be zeroes not garbage.
Also, NULL the subscan pointer after freeing (and don't free if it's NULL).

is set: this insures that uninitialized msg-scan ptrs/cfg won't be
written to disk unless a successful logon()/getmsgptrs() was called first.
This probably fixes the sighting that echicken reported where a failed
SSH login caused his sub-scan config file (data/user/0001.subs) to contain
uninitialized/garbage values.
logout() could be called from multiple places (e.g. JS and Baja modules),
even before a successful login is completed, so this sighting is not
entirely impractical.

With the change to smblib of March 14 (smbstr.c 1.29), netaddr_type() will
parse generic words as QWK-network addresses. The fix here is to only
attempt a net-type lookup if the 'to' field contains an '@'.

Front-pad cell contents with 2+ spaces for right align.
Pad each end with 2+ spaces for centre align.
No attempt has been made to make this play nicely with colspans,
but it does work with wrapped cells.

domain name from sbbsecho.ini), use its value as the domain name in the
lightbar list.
For nodelist_DomainName keys, use the DomainName portion as the domain
name in the lightbar list.
(Don't use the parsed domain name from the nodelist file's first line,
this is unreliable.)

log the filename and error if one occurs.

Replaces 'ftnnv' thing that's been floating around.
Loads any nodelists you've configured in echocfg/sbbsecho.ini.
Has a search feature, let's you send netmail.

You can optionally add this section and any keys to modopts.ini:

[fido_nodelist_browser]
auto_close_domain = true
auto_close_zone = true
auto_close_net = true
nodelist_a = /path/to/some/nodelist
nodelist_b = /path/to/some/other/nodelist

The auto_close settings control whether branches in the lightbar tree are
closed when you open another at the same level.  The defaults are more
memory friendly.

If you have nodelists not known to sbbsecho (or aren't using sbbsecho 3)
you can add them here; the key must begin with 'nodelist_'.  Wildcards
are not supported; you should have some external mechanism copying the
current nodelist to a fixed path & filename.

record in the node.dab - only the node(s) that have the requested user
number.
In sbbs_t::getsmsg() and ::getsmsg(), strip all invalid Ctrl-A attribute
codes (e.g. clear screen, pause, etc.) since short-messages (telegrams)
can come from external sources.

Double the duration to wait for client threads to terminate. Heck, this might
should be an infinite wait since "bad things" happen if the client thread
continues after a cleanup().

actual message number (rather than a 1-based message index offset) by using
#<number>, e.g. "smbutil r#3694" will read the message base starting at
message number 3694, if it exists.

Also documented the [-n] syntax for reading/listing messages less than
n days old.

with the terminal and mail servers' log output and provide more details
(e.g. on errors).

separate from the log text and is consistent with the mail server log
output.

alphabetized, so the indexes don't necessarily match the order (of timed
events) in SCFG.

Don't use the word "module".

; Exported from Vertrauen on Wed Oct 03 2018 01:00:17 GMT-0700 (Pacific Daylight Time)

and the "imsglist" command (ditto) - better dupe detection.

- be used to enter the inter-BBS instant message module with the 'I' command
  (this should make responding to inter-BBS instant messages much easier as
  the recipient can respond from anywhere using Ctrl-P global hotkey).
- be installed using "jsexec privatemsg.js install"

- less verbose startup (don't display every system being pinged)
- store the info for the last sent message and use that or the last
  received message to automatically fill in the recipient of telegrams.

This entire module could still use some re-write. It'd be nice if it
automatically re-pinged all the systems and displayed newly discovered
users or those who have apparently logged-off.

- Fix apparent bug when there was no incoming data.
- Include the sender's avatar if one is found and the sender did not send
  the most recent message to the recipient (don't repeat the avatar
  needlessly).
- Store the information (name, address, etc.) for received imsg's in the
  recipient's property (.ini) file. This makes quickly replying easier.

Note: the receiving messages for a node-number feature should probably just
be removed.