This allows a message displayer to indicate to the user that some MIME-decoding
took place.

trailing white-space.

- Decoded UTF-8 chars are still a problem (for ANSI/cp437 terminals)
- Only supported encoded ctrl char (< 0x20) is a tab character (currently)
Improved MIME header field searching:
- case insensitive matching of content-type header field
- support MIME header fields in any order (not always Content-Type first)

would be no pause on exit. Now we insure an error level of (at least) 1 if the
script execution fails for any reason.

The 'expand_fields' argument wasn't be parsed correctly and defaults to 'true',
so any script that modifies a message header could be writing-back expandeed
header fields which may sometimes fail depending on how much the total header
size expanded.
Enhancement: the put_msg_header() method will now fail with an exception if a
script tries to write-back a message header that was read with expanded fields.
This should help to avoid potential message base corruption through a script
bug.

selecting an external program "section" will auto-execute the one available
program if there is only one program available to the current user. For
C.G. Learn, AKA: DesotoFireflite

If base64 decode fails, return the full (MIME) text.

- only a single file attachment is supported
- the attachment must be MIME/base64 encoded
- "inline" files are not decoded/downloadable

- adjusts stats (not credits) for the current logon and user
- logs the download
- accepts an optional "description" argument

char, don't try to match it with a transfer protocol. When a user doesn't have
a default transfer protocol selected, their "prot" property may be a space.

"text/plain" MIME entities, for displaying to a terminal user.
New function smb_getattachment() can parse and return an attached file
(supports a single attached file only and only base64 encoding).

"connection from" message sent to the remote terminal. This could be
potentially helpful debug output for a file corruption sighting

charset" for the message plain-text instead of hard-coding ISO-8559-1. If no
default charset is configured, specifies ISO-8559-1 just as before.

characters in the input (source) stream.

Do the DLL-dance for Windows.

This may require a clean rebuild due to dependency changes.

"entities" to find the "plain-text" representation of the body text in nested
MIME-encoded bodies. Still todo: decode Base64 and QP-encoded "plain text"
MIME parts.

A good way to use the 'R' command woud be:
"smbutil -C Rcs <base>" which tells smbutil to:
-continue on error opening the msg base (e.g. corruption)
-re-init the SMB/status headers
-change/config the status header values (e.g. max msgs, crcs, age)
-show the status header

- Added 'R' (capital 'R') command, which can be used to repair a corrupted
  "SMB header" and status header in the *.shd file. The status header
  fields "max_msgs", "max_crcs", and "max_age" are not recovered (just
  initialized to 0) since we don't have those configuration settings in
  smbutil. Modifying the base configuration in SCFG and saving changes
  will recover those values.
- Added '-C' (capital 'C') option: to continue to open a msg base even when
  some forms of SMB header corruption are detected. This option may be used
  in combination with some commands (e.g. 'c' and 'R') to recover a
  corrupted message base.

Command-line options were previously not case-sensistive (all options were
treated the same regardless of letter case) - now, most options are still
treated the same regardless of case, but newer options will be redefining
the uppercase equivalent (e.g. '-C' is now not the same as '-c').

it justs initializes/re-initializes the SMB header and status header
records.
Created smb_t.continue_on_error which (currently) allows an smb_open() to
continue event though some (normally fatal) errors have been detected
(e.g. corrupted SMB header).
This is all in the name of being able to recover message bases after more
forms of corruption.

warning: this else clause does not guard... [-Wmisleading-indentation]
js_conio.c:343:4: note: ...this statement, but the latter is misleadingly
                  indented as if it is guarded by the else

- Expose the node's "name" property to be edited
- Expose the node's "areafix support" property to be toggled
- Renamed "AreaFix Keys" to "EchoList" keys (these are keys to EchoLists)
- Display the node number's 8-char hexadecimal value, helpful for filename
  mapping

EchoCfg->NetMail Settings:
- New optino: Ignore NetMail 'KillSent' Attribute
  when set, sent netmails with the "KillSent" flag won't be deleted by SBBSecho

EchoCfg->EchoLists:
- The name (destination) of forwarded AreaFix requests is now configurable
  (no longer hard-coded to "AreaFix")

Enforce the SM_DELREADM option.
Use smb_storage_mode().

logic everywhere.
Enforce the sys_misc SM_DELREADM flag (SCFG->Message Options->Kill Read E-mail)
in more places (set the Kill After Read flag automatically).
Create a Message-ID (RFC822-style) for locally created email messages.

call to either lputs or eputs based on the node number (0 = event thread).
Created a sbbs_t::backup() wrapper for the C version which logs some helpful
debug output.
Backup the mail.hash and mail.ini file too.
Log the number of emails removed during daily maintenance.
DLL-export smb_open_sub() and smb_storage_mode() so they can be used in more
places.

messages (frame), introduced in rev 1.231.

passed (as an array), the message's data blocks would be allocated with a
refcount of 1, as though only one message header referenced the data. This
is really only an issue with bulkmail/multiple-recipient email and when the
first message was deleted, the remaining (headers) would point to free
data blocks which could and eventually would be overwritten by another
message's data (body text). chksmb would only catch the problem when the
refcount reached 0 but there was still one or more message headers pointing
at the data.

and smb_incmsg_dfields(), now lock and unlock the SMB header.
This shouldprevent some mail base corruption as well as this error:
-203 (smb_incmsgdat 13 'Permission denied' reading allocation record at offset
795568) incrementing data allocation units